https://bugs.kde.org/show_bug.cgi?id=356328
--- Comment #5 from Thomas Lübking ---
(In reply to bluescreen_avenger from comment #4)
> Moving the window to the bottom right hand corner does bring up the
> semi-transparent window resize thing.
No, I meant whether you
https://bugs.kde.org/show_bug.cgi?id=356381
Thomas Lübking changed:
What|Removed |Added
URL|
https://bugs.kde.org/show_bug.cgi?id=356346
--- Comment #7 from Thomas Lübking ---
(In reply to ioann from comment #6)
> At now, I ran Plasma session as "vblank_mode=0 /usr/bin/primusrun
> /usr/bin/startkde".
I kinda doubt this works - startkde just forks a bunch of
https://bugs.kde.org/show_bug.cgi?id=316372
--- Comment #38 from Thomas Lübking ---
Ok, thanks.
Closing "worksforme" then.
As of any "Desktop switching OSD is ugly, should have bigger fonts, ..."
concerns, please file a new bug (we maybe need to involve HIG and VDG
https://bugs.kde.org/show_bug.cgi?id=356346
--- Comment #9 from Thomas Lübking ---
check the output of "echo $PATH" - the more left, the more preferred the binary
path is.
"/usr/local/bin" is usually there and should shadow "/usr/bin"
If unsure about kwin ./.
https://bugs.kde.org/show_bug.cgi?id=348753
--- Comment #44 from Thomas Lübking ---
Did you *only* update KWin? (I don't recall we touched anything in that area at
all)
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=356161
Thomas Lübking changed:
What|Removed |Added
Status|CONFIRMED |RESOLVED
https://bugs.kde.org/show_bug.cgi?id=356381
Thomas Lübking changed:
What|Removed |Added
Resolution|--- |FIXED
Latest
https://bugs.kde.org/show_bug.cgi?id=356343
--- Comment #12 from Thomas Lübking ---
Outmost weird.
Xuetian, how do you start konsole maximized (by restored size, kwin rule,
kstart, some konsole key I don't know ... ;-) and does it matter whether you
flag
https://bugs.kde.org/show_bug.cgi?id=356161
--- Comment #6 from Thomas Lübking ---
(In reply to Thomas Pfeiffer from comment #5)
> What would be the usecase for that?
Bug #67406 :-P
Basically, a bunch of users didn't like how ShowDesktop behaved (when some
window was
https://bugs.kde.org/show_bug.cgi?id=356161
--- Comment #7 from Thomas Lübking ---
PS: I'm fine with throwing random modifications at the users and shipping all
alternatives via GHNS.
If there had not been this <*censored*> <*censored*> <*really?? you kiss your
mom
https://bugs.kde.org/show_bug.cgi?id=356128
Thomas Lübking changed:
What|Removed |Added
Severity|normal |wishlist
---
https://bugs.kde.org/show_bug.cgi?id=356168
--- Comment #1 from Thomas Lübking ---
Could you please elaborate on "how" and "why"
How:
- Do you intend to edit the raw message text (inc. headers)
- How does trojita know when to send the mail? (When the process
https://bugs.kde.org/show_bug.cgi?id=344326
--- Comment #87 from Thomas Lübking ---
Suspend To Ram ;-)
Can you interact with the login screen with the bricky text?
(Either the particular greeter GL context - *in* the client - has trouble with
its glyph cache or the
https://bugs.kde.org/show_bug.cgi?id=350826
Thomas Lübking changed:
What|Removed |Added
Version|5.3.2 |5.4.3
Target
https://bugs.kde.org/show_bug.cgi?id=356205
Thomas Lübking changed:
What|Removed |Added
See Also|
https://bugs.kde.org/show_bug.cgi?id=355787
Thomas Lübking changed:
What|Removed |Added
Resolution|WONTFIX |DOWNSTREAM
---
https://bugs.kde.org/show_bug.cgi?id=355787
--- Comment #15 from Thomas Lübking ---
You *clearly* stated:
> Xorg can't find display driver, but don't try to load nvidia driver.
If X doesn't find a usable display driver, it won't start. And that is
*certainly* NOT
https://bugs.kde.org/show_bug.cgi?id=347281
Thomas Lübking changed:
What|Removed |Added
CC||bjou...@gmail.com
https://bugs.kde.org/show_bug.cgi?id=356238
Thomas Lübking changed:
What|Removed |Added
Resolution|INVALID |DUPLICATE
---
https://bugs.kde.org/show_bug.cgi?id=350826
--- Comment #49 from Thomas Lübking ---
(In reply to Marco Martin from comment #48)
> is it safe (and fast enough) checking what the existing window type is
> fairly often?
I beg your pardon??
The KWindowSystem classes
https://bugs.kde.org/show_bug.cgi?id=356328
--- Comment #3 from Thomas Lübking ---
I think we've two bugs here:
1. the old mousecursor area isn't marked damaged at all?
2. The old geometry is repainted insufficiently or not at all.
What happens if you move the window
https://bugs.kde.org/show_bug.cgi?id=350785
Thomas Lübking changed:
What|Removed |Added
CC|
https://bugs.kde.org/show_bug.cgi?id=356263
Thomas Lübking changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
https://bugs.kde.org/show_bug.cgi?id=356343
--- Comment #2 from Thomas Lübking ---
Wild guess: is it reproducible with the blur effect disabled?
(If not, what if you disable "cache intermediate results" in the blur effects
config dialog. It's the only checkbox)
--
https://bugs.kde.org/show_bug.cgi?id=356412
--- Comment #2 from Thomas Lübking ---
please post the output of "xrandr -q" and "xprop" (for the latter click the
panel after the cursor turned into a '+')
--
You are receiving this mail because:
You are watching all bug
https://bugs.kde.org/show_bug.cgi?id=356437
Thomas Lübking changed:
What|Removed |Added
Ever confirmed|0 |1
https://bugs.kde.org/show_bug.cgi?id=353428
--- Comment #24 from Thomas Lübking ---
No, but this is no deterministic error (depends on when the crash occurs and
when the next xcb flush takes place) - I personally saw it once or twice only.
Also kwin should not crash
https://bugs.kde.org/show_bug.cgi?id=348550
Thomas Lübking changed:
What|Removed |Added
Resolution|--- |WORKSFORME
https://bugs.kde.org/show_bug.cgi?id=356322
Thomas Lübking changed:
What|Removed |Added
See Also|
https://bugs.kde.org/show_bug.cgi?id=349219
Thomas Lübking changed:
What|Removed |Added
See Also|
https://bugs.kde.org/show_bug.cgi?id=328718
Thomas Lübking changed:
What|Removed |Added
See Also|
https://bugs.kde.org/show_bug.cgi?id=350826
Thomas Lübking changed:
What|Removed |Added
Ever confirmed|0 |1
https://bugs.kde.org/show_bug.cgi?id=350785
--- Comment #9 from Thomas Lübking ---
Looks good reg. bug #350288 (ie. I can confirm the fix) - thanksalot.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=341930
--- Comment #78 from Thomas Lübking ---
(In reply to Leslie Zhai from comment #77)
> 2. As Andreas suggested, I patched the kxmlgui to Remove
> QCoreApplication::setQuitLockEnabled(true) from KMainWindowPrivate::init()
Read
https://bugs.kde.org/show_bug.cgi?id=356480
--- Comment #2 from Thomas Lübking ---
Looks a lot like bug #351839, would likely be induced by aurorae decoration.
run: kwriteconfig5 --file kwinrc --group org.kde.kdecoration2 --key library
org.kde.breeze
problem gone?
https://bugs.kde.org/show_bug.cgi?id=356437
--- Comment #2 from Thomas Lübking ---
Since we cannot query the virtual desktop (w/o some X11 code or linking eg.
kwindowsystem in the Qt5 build), we'll have to make a choice here.
Either we turn this into a transient
https://bugs.kde.org/show_bug.cgi?id=356515
--- Comment #4 from Thomas Lübking ---
Nobody -at least not me- really cares about that flag =)
(I sometimes set it if I can explain a non-deterministic nor reproducible weird
behavior from the code, but otherwise a bug is
https://bugs.kde.org/show_bug.cgi?id=356516
--- Comment #1 from Thomas Lübking ---
can you please check the time settings in "kcmshell5 kwinscreenedges", notably
the distance between activation and reactivation?
--
You are receiving this mail because:
You are
https://bugs.kde.org/show_bug.cgi?id=356516
--- Comment #3 from Thomas Lübking ---
It would also not explain the apparent "good" left edge.
- Do you have (autohiding or other) panels on either edge?
- What happens if you lower activation to 0.
- Is this by moving
https://bugs.kde.org/show_bug.cgi?id=318322
Thomas Lübking changed:
What|Removed |Added
Status|UNCONFIRMED |CONFIRMED
Ever
https://bugs.kde.org/show_bug.cgi?id=356740
--- Comment #3 from Thomas Lübking ---
(In reply to Côme Chilliet from comment #2)
> had to reboot as kwin was crashed and nothing worked anymore.
So it's no segfault? What makes you believe that kwin "crashed"? (And not
https://bugs.kde.org/show_bug.cgi?id=356740
Thomas Lübking changed:
What|Removed |Added
Resolution|--- |BACKTRACE
https://bugs.kde.org/show_bug.cgi?id=354724
--- Comment #19 from Thomas Lübking ---
(In reply to Andreas Hartmetz from comment #18)
> How should that be done, sending close events and expecting applications to
> save their state in response, but not close windows or
https://bugs.kde.org/show_bug.cgi?id=356581
Thomas Lübking changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
https://bugs.kde.org/show_bug.cgi?id=356581
--- Comment #2 from Thomas Lübking ---
PS, we're probably gonna need the "glxinfo" output as well.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=356557
--- Comment #11 from Thomas Lübking ---
To gain less flexibility?
Despite Martins concern, the scripting overhead is neglectable - switching
fullscreen state doesn't happen that often (and far more expensive things than
a
https://bugs.kde.org/show_bug.cgi?id=356600
--- Comment #4 from Thomas Lübking ---
> I agree that the current font size is too small to read at a glance.
Which would be my concern as well.
I don't think there's a global OSD font, but the item isn't sufficiently "in
https://bugs.kde.org/show_bug.cgi?id=356600
--- Comment #6 from Thomas Lübking ---
Increase the size.
If it wasn't QML, I'd ensure the resulting size, but for QML use sth. like 32pt
or 3em (iff the latter is supported) as static values.
I randomly changed the size
https://bugs.kde.org/show_bug.cgi?id=340294
--- Comment #40 from Thomas Lübking ---
Completely unrelated to this bug, the driver waits for a vblank signal that
never occurs, suspend the compositor on the inactive VTs.
See bug #328122 or bug #330954
--
You are
https://bugs.kde.org/show_bug.cgi?id=328122
--- Comment #18 from Thomas Lübking ---
KWin has never fixed and actually cannot fix this (we'd need to track the VT
and that requires root permissions), the behavior is completely in the driver
(we just could at some point
https://bugs.kde.org/show_bug.cgi?id=354724
--- Comment #13 from Thomas Lübking ---
Andreas, the Qt patch kills the ability to cancel the logout process (when the
process or user prevents closing a window), I'm not sure it will be accepted
and if, you probably will
https://bugs.kde.org/show_bug.cgi?id=356557
--- Comment #15 from Thomas Lübking ---
Which is not part of the rule system (as your request initially pointed) and
totally broken/useless to begin with (because it doesn't cover unmanaged
windows which many games actually
https://bugs.kde.org/show_bug.cgi?id=356480
Thomas Lübking changed:
What|Removed |Added
Resolution|--- |DUPLICATE
https://bugs.kde.org/show_bug.cgi?id=351839
Thomas Lübking changed:
What|Removed |Added
CC||eloy...@gmail.com
https://bugs.kde.org/show_bug.cgi?id=356581
--- Comment #6 from Thomas Lübking ---
Will you please attach the informations I asked for?
fglrx could simply perform lousy because one context is now on a core profile
or it stumbles across the syncing between X11 and glx
https://bugs.kde.org/show_bug.cgi?id=356368
Thomas Lübking changed:
What|Removed |Added
See Also|
https://bugs.kde.org/show_bug.cgi?id=356600
Thomas Lübking changed:
What|Removed |Added
CC|
https://bugs.kde.org/show_bug.cgi?id=356600
--- Comment #1 from Thomas Lübking ---
@Thomas P.
kcmshell5 desktop, "Switching" tab (2nd), enable "Desktop switch on-screen
display", DISable "show desktop layout indicators" and switch between virtual
desktops.
I don't use
https://bugs.kde.org/show_bug.cgi?id=356616
Thomas Lübking changed:
What|Removed |Added
Status|UNCONFIRMED |NEEDSINFO
https://bugs.kde.org/show_bug.cgi?id=356516
Thomas Lübking changed:
What|Removed |Added
CC|
https://bugs.kde.org/show_bug.cgi?id=356574
Thomas Lübking changed:
What|Removed |Added
Status|CONFIRMED |RESOLVED
https://bugs.kde.org/show_bug.cgi?id=356523
Thomas Lübking changed:
What|Removed |Added
Product|kwin
https://bugs.kde.org/show_bug.cgi?id=344359
Thomas Lübking changed:
What|Removed |Added
Flags||ReviewRequest+
https://bugs.kde.org/show_bug.cgi?id=320892
Thomas Lübking changed:
What|Removed |Added
Flags||ReviewRequest+
https://bugs.kde.org/show_bug.cgi?id=318322
Thomas Lübking changed:
What|Removed |Added
See Also|
https://bugs.kde.org/show_bug.cgi?id=344359
Thomas Lübking changed:
What|Removed |Added
See Also|
https://bugs.kde.org/show_bug.cgi?id=356562
Thomas Lübking changed:
What|Removed |Added
See Also|
https://bugs.kde.org/show_bug.cgi?id=356516
Thomas Lübking changed:
What|Removed |Added
Summary|moving from one to another |Electric borders
https://bugs.kde.org/show_bug.cgi?id=356076
Thomas Lübking changed:
What|Removed |Added
CC||wen...@gmail.com
https://bugs.kde.org/show_bug.cgi?id=344359
Thomas Lübking changed:
What|Removed |Added
See Also|
https://bugs.kde.org/show_bug.cgi?id=354724
Thomas Lübking changed:
What|Removed |Added
CC|
https://bugs.kde.org/show_bug.cgi?id=356523
Thomas Lübking changed:
What|Removed |Added
Resolution|--- |INVALID
https://bugs.kde.org/show_bug.cgi?id=354811
--- Comment #14 from Thomas Lübking ---
Less workaround, equally not tested - much fun ;-)
https://git.reviewboard.kde.org/r/126403/
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=340489
--- Comment #35 from Thomas Lübking ---
Run
KWIN_USE_BUFFER_AGE=0 KWIN_EXPLICIT_SYNC=0 kwin_x11 --replace &
and see what happens.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=348753
--- Comment #48 from Thomas Lübking ---
You can add random environments to /etc/profile - do NOT source that script
there!
It's a script to shadow the actual kwin binary, but I wrote it for KDE SC4 (to
control some GL
https://bugs.kde.org/show_bug.cgi?id=356843
--- Comment #3 from Thomas Lübking ---
does maybe the "plasmashell" process crash/restart?
what happens if you suspend the compositor after such incident? old wp remains
or new (and plasmoids) back?
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=356843
--- Comment #6 from Thomas Lübking ---
> When I have turned off compositor and I change wallpaper then it remains.
What I wanted you to check is to
- enable the compositor
- change wallpaper
- show krunner
- make the
https://bugs.kde.org/show_bug.cgi?id=354724
--- Comment #17 from Thomas Lübking ---
Yes, my concern is that status quo for several/many applications is that they
do no connect to saveStateRequest() or commitDataRequest() and *only* perform
interaction on window close
https://bugs.kde.org/show_bug.cgi?id=353428
--- Comment #32 from Thomas Lübking ---
PS, dev note: we could investigate in "stealing" the WM selection from the
restarted instance if there's a crashcounter flag in the args.
--
You are receiving this mail because:
You
https://bugs.kde.org/show_bug.cgi?id=353428
--- Comment #31 from Thomas Lübking ---
I do not question that the KWin GL context "somehow™" triggers this condition -
but it really sounds like a kernel bug (and is hard to debug for this)
You could simply avoid the ugly
https://bugs.kde.org/show_bug.cgi?id=318322
--- Comment #28 from Thomas Lübking ---
See updated patch on reviewboard - I bet your arm on it ;-)
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=354724
--- Comment #15 from Thomas Lübking ---
The typical fail will be the "there are 5 tabs open, close/cancel" dialogs.
Afaiu this was added because of some MS Windows behavior and even if not, one
has to assume that clients
https://bugs.kde.org/show_bug.cgi?id=353428
--- Comment #33 from Thomas Lübking ---
In theory™, this should do:
diff --git a/main_x11.cpp b/main_x11.cpp
index 2c13743..1736f0d 100644
--- a/main_x11.cpp
+++ b/main_x11.cpp
@@ -173,7 +173,8 @@ void
https://bugs.kde.org/show_bug.cgi?id=356469
Thomas Lübking changed:
What|Removed |Added
CC|
https://bugs.kde.org/show_bug.cgi?id=341930
--- Comment #81 from Thomas Lübking ---
Can we please concentrate the discussion on bug #354724 to not "pollute" this
one w/ OT content?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=356557
--- Comment #9 from Thomas Lübking ---
Please notice that there's nothing such as a buil-in script, it's only a matter
of distribution policy.
Whether your distro installs the script with kwin, in a side package or you
fetch
https://bugs.kde.org/show_bug.cgi?id=356557
--- Comment #17 from Thomas Lübking ---
That probably means we've to tell the HIG team that their efforts to stash the
compositing kcm from end users failed miserably ;-P
On the bottom line, you say "kwin has this nice and
https://bugs.kde.org/show_bug.cgi?id=349356
--- Comment #5 from Thomas Lübking ---
Sorry for the delay.
Fyi, you changed the assignment of the bug to "unassigned-b...@kde.org" - I
found it by pure luck.
Be careful about the field unless you know what you do.
--
You
https://bugs.kde.org/show_bug.cgi?id=318322
--- Comment #25 from Thomas Lübking ---
Ok, actually this *can* not work since whatever it's called, at least the
default plasma application launcher doesn't use the sliding popups effect
(here)
I however neither get such
https://bugs.kde.org/show_bug.cgi?id=356557
--- Comment #7 from Thomas Lübking ---
(In reply to Martin Gräßlin from comment #6)
> I'm not sure about it as it introduces string comparisons for all windows at
> all time.
If QtScript isn't totally broken: only on
https://bugs.kde.org/show_bug.cgi?id=347900
Thomas Lübking changed:
What|Removed |Added
CC|
https://bugs.kde.org/show_bug.cgi?id=356562
--- Comment #4 from Thomas Lübking ---
Ah, thanks.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=356523
--- Comment #4 from Thomas Lübking ---
it does completely not matter what you "believe" and you did not specify "all".
the clients destroy and create new windows and demand a new position when
closed to the systray, that is
https://bugs.kde.org/show_bug.cgi?id=356526
--- Comment #3 from Thomas Lübking ---
if it's strictly reverse (ie. the forwad wheel acts always backward et vv.)
that would mean the buttons are swapped, resp. the driver generates the wrong
event.
the window manager has
https://bugs.kde.org/show_bug.cgi?id=356469
--- Comment #2 from Thomas Lübking ---
Is this a visual problem (ie. does it not happen with the compositor suspended,
SHIFT+Alt+F12) or is it truely not there?
--
You are receiving this mail because:
You are watching all
https://bugs.kde.org/show_bug.cgi?id=356526
Thomas Lübking changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
https://bugs.kde.org/show_bug.cgi?id=353428
--- Comment #28 from Thomas Lübking ---
The inability to switch to another VT means a problem in the kernel (at least
framebuffer control)
Nobody said this is fixed and I assume you hit this on "your" account because
of some
https://bugs.kde.org/show_bug.cgi?id=336089
--- Comment #32 from Thomas Lübking ---
a) @Martin K., wtf happened to Craig, is he fine? (pm me in doubt)
b) in any case this is apparently unmaintained bitrot - and that's neither an
"excuse" nor a "reason" for the bug -
https://bugs.kde.org/show_bug.cgi?id=348156
--- Comment #16 from Thomas Lübking ---
There're two reasons to avoid compositing:
a) Spare resources
b) Work around a bug
(a) is *not* reasonably gained by unredirection.
(b) is a bad approach to deal with problems
1 - 100 of 1287 matches
Mail list logo