https://bugs.kde.org/show_bug.cgi?id=498036
Oswald Buddenhagen changed:
What|Removed |Added
Resolution|WAITINGFORINFO |---
Status|NEEDSINFO
https://bugs.kde.org/show_bug.cgi?id=498030
--- Comment #9 from Oswald Buddenhagen ---
if you can't repro it, then say so right away.
i did some more experiments now.
looking at klipper, i'd say that was a false alert. the UI is just bad (at
least with theme breeze) - the popup look
https://bugs.kde.org/show_bug.cgi?id=498030
--- Comment #7 from Oswald Buddenhagen ---
why are you being pedantic over what "klipper" exactly is rather than just
trying with what it seems to be (which is exactly what you described)?
anyone with a kde6 desktop and some familiarit
https://bugs.kde.org/show_bug.cgi?id=498030
Oswald Buddenhagen changed:
What|Removed |Added
Resolution|WAITINGFORINFO |---
Status|NEEDSINFO
https://bugs.kde.org/show_bug.cgi?id=498030
Oswald Buddenhagen changed:
What|Removed |Added
Status|NEEDSINFO |REPORTED
Resolution
https://bugs.kde.org/show_bug.cgi?id=498035
--- Comment #4 from Oswald Buddenhagen ---
> Clearly there is a use case or else this option wouldn’t exist.
i didn't question the option, but a particular aspect of it. and that could
have been just coincidental, or "just because&quo
https://bugs.kde.org/show_bug.cgi?id=498035
Oswald Buddenhagen changed:
What|Removed |Added
Ever confirmed|0 |1
Status|RESOLVED
https://bugs.kde.org/show_bug.cgi?id=486701
--- Comment #5 from Oswald Buddenhagen ---
as noted in the duplicate, "dodge windows" mode is NOT an adequate replacement
- it's "jumpy", and it's counter-productive to hide the entire panel when it
would be only pa
https://bugs.kde.org/show_bug.cgi?id=498029
--- Comment #4 from Oswald Buddenhagen ---
turns out i actually _am_ on wayland and didn't even notice, except for the
regressions. duh.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=455431
Oswald Buddenhagen changed:
What|Removed |Added
CC||o...@kde.org
--- Comment #24 from Oswald
https://bugs.kde.org/show_bug.cgi?id=498057
Oswald Buddenhagen changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=498027
--- Comment #2 from Oswald Buddenhagen ---
so yet another intentional regression. truly the way of the future.
but i'm stunned that i actually _am_ on wayland. something went wrong with
session selection in lightdm, and i didn't even noti
https://bugs.kde.org/show_bug.cgi?id=498057
Bug ID: 498057
Summary: spare layouts broken on x11
Classification: Plasma
Product: plasmashell
Version: 6.2.4
Platform: Debian unstable
OS: Linux
Status: REPORTED
https://bugs.kde.org/show_bug.cgi?id=498029
--- Comment #3 from Oswald Buddenhagen ---
somewhat probably related to that, "suppress if fullscreen windows present"
also doesn't work anymore.
hmm, come to think of it, the activity tracking doesn't work anymore, either.
--
Yo
https://bugs.kde.org/show_bug.cgi?id=498029
Oswald Buddenhagen changed:
What|Removed |Added
Status|NEEDSINFO |REPORTED
Resolution
https://bugs.kde.org/show_bug.cgi?id=498036
Bug ID: 498036
Summary: window title & icon should reflect current session
Classification: Applications
Product: konsole
Version: 24.12.0
Platform: Debian unstable
OS: Linux
https://bugs.kde.org/show_bug.cgi?id=498035
Bug ID: 498035
Summary: "always visible" vs. "windows go below" panel
visibility modes
Classification: Plasma
Product: plasmashell
Version: 6.2.4
Platform: Debian unstable
https://bugs.kde.org/show_bug.cgi?id=498032
Bug ID: 498032
Summary: re-introduce "windows can cover" visibility mode
Classification: Plasma
Product: plasmashell
Version: 6.2.4
Platform: Debian unstable
OS: Linux
https://bugs.kde.org/show_bug.cgi?id=498030
Bug ID: 498030
Summary: "dodge windows", "windows go below", and "auto hide"
visibility modes vs. tray popup windows
Classification: Plasma
Product: plasmashell
Version: 6.2.4
https://bugs.kde.org/show_bug.cgi?id=498029
Bug ID: 498029
Summary: overlay window isn't actually fullscreen
Classification: Applications
Product: rsibreak
Version: unspecified
Platform: Debian unstable
OS: Linux
https://bugs.kde.org/show_bug.cgi?id=498027
Bug ID: 498027
Summary: kwin ignores applications' initial geometry requests
Classification: Plasma
Product: kwin
Version: 6.2.4
Platform: Debian unstable
OS: Linux
St
https://bugs.kde.org/show_bug.cgi?id=494048
Bug ID: 494048
Summary: add option to switch to alternate screen
Classification: Applications
Product: konsole
Version: 23.08.1
Platform: Debian unstable
OS: Linux
Sta
https://bugs.kde.org/show_bug.cgi?id=492672
Bug ID: 492672
Summary: switching virtual desktop does not unmap windows
Classification: Plasma
Product: kwin
Version: 5.27.11
Platform: Debian unstable
OS: Linux
Stat
https://bugs.kde.org/show_bug.cgi?id=486512
Bug ID: 486512
Summary: --log-fd does not mix well with --trace-children=yes
Classification: Developer tools
Product: valgrind
Version: 3.24 GIT
Platform: Other
OS: Linux
https://bugs.kde.org/show_bug.cgi?id=194144
Oswald Buddenhagen changed:
What|Removed |Added
CC||o...@kde.org
--- Comment #1 from Oswald
https://bugs.kde.org/show_bug.cgi?id=486488
Bug ID: 486488
Summary: poor handling of invalid --log-fd
Classification: Developer tools
Product: valgrind
Version: 3.24 GIT
Platform: Other
OS: Linux
Status: REPORTE
https://bugs.kde.org/show_bug.cgi?id=443723
Oswald Buddenhagen changed:
What|Removed |Added
CC||o...@kde.org
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=472274
Bug ID: 472274
Summary: omit trailing punctuation when highlighting/invoking
urls
Classification: Applications
Product: konsole
Version: 22.12.3
Platform: Debian unstable
https://bugs.kde.org/show_bug.cgi?id=399291
--- Comment #6 from Oswald Buddenhagen ---
hard-coding the exception is a rather questionable solution.
a fully generic solution would be a configurable regular expression.
however, that might be considered too complex for regular users, and not
https://bugs.kde.org/show_bug.cgi?id=399291
Oswald Buddenhagen changed:
What|Removed |Added
CC||o...@kde.org
Summary|Don
https://bugs.kde.org/show_bug.cgi?id=456420
--- Comment #10 from Oswald Buddenhagen ---
if supporting switching the font size in such a simple widget would impose an
unbearable maintenance burden, then you should seriously rethink your
technology choices.
i wonder how bit-rotting would work for
https://bugs.kde.org/show_bug.cgi?id=456420
Oswald Buddenhagen changed:
What|Removed |Added
Resolution|DUPLICATE |---
Status|RESOLVED
https://bugs.kde.org/show_bug.cgi?id=467271
Bug ID: 467271
Summary: stacked here-docs confuse the highlighter
Classification: Frameworks and Libraries
Product: frameworks-syntax-highlighting
Version: 5.103.0
Platform: Other
https://bugs.kde.org/show_bug.cgi?id=402540
Oswald Buddenhagen changed:
What|Removed |Added
Version Fixed In||5.54.0
Latest Commit
https://bugs.kde.org/show_bug.cgi?id=429211
Oswald Buddenhagen changed:
What|Removed |Added
CC||ed...@inbox.lv
--- Comment #47 from
https://bugs.kde.org/show_bug.cgi?id=431446
--- Comment #40 from Oswald Buddenhagen ---
i guess bug 429211 is a more appropriate reference.
fwiw, i identified another situation which might or might not be related: when
i restore a chromium session with tens of windows (and hundreds of tabs
https://bugs.kde.org/show_bug.cgi?id=429211
Oswald Buddenhagen changed:
What|Removed |Added
CC||o...@kde.org
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=431446
--- Comment #33 from Oswald Buddenhagen ---
i don't think the cursor problem is related. as you note yourself, the cursor
is a separate entity, and the fact that it's not in the captured framebuffer is
further evidence of this.
--
You are
https://bugs.kde.org/show_bug.cgi?id=431446
--- Comment #30 from Oswald Buddenhagen ---
this suggests that this might have something to do with partial repaints. maybe
it's picking the wrong buffer for updating.
this is consistent with my observation that for me this usually affects onl
https://bugs.kde.org/show_bug.cgi?id=456422
--- Comment #5 from Oswald Buddenhagen ---
@nate:
it's a weee bit over the top to call this malicious. if somebody had thought
that this is a security or otherwise issue, the spec wouldn't make it so easy
to "fake" it. and "N
https://bugs.kde.org/show_bug.cgi?id=456420
--- Comment #6 from Oswald Buddenhagen ---
my primary use case is explained in bug 456422. these notifications do get
through.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=456420
Oswald Buddenhagen changed:
What|Removed |Added
Resolution|INTENTIONAL |---
Status|CLOSED
https://bugs.kde.org/show_bug.cgi?id=456422
Oswald Buddenhagen changed:
What|Removed |Added
Ever confirmed|0 |1
Resolution|DOWNSTREAM
https://bugs.kde.org/show_bug.cgi?id=456420
Oswald Buddenhagen changed:
What|Removed |Added
Resolution|INTENTIONAL |---
Ever confirmed|0
https://bugs.kde.org/show_bug.cgi?id=456422
Bug ID: 456422
Summary: introduce clean solution for notification popups
without summary
Product: plasmashell
Version: 5.24.5
Platform: Debian unstable
OS: Linux
https://bugs.kde.org/show_bug.cgi?id=456421
Bug ID: 456421
Summary: delay timeout of notification popups when user appears
to be absent
Product: plasmashell
Version: 5.24.5
Platform: Debian unstable
OS: Linu
https://bugs.kde.org/show_bug.cgi?id=456420
Bug ID: 456420
Summary: scale up notification popups in fullscreen
Product: plasmashell
Version: 5.24.5
Platform: Debian unstable
OS: Linux
Status: REPORTED
Seve
https://bugs.kde.org/show_bug.cgi?id=413964
Oswald Buddenhagen changed:
What|Removed |Added
CC||o...@kde.org
--- Comment #2 from Oswald
https://bugs.kde.org/show_bug.cgi?id=313571
Oswald Buddenhagen changed:
What|Removed |Added
CC||o...@kde.org
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=392679
Oswald Buddenhagen changed:
What|Removed |Added
CC||o...@kde.org
--- Comment #4 from Oswald
https://bugs.kde.org/show_bug.cgi?id=412257
Oswald Buddenhagen changed:
What|Removed |Added
Status|NEEDSINFO |REPORTED
Resolution
https://bugs.kde.org/show_bug.cgi?id=412257
--- Comment #15 from Oswald Buddenhagen ---
what is (not), and why?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=412257
--- Comment #13 from Oswald Buddenhagen ---
it should be obvious that kde locking out other frameworks from accessing mtp
devices by its mere presence is not acceptable, and deferring to a pipe dream
solution just doesn't cut it.
so kde needs
https://bugs.kde.org/show_bug.cgi?id=431446
--- Comment #17 from Oswald Buddenhagen ---
as for my issue, that seems unlikely - that appears to be a recent regression,
while i've been seeing this issue for ... well, i guess one should count it in
years.
--
You are receiving this mail be
https://bugs.kde.org/show_bug.cgi?id=431446
Oswald Buddenhagen changed:
What|Removed |Added
CC||o...@kde.org
--- Comment #15 from Oswald
https://bugs.kde.org/show_bug.cgi?id=442170
Oswald Buddenhagen changed:
What|Removed |Added
CC||o...@kde.org
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=412257
Oswald Buddenhagen changed:
What|Removed |Added
CC||o...@kde.org
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=440794
Oswald Buddenhagen changed:
What|Removed |Added
CC||o...@kde.org
--- Comment #1 from Oswald
https://bugs.kde.org/show_bug.cgi?id=413204
Oswald Buddenhagen changed:
What|Removed |Added
CC||o...@kde.org
--- Comment #2 from Oswald
https://bugs.kde.org/show_bug.cgi?id=432557
Oswald Buddenhagen changed:
What|Removed |Added
Alias|barkingbandicoot|
CC
https://bugs.kde.org/show_bug.cgi?id=401898
--- Comment #8 from Oswald Buddenhagen ---
that sendEOF stuff is all nonsense; it's already explained in bug #185140 why
it's technically unnecessary.
bash isn't the only process that will behave weirdly on EOF when a line has
been sta
https://bugs.kde.org/show_bug.cgi?id=185140
Oswald Buddenhagen changed:
What|Removed |Added
CC||o...@kde.org
--- Comment #12 from Oswald
https://bugs.kde.org/show_bug.cgi?id=198199
--- Comment #10 from Oswald Buddenhagen ---
probably ;)
(In reply to Justin Zobel from comment #9)
> Thank you for the bug report.
>
> As this report hasn't seen any changes in 5 years or more, we ask if you can
> please confirm tha
https://bugs.kde.org/show_bug.cgi?id=409994
--- Comment #2 from Oswald Buddenhagen ---
(also, some cases simply can't be expected to be covered by the OSC8 support -
an url that appears in a text file that is being edited most likely won't be
recognized and marked as such by
https://bugs.kde.org/show_bug.cgi?id=409994
--- Comment #1 from Oswald Buddenhagen ---
btw, #379294 provides a better solution than smart heuristics, but i think we
will wait a really long time until all TUI programs will support it - not sure
if even one of the toolkits supports this by now
https://bugs.kde.org/show_bug.cgi?id=421926
--- Comment #10 from Oswald Buddenhagen ---
so, there already is an action which is (mostly?) equivalent with the proposed
new-tab-current: clone-tab.
and as indicated on gitlab, the maintainers seem to be fine with changing the
meaning of new-tab to
https://bugs.kde.org/show_bug.cgi?id=412598
Oswald Buddenhagen changed:
What|Removed |Added
Resolution|--- |FIXED
Status|REOPENED
https://bugs.kde.org/show_bug.cgi?id=421926
--- Comment #9 from Oswald Buddenhagen ---
--all-tab-profile=... maybe, to make it less verbose.
note that this is lacking the "copy current" mode. one could add
--new-tab-profile={default,current,smart} instead, but that just shifts the
https://bugs.kde.org/show_bug.cgi?id=421926
--- Comment #7 from Oswald Buddenhagen ---
the wording was fairly indicative of sarcasm. ;)
anyway, having multiple additional actions wouldn't be that bad in this case,
as they would appear only in the shortcut config dialog (they aren't re
https://bugs.kde.org/show_bug.cgi?id=421926
--- Comment #5 from Oswald Buddenhagen ---
i don't see why changing the behavior should be a notable problem in this case.
anyway, how about separate actions? new-tab-default (aliased to the current
new-tab), new-tab-current, new-tab-selected, an
https://bugs.kde.org/show_bug.cgi?id=421926
Oswald Buddenhagen changed:
What|Removed |Added
CC||o...@kde.org
Ever confirmed|0
https://bugs.kde.org/show_bug.cgi?id=412598
Oswald Buddenhagen changed:
What|Removed |Added
Ever confirmed|0 |1
CC
https://bugs.kde.org/show_bug.cgi?id=412598
Oswald Buddenhagen changed:
What|Removed |Added
Resolution|--- |NOT A BUG
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=412598
--- Comment #6 from Oswald Buddenhagen ---
it's *weird*: running mutt (instead of konsole) in valgrind makes the issue
disappear. however, running mutt (without vg) inside "xterm -tn xterm-256color"
(that's what $TERM is inside ko
https://bugs.kde.org/show_bug.cgi?id=412598
--- Comment #5 from Oswald Buddenhagen ---
i also had the case in this mail display where the whole screen appeared to be
scrolled up, so the top was missing, while the bottom was not repainted. in
this case, pressing ctrl-l cleared the screen, but the
https://bugs.kde.org/show_bug.cgi?id=412598
--- Comment #4 from Oswald Buddenhagen ---
Created attachment 123012
--> https://bugs.kde.org/attachment.cgi?id=123012&action=edit
screenshot: mutt mail ok
... and in this case returns to normal when pressing ctrl-l.
--
You are receiving th
https://bugs.kde.org/show_bug.cgi?id=412598
--- Comment #3 from Oswald Buddenhagen ---
Created attachment 123011
--> https://bugs.kde.org/attachment.cgi?id=123011&action=edit
screenshot: mutt mail botched
it gets crazier when i open your mail ...
--
You are receiving this mail becau
https://bugs.kde.org/show_bug.cgi?id=412598
--- Comment #2 from Oswald Buddenhagen ---
Created attachment 123010
--> https://bugs.kde.org/attachment.cgi?id=123010&action=edit
screenshot: mutt index
there.
i think it's obvious how it should look instead. ;)
this is now
https://bugs.kde.org/show_bug.cgi?id=412598
Bug ID: 412598
Summary: messed up character placement
Product: konsole
Version: 19.08.1
Platform: Debian unstable
OS: Linux
Status: REPORTED
Severity: normal
https://bugs.kde.org/show_bug.cgi?id=412479
Bug ID: 412479
Summary: "trim leading spaces" eats empty lines
Product: konsole
Version: 19.08.1
Platform: Debian unstable
OS: Linux
Status: REPORTED
Severity: n
https://bugs.kde.org/show_bug.cgi?id=409994
Bug ID: 409994
Summary: better (link) support for TUI applications
Product: konsole
Version: 18.04.0
Platform: Debian unstable
OS: Linux
Status: REPORTED
Severit
https://bugs.kde.org/show_bug.cgi?id=402540
--- Comment #4 from Oswald Buddenhagen ---
this code is only ever relevant if a not entirely well-behaved process (which
doesn't use FD_CLOEXEC) launches kdeinit directly. i'm not even sure when that
would happen.
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=347946
Oswald Buddenhagen changed:
What|Removed |Added
CC||o...@kde.org
--- Comment #4 from Oswald
https://bugs.kde.org/show_bug.cgi?id=341934
Oswald Buddenhagen changed:
What|Removed |Added
CC||o...@kde.org
--- Comment #24 from Oswald
https://bugs.kde.org/show_bug.cgi?id=366047
Bug ID: 366047
Summary: sni proxy scaling not always appropriate
Product: plasmashell
Version: 5.6.5
Platform: Debian unstable
OS: Linux
Status: UNCONFIRMED
Seve
https://bugs.kde.org/show_bug.cgi?id=356937
Oswald Buddenhagen changed:
What|Removed |Added
CC||o...@kde.org
--- Comment #13 from Oswald
https://bugs.kde.org/show_bug.cgi?id=357443
Oswald Buddenhagen changed:
What|Removed |Added
Ever confirmed|0 |1
Status|UNCONFIRMED
87 matches
Mail list logo