https://bugs.kde.org/show_bug.cgi?id=35
Roman Gilg changed:
What|Removed |Added
Resolution|--- |FIXED
Status|UNCONFIRMED
https://bugs.kde.org/show_bug.cgi?id=35
Roman Gilg changed:
What|Removed |Added
CC||subd...@gmail.com
--- Comment #6 from Roman Gilg
https://bugs.kde.org/show_bug.cgi?id=385743
--- Comment #12 from Roman Gilg ---
Best way forward would be to get the mesa debug symbols and report the crash
upstream.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=385743
Roman Gilg changed:
What|Removed |Added
CC||subd...@gmail.com
--- Comment #9 from Roman Gilg
https://bugs.kde.org/show_bug.cgi?id=394787
Roman Gilg changed:
What|Removed |Added
Resolution|--- |FIXED
Latest Commit
https://bugs.kde.org/show_bug.cgi?id=394787
--- Comment #2 from Roman Gilg ---
Thank you both for reporting and confirming. Seems to be a simple copy-paste
issue: https://phabricator.kde.org/D13270
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=390617
Roman Gilg changed:
What|Removed |Added
CC||subd...@gmail.com
--- Comment #5 from Roman Gilg
https://bugs.kde.org/show_bug.cgi?id=386304
--- Comment #15 from Roman Gilg <subd...@gmail.com> ---
Potential fix: https://phabricator.kde.org/D13084
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=394571
Roman Gilg <subd...@gmail.com> changed:
What|Removed |Added
CC||ludwig.schweit...@api
https://bugs.kde.org/show_bug.cgi?id=394645
Roman Gilg <subd...@gmail.com> changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
https://bugs.kde.org/show_bug.cgi?id=389222
Roman Gilg <subd...@gmail.com> changed:
What|Removed |Added
CC||subd...@gmail.com
--- C
https://bugs.kde.org/show_bug.cgi?id=377914
Roman Gilg <subd...@gmail.com> changed:
What|Removed |Added
CC||subd...@gmail.com
--- C
https://bugs.kde.org/show_bug.cgi?id=380311
Roman Gilg <subd...@gmail.com> changed:
What|Removed |Added
CC||subd...@gmail.com
--- C
https://bugs.kde.org/show_bug.cgi?id=394571
Roman Gilg <subd...@gmail.com> changed:
What|Removed |Added
CC||subd...@gmail.com
--- C
https://bugs.kde.org/show_bug.cgi?id=386304
--- Comment #14 from Roman Gilg <subd...@gmail.com> ---
I have created a Phab task for in-depth technical discussion of the problem(s):
https://phabricator.kde.org/T8771
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=394553
Bug ID: 394553
Summary: Empty slot in "Frequently used" on intro page
Product: systemsettings
Version: unspecified
Platform: Other
OS: Linux
Status: UNCONFIRMED
https://bugs.kde.org/show_bug.cgi?id=394531
--- Comment #3 from Roman Gilg <subd...@gmail.com> ---
Can changing the import from QQC1 to QQC2 do have side effects?
Because since it's only a small visual imperfection I would say it's not worth
the risk of introducing regressions and I woul
https://bugs.kde.org/show_bug.cgi?id=370377
--- Comment #3 from Roman Gilg <subd...@gmail.com> ---
* background is darker and more blurred now I believe, making it easier to
read,
* difference between activated and not activated items is still too small imo
(just a subtle brightness diff
https://bugs.kde.org/show_bug.cgi?id=394100
Roman Gilg <subd...@gmail.com> changed:
What|Removed |Added
See Also||https://bugs.freedesk
https://bugs.kde.org/show_bug.cgi?id=394100
Roman Gilg <subd...@gmail.com> changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
https://bugs.kde.org/show_bug.cgi?id=386304
Roman Gilg <subd...@gmail.com> changed:
What|Removed |Added
CC||subd...@gmail.com
--- C
https://bugs.kde.org/show_bug.cgi?id=370344
--- Comment #5 from Roman Gilg <subd...@gmail.com> ---
There is currently work being done to enable this feature again:
https://phabricator.kde.org/D12820
But this is only the beginning and more needs to be done. This might be ready
for 5.14.
-
https://bugs.kde.org/show_bug.cgi?id=394202
Bug ID: 394202
Summary: Single letter upper case search hides Application and
System Settings categories
Product: krunner
Version: unspecified
Platform: Other
OS:
https://bugs.kde.org/show_bug.cgi?id=394040
Bug ID: 394040
Summary: Delayed crash on startup
Product: plasmashell
Version: master
Platform: Other
OS: Linux
Status: UNCONFIRMED
Severity: normal
https://bugs.kde.org/show_bug.cgi?id=387153
Roman Gilg <subd...@gmail.com> changed:
What|Removed |Added
CC||subd...@gmail.com
--- C
https://bugs.kde.org/show_bug.cgi?id=389191
--- Comment #12 from Roman Gilg <subd...@gmail.com> ---
The addition of XDG Output Protocol could solve this issue:
https://phabricator.kde.org/D12235
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=393845
Roman Gilg <subd...@gmail.com> changed:
What|Removed |Added
CC||subd...@gmail.com
--- C
https://bugs.kde.org/show_bug.cgi?id=389191
Roman Gilg <subd...@gmail.com> changed:
What|Removed |Added
CC||subd...@gmail.com
--- C
https://bugs.kde.org/show_bug.cgi?id=393649
Roman Gilg <subd...@gmail.com> changed:
What|Removed |Added
CC||subd...@gmail.com
--- C
https://bugs.kde.org/show_bug.cgi?id=362125
Roman Gilg <subd...@gmail.com> changed:
What|Removed |Added
CC||subd...@gma
https://bugs.kde.org/show_bug.cgi?id=393547
--- Comment #3 from Roman Gilg <subd...@gmail.com> ---
Not sure why I said this back then. Probably because the plan was to get rid of
this KCM with the only two checkboxes.
But I now think it's better to keep it and make it more relevant by
https://bugs.kde.org/show_bug.cgi?id=393547
Roman Gilg <subd...@gmail.com> changed:
What|Removed |Added
CC||subd...@gmail.com
--- C
https://bugs.kde.org/show_bug.cgi?id=392752
Roman Gilg <subd...@gmail.com> changed:
What|Removed |Added
CC||subd...@gmail.com
--- C
https://bugs.kde.org/show_bug.cgi?id=383379
Bug 383379 depends on bug 350688, which changed state.
Bug 350688 Summary: Mouse acceleration setting has no effect with libinput
https://bugs.kde.org/show_bug.cgi?id=350688
What|Removed |Added
https://bugs.kde.org/show_bug.cgi?id=350688
Roman Gilg <subd...@gmail.com> changed:
What|Removed |Added
Status|CONFIRMED |RESOLVED
Reso
https://bugs.kde.org/show_bug.cgi?id=391623
Roman Gilg <subd...@gmail.com> changed:
What|Removed |Added
Latest Commit||https://commits.kde.o
https://bugs.kde.org/show_bug.cgi?id=392029
Roman Gilg <subd...@gmail.com> changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Latest
https://bugs.kde.org/show_bug.cgi?id=392029
Roman Gilg <subd...@gmail.com> changed:
What|Removed |Added
Assignee|rajeeshknamb...@gmail.com |subd...@gmail.com
-
https://bugs.kde.org/show_bug.cgi?id=390761
--- Comment #4 from Roman Gilg <subd...@gmail.com> ---
Yea, I was more interested in the "virtual middle-click button".
The emulation will work with
* https://phabricator.kde.org/D11468 on Wayland and
* https://phabricator.kde.org/D1146
https://bugs.kde.org/show_bug.cgi?id=392029
Bug ID: 392029
Summary: Clicking on Defaults does not change values in Wayland
session
Product: Touchpad-KCM
Version: unspecified
Platform: Neon Packages
OS:
https://bugs.kde.org/show_bug.cgi?id=377313
Roman Gilg <subd...@gmail.com> changed:
What|Removed |Added
CC||subd...@gmail.com
--- C
https://bugs.kde.org/show_bug.cgi?id=390761
Roman Gilg <subd...@gmail.com> changed:
What|Removed |Added
CC||subd...@gmail.com
--- C
https://bugs.kde.org/show_bug.cgi?id=391623
--- Comment #1 from Roman Gilg <subd...@gmail.com> ---
Thank you for the bug report and your encouraging feedback. :)
Indeed I overlooked this problem. I have a very simple patch, that solves this
issue (I just connected to the output added
https://bugs.kde.org/show_bug.cgi?id=391623
Roman Gilg <subd...@gmail.com> changed:
What|Removed |Added
Assignee|kwin-bugs-n...@kde.org |subd...@gmail.com
-
https://bugs.kde.org/show_bug.cgi?id=391530
Bug ID: 391530
Summary: Plasmashell crash on task manager context menu of
Konversation and Kickoff History tab
Product: frameworks-kactivities-stats
Version: unspecified
https://bugs.kde.org/show_bug.cgi?id=390280
Roman Gilg <subd...@gmail.com> changed:
What|Removed |Added
Resolution|--- |FIXED
Latest
https://bugs.kde.org/show_bug.cgi?id=390057
--- Comment #5 from Roman Gilg <subd...@gmail.com> ---
The MX Anywhere 2 entry is still there after turning the mouse / bt off. That's
not an issue with the mouse kcm then, but with the underlying bt hardware
detection I would say.
-
https://bugs.kde.org/show_bug.cgi?id=390021
--- Comment #1 from Roman Gilg <subd...@gmail.com> ---
The idea was to put the daytime/overall color temperature value in the end in a
separate KCM, that replaces KGamma on Wayland and handles all color correction.
This should then also do th
https://bugs.kde.org/show_bug.cgi?id=381630
--- Comment #88 from Roman Gilg <subd...@gmail.com> ---
Patch should have been backported to Neon now as well. Sorry for the delay.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=389200
Roman Gilg <subd...@gmail.com> changed:
What|Removed |Added
Resolution|--- |UPSTREAM
https://bugs.kde.org/show_bug.cgi?id=389200
Bug ID: 389200
Summary: Session startup hangs on Wayland master
Product: kwin
Version: git master
Platform: Other
OS: Linux
Status: UNCONFIRMED
Severity: normal
https://bugs.kde.org/show_bug.cgi?id=389147
--- Comment #4 from Roman Gilg <subd...@gmail.com> ---
The first bad commit for the seg fault is:
1a6b3c0a2baba955259d6083c0a3f25dfb44a682
The first bad commit for the original problem (edit of places entries is not
possible) does no
https://bugs.kde.org/show_bug.cgi?id=389147
Roman Gilg <subd...@gmail.com> changed:
What|Removed |Added
Summary|Edit of places entries not |Edit of places e
https://bugs.kde.org/show_bug.cgi?id=389147
Roman Gilg <subd...@gmail.com> changed:
What|Removed |Added
Severity|normal |critical
--- Comment #
https://bugs.kde.org/show_bug.cgi?id=389147
Bug ID: 389147
Summary: Edit of places entries not possible
Product: dolphin
Version: unspecified
Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
https://bugs.kde.org/show_bug.cgi?id=387502
Roman Gilg <subd...@gmail.com> changed:
What|Removed |Added
CC||subd...@gmail.com
--- C
https://bugs.kde.org/show_bug.cgi?id=387156
--- Comment #1 from Roman Gilg <subd...@gmail.com> ---
Ok, so for reference the difference between click method "Fingers" and "Multi
tapping" is:
* Fingers is associated with the _physical_ down-pressing of the whole t
https://bugs.kde.org/show_bug.cgi?id=389110
Roman Gilg <subd...@gmail.com> changed:
What|Removed |Added
CC||subd...@gma
https://bugs.kde.org/show_bug.cgi?id=389098
Roman Gilg <subd...@gmail.com> changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Reso
https://bugs.kde.org/show_bug.cgi?id=385626
Roman Gilg <subd...@gmail.com> changed:
What|Removed |Added
CC||subd...@gmail.com
--- C
https://bugs.kde.org/show_bug.cgi?id=389098
Roman Gilg <subd...@gmail.com> changed:
What|Removed |Added
Assignee|kwin-bugs-n...@kde.org |subd...@gmail.com
-
https://bugs.kde.org/show_bug.cgi?id=381630
--- Comment #77 from Roman Gilg <subd...@gmail.com> ---
Antonio backported David's patch for Arch already:
https://git.archlinux.org/svntogit/packages.git/tree/trunk/PKGBUILD?h=packages/qt5-wayland#n17
--
You are receiving this mail becaus
https://bugs.kde.org/show_bug.cgi?id=389098
Bug ID: 389098
Summary: Freeze on Alt+Tab with AMDGPU driver
Product: kwin
Version: git master
Platform: Other
OS: Linux
Status: UNCONFIRMED
Severity: normal
https://bugs.kde.org/show_bug.cgi?id=381630
--- Comment #75 from Roman Gilg <subd...@gmail.com> ---
I assume it will be backported by the Neon Team for 5.12 LTS release if Qt
isn't fast enough with releasing a bugfixed Qt 5.9.
--
You are receiving this mail because:
You are watching a
https://bugs.kde.org/show_bug.cgi?id=388749
--- Comment #4 from Roman Gilg <subd...@gmail.com> ---
Yes, this is a problem with the group / proxy / model behind it. In short my
believe is that a backend model change does not update the QML code reliable.
But this is a fragile area b
https://bugs.kde.org/show_bug.cgi?id=388628
Bug ID: 388628
Summary: Long delay on startup
Product: kwin
Version: git master
Platform: Other
OS: Linux
Status: UNCONFIRMED
Severity: normal
https://bugs.kde.org/show_bug.cgi?id=375969
Roman Gilg <subd...@gmail.com> changed:
What|Removed |Added
Latest Commit||https://commits.kde.o
https://bugs.kde.org/show_bug.cgi?id=382067
--- Comment #15 from Roman Gilg <subd...@gmail.com> ---
Well, I should have checked the attachment in the first post more carefully
after I was cc'd. This problem is with the old version of the thumbnails before
my rewrite one year ago.
Sinc
https://bugs.kde.org/show_bug.cgi?id=387692
Roman Gilg <subd...@gmail.com> changed:
What|Removed |Added
Resolution|--- |FIXED
https://bugs.kde.org/show_bug.cgi?id=371494
Roman Gilg <subd...@gmail.com> changed:
What|Removed |Added
Latest Commit||https://commits.kde.o
https://bugs.kde.org/show_bug.cgi?id=387692
--- Comment #4 from Roman Gilg <subd...@gmail.com> ---
Well, for now I did change it back to 4.0 in the packaging:
https://packaging.neon.kde.org/kde-std/kdevelop.git/commit/?h=Neon/unstable=6e04361e00bc1fc3d637d0f813327f01b5e5e490
Cur
https://bugs.kde.org/show_bug.cgi?id=387692
Roman Gilg <subd...@gmail.com> changed:
What|Removed |Added
Resolution|INVALID |---
Versi
https://bugs.kde.org/show_bug.cgi?id=387692
Bug ID: 387692
Summary: Seg fault when opening CMake file as project
Product: kdevelop
Version: git master
Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
https://bugs.kde.org/show_bug.cgi?id=387579
Bug ID: 387579
Summary: High CPU usage
Product: systemsettings
Version: unspecified
Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
Severity: normal
https://bugs.kde.org/show_bug.cgi?id=386811
Roman Gilg <subd...@gmail.com> changed:
What|Removed |Added
CC||subd...@gmail.com
--- C
https://bugs.kde.org/show_bug.cgi?id=380879
--- Comment #22 from Roman Gilg <subd...@gmail.com> ---
(IMO the default should be to not expand - it is aligned then with what Dolphin
and Kate are doing per default)
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=380879
--- Comment #21 from Roman Gilg <subd...@gmail.com> ---
The default should be either:
- Expand and show new tab + close tab buttons
- Not expand
to give the user a visual hint about the possibility to open multiple tabs.
With the patch the d
https://bugs.kde.org/show_bug.cgi?id=386490
--- Comment #3 from Roman Gilg <subd...@gmail.com> ---
Yes, that's a good idea. We could then decide to not use this
plane/crtc/connector.
That said, my assumption is that for an atomic mode property this should never
happen. But since we wo
https://bugs.kde.org/show_bug.cgi?id=386490
--- Comment #1 from Roman Gilg <subd...@gmail.com> ---
The problem seems to be, that not all drivers export the newly queried
"rotation" property to user space in contrast to the atomic mode setting
propertiers, which are expected to
https://bugs.kde.org/show_bug.cgi?id=381630
Roman Gilg <subd...@gmail.com> changed:
What|Removed |Added
CC||subd...@gmail.com
--- C
https://bugs.kde.org/show_bug.cgi?id=375680
Roman Gilg <subd...@gmail.com> changed:
What|Removed |Added
Resolution|WAITINGFORINFO |---
https://bugs.kde.org/show_bug.cgi?id=382571
--- Comment #7 from Roman Gilg <subd...@gmail.com> ---
Potential fix: https://phabricator.kde.org/D7769
Maybe you can test it out Dr. Chapatin?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=384600
Bug ID: 384600
Summary: First tool tip to be shown has larger width than
needed
Product: plasmashell
Version: master
Platform: Other
OS: Linux
Status:
https://bugs.kde.org/show_bug.cgi?id=383886
Roman Gilg <subd...@gmail.com> changed:
What|Removed |Added
CC||subd...@gmail.com
--- C
https://bugs.kde.org/show_bug.cgi?id=383882
Roman Gilg <subd...@gmail.com> changed:
What|Removed |Added
CC||subd...@gmail.com
--- C
https://bugs.kde.org/show_bug.cgi?id=384514
Roman Gilg <subd...@gmail.com> changed:
What|Removed |Added
CC||subd...@gmail.com
--- C
https://bugs.kde.org/show_bug.cgi?id=375680
Roman Gilg <subd...@gmail.com> changed:
What|Removed |Added
Status|CONFIRMED |NEEDSINFO
Reso
https://bugs.kde.org/show_bug.cgi?id=375680
--- Comment #2 from Roman Gilg <subd...@gmail.com> ---
I'm open for a proposal on how the thumbnail item should be highlighted on
mouse over. It must be consistent with other forms of highlighting used in
Plasma and also must not create a arti
https://bugs.kde.org/show_bug.cgi?id=383410
--- Comment #17 from Roman Gilg <subd...@gmail.com> ---
(based on https://wayland.freedesktop.org/ubuntu16.04.html)
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=383410
--- Comment #16 from Roman Gilg <subd...@gmail.com> ---
You can use my script for compiling (change the rootdir and INST vars to your
liking, an install in /usr/local though makes KWin directly using the compiled
Xwayland on next launch):
#!/
https://bugs.kde.org/show_bug.cgi?id=383410
--- Comment #14 from Roman Gilg <subd...@gmail.com> ---
I just tried and the problem is still there. KWin log with
WAYLAND_DEBUG=server:
[2240489,397] wl_surface@20.attach(wl_buffer@11, 0, 0)
[2240489,410] wl_surface@20.damage(0, 0, 3840
https://bugs.kde.org/show_bug.cgi?id=383146
Roman Gilg <subd...@gmail.com> changed:
What|Removed |Added
CC||subd...@gmail.com
--- C
https://bugs.kde.org/show_bug.cgi?id=363147
--- Comment #18 from Roman Gilg <subd...@gmail.com> ---
Hi Brennan,
from my side the patch worked. It felt though like there were some performance
issues when using the many sizes (since it loops through them), but that might
be also in my imagi
https://bugs.kde.org/show_bug.cgi?id=362546
--- Comment #6 from Roman Gilg <subd...@gmail.com> ---
I think it's somehow related with the behavior when you have selected multiple
files and then press Ctrl+Arrow-up/down.
In this case the selection won't change but the "underlined/a
https://bugs.kde.org/show_bug.cgi?id=362546
--- Comment #4 from Roman Gilg <subd...@gmail.com> ---
Hey, thanks for the tip. Could be still make more sense to have the selection
marker move always to the last selected item with or without the mouse cursor
hovering about it. This feels stil
https://bugs.kde.org/show_bug.cgi?id=362546
Roman Gilg <subd...@gmail.com> changed:
What|Removed |Added
Status|RESOLVED|REOPENED
Reso
https://bugs.kde.org/show_bug.cgi?id=383410
--- Comment #10 from Roman Gilg <subd...@gmail.com> ---
Thanks for digging into this. You're right that the cursor can't be locked and
confined at the same time.
The Xwayland code works like this: First confine. If then a certain condition
https://bugs.kde.org/show_bug.cgi?id=383410
--- Comment #5 from Roman Gilg <subd...@gmail.com> ---
You're sure it's created only once? While s_osd is a static
OnScreenNotification pointer, we still always call create() in osd() and in
create() a new OnScreenNotification instance is c
https://bugs.kde.org/show_bug.cgi?id=383410
--- Comment #2 from Roman Gilg <subd...@gmail.com> ---
We get confined and locked probably at the same time, but we setConfined first
in https://cgit.kde.org/kwin.git/tree/pointer_input.cpp#n599, show the confined
OSD and return on
https://cgit.k
https://bugs.kde.org/show_bug.cgi?id=383410
Bug ID: 383410
Summary: Creating both OSD for pointer confinement + lock in
short succesion hangs Wayland session
Product: kwin
Version: git master
Platform: Other
301 - 400 of 513 matches
Mail list logo
