[okular] [Bug 476759] Change default Page Up/Down overlap to, e.g., 10%
https://bugs.kde.org/show_bug.cgi?id=476759 Joe Breuer changed: What|Removed |Added CC||k...@jmbreuer.net --- Comment #1 from Joe Breuer --- Seconded... I did not even know this setting exists because it's shown in an area that's somewhat non-obviously (possibly due to my theme) scrolled outside of the visible area of the settings panel. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 353389] REQUEST: Obvious overlap position indicator to prevent re-reading overlap
https://bugs.kde.org/show_bug.cgi?id=353389 Joe Breuer changed: What|Removed |Added CC||k...@jmbreuer.net --- Comment #1 from Joe Breuer --- What... overlap? Did you turn that on at some place? (Where?) I came here with the feature request to have (some, ideally configurable) overlap when using PgUp/PgDn in Continuous Mode. In the PDF document I'm currently reading, Okular will skip by _exactly_ the whole page, even when that means splitting a line of text in half. ... -- You are receiving this mail because: You are watching all bug changes.
[subtitlecomposer] [Bug 481318] subtitlecomposer crashes
https://bugs.kde.org/show_bug.cgi?id=481318 --- Comment #3 from Joe Breuer --- On a fresh day, with sufficient coffee, I managed to pull in that "tests-optional" patchset. And I'm happy to report that the crash is gone; I can play and seek to and past the point that always was a problem in 0.8.0 without any issues now. How does KDE handle bug reports? Do you have/use a specific state for "it's fixed in git, but no release yet", or would this be just RESOLVED FIXED? -- You are receiving this mail because: You are watching all bug changes.
[subtitlecomposer] [Bug 481318] subtitlecomposer crashes
https://bugs.kde.org/show_bug.cgi?id=481318 --- Comment #2 from Joe Breuer --- (In reply to Mladen Milinkovic, Max from comment #1) > Thanks for the report. > This is probably fixed with commit 0f99f801e3a4bf779167e15e151b14e8ca962f87. > Can you try building/testing current master? Thank you, that's a great idea! Unfortunately, the master branch doesn't readily build on gentoo. The ebuild mentions some patches having to do with turning off unavailable tests - I'll have a deeper look tomorrow / "soon". -- You are receiving this mail because: You are watching all bug changes.
[subtitlecomposer] [Bug 481315] subtitlecomposer crashes
https://bugs.kde.org/show_bug.cgi?id=481315 --- Comment #1 from Joe Breuer --- I've since replicated my original issue and reported it as bug #481318. drkonqi did not allow me to directly pick this issue as related; I'm not sure whether there is any causal relation in the first place, or rather this assertion is an unrelated finding that I stumbled across. -- You are receiving this mail because: You are watching all bug changes.
[subtitlecomposer] [Bug 481318] subtitlecomposer crashes
https://bugs.kde.org/show_bug.cgi?id=481318 Joe Breuer changed: What|Removed |Added Assignee|unassigned-b...@kde.org |max...@smoothware.net Product|unknown |subtitlecomposer Version|unspecified |0.8.0 Component|general |general -- You are receiving this mail because: You are watching all bug changes.
[unknown] [Bug 481318] New: subtitlecomposer crashes
https://bugs.kde.org/show_bug.cgi?id=481318 Bug ID: 481318 Summary: subtitlecomposer crashes Classification: Miscellaneous Product: unknown Version: unspecified Platform: Gentoo Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: k...@jmbreuer.net Target Milestone: --- Application: subtitlecomposer (0.8.0) Qt Version: 5.15.12 Frameworks Version: 5.113.0 Operating System: Linux 6.6.13-gentoo x86_64 Windowing System: X11 Distribution: "Gentoo Linux" DrKonqi: 5.27.10 [KCrashBackend] -- Information about the crash: subtitlecomposer crashes when I seek to/past a certain time in my video file. Since the backtrace mentions audio, it does look to me like the audio waveform displayed does not exactly correspond to the audio I'm hearing at the playback mark. This is related to bug #481315 (which might or might not be causally related), that I came across while setting up a sensible debug environment for this issue. The crash can be reproduced every time. -- Backtrace: Application: Subtitle Composer (subtitlecomposer), signal: Segmentation fault [KCrash Handler] #4 0x55b648986095 in SubtitleComposer::WaveRenderer::paintWaveform(QPainter&, unsigned int, unsigned int) (this=this@entry=0x55b6495ede50, painter=..., widgetWidth=widgetWidth@entry=279, widgetHeight=widgetHeight@entry=828) at /var/tmp/portage/media-video/subtitlecomposer-0.8.0/work/subtitlecomposer-0.8.0/src/gui/waveform/waverenderer.cpp:148 #5 0x55b648986dc2 in SubtitleComposer::WaveRenderer::paintGraphics(QPainter&) (this=this@entry=0x55b6495ede50, painter=...) at /var/tmp/portage/media-video/subtitlecomposer-0.8.0/work/subtitlecomposer-0.8.0/src/gui/waveform/waverenderer.cpp:176 #6 0x55b64898712b in SubtitleComposer::WaveRenderer::event(QEvent*) (this=0x55b6495ede50, evt=0x7ffd74eba400) at /var/tmp/portage/media-video/subtitlecomposer-0.8.0/work/subtitlecomposer-0.8.0/src/gui/waveform/waverenderer.cpp:88 #7 0x7fe000762e8e in QApplicationPrivate::notify_helper(QObject*, QEvent*) (this=, receiver=0x55b6495ede50, e=0x7ffd74eba400) at /var/tmp/portage/dev-qt/qtwidgets-5.15.12/work/qtbase-everywhere-src-5.15.12/src/widgets/kernel/qapplication.cpp:3640 #8 0x7fdfffa88258 in QCoreApplication::notifyInternal2(QObject*, QEvent*) (receiver=0x55b6495ede50, event=0x7ffd74eba400) at /var/tmp/portage/dev-qt/qtcore-5.15.12-r1/work/qtbase-everywhere-src-5.15.12/src/corelib/kernel/qcoreapplication.cpp:1064 #9 0x7fdfffa8843e in QCoreApplication::sendSpontaneousEvent(QObject*, QEvent*) (receiver=, event=) at /var/tmp/portage/dev-qt/qtcore-5.15.12-r1/work/qtbase-everywhere-src-5.15.12/src/corelib/kernel/qcoreapplication.cpp:1474 #10 0x7fe00079cf95 in QWidgetPrivate::sendPaintEvent(QRegion const&) (this=this@entry=0x55b6494d0fb0, toBePainted=...) at /var/tmp/portage/dev-qt/qtwidgets-5.15.12/work/qtbase-everywhere-src-5.15.12/src/widgets/kernel/qwidget.cpp:5479 #11 0x7fe00079d8db in QWidgetPrivate::drawWidget(QPaintDevice*, QRegion const&, QPoint const&, QFlags, QPainter*, QWidgetRepaintManager*) (this=this@entry=0x55b6494d0fb0, pdev=0x55b64995fd30, rgn=..., offset=..., flags=..., sharedPainter=sharedPainter@entry=0x0, repaintManager=) at /var/tmp/portage/dev-qt/qtwidgets-5.15.12/work/qtbase-everywhere-src-5.15.12/src/widgets/kernel/qwidget.cpp:5429 #12 0x7fe000773f90 in QWidgetRepaintManager::paintAndFlush() (this=0x55b649bfb810) at /var/tmp/portage/dev-qt/qtwidgets-5.15.12/work/qtbase-everywhere-src-5.15.12/src/widgets/kernel/qwidgetrepaintmanager.cpp:1016 #13 0x7fe0007a5516 in QWidget::event(QEvent*) (this=this@entry=0x55b6495b7e70, event=event@entry=0x7fdf6c218880) at /var/tmp/portage/dev-qt/qtwidgets-5.15.12/work/qtbase-everywhere-src-5.15.12/src/widgets/kernel/qwidget.cpp:8990 #14 0x7fe0008bae20 in QMainWindow::event(QEvent*) (this=this@entry=0x55b6495b7e70, event=event@entry=0x7fdf6c218880) at /var/tmp/portage/dev-qt/qtwidgets-5.15.12/work/qtbase-everywhere-src-5.15.12/src/widgets/widgets/qmainwindow.cpp:1341 #15 0x7fe0011f23ce in KMainWindow::event(QEvent*) (this=this@entry=0x55b6495b7e70, ev=ev@entry=0x7fdf6c218880) at /var/tmp/portage/kde-frameworks/kxmlgui-5.113.0/work/kxmlgui-5.113.0/src/kmainwindow.cpp:961 #16 0x7fe0012349f7 in KXmlGuiWindow::event(QEvent*) (this=0x55b6495b7e70, ev=0x7fdf6c218880) at /var/tmp/portage/kde-frameworks/kxmlgui-5.113.0/work/kxmlgui-5.113.0/src/kxmlguiwindow.cpp:220 #17 0x7fe000762e8e in QApplicationPrivate::notify_helper(QObject*, QEvent*) (this=, receiver=0x55b6495b7e70, e=0x7fdf6c218880) at /var/tmp/portage/dev-qt/qtwidgets-5.15.12/work/qtbase-everywhere-src-5.15.12/src/widgets/kernel/qapplication.cpp:3640 #18 0x7fdfffa88258 in QCoreApplication::notifyInternal2(QObject*, QEvent*) (receiver=0x55b6495b7e70,
[subtitlecomposer] [Bug 481315] subtitlecomposer crashes
https://bugs.kde.org/show_bug.cgi?id=481315 Joe Breuer changed: What|Removed |Added Product|unknown |subtitlecomposer Assignee|unassigned-b...@kde.org |max...@smoothware.net Component|general |general Version|unspecified |0.8.0 -- You are receiving this mail because: You are watching all bug changes.
[unknown] [Bug 481315] subtitlecomposer crashes
https://bugs.kde.org/show_bug.cgi?id=481315 Joe Breuer changed: What|Removed |Added Platform|Compiled Sources|Gentoo Packages -- You are receiving this mail because: You are watching all bug changes.
[unknown] [Bug 481315] New: subtitlecomposer crashes
https://bugs.kde.org/show_bug.cgi?id=481315 Bug ID: 481315 Summary: subtitlecomposer crashes Classification: Miscellaneous Product: unknown Version: unspecified Platform: Compiled Sources OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: k...@jmbreuer.net Target Milestone: --- Application: subtitlecomposer (0.8.0) (Compiled from sources) Qt Version: 5.15.12 Frameworks Version: 5.113.0 Operating System: Linux 6.6.13-gentoo x86_64 Windowing System: X11 Distribution: "Gentoo Linux" DrKonqi: 5.27.10 [KCrashBackend] -- Information about the crash: I had an issue with subtitlecomposer crashing, as it turned out, whenever I reached a specific point in the video I was working on. That crash report was not useful, so I rebuilt subtitlecomposer and its relevant dependencies with debug symbols. In this first attempt, this changes the behaviour, causing an assertion immediately upon starting subtitlecomposer, that I guess is optimized out in a release build: ASSERT: "last < rowCount(parent)" in file /var/tmp/portage/dev-qt/qtcore-5.15.12-r1/work/qtbase-everywhere-src-5.15.12/src/corelib/itemmodels/qabstractitemmodel.cpp, line 2817 How can I find out which database file (I guess) is causing this assertion, to 'fix' that (i.e. probably delete and have it rebuilt)? Meanwhile, I'll see to rebuild with debug symbols but with a release-equivalent configuration, i.e. without the assertion(s). The crash can be reproduced every time. -- Backtrace: Application: Subtitle Composer (subtitlecomposer), signal: Aborted [KCrash Handler] #4 0x7f4d78cb0e5c in () at /lib64/libc.so.6 #5 0x7f4d78c625e2 in raise () at /lib64/libc.so.6 #6 0x7f4d78c4b4ed in abort () at /lib64/libc.so.6 #7 0x7f4d7c491eab in qt_message_fatal (message=..., context=) at /var/tmp/portage/dev-qt/qtcore-5.15.12-r1/work/qtbase-everywhere-src-5.15.12/src/corelib/global/qlogging.cpp:1919 #8 QMessageLogger::fatal(char const*, ...) const (this=this@entry=0x7ffdddfc83f8, msg=msg@entry=0x7f4d7c78b6a8 "ASSERT: \"%s\" in file %s, line %d") at /var/tmp/portage/dev-qt/qtcore-5.15.12-r1/work/qtbase-everywhere-src-5.15.12/src/corelib/global/qlogging.cpp:898 #9 0x7f4d7c49094a in qt_assert(char const*, char const*, int) (assertion=assertion@entry=0x7f4d7c7a5e44 "last < rowCount(parent)", file=file@entry=0x7f4d7c796ac8 "/var/tmp/portage/dev-qt/qtcore-5.15.12-r1/work/qtbase-everywhere-src-5.15.12/src/corelib/itemmodels/qabstractitemmodel.cpp", line=line@entry=2817) at /var/tmp/portage/dev-qt/qtcore-5.15.12-r1/work/qtbase-everywhere-src-5.15.12/src/corelib/global/qglobal.cpp:3392 #10 0x7f4d7c4b2c3a in QAbstractItemModel::beginRemoveRows(QModelIndex const&, int, int) (this=0x5611a8dd9800, parent=, first=0, last=0) at /var/tmp/portage/dev-qt/qtcore-5.15.12-r1/work/qtbase-everywhere-src-5.15.12/src/corelib/itemmodels/qabstractitemmodel.cpp:2817 #11 0x5611a6d545d5 in SubtitleComposer::InstalledScriptsModel::removeAll() (this=0x5611a8dd9800) at /var/tmp/portage/media-video/subtitlecomposer-0.8.0/work/subtitlecomposer-0.8.0/src/scripting/scriptsmanager.cpp:305 #12 SubtitleComposer::ScriptsManager::reloadScripts() (this=0x5611a8f8c1a0) at /var/tmp/portage/media-video/subtitlecomposer-0.8.0/work/subtitlecomposer-0.8.0/src/scripting/scriptsmanager.cpp:711 #13 0x5611a6c9bf99 in SubtitleComposer::Application::createMainWindow() (this=this@entry=0x7ffdddfc87e0) at /var/tmp/portage/media-video/subtitlecomposer-0.8.0/work/subtitlecomposer-0.8.0/src/application.cpp:280 #14 0x5611a6c900b2 in main(int, char**) (argc=, argv=) at /var/tmp/portage/media-video/subtitlecomposer-0.8.0/work/subtitlecomposer-0.8.0/src/main.cpp:183 [Inferior 1 (process 1967481) detached] Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 472211] New: Feature Request: please add a way to change the Z-order of annotations
https://bugs.kde.org/show_bug.cgi?id=472211 Bug ID: 472211 Summary: Feature Request: please add a way to change the Z-order of annotations Classification: Applications Product: okular Version: 23.04.2 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: PDF backend Assignee: okular-de...@kde.org Reporter: k...@jmbreuer.net Target Milestone: --- SUMMARY (PDF) Annotations seem to be added to the document in a fixed "new on top" Z-order. There are no move higher/lower/bring to front/send to back editing tools (that I could find). STEPS TO REPRODUCE 1. Add a PDF annotation, e.g. a large-ish inline note 2. Add another PDF annotation, e.g. another large-ish inline note, that overlaps the other one 3. Observe that OBSERVED RESULT The annotation added second stays on top of the one added first for good, no way to change this. EXPECTED RESULT A way to re-order the z stack of annotations to e.g. make text in partially overlapping notes fully readable (without requiring to click-through to the annotation content or such). I'm sure there's a few other use cases. The only remaining way to change the ordering, deleting a lower annotation and re-creating it on top, is effortful. Especially since there's no cut/copy/paste of annotation elements, either. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Gentoo Linux 2.13, Kernel 6.1.38-gentoo (64-bit) KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.106.0 Qt Version: 5.15.9 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 471792] Annotations greatly increase PDF file size and massively slow down Okular
https://bugs.kde.org/show_bug.cgi?id=471792 Joe Breuer changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #5 from Joe Breuer --- (In reply to Sune Vuorela from comment #4) > (In reply to Joe Breuer from comment #3) > > What method/tool do you use to obtain this information? > > poppler source package (Often in a binary package like poppler-utils or > poppler-tools) contains pdffonts tool that list all of the fonts in the pdf > file. Ah, that's great to know! > > > With poppler 23.06, adding annotations should grow the document with > > > approximately 600k. With poppler 23.07, it should grow the document with > > > approximately 300 k, assuming noto sans (okular default) is used. > > > > Is that to be expected "per each annotation", or once per adding annotations > > at all, or per annotation type, ...? > > Technically, it is per different font, assuming every font is as big as Noto > Sans and compresses with zlib similar to Noto Sans. Ah thanks, I get it and know where to look now! I've added another example using Okular 23.02.4 (with/against Poppler 23.06.0), and that noticeably keeps a stable file size also when adding multiple annotations. It is somewhat smaller than the Okular 22.12.3/Poppler 23.06.0/built against Poppler 23.01.0 sample, the difference seems to be down to Okular 23 only embedding Noto Sans, not Noto Sans and Noto Sans Regular both. So - for my purposes - Poppler 23.06.0 and possibly Okular 23.02.4 are the required combination for a PDF annotation workflow without... "file size and performance surprises." -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 471792] Annotations greatly increase PDF file size and massively slow down Okular
https://bugs.kde.org/show_bug.cgi?id=471792 --- Comment #3 from Joe Breuer --- (In reply to Sune Vuorela from comment #1) > Some versions did embed the same fonts multiple times, and your "big" > document contains ~140 copies of noto fonts What method/tool do you use to obtain this information? > It should be fixed in version 23.06 of the poppler library. Simply upgrading my poppler library to 23.06 still gives me PDFs increasing significantly in size with each additional annotation, though by far by not as much as with 23.05. I've added a corresponding sample: https://github.com/jmbreuer/heap/tree/main/kde-okular-bug-20230630 In "About Backend", my Okular 22.12.3 now displays "Using Poppler 23.06.0, Built against Poppler 23.01.0". Building this version of Okular against Poppler 23.06.0 yields a compile error, I'll see about trying out a newer Okular version. > With poppler 23.06, adding annotations should grow the document with > approximately 600k. With poppler 23.07, it should grow the document with > approximately 300 k, assuming noto sans (okular default) is used. Is that to be expected "per each annotation", or once per adding annotations at all, or per annotation type, ...? -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 471792] Annotations greatly increase PDF file size and massively slow down Okular
https://bugs.kde.org/show_bug.cgi?id=471792 --- Comment #2 from Joe Breuer --- (In reply to Sune Vuorela from comment #1) > What version of the underlying Poppler library are you using ? 23.05 > Some versions did embed the same fonts multiple times, and your "big" > document contains ~140 copies of noto fonts Ah, thank you! That makes (altogether too much) sense. > It should be fixed in version 23.06 of the poppler library. > > With poppler 23.06, adding annotations should grow the document with > approximately 600k. With poppler 23.07, it should grow the document with > approximately 300 k, assuming noto sans (okular default) is used. I'll have a look into that very shortly and let you know - 23.06 looks to be available in gentoo 'testing'. Trying a 23.07 bump is not immediately accessible to me, since there's apparently no release or even git tag yet. Not sure that I want to run git master on a production system. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 470128] Saving document with resized text creates huge memory footprint
https://bugs.kde.org/show_bug.cgi?id=470128 --- Comment #5 from Joe Breuer --- My bug #471792 has one sample which massively demonstrates this - file size from 6.4 MB (original) to 143.4 MB (two Inline Notes with resized fonts). -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 470128] Saving document with resized text creates huge memory footprint
https://bugs.kde.org/show_bug.cgi?id=470128 Joe Breuer changed: What|Removed |Added CC||k...@jmbreuer.net -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 471792] New: Annotations greatly increase PDF file size and massively slow down Okular
https://bugs.kde.org/show_bug.cgi?id=471792 Bug ID: 471792 Summary: Annotations greatly increase PDF file size and massively slow down Okular Classification: Applications Product: okular Version: 22.12.3 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: PDF backend Assignee: okular-de...@kde.org Reporter: k...@jmbreuer.net Target Milestone: --- SUMMARY Adding annotations to a run-of-the-mill PDF file (out of pdfLaTeX, I presume) hugely increases the file size with each additional annotation. STEPS TO REPRODUCE 1. Open a PDF file 2. Add a couple of annotations (I mostly used Inline Notes, but also some underlines and Pop-up Notes) 3. Save as PDF OBSERVED RESULT Saving my 6.4 MB sample PDF with very few test annotations and saving as PDF yields a 7.4 MB file. Removing those and adding a couple of 'real' annotations, the saved PDF weighs in at 20.7 MB. Changing font size of two Inline Note annotations after they have been created yields a huge PDF of 143.4 MB. With the increase in file size also comes an increase in CPU usage to the point that Okular slows down and becomes practically unusable (especially / immediately noticable with the "resized font" case). EXPECTED RESULT Annotations should only slightly increase file size and not strongly affect interactive performance. SOFTWARE/OS VERSIONS Linux/KDE Plasma: gentoo Linux 2.13, Kernel 6.1.31-gentoo (64-bit) KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.106.0 Qt Version: 5.15.9 ADDITIONAL INFORMATION Since attachments cannot exceed 4000kB, and all my samples are larger than that, I've put together my sample files here: https://github.com/jmbreuer/heap/tree/main/kde-okular-bug-20230630 I've also seen bug #470128, and also noticed that changing the font size of an Inline Note annotation after adding it would hugely increase the file size (changing two notes, from those 6.4/7.4 MB to 143.4 MB). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 469976] Allow a keyboard shortcut for existing functionality of toggling audio mute of the currently active window/application only
https://bugs.kde.org/show_bug.cgi?id=469976 --- Comment #2 from Joe Breuer --- ... ah, and I think Alt+Mute would be a good/useful key combination for this; but maybe that only happens to be convenient on the keyboard I have in front of me. ... -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 469976] Allow a keyboard shortcut for existing functionality of toggling audio mute of the currently active window/application only
https://bugs.kde.org/show_bug.cgi?id=469976 --- Comment #1 from Joe Breuer --- Thinking about it some more, I'd like to suggest a kind of special case on top: When the mouse pointer is hovering over a Task Manager tile, highlighting that application/window to be activated on click, that keyboard shortcut should operate on the thusly highlighted application. In all other cases - pointer not highlighting something in the 'task bar' - mute state of the application associated with the currently active/focused window should toggle (the one that's shown highlighted on the 'task bar' regardless of any mouse-over things). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 469976] New: Allow a keyboard shortcut for existing functionality of toggling audio mute of the currently active window/application only
https://bugs.kde.org/show_bug.cgi?id=469976 Bug ID: 469976 Summary: Allow a keyboard shortcut for existing functionality of toggling audio mute of the currently active window/application only Classification: Plasma Product: plasmashell Version: 5.27.4 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: Task Manager and Icons-Only Task Manager Assignee: plasma-b...@kde.org Reporter: k...@jmbreuer.net Target Milestone: 1.0 Since recently, there's this very nice feature of the little speaker icons shown on the window selectors in the task manager, which toggles audio mute of that specific application. As far as I could determine, there's currently no way to activate this functionality using a keyboard shortcut. I've been in a number of situations where I was wishing for that exact keyboard shortcut, such as: - (quickly) muting an audio player on an incoming video conference / soft phone call - muting a full screen game when a "hard" phone call comes in, but leaving audio notifications from other applications intact during the call - Wanting to quickly silence audio prompts by one certain set of applications, while enabling others ... etc. All necessary information (active task, how to do the per-application mute toggle) is obviously already available to the Task Manager - the active application is shown highlighted, and the mute button there knows what to do. I'm tempted to have a look to roll a patch / enhancement myself, in that regard a question to the people who might know: Is the Task Manager an integral part of kwin, or is it a separate/different component (which/where)? ... since kwin already registers a number of keyboard shortcuts, extending this by the one more feels feasible to me even without knowing KDE code in depth. However, adding keyboard shortcut functionality to a component that doesn't have any at all so far, not so much. ;-) -- You are receiving this mail because: You are watching all bug changes.
