[kcalc] [Bug 488995] Organize the behavior of cut/copy/paste actions
https://bugs.kde.org/show_bug.cgi?id=488995 --- Comment #4 from Sjoerd --- Created attachment 172011 --> https://bugs.kde.org/attachment.cgi?id=172011=edit paste text Follow up to my previous post, here is an example video about pasting. It sometimes stops pasting after completing a calculation. I noticed this because when I copy multiple numbers one by one from a text file and adding them to each other, halfway through it just stops pasting from the text file. -- You are receiving this mail because: You are watching all bug changes.
[kcalc] [Bug 488995] Organize the behavior of cut/copy/paste actions
https://bugs.kde.org/show_bug.cgi?id=488995 Sjoerd changed: What|Removed |Added CC||k...@brinkmail.org --- Comment #3 from Sjoerd --- Created attachment 172010 --> https://bugs.kde.org/attachment.cgi?id=172010=edit copy text I'm also having some problems with copying and pasting, but I'm not sure if it is related to this bug. It seems like the copy/paste functions are just unreliable. Sometimes it copies text, sometimes it does not. Sometimes it only works when using ctrl+c, but not when right clicking and selecting copy. Sometimes paste works, and after a calculation it doesn't. I have this problem on multiple machines with up to date openSUSE Tumbleweed with KCalc 24.05.2. See the attached video (sorry for the quality, screenrecording doesnt work due to a different bug). Selecting text and right clicking copy doesn't work, but in the last attempt I used ctrl+c and suddenly it does work. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 481933] Menus somtimes appear as normal windows when activated from anything other than the current active window
https://bugs.kde.org/show_bug.cgi?id=481933 Sjoerd changed: What|Removed |Added CC||k...@brinkmail.org --- Comment #14 from Sjoerd --- (In reply to Nate Graham from comment #12) > I can reproduce what I'm pretty sure is the same issue in the following way: > > 1. Open Konsole > 2. Type the text "green" > 3. Focus another window > 4. Hover over the word "green" I can reproduce it in this way as well. The wierd thing is, it only happens with the plasma panel after a while (maybe in combination with suspends as been said before in bug #482185). So since I just rebooted, I can't reproduce it right now with the panel in the usal way (focus on another window and right click the plasma panel), but I can reproduce it in your way. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482185] Context menu (when right-clicking on the desktop) appears in a separate window after external monitor restart
https://bugs.kde.org/show_bug.cgi?id=482185 --- Comment #13 from Sjoerd --- Created attachment 168872 --> https://bugs.kde.org/attachment.cgi?id=168872=edit Context menu window Happens for me as well with Tumbleweed and Plasma 6.0.4 on Wayland. When I have a window focused, and right click on the desktop, the context menu opens in a window. If I then click again, with no window focused, it opens normally. And the same happens for the right click menu of the taskbar, see attachted picture. Also only when a different window is focused. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482185] Context menu (when right-clicking on the desktop) appears in a separate window after external monitor restart
https://bugs.kde.org/show_bug.cgi?id=482185 Sjoerd changed: What|Removed |Added CC||k...@brinkmail.org -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 482195] Gwenview fails to open large images
https://bugs.kde.org/show_bug.cgi?id=482195 --- Comment #15 from Sjoerd --- (In reply to Oded Arbel from comment #14) > (In reply to Sjoerd from comment #13) > > ... was talking about 200 megapixel photos which is bigger than what I > > tested with. > > A 200MP image at standard RGB 24bpp is 600MB uncompressed. > > The current default of 256MB is enough to open a 85MP image. If I read the Qt docs right (https://doc.qt.io/qt-6/qimagereader.html#setAllocationLimit), it internally converts images to 32 bits, so the effective limit is smaller. A 200MP image would then be ~760 MB. So to fix the issue for the person who opened this bug the limit would need to be at least 800 MB. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 482195] Gwenview fails to open large images
https://bugs.kde.org/show_bug.cgi?id=482195 --- Comment #13 from Sjoerd --- (In reply to Bug Janitor Service from comment #12) > A possibly relevant merge request was started @ > https://invent.kde.org/graphics/gwenview/-/merge_requests/262 I saw that the proposal is to increase the limit to 400 mb. If I set QT_IMAGEIO_MAXALLOC to 400 and open images in Gwenview, I am still hitting the limit. I need at least 600 mb to open some of my images, and I think if I need this much others will too, and probably even more. The original poster of this bug was talking about 200 megapixel photos which is bigger than what I tested with. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 482195] Gwenview fails to open large images
https://bugs.kde.org/show_bug.cgi?id=482195 --- Comment #10 from Sjoerd --- But this problem is not with very large images. I have images in my library, some only 6 mb big, which I currently cannot open with anything but GIMP. And GIMP does not show the warning, it just opens it. Okular, Gwenview and Kolourpaint all have the "Rejecting image as it exceeds the current allocation limit of 256 megabytes" error when I try to open these images. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 482195] Gwenview fails to open large images
https://bugs.kde.org/show_bug.cgi?id=482195 --- Comment #5 from Sjoerd --- There is a workaround posted in https://bugs.kde.org/show_bug.cgi?id=483534 which I think is a duplicate bug. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 483534] gwenvew doesn't open high resolution png file
https://bugs.kde.org/show_bug.cgi?id=483534 Sjoerd changed: What|Removed |Added CC||k...@brinkmail.org --- Comment #2 from Sjoerd --- I think this is a duplicate of bug https://bugs.kde.org/show_bug.cgi?id=482195 And the problem is not only with Gwenview, it's also with other KDE image viewer/editors since the Plasma 6 update. Okular and Kolourpaint give the same error. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 482195] Gwenview fails to open large images
https://bugs.kde.org/show_bug.cgi?id=482195 Sjoerd changed: What|Removed |Added CC||k...@brinkmail.org --- Comment #4 from Sjoerd --- The problem is not only in Gwenview. Okular and Kolourpaint used to be able to open large images, and since I upgraded to Plasma 6 they both give an error. The same image opens fine in Gwenview, Okular and Kolourpaint on a Plasma 5.27 machine. The images I can't open aren't even that big, some of them are only 6 MB. It's just the resolution that's very high, around 14000x1 pixels. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483942] 'Keep launchers separate' setting does not hide open programs
https://bugs.kde.org/show_bug.cgi?id=483942 --- Comment #2 from Sjoerd --- The wierd thing is that I can almost create the original Plasma 5 behaviour sometimes. When I set sorting to 'Manually' in the Task Manager, and enable the 'Keep launchers separate'. I have all the pinned launchers to the left and they do not disappear (so not as I want/expect/as plasma 5 behaved). And if I then set sorting to 'Do not sort', I cannot change the 'keep launchers separate' setting, it's greyed out. And nothing really changes, I just cannot sort windows anymore. But if I then set sorting to 'Manually', and disable 'keep launchers separate', and then change sorting to 'Do not sort' again, and click OK, the behaviour is completely different than before. Now the pinned applications DO disappear when I open them. It's just that I can't sort them anymore. So even though 'keep launchers separate' is greyed out when sorting is set to 'Do not sort', the behaviour is different if you disable or enable it before you set sorting to 'Do not sort'. This feels like a bug? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 478851] "Task manager" mode: Pinned icons should be replaced by opened programs
https://bugs.kde.org/show_bug.cgi?id=478851 --- Comment #17 from Sjoerd --- Opened a new bug for this: https://bugs.kde.org/show_bug.cgi?id=483942 And thanks for all the work on Plasma 6 by the way. And for giving simple bug reports like this attention as well. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483942] 'Keep launchers separate' setting does not hide open programs
https://bugs.kde.org/show_bug.cgi?id=483942 --- Comment #1 from Sjoerd --- Created attachment 167434 --> https://bugs.kde.org/attachment.cgi?id=167434=edit separate launchers disabled -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483942] New: 'Keep launchers separate' setting does not hide open programs
https://bugs.kde.org/show_bug.cgi?id=483942 Bug ID: 483942 Summary: 'Keep launchers separate' setting does not hide open programs Classification: Plasma Product: plasmashell Version: 6.0.2 Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Task Manager and Icons-Only Task Manager Assignee: plasma-b...@kde.org Reporter: k...@brinkmail.org CC: qydwhotm...@gmail.com Target Milestone: 1.0 Created attachment 167433 --> https://bugs.kde.org/attachment.cgi?id=167433=edit separate launchers STEPS TO REPRODUCE 1. Enable setting "keep launchers separate" in the task manager (not-icons only) settings 2. Pin some applications to the task manager 3. Open some of the pinned applications OBSERVED RESULT The icons of the pinned applications are all to the left of the task manger, so they are separate as intended. But the icons of the pinned applications do not disappear when the application is open. See attachment 'seperate launchers.png'. The pinned launchers of the applications that have open windows are still visible to the left. EXPECTED RESULT The icons of the pinned applications should disappear when the application is opened. The pinned application should move into a 'window' instead of a pinned icon. This happens when the setting 'keep launchers seperate' is disabled. See attachment 'separate launchers disabled.png'. Firefox is pinned, but because it is open, the launcher icon is hidden. But Dolphin is not open, and the launcher is visible. But now the launchers are in the middle of open windows, and not separate to the left. So in my opinion the setting 'keep launchers separate' should behave the same way as when it's disabled, and hide open windows. But it should just keep them separate to the left of the task manager. SOFTWARE/OS VERSIONS Linux/KDE Plasma: openSuse Tumbleweed KDE Plasma Version: 6.0.2 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION Opened a new bug for this as requested by Nate Graham in https://bugs.kde.org/show_bug.cgi?id=478851 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 481413] symbol lookup error: /usr/lib/plasma.so.6 failure. Unable to start from tty using startplasma-wayland or startplasma-x11
https://bugs.kde.org/show_bug.cgi?id=481413 --- Comment #1 from Sjoerd --- Just updated libplasma now. The error is no longer there and I get a black screen instead when running startplasma-wayland -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 481413] New: symbol lookup error: /usr/lib/plasma.so.6 failure. Unable to start from tty using startplasma-wayland or startplasma-x11
https://bugs.kde.org/show_bug.cgi?id=481413 Bug ID: 481413 Summary: symbol lookup error: /usr/lib/plasma.so.6 failure. Unable to start from tty using startplasma-wayland or startplasma-x11 Classification: Plasma Product: plasmashell Version: 5.93.0 Platform: Arch Linux OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: generic-crash Assignee: plasma-b...@kde.org Reporter: s21926...@gmail.com Target Milestone: 1.0 SUMMARY plasma doesnt launch with error: "symbol lookup error: /usr/lib/libPlasma6.so.6: undefined symbol: _ZNK11QMetaObject17indexOfEnumeratorE14ByteArrayView, version QT_6". Im sorry cant get a good dump out of this since gdb and qmlls6 seem to not like each other and segfault. It could be me though since its my first time using gdb without a frontend. However it could also be a something wrong with the toolkit (maybe, very maybe). STEPS TO REPRODUCE 1. start from the tty using either "startplasma-wayland" or startplasma-x11 (also crashes when with same result when using plasmashell) command. OBSERVED RESULT no start and the above error message EXPECTED RESULT no error message and the desktop SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.93.0-beta3 KDE Frameworks Version: 5.93.0-beta3 Qt Version: 6.7.0-beta3 ADDITIONAL INFORMATION Done in a 64bit virtualbox environment with 8gb of ram, 12 cores and 60gb of space -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 478922] Global menu when hovering over sub menu with child menu. The child menu on first hover does not detect the edge of the screen.
https://bugs.kde.org/show_bug.cgi?id=478922 --- Comment #2 from Sjoerd --- Also the qml version of plasma 6 was 6.7.0. Sorry for the excessive corrections. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 478922] Global menu when hovering over sub menu with child menu. The child menu on first hover does not detect the edge of the screen.
https://bugs.kde.org/show_bug.cgi?id=478922 --- Comment #1 from Sjoerd --- Some already reported the issue I mentioned at the end of my post. Its bug 478910 Also the framework version is 5.247.0 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 478922] Global menu when hovering over sub menu with child menu. The child menu on first hover does not detect the edge of the screen.
https://bugs.kde.org/show_bug.cgi?id=478922 Sjoerd changed: What|Removed |Added CC||s21926...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 478922] New: Global menu when hovering over sub menu with child menu. The child menu on first hover does not detect the edge of the screen.
https://bugs.kde.org/show_bug.cgi?id=478922 Bug ID: 478922 Summary: Global menu when hovering over sub menu with child menu. The child menu on first hover does not detect the edge of the screen. Classification: Plasma Product: plasmashell Version: 5.91.0 Platform: Arch Linux OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: Global Menu Assignee: plasma-b...@kde.org Reporter: s21926...@gmail.com CC: k...@privat.broulik.de, mvourla...@gmail.com Target Milestone: 1.0 Flags: Wayland+, X11+ Created attachment 164394 --> https://bugs.kde.org/attachment.cgi?id=164394=edit top bar layout to recreate the issue. Also happens with a clean top bar with only 'Global Menu' SUMMARY The layout that I am using is fairly peculiar. It basically amounts to a vertically flipped macOS layout with the global menu on the right side of a topbar. This mostly works as expected except that when accessing a sub drop down from within a drop down from the global menu, on first hover it doesn't detect the edge of the screen it gets displayed on the right side. Meaning the sub drop-down gets cutoff by the screen. However when I hover over the same option again in the drop down it will detect the edge of the screen and display on the left side like it should. This is recreated on both plasma 5 and 6's most recent releases. Also on both wayland and X11 STEPS TO REPRODUCE 1. Have a layout as shown in the provided image with a bar that has the 'Global Menu' on the right side of the screen. 2. Open a program that supports the 'Global Menu' for example 'Kate' 3. Once open find a drop down from the Global menu that has an arrow pointing to the right of it indicating a sub-menu. 4. Hover over it. A sub-menu should now appear to the right side of the hovered over menu item. If the drop down is close enough to the edge and/or if the menu sub-menu is sufficiently big enough it should fall off the monitor. 5. Stop hovering over the menu item periodically to disappear the sub-menu. Hover back over it again to make it reappear. It should now appear on the left side of the drop down. This also works when keeping the application using the global menu in focus and leaving the drop down entirely and going back to the same menu item again. OBSERVED RESULT On First hover the sub menu appears on the right, falling off of the screen. On Second hover of the same menu item it appears on the left as it should. EXPECTED RESULT The sub menu of the drop down from the 'Global Menu' should appear on the left of the drop down on first hover. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.27.10 KDE Frameworks Version: 5.113.0 Qt Version: 5.15.11 Kernel Version: 6.6.7-arch1-1 (64-bit) Graphics Platform: X11 System Version: -CF OTHER OS Operating System: Arch Linux KDE Plasma Version: 5.91.0 KDE Frameworks Version: Cant check bc system setting is broken(Ill file a bug report for that). Qt Version: 6.6.1 Kernel Version: 6.6.8-arch1-1 (64-bit) Graphics Platform: Wayland System Version: -CF -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 478617] kwin scripting reports needing ';' or ',' in lines of good javascript code seen in the declaration 'async' as well as the 'await' operator.
https://bugs.kde.org/show_bug.cgi?id=478617 Sjoerd changed: What|Removed |Added Flags|X11+, NVIDIA+ | -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 478617] New: kwin scripting reports needing ';' or ',' in lines of good javascript code seen in the declaration 'async' as well as the 'await' operator.
https://bugs.kde.org/show_bug.cgi?id=478617
Bug ID: 478617
Summary: kwin scripting reports needing ';' or ',' in lines of
good javascript code seen in the declaration 'async'
as well as the 'await' operator.
Classification: Plasma
Product: kwin
Version: 5.27.10
Platform: Arch Linux
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: scripts
Assignee: kwin-bugs-n...@kde.org
Reporter: s21926...@gmail.com
Target Milestone: ---
Flags: X11+, NVIDIA+
SUMMARY
kwin scripting despite having support and working with promise and thenable
objects under kwin. Does not seem to recognise the operator 'await' or 'async'
declarations which are features of ES6 along with the mentioned thenables and
the class syntax. Both of which I use in my kwin script. Instead of just
working I get syntax errors in the console saying that the specific line is
missing a semicolon or comma.
STEPS TO REPRODUCE
1.
type something like:
```
async function() {
}
```
or like:
```
const variable = await Promise.race([myFunc(500), myAsyncFunc()]);
```
in the plasmainteractive console.
2.
Open up a journalctl listener with:
```
journalctl -f QT_CATEGORY=js QT_CATEGORY=kwin_scripting
```
3.
And execute the scripting using the kwin environment setting in the interactive
console.
OBSERVED RESULT
Outputs these errors in the console:
```
Dec 16 20:48:52 TRKY2 kwin_x11[1095]: kwin_scripting:
/home/s/.local/share/plasma-interactiveconsole/interactiveconsoleautosave.js:65:
error: Expected token `,'
Dec 16 20:49:13 TRKY2 kwin_x11[1095]: kwin_scripting:
/home/s/.local/share/plasma-interactiveconsole/interactiveconsoleautosave.js:60:
error: Expected token `;'
```
EXPECTED RESULT
Executing the code asynchronously with expected behavior.
SOFTWARE/OS VERSIONS
Operating System: Arch Linux
KDE Plasma Version: 5.27.10
KDE Frameworks Version: 5.113.0
Qt Version: 5.15.11
Kernel Version: 6.6.7-arch1-1 (64-bit)
Graphics Platform: X11
Processors: 24 × AMD Ryzen 9 3900X 12-Core Processor
Memory: 31.3 GiB of RAM
Graphics Processor: NVIDIA GeForce GTX 1080/PCIe/SSE2
Manufacturer: Gigabyte Technology Co., Ltd.
Product Name: X570 AORUS ELITE
System Version: -CF
ADDITIONAL INFORMATION
bug report 447922 seems to be the same issue however it is slightly different
as lambda functions do seem to work for me and it doesnt mention 'await'
--
You are receiving this mail because:
You are watching all bug changes.
[kwin] [Bug 432264] Wayland context Menus entries disappear/ graphic glitching
https://bugs.kde.org/show_bug.cgi?id=432264 Sjoerd van Leent changed: What|Removed |Added CC||sjoerd.van.le...@pm.me --- Comment #33 from Sjoerd van Leent --- I have exactly the same issue, with the left-monitoring working fine on 125%, the right-monitor on 100% fails to render the popup menus properly. My setup, the right-monitor is the primary monitor, so AFAIK it has nothing to do with primary/secondary, but with the position of the monitor. If I swap left to right, and keep the primary monitor the same as it was (so it becomes left), then the 125% monitor fails rendering the popup menus. -- You are receiving this mail because: You are watching all bug changes.
