[krdc] [Bug 485681] Keyboard is not working
https://bugs.kde.org/show_bug.cgi?id=485681 Tilman Vogel changed: What|Removed |Added CC||tilman.vo...@web.de --- Comment #3 from Tilman Vogel --- Broken on openSUSE Tumbleweed 20240524, KRDC Version 24.02.2. No workaround known. Setting layout to en-US as noted in a previous bug report does not help. Keyboard control works fine with freerdp-3.5.1-1.2.x86_64. -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 482950] KRDC RDP Blue screen shows nothing
https://bugs.kde.org/show_bug.cgi?id=482950 Tilman Vogel changed: What|Removed |Added CC||tilman.vo...@web.de --- Comment #17 from Tilman Vogel --- Broken on openSUSE Tumbleweed 20240524. Thanks to https://bugs.kde.org/show_bug.cgi?id=482950#c10 for the workaround! -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kactivities] [Bug 453570] activitymanagerd created database which took 80 GB in file system
https://bugs.kde.org/show_bug.cgi?id=453570 --- Comment #20 from Tilman Vogel --- > Are you all on Arch? No, I am on openSUSE Tumbleweed and had that problem. Also, kactivitymanagerd ate 100% of one of my cores. I removed database and config files. After that, it did not happen again yet. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kactivities] [Bug 453570] activitymanagerd created database which took 80 GB in file system
https://bugs.kde.org/show_bug.cgi?id=453570 Tilman Vogel changed: What|Removed |Added CC||tilman.vo...@web.de -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 439256] Comments are treated as whitespace even when not selected in preferences
https://bugs.kde.org/show_bug.cgi?id=439256 --- Comment #4 from Tilman Vogel --- Created attachment 139717 --> https://bugs.kde.org/attachment.cgi?id=139717=edit Screenshot showing the preference that should control the behaviour. -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 439256] Comments are treated as whitespace even when not selected in preferences
https://bugs.kde.org/show_bug.cgi?id=439256 --- Comment #3 from Tilman Vogel --- Created attachment 139716 --> https://bugs.kde.org/attachment.cgi?id=139716=edit Screenshot showing actual behaviour -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 439256] Comments are treated as whitespace even when not selected in preferences
https://bugs.kde.org/show_bug.cgi?id=439256 --- Comment #2 from Tilman Vogel --- Created attachment 139715 --> https://bugs.kde.org/attachment.cgi?id=139715=edit example data B.txt -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 439256] Comments are treated as whitespace even when not selected in preferences
https://bugs.kde.org/show_bug.cgi?id=439256 --- Comment #1 from Tilman Vogel --- Created attachment 139714 --> https://bugs.kde.org/attachment.cgi?id=139714=edit example data A.txt -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 439256] New: Comments are treated as whitespace even when not selected in preferences
https://bugs.kde.org/show_bug.cgi?id=439256
Bug ID: 439256
Summary: Comments are treated as whitespace even when not
selected in preferences
Product: kdiff3
Version: 1.9.2
Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: application
Assignee: reeves...@gmail.com
Reporter: tilman.vo...@web.de
Target Milestone: ---
In 1.9.2 and later, changes in C-style comments are treated as "only
whitespace" differences even when the corresponding setting in the preferences
is not active.
STEPS TO REPRODUCE
1. Make sure the "Ignore C/C++ comments (treat as white space)" option is off
under Configure->Diff
2. Run a merge with the attached files:
LANG=C kdiff3 -m {A,B}.txt
3. Take a look at how the difference in the comment-only line is treated.
OBSERVED RESULT
The change in the comment is marked as "Merge Conflict (Whitespace only)".
EXPECTED RESULT
The change in the comment is marked as "Merge Conflict".
SOFTWARE/OS VERSIONS
Operating System: openSUSE Tumbleweed 20210524
KDE Plasma Version: 5.21.5
KDE Frameworks Version: 5.82.0
Qt Version: 5.15.2
Kernel Version: 5.12.4-1-default
OS Type: 64-bit
Graphics Platform: X11
Processors: 8 × Intel® Core™ i7-7700HQ CPU @ 2.80GHz
Memory: 15.5 GiB of RAM
Graphics Processor: Mesa DRI Intel® HD Graphics 630
ADDITIONAL INFORMATION
--
You are receiving this mail because:
You are watching all bug changes.
[kdiff3] [Bug 437910] Manual diff alignment does not work anymore (regression in comparison to 1.8.4)
https://bugs.kde.org/show_bug.cgi?id=437910 --- Comment #6 from Tilman Vogel --- Made a fix: https://invent.kde.org/sdk/kdiff3/-/merge_requests/30 -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 437910] Manual diff alignment does not work anymore (regression in comparison to 1.8.4)
https://bugs.kde.org/show_bug.cgi?id=437910 Tilman Vogel changed: What|Removed |Added Platform|Other |openSUSE RPMs -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 437910] Manual diff alignment does not work anymore (regression in comparison to 1.8.4)
https://bugs.kde.org/show_bug.cgi?id=437910 Tilman Vogel changed: What|Removed |Added Attachment #138901|0 |1 is obsolete|| -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 437910] Manual diff alignment does not work anymore (regression in comparison to 1.8.4)
https://bugs.kde.org/show_bug.cgi?id=437910 --- Comment #5 from Tilman Vogel --- Created attachment 138906 --> https://bugs.kde.org/attachment.cgi?id=138906=edit Screenshot from 1.9.2 (incorrect behaviour) -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 437910] Manual diff alignment does not work anymore (regression in comparison to 1.8.4)
https://bugs.kde.org/show_bug.cgi?id=437910 --- Comment #4 from Tilman Vogel --- Created attachment 138905 --> https://bugs.kde.org/attachment.cgi?id=138905=edit Screenshot from 1.8.4 (correct behaviour) -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 437910] Manual diff alignment does not work anymore (regression in comparison to 1.8.4)
https://bugs.kde.org/show_bug.cgi?id=437910 --- Comment #3 from Tilman Vogel --- Created attachment 138904 --> https://bugs.kde.org/attachment.cgi?id=138904=edit C.txt -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 437910] Manual diff alignment does not work anymore (regression in comparison to 1.8.4)
https://bugs.kde.org/show_bug.cgi?id=437910 --- Comment #2 from Tilman Vogel --- Created attachment 138903 --> https://bugs.kde.org/attachment.cgi?id=138903=edit B.txt -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 437910] Manual diff alignment does not work anymore (regression in comparison to 1.8.4)
https://bugs.kde.org/show_bug.cgi?id=437910 --- Comment #1 from Tilman Vogel --- Created attachment 138902 --> https://bugs.kde.org/attachment.cgi?id=138902=edit A.txt -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 437910] New: Manual diff alignment does not work anymore (regression in comparison to 1.8.4)
https://bugs.kde.org/show_bug.cgi?id=437910
Bug ID: 437910
Summary: Manual diff alignment does not work anymore
(regression in comparison to 1.8.4)
Product: kdiff3
Version: 1.9.2
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: application
Assignee: reeves...@gmail.com
Reporter: tilman.vo...@web.de
Target Milestone: ---
Created attachment 138901
--> https://bugs.kde.org/attachment.cgi?id=138901=edit
example data
SUMMARY
Manual diff alignment is (was) a wonderful tool to help kdiff3 figure out
alignment and often find the right conflict resolution after aligning manually.
Unfortunately between 1.8.4 and 1.9.2 something has changed to make the
alignment markers non-effective.
STEPS TO REPRODUCE
1. Save attached {A,B,C}.txt
2. Run `kdiff3 -m A.txt B.txt C.txt`
3. Place alignment markers on the respective `(align here)` lines
OBSERVED RESULT
In 1.8.4, the alignment lines are in fact visually aligned. A correct conflict
is reported and waits for resolution.
In 1.9.2, the alignment lines are in fact _not_ visually aligned. An incorrect
automatic conflict resolution is produced that arbitrarily orders the
conflicting changes!
Please see screenshots.
EXPECTED RESULT
The correct behaviour observed in 1.8.4.
SOFTWARE/OS VERSIONS
Linux/KDE Plasma: openSUSE Tumbleweed snapshot 20210524
(available in About System)
KDE Frameworks 5.82.0
Qt 5.15.2 (built against 5.15.2)
The xcb windowing system
ADDITIONAL INFORMATION
The 1.8.4 behaviour was recorded with openSUSE Tumbleweed snapshot 20210106.
--
You are receiving this mail because:
You are watching all bug changes.
[plasma-pa] [Bug 389433] Virtual streams should be included (optionally?) under devices or in a new tab.
https://bugs.kde.org/show_bug.cgi?id=389433 Tilman Vogel <tilman.vo...@web.de> changed: What|Removed |Added CC||tilman.vo...@web.de -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 389433] Virtual streams should be included (optionally?) under devices or in a new tab.
https://bugs.kde.org/show_bug.cgi?id=389433 Tilman Vogel <tilman.vo...@web.de> changed: What|Removed |Added Platform|Other |openSUSE RPMs -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 389433] New: Virtual streams should be included (optionally?) under devices or in a new tab.
https://bugs.kde.org/show_bug.cgi?id=389433 Bug ID: 389433 Summary: Virtual streams should be included (optionally?) under devices or in a new tab. Product: plasma-pa Version: 5.8.7 Platform: Other OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: applet Assignee: now...@gmail.com Reporter: tilman.vo...@web.de CC: plasma-b...@kde.org Target Milestone: --- I am using bs2b (http://bs2b.sourceforge.net/) as a cross-feed plugin for hearing with headphones (try it - it's just great!). Use `pacmd load-module module-ladspa-sink sink_name=crossfeed-CORDA plugin=bs2b label=bs2b control=650,9.5 master=` to load it. Once it is loaded, you can drag applications to the new "LADSPA Plugin Bauer stereophonic-to-binaural" device. However, because virtual output streams are not shown, you cannot redefine the output device of the plugin. It's possible to do this using pavucontrol under "Playback" if you enable "Virtual Streams" or "All Streams". -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 388772] New: Filter: Hitting "Apply" resets target folder to "empty"
https://bugs.kde.org/show_bug.cgi?id=388772 Bug ID: 388772 Summary: Filter: Hitting "Apply" resets target folder to "empty" Product: kmail2 Version: 5.5.2 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: misc Assignee: kdepim-b...@kde.org Reporter: tilman.vo...@web.de Target Milestone: --- I am using an IMAP account. I created a new client-side filter with a single "move-to-folder" action. After selecting the target folder and hitting "apply" (because I want to manually apply the filter to a given folder and it complained, I needed to first "save" the filter), the target folder text edit is reset to empty. Because I don't want to try the filter with an empty target folder, I cannot do the filtering. -- You are receiving this mail because: You are watching all bug changes.
