https://bugs.kde.org/show_bug.cgi?id=386509
Bug ID: 386509
Summary: No Settings Icon
Product: kwin
Version: 5.11.2
Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
Severity: normal
https://bugs.kde.org/show_bug.cgi?id=386148
Bug ID: 386148
Summary: Can not apply gtk theme
Product: systemsettings
Version: 5.11.2
Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
Severity:
https://bugs.kde.org/show_bug.cgi?id=386031
Bug ID: 386031
Summary: Can not adjust the geometry of Kate on startup
Product: kate
Version: 17.08.2
Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
https://bugs.kde.org/show_bug.cgi?id=386021
Bug ID: 386021
Summary: Can not adjust the geometry of Kate
Product: kwin
Version: 5.11.1
Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
Severity:
https://bugs.kde.org/show_bug.cgi?id=386021
--- Comment #2 from LinG <lingtj...@hotmail.com> ---
But there are two different scenarios in which the application behaves
differently. Allow me to provide two small examples which illustrate what I'm
experiencing to be weird
case 1.
https://bugs.kde.org/show_bug.cgi?id=386021
--- Comment #5 from LinG <lingtj...@hotmail.com> ---
Also the workspace.getClient() function does not work for newly added clients
until the workspace.clientAdded() routine is finished, the client is not added
internally to the workspace. Which
https://bugs.kde.org/show_bug.cgi?id=386021
--- Comment #7 from LinG <lingtj...@hotmail.com> ---
my main problem is that you're basically setting up default settings for the
application in kwin and then you pray to god the application does not define
its own settings which override your d
https://bugs.kde.org/show_bug.cgi?id=386021
--- Comment #9 from LinG <lingtj...@hotmail.com> ---
I've taken a look at those at first but they did not satisfy my needs.
Regardless of that, don't you think that a window manager API that is not able
to change the geometry of applic
https://bugs.kde.org/show_bug.cgi?id=386021
--- Comment #4 from LinG <lingtj...@hotmail.com> ---
that was intentional in this example, if I had not done that and the second
script would work (which it doesn't) then you would not notice a difference in
the geometries.
Anyways, while tryi
https://bugs.kde.org/show_bug.cgi?id=386021
--- Comment #6 from LinG <lingtj...@hotmail.com> ---
Or is there a way to call clientAdded() after the application has started up
instead of before?
Right now it goes:
- apply settings in kwin
- startup application -> applies settings from app
https://bugs.kde.org/show_bug.cgi?id=386021
LinG <lingtj...@hotmail.com> changed:
What|Removed |Added
Summary|Can not adjust the geometry |Can not adjust the ge
https://bugs.kde.org/show_bug.cgi?id=392840
--- Comment #4 from LinG <lingtj...@hotmail.com> ---
That's because of a different bug (which I should probably report as well...).
But if you open "WM console" it shows the default state as "kwin" but it's
actually on "
https://bugs.kde.org/show_bug.cgi?id=392840
--- Comment #5 from LinG <lingtj...@hotmail.com> ---
you can test that you are not on "kwin" because you can't use the global
`workspace` for example if you try this, when you first open the console:
print(workspace.desktopGridWid
https://bugs.kde.org/show_bug.cgi?id=392840
--- Comment #8 from LinG <lingtj...@hotmail.com> ---
Ah okay, so it seems to be purely a console thing. Btw I've only ever used the
"wm console" to write my kwin scripts, could you explain to me how to use and
set this "KDe
https://bugs.kde.org/show_bug.cgi?id=392840
--- Comment #2 from LinG <lingtj...@hotmail.com> ---
just javascript, everything works fine when I only use the print() method once.
But when I start to use the print() method multiple times in quick succession
then it won't print() some of the
https://bugs.kde.org/show_bug.cgi?id=397397
Bug ID: 397397
Summary: No access to the client that changed desktop in
KWin::Client.desktopChanged() signal
Product: kwin
Version: 5.13.3
Platform: Archlinux Packages
https://bugs.kde.org/show_bug.cgi?id=397397
--- Comment #2 from LinG ---
Yes, I understand that at the moment when I'm connecting to the signal I have
access to the client, but I don't understand how I get access to the client
inside the callback method that I provide for when the signal gets
https://bugs.kde.org/show_bug.cgi?id=396751
Bug ID: 396751
Summary: Global shortcut new instance for entry 9 missing
Product: latte-dock
Version: 0.8.0
Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
https://bugs.kde.org/show_bug.cgi?id=392840
Bug ID: 392840
Summary: Can't seem to use print() multiple times
Product: kwin
Version: 5.12.4
Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
https://bugs.kde.org/show_bug.cgi?id=401025
Bug ID: 401025
Summary: Focus loss on menu and set to main window
Product: kate
Version: unspecified
Platform: Archlinux Packages
OS: Linux
Status: REPORTED
https://bugs.kde.org/show_bug.cgi?id=401025
LinG changed:
What|Removed |Added
Summary|Focus loss on menu and set |Focus loss on menu entry
|to main
https://bugs.kde.org/show_bug.cgi?id=401109
Bug ID: 401109
Summary: GTK global menu shortcut not working
Product: kded-appmenu
Version: unspecified
Platform: Archlinux Packages
OS: Linux
Status: REPORTED
https://bugs.kde.org/show_bug.cgi?id=403172
--- Comment #2 from LinG ---
Interesting, I assumed that they would use the same call to send the client to
a different virtual desktop (Workspace::sendClientToDesktop()) but then only
add an additional call in case 5c where you call a method to change
https://bugs.kde.org/show_bug.cgi?id=403172
--- Comment #4 from LinG ---
`qdbus org.kde.KWin /KWin supportInformation`
```
KWin Support Information:
The following information should be used when requesting support on e.g.
http://forum.kde.org.
It provides information about the currently running
https://bugs.kde.org/show_bug.cgi?id=403172
Bug ID: 403172
Summary: client geometry can not be changed in
desktopPresenceChanged callback when using the action
menu or virtual desktop grid view
Product: kwin
https://bugs.kde.org/show_bug.cgi?id=386509
LinG changed:
What|Removed |Added
Component|libplasma |default
Version|5.39.0
https://bugs.kde.org/show_bug.cgi?id=416093
--- Comment #10 from LinG ---
(In reply to Vlad Zahorodnii from comment #8)
> (In reply to LinG from comment #7)
> > I've always used this screen property of the client the same way as I have
> > been using the desktop property and am
https://bugs.kde.org/show_bug.cgi?id=416093
--- Comment #7 from LinG ---
(In reply to Vlad Zahorodnii from comment #3)
> (In reply to LinG from comment #0)
> > The screen property of a client is now readonly? I'm pretty sure it used to
> > be read and write, thus allowing me to ch
https://bugs.kde.org/show_bug.cgi?id=416093
--- Comment #12 from LinG ---
(In reply to Vlad Zahorodnii from comment #11)
> (In reply to LinG from comment #10)
> > Alright, where can I find the most recent documentation about the methods
> > and properties that I should use?
> U
https://bugs.kde.org/show_bug.cgi?id=416093
--- Comment #1 from LinG ---
Here is a MWE
var clients = workspace.clientList();
for (var i = 0; i < clients.length; i++)
{
if (clients[i] === null) {continue;}
if (clients[i].resourceName.toString() === 'konsole') // or any other client
that
https://bugs.kde.org/show_bug.cgi?id=416093
Bug ID: 416093
Summary: client screen property now readonly?
Product: kwin
Version: 5.17.5
Platform: Archlinux Packages
OS: Linux
Status: REPORTED
Severity:
https://bugs.kde.org/show_bug.cgi?id=426988
Bug ID: 426988
Summary: Client unresponsive when geometry changes if both
signals are connected
Product: kwin
Version: unspecified
Platform: Archlinux Packages
https://bugs.kde.org/show_bug.cgi?id=429595
Bug ID: 429595
Summary: client.activitiesChanged signal triggered when desktop
in menu changed to same desktop
Product: kwin
Version: unspecified
Platform: Archlinux Packages
https://bugs.kde.org/show_bug.cgi?id=428989
LinG changed:
What|Removed |Added
Status|NEEDSINFO |REPORTED
Resolution|WAITINGFORINFO
https://bugs.kde.org/show_bug.cgi?id=401025
--- Comment #3 from LinG ---
I just tried it and it seems to have been fixed, the bookmark entry is passed
by normally and I can also enter it normally. Thanks for looking into it :)
--
You are receiving this mail because:
You are watching all bug
https://bugs.kde.org/show_bug.cgi?id=428989
Bug ID: 428989
Summary: When are build plugin settings saved, if at all?
Product: kate
Version: unspecified
Platform: Archlinux Packages
OS: Linux
Status: REPORTED
https://bugs.kde.org/show_bug.cgi?id=428989
--- Comment #13 from LinG ---
(I just checked out the kate source code from github and compiled it and am
testing by running the kate binary in the bin directory)
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=428989
--- Comment #12 from LinG ---
It doesn't even enter this method. I tried to std::cout the numTargets int but
it never printed to the terminal, then I put a std::cout before the
cg.readEntry in this function but it never printed that either
I
https://bugs.kde.org/show_bug.cgi?id=428989
--- Comment #2 from LinG ---
I tried it with a session as well and it didn't work either. I attached a
recording
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=428989
--- Comment #3 from LinG ---
Created attachment 133259
--> https://bugs.kde.org/attachment.cgi?id=133259=edit
kate_build_plugin.mp4
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=428989
--- Comment #5 from LinG ---
Created attachment 133354
--> https://bugs.kde.org/attachment.cgi?id=133354=edit
full debug log
I turned on all debugging in kdebugsettings and wrote the output to this log
file.
I then did these steps:
1. open k
https://bugs.kde.org/show_bug.cgi?id=428989
--- Comment #7 from LinG ---
Yes, but they all disappear and return tot the default values, once I close
Kate and start it up again.
Where does kate save this build plugin information (so I can check if it's in
there while kate is still open)? Also
https://bugs.kde.org/show_bug.cgi?id=428989
--- Comment #8 from LinG ---
(It's a new laptop, that I just received last week and just installed Arch
Linux on, so it's a fresh install with barely any history in it (1 week of
history max)
--
You are receiving this mail because:
You are watching
https://bugs.kde.org/show_bug.cgi?id=428989
--- Comment #10 from LinG ---
Yeah I found it. I did this:
1. start kate
2. change the build plugin command to xelatex %f and name to test
3. close kate
4. open ~/.local/share/kate/sessions/*name*
[Plugin:katebuildplugin:MainWindow:0]
0 BuildCmd
https://bugs.kde.org/show_bug.cgi?id=428989
--- Comment #17 from LinG ---
I am currently not running Kate for my dev work, so I don't have it installed
anymore. However, if I do in the future start using Kate again, then I can
always file a new report if the problem still persists. Probably best
https://bugs.kde.org/show_bug.cgi?id=485266
Bug ID: 485266
Summary: Feature Request/Question
Classification: Plasma
Product: kwin
Version: master
Platform: Arch Linux
OS: Linux
Status: REPORTED
https://bugs.kde.org/show_bug.cgi?id=485267
Bug ID: 485267
Summary: Window output readonly
Classification: Plasma
Product: kwin
Version: master
Platform: Arch Linux
OS: Linux
Status: REPORTED
https://bugs.kde.org/show_bug.cgi?id=485266
--- Comment #2 from LinG ---
Cool, thank you for the explanation. Then based on your description, name is
unique enough for my use case.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=431020
Bug ID: 431020
Summary: kdeconnect-sms crashes when accessing a group SMS chat
Product: kdeconnect
Version: unspecified
Platform: Archlinux Packages
OS: Linux
Status:
https://bugs.kde.org/show_bug.cgi?id=452154
Bug ID: 452154
Summary: File xfer with kdeconnect starts fatal plasmashell
memory consumption
Product: kdeconnect
Version: unspecified
Platform: Archlinux Packages
50 matches
Mail list logo
