[Powerdevil] [Bug 489510] Screen dims despite video playing

[Szymon Łągiewka]

https://bugs.kde.org/show_bug.cgi?id=489510

Szymon Łągiewka  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|WAITINGFORINFO  |DUPLICATE

--- Comment #2 from Szymon Łągiewka  ---
You're indubitably right. Tested quickly with VLC from rpm and it doesn't seem
to be an issue there.

*** This bug has been marked as a duplicate of bug 486506 ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[Powerdevil] [Bug 486506] Firefox (Flatpak) does not inhibit power management when playing videos

[Szymon Łągiewka]

https://bugs.kde.org/show_bug.cgi?id=486506

Szymon Łągiewka  changed:

   What|Removed |Added

 CC||bugs-...@lagiewka.pl

--- Comment #9 from Szymon Łągiewka  ---
*** Bug 489510 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[Powerdevil] [Bug 489510] New: Screen dims despite video playing

[Szymon Łągiewka]

https://bugs.kde.org/show_bug.cgi?id=489510

Bug ID: 489510
   Summary: Screen dims despite video playing
Classification: Plasma
   Product: Powerdevil
   Version: 6.1.1
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: bugs-...@lagiewka.pl
CC: m...@ratijas.tk, natalie_clar...@yahoo.de
  Target Milestone: ---

***
If you're not sure this is actually a bug, instead post about it at
https://discuss.kde.org

If you're reporting a crash, attach a backtrace with debug symbols; see
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***

SUMMARY


STEPS TO REPRODUCE
1. Have "dim automatically" enabled (e.g. after 30s to see it quickly)
2. Start video playback (e.g. in Firefox)
3. Confirm in "Power and Battery" tray widget that sleep and screen locking are
blocked due to FF "video-playing"
4. Wait period specified in 1.

OBSERVED RESULT
Screen dims after 30s

EXPECTED RESULT
Screen is not dimmed for as long as the video is playing.

SOFTWARE/OS VERSIONS
Operating System: Fedora Linux 40
KDE Plasma Version: 6.1.1
KDE Frameworks Version: 6.3.0
Qt Version: 6.7.1
Kernel Version: 6.9.6-200.fc40.x86_64 (64-bit)
Graphics Platform: Wayland

ADDITIONAL INFORMATION
I see no UX reason why screen should get dimmed whilst the video is playing. It
just doesn't make any sense to reduce the experience, especially when watching
full screen and not performing any mouse/keyboard actions.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 446431] Automatic do not disturb reason can be confusing

[Szymon Łągiewka]

https://bugs.kde.org/show_bug.cgi?id=446431

--- Comment #5 from Szymon Łągiewka  ---
Created attachment 171208
  --> https://bugs.kde.org/attachment.cgi?id=171208=edit
DND reason as of 30.06.2024

The DND message now shows Firefox Web Browser as the reason. It looks like a
FIXED issue to me.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasma-pa] [Bug 487658] New naming style is not great when a lot of similar devices are all connected at once

[Szymon Łągiewka]

https://bugs.kde.org/show_bug.cgi?id=487658

Szymon Łągiewka  changed:

   What|Removed |Added

 CC||bugs-...@lagiewka.pl

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasma-pa] [Bug 488897] Devices' names are different from System Settings

[Szymon Łągiewka]

https://bugs.kde.org/show_bug.cgi?id=488897

--- Comment #4 from Szymon Łągiewka  ---
I knew this change was coming to the applet, so I checked the MR behind it. It
seems to use `node.nick` property to display prettier names.
https://invent.kde.org/plasma/plasma-pa/-/merge_requests/239

However, it's seems to be the audio stack PipeWire (or it's PulseAudio/ALSA
compatibility) that provides the weird data. Here's output of `pw-dump` props
for a device that shows us "USB Device #1"

```
  "props": {
"alsa.card": 0,
"alsa.card_name": "SteelSeries Arctis 5",
"alsa.class": "generic",
"alsa.components": "USB1038:12aa",
"alsa.device": 1,
"alsa.driver_name": "snd_usb_audio",
"alsa.id": "S5",
"alsa.long_card_name": "SteelSeries SteelSeries Arctis 5 at
usb-:0c:00.3-3, full speed",
"alsa.mixer_name": "USB Mixer",
"alsa.name": "USB Audio #1",
"alsa.resolution_bits": 16,
"alsa.subclass": "generic-mix",
"alsa.subdevice": 0,
"alsa.subdevice_name": "subdevice #0",
"api.alsa.card.longname": "SteelSeries SteelSeries Arctis 5 at
usb-:0c:00.3-3, full speed",
"api.alsa.card.name": "SteelSeries Arctis 5",
"api.alsa.path": "hw:0,1,0",
"api.alsa.pcm.card": 0,
"api.alsa.pcm.stream": "playback",
"audio.adapt.follower": "",
"audio.channels": 2,
"audio.position": "FL,FR",
"card.profile.device": 1,
"client.id": 48,
"clock.quantum-limit": 8192,
"device.api": "alsa",
"device.class": "sound",
"device.id": 72,
"device.profile.description": "Game",
"device.profile.name": "analog-game",
"device.routes": 1,
"factory.id": 18,
"factory.mode": "merge",
"factory.name": "api.alsa.pcm.sink",
"library.name": "audioconvert/libspa-audioconvert",
"media.class": "Audio/Sink",
"node.description": "SteelSeries Arctis 5 Game",
"node.driver": true,
"node.name":
"alsa_output.usb-SteelSeries_SteelSeries_Arctis_5_-00.analog-game",
"node.nick": "USB Audio #1",
"node.pause-on-idle": false,
"object.id": 78,
"object.path": "alsa:pcm:0:hw:0,1,0:playback",
"object.serial": 585,
"priority.driver": 737,
"priority.session": 737
  }
```

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasma-pa] [Bug 488897] Devices' names are different from System Settings

[Szymon Łągiewka]

https://bugs.kde.org/show_bug.cgi?id=488897

Szymon Łągiewka  changed:

   What|Removed |Added

 CC||bugs-...@lagiewka.pl

--- Comment #3 from Szymon Łągiewka  ---
Created attachment 170914
  --> https://bugs.kde.org/attachment.cgi?id=170914=edit
Device names as seen under macOS

I'm attaching how macOS sees the same input devices (Arctis headphones with
chat+game mode)

I'm glad that I finally see devices' more natural names. "USB Audio Codec" is
in place of "Analog Output (PCM2902 Audio Codec Analog Stereo)" which never
made any sense to me. Now it matches what macOS was always reporting. 
However, the Arctis case makes it seem unpolished. Looking forward to more
updates!

-- 
You are receiving this mail because:
You are watching all bug changes.

[krusader] [Bug 471828] New: KrViewer showing black background instead of displaying the picture until Generic Viewer re-selected.

[Szymon Kosecki]

https://bugs.kde.org/show_bug.cgi?id=471828

Bug ID: 471828
   Summary: KrViewer showing black background instead of
displaying the picture until Generic Viewer
re-selected.
Classification: Applications
   Product: krusader
   Version: Git
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: krviewer
  Assignee: krusader-bugs-n...@kde.org
  Reporter: skose...@gmail.com
CC: krusader-bugs-n...@kde.org
  Target Milestone: ---

Created attachment 160019
  --> https://bugs.kde.org/attachment.cgi?id=160019=edit
Screen capture showing the problem and a matching krusader debug log text file.

SUMMARY
***
Krusader settings set to default viewer being Generic Viewer. 
KrViewer displays images (tested jpg/png) as blank (white or black background -
depending on the theme)  
Once the Generic Viewer is reselected from KrViever Menu  

***


STEPS TO REPRODUCE
1. Select an image in one of the panes then click on View or press F3 key
2. KrViever Opens the image but it is only black placeholder. 

OBSERVED RESULT

1. Image does not show - Black background only
2. Selecting Generic Viewer from the KrViewer menu reloads the image correctly. 

EXPECTED RESULT

1. Image displays on first load

SOFTWARE/OS VERSIONS

Windows: n/a
macOS: n/a
Linux/KDE Plasma:  Kernel 6.3.9-zen1-1-zen / X11
(available in About System)
KDE Plasma Version:  5.27.6
KDE Frameworks Version:  5.107.0
Qt Version:  5.15.10 

ADDITIONAL INFORMATION
Same behaviour in version 2.72, 2.8.0 - did not test any other versions

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 446948] Qt apps scaling breaks in multi-monitor setup with 90 degree rotation

[Szymon Łągiewka]

https://bugs.kde.org/show_bug.cgi?id=446948

Szymon Łągiewka  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
 Resolution|--- |FIXED

--- Comment #5 from Szymon Łągiewka  ---
Closing ;)

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 446948] Qt apps scaling breaks in multi-monitor setup with 90 degree rotation

[Szymon Łągiewka]

https://bugs.kde.org/show_bug.cgi?id=446948

--- Comment #4 from Szymon Łągiewka  ---
I can no longer see the issue!

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kio] [Bug 451774] Selecting remote protocol does not properly auto-fill "//"

[Szymon Zielonka]

https://bugs.kde.org/show_bug.cgi?id=451774

Szymon Zielonka  changed:

   What|Removed |Added

Version|git master  |5.104.0

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kio] [Bug 451774] Selecting remote protocol does not properly auto-fill "//"

[Szymon Zielonka]

https://bugs.kde.org/show_bug.cgi?id=451774

Szymon Zielonka  changed:

   What|Removed |Added

  Component|bars: location  |URL navigator
 CC||kdelibs-b...@kde.org
Product|dolphin |frameworks-kio
Version|22.12.2 |git master

-- 
You are receiving this mail because:
You are watching all bug changes.

[dolphin] [Bug 451774] Selecting remote protocol does not properly auto-fill "//"

[Szymon Zielonka]

https://bugs.kde.org/show_bug.cgi?id=451774

Szymon Zielonka  changed:

   What|Removed |Added

   Assignee|dolphin-bugs-n...@kde.org   |szy...@zsdev.eu
 CC||szy...@zsdev.eu

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 466690] On top panel some types of app windows react wrong on restore from maximize

[Szymon]

https://bugs.kde.org/show_bug.cgi?id=466690

--- Comment #2 from Szymon  ---
Problem is declared on thread title, some applications don't restore thier
sizes after maximize when panel bar is on top of screen. All electron apps and
Qt6 apps won't work at all, and some older gtk applications to. Original size
that windows are overwritten after first attempt to unmaximize. Idk how to
explain simpler to understand , my english is pretty bad.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 466690] New: On top panel some types of app windows react wrong on restore from maximize

[Szymon]

https://bugs.kde.org/show_bug.cgi?id=466690

Bug ID: 466690
   Summary: On top panel some types of app windows react wrong on
restore from maximize
Classification: Plasma
   Product: plasmashell
   Version: 5.27.2
  Platform: Archlinux
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Panel
  Assignee: plasma-b...@kde.org
  Reporter: szymondud...@gmail.com
CC: niccolo.venera...@gmail.com
  Target Milestone: 1.0

STEPS TO REPRODUCE

1. Login to Wayland Session
2. Move panel from bottom to top
3. Maximize app like : firefox, vscode, discord, timeshift, qtcreator by
dragging to top or double click.
4. Pull down that window ( disconnect the maximized window from the panel )
5. To restore original size of window, maximize again by double click or move
by mouse to top of screen ( stick to panel )

OBSERVED RESULT

On electron apps problem occur without exception and on others like Vala :
Timeshift, or QT-6 : OBS, QTCreator, QBittorrent, GTK2 : gimp, Java :
JetBrains, and Others : Krita. Occur also. 

on KDE apps, or when panel is not on top of screen, problem not appear.

EXPECTED RESULT

un-maximize must restore original window size.

SOFTWARE/OS VERSIONS
Linux : 6.1.x
KDE Plasma Version:  5.26.5, 5.27.2
KDE Frameworks Version: 5.103.0
Qt Version: 5.18.8

-- 
You are receiving this mail because:
You are watching all bug changes.

[Breeze] [Bug 465948] Option to disable window border introduced in 5.27

[Szymon Szypulski]

https://bugs.kde.org/show_bug.cgi?id=465948

Szymon Szypulski  changed:

   What|Removed |Added

 CC||s...@gen2.org

-- 
You are receiving this mail because:
You are watching all bug changes.

[Breeze] [Bug 457565] Multiscreen: Window's shadow and outline bleed over when window is maximized or tiled to an edge adjacent to another screen

[Szymon Szypulski]

https://bugs.kde.org/show_bug.cgi?id=457565

Szymon Szypulski  changed:

   What|Removed |Added

 CC||s...@gen2.org

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 464785] New: [Wayland] - "Minimize All Windows" don't restore windows on Wayland

[Szymon]

https://bugs.kde.org/show_bug.cgi?id=464785

Bug ID: 464785
   Summary: [Wayland] - "Minimize All Windows" don't restore
windows on Wayland
Classification: Plasma
   Product: plasmashell
   Version: 5.26.5
  Platform: Manjaro
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Show Desktop/Minimize All
  Assignee: plasma-b...@kde.org
  Reporter: szymondud...@gmail.com
  Target Milestone: 1.0

SUMMARY

STEPS TO REPRODUCE

( Wayland Session )
1.  Change "Peak at Desktop" applet to "Minimize all Windows"
2.  Open two or more applications
3.  Remember which application was first and second, and so on.
4.  So last opened app is now active.
5. Change active window to 1th app
6. Use "Minimize all Windows" twice, and make sure that others 2 apps windows
are "behind" this activated. 


Behavior :

For example if u opened 6 apps ( from 1 to 6 in order ) . Then make sure that
2th app is active and 1th is behind .  Now if u use "Minimize All Windows" then
it will be work, why ? Because app which was opened at last in row work with
anything under. So if u take last opened app as active window and others
behind. This will be work. If u that 6th app just minimize alone by button and
left 5 apps in order from 5 to 1 ( 5th active ) then it still be working. But
if u change order from 1 to 6 or 5 and so on, then "Minimize All Windows" won't
work. 

I don't know why it works that way, but the problem always occurs 100% of the
time. I reported it before version 5.24 and it was considered fixed. But from
what I remember I tested the fix after the release of 5.24 and then 5.25 and
now 5.26 and the error still occurs.



SOFTWARE/OS VERSIONS
Linux: 6.1.7-1
KDE Plasma Version: 5.26.5
KDE Frameworks Version: 5.102.0
Qt Version: 5.15.8

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 446948] Qt apps scaling breaks in multi-monitor setup with 90 degree rotation

[Szymon Łągiewka]

https://bugs.kde.org/show_bug.cgi?id=446948

--- Comment #3 from Szymon Łągiewka  ---
>From Nate's blog I heard about 

```
In the Plasma Wayland session, when you drag a window containing QtQuick-based
user interface elements to another screen that’s using a different scale
factor, the window instantly adjusts itself to display properly according to
that screen’s scale factor, with no blurriness or pixelation. It even works
when a window is partially on one screen and partially on another! (David
Edmundson, Frameworks 5.101. Link 1 and link 2)
```

This seems like it's similar. I will test if (or when) I get the chance to
update to 5.101.

-- 
You are receiving this mail because:
You are watching all bug changes.

[Spectacle] [Bug 453352] [Wayland] Undesired save to default folder

[Szymon Łągiewka]

https://bugs.kde.org/show_bug.cgi?id=453352

Szymon Łągiewka  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |FIXED
 Status|NEEDSINFO   |RESOLVED

--- Comment #2 from Szymon Łągiewka  ---
Updated my system to latest Fedora packages: frameworks 5.99, gear 22.08.1,
Plasma 5.25.5. 

Quick test and seems like this is working properly - screenshots are saved only
to the clipboard. 

I'm not using this PC much lately, so I will assume that this won't go rouge
again. Closing as resolved.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdeconnect] [Bug 458444] kdeconnect crash after click "making sound"

[Szymon Rutkowski]

https://bugs.kde.org/show_bug.cgi?id=458444

Szymon Rutkowski  changed:

   What|Removed |Added

 Resolution|--- |WAITINGFORINFO
 CC||sz.rutkow...@protonmail.ch
 Status|REPORTED|NEEDSINFO

--- Comment #1 from Szymon Rutkowski  ---
Hello, thanks for reporting. With "make sound", do you mean "Ring", the first
thing in the top-right '...' menu? I switched to English US on Android for a
moment to see what it's called, I don't know about the language you're using.

If this interpretation is correct, for what it's worth, I wasn't able to
reproduce it with an Asus Zenfone 6 and frameworks 5.97.0, Qt 5.15.5 and
kdeconnect 22.04.1-3 from the Fedora repo.

Does other stuff work, like moving the mouse cursor?

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 455684] The cursor was inverted and the selected region was above the cursor position in VMs with 3D acceleration enabled

[Szymon Łągiewka]

https://bugs.kde.org/show_bug.cgi?id=455684

--- Comment #7 from Szymon Łągiewka  ---
Updated my guest Fedora to 5.25.4. Host Arch still on 25.3. Issues seems
resolved with .4 - cursor is no longer flipped!

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 455684] The cursor was inverted and the selected region was above the cursor position in VMs with 3D acceleration enabled

[Szymon Łągiewka]

https://bugs.kde.org/show_bug.cgi?id=455684

--- Comment #5 from Szymon Łągiewka  ---
I can confirm the same issue. QEMU, KVM, virt manager and virgl.

Host: Arch Linux
Guests: Fedora 36, openSUSE Tumbleweed.

This didn't happen with Fedora when it was on 5.24. TW had 5.25 when I first
installed it.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 455684] The cursor was inverted and the selected region was above the cursor position in VMs with 3D acceleration enabled

[Szymon Łągiewka]

https://bugs.kde.org/show_bug.cgi?id=455684

--- Comment #4 from Szymon Łągiewka  ---
Created attachment 150624
  --> https://bugs.kde.org/attachment.cgi?id=150624=edit
openSUSE Tumbleweed, Plasma 5.25.2, virgl and reverted cursor

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 455684] The cursor was inverted and the selected region was above the cursor position in VMs with 3D acceleration enabled

[Szymon Łągiewka]

https://bugs.kde.org/show_bug.cgi?id=455684

Szymon Łągiewka  changed:

   What|Removed |Added

 CC||bugs-...@lagiewka.pl

--- Comment #3 from Szymon Łągiewka  ---
Created attachment 150623
  --> https://bugs.kde.org/attachment.cgi?id=150623=edit
Fedora 36, Plasma 5.25.3, virgl and reverted cursor

-- 
You are receiving this mail because:
You are watching all bug changes.

[Spectacle] [Bug 453352] New: [Wayland] Undesired save to default folder

[Szymon Łągiewka]

https://bugs.kde.org/show_bug.cgi?id=453352

Bug ID: 453352
   Summary: [Wayland] Undesired save to default folder
   Product: Spectacle
   Version: 22.04.0
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: General
  Assignee: m...@baloneygeek.com
  Reporter: bugs-...@lagiewka.pl
CC: k...@david-redondo.de
  Target Milestone: ---

Created attachment 148542
  --> https://bugs.kde.org/attachment.cgi?id=148542=edit
Undesired file on disk is confirmed

SUMMARY
When using a shortcut to capture rectangular region, a screenshot is saved both
to clipboard and as file. The option to save to a default folder is disabled.

My settings:
"Save file to default folder" off
After taking a screenshot: Copy image to clipboard

STEPS TO REPRODUCE
1.  Set "Save file to default folder" to off
2. Set "After taking a screenshot" to "Copy image to clipboard"
(possibly relog/reboot to make sure it applies properly)
3. Press meta+shift+prtscr
4. Select rectangular region

OBSERVED RESULT
1. Confirmation notification pops up for clipboard
1a. SS is indeed in clipboard
2. Confirmation notification pops up for file on disk 
2a. SS file is indeed in the default folder

EXPECTED RESULT
1. Confirmation notification pops up for clipboard
1a. SS is indeed in clipboard

SOFTWARE/OS VERSIONS
Operating System: Arch Linux
KDE Plasma Version: 5.24.5
KDE Frameworks Version: 5.93.0
Qt Version: 5.15.3
Kernel Version: 5.17.5-arch1-1 (64-bit)
Graphics Platform: Wayland
Processors: 12 × AMD Ryzen 5 5600X 6-Core Processor
Memory: 31.3 GiB of RAM
Graphics Processor: AMD Radeon RX 6600 XT

ADDITIONAL INFORMATION
I've seen https://bugs.kde.org/show_bug.cgi?id=433442, which is a reverse of my
issue. I just want the region to be in clipboard so I can forward it easily.
Files on disk are just polluting my folder.

Great to see 22.04 finally support shortcuts without Spectacle running, but
this file thing is just annoying.  

I've also observed things (I can't reproduce now) like:
a) clipboard not receiving the SS on the first try,
b) shortcut + region selection causing the opening of the Spectacle window,
saving to clipboard with no file present. That's also annoying since I don't
need that  window and need to close it manually. This might've been related to
some weird steps I did why writing this issue. I also updated to 5.24.5,
rebooted so there might've been something to that.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 358277] Chrome apps assuming same icon from chrome browser, in Icon-Only Task Manager

[Szymon Łągiewka]

https://bugs.kde.org/show_bug.cgi?id=358277

Szymon Łągiewka  changed:

   What|Removed |Added

 CC||bugs-...@lagiewka.pl

--- Comment #12 from Szymon Łągiewka  ---
My two pennies worth:

Just updated Chrome to v99. I use Ozone/Wayland backend. This release sets
proper Icons for Chrome apps for me. Tested with Spotify and Tidal. The icon is
also properly set for all effects presenting window with its icon visible, i.e.
the overview effect.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 432264] Wayland context Menus entries disappear/ graphic glitching

[Szymon Łągiewka]

https://bugs.kde.org/show_bug.cgi?id=432264

--- Comment #13 from Szymon Łągiewka  ---
Small update from me. Today I found out that when I open the context menu and
then press left alt (as for using hints etc) the context menu gets redrawn (?)
to make it all solid as expected.

Example: https://youtu.be/qJI0ezn-91Y

Hope this helps to point devs into right direction.

-- 
You are receiving this mail because:
You are watching all bug changes.

[okular] [Bug 450453] JavaScript filling other form fields in PDF not working

[Szymon Rutkowski]

https://bugs.kde.org/show_bug.cgi?id=450453

Szymon Rutkowski  changed:

   What|Removed |Added

Summary|Cannot fill out form fields |JavaScript filling other
   |correct |form fields in PDF not
   ||working
 CC||sz.rutkow...@protonmail.ch
 Ever confirmed|0   |1
 Status|REPORTED|CONFIRMED

--- Comment #1 from Szymon Rutkowski  ---
Hi, thanks for reporting.

The reporter expects the data entered into form fields in the pages 1-2 to be
automatically replicated on the subsequent pages (with different language
versions of the document). This works on the official Adobe reader, at least on
Windows.

This seems related to embedded JavaScript in the document. For example, the PDF
object number 297 contains the snippet
"event.value=this.getField("b4").value;", which (I assume) fills the field with
the value of another field and (I also assume) this is not executed.

Similar, not quite the same bugs:
https://bugs.kde.org/show_bug.cgi?id=271728
https://bugs.kde.org/show_bug.cgi?id=307304
https://bugs.kde.org/show_bug.cgi?id=403632
Older broad tickets about JS, I don't know about their current actual status:
https://bugs.kde.org/show_bug.cgi?id=223022
https://bugs.kde.org/show_bug.cgi?id=258941
https://bugs.kde.org/show_bug.cgi?id=306855

The example file(s) can be also downloaded from:
https://www.impots.gouv.fr/formulaire/5000-sd/attestation-de-residence-destinee-ladministration-etrangere

-- 
You are receiving this mail because:
You are watching all bug changes.

[ark] [Bug 450134] Opening an archive containing a directory with a name ending in ".." fails with an error message.

[Szymon Rutkowski]

https://bugs.kde.org/show_bug.cgi?id=450134

Szymon Rutkowski  changed:

   What|Removed |Added

 Status|REPORTED|CONFIRMED
Version|19.12.3 |20.12.2
 CC||sz.rutkow...@protonmail.ch
 Ever confirmed|0   |1

--- Comment #1 from Szymon Rutkowski  ---
Can confirm the issue on a newer version (20.12.2). The example file extracts
with no problem with "tar -xf test.tar", so it seems a reasonable expectation
that it would work.

Thanks for reporting. As you were able to find the likely cause in the code, be
aware that a submitting patch to Ark would probably be welcome:
https://community.kde.org/Get_Involved/development

-- 
You are receiving this mail because:
You are watching all bug changes.

[i18n] [Bug 449791] "KSqueezedTextLabel" shown instead of the mount point in Dolphin info window (Punjabi)

[Szymon Rutkowski]

https://bugs.kde.org/show_bug.cgi?id=449791

Szymon Rutkowski  changed:

   What|Removed |Added

Product|dolphin |i18n
Summary|Dolphin Mount Point Is  |"KSqueezedTextLabel" shown
   |Wrong   |instead of the mount point
   ||in Dolphin info window
   ||(Punjabi)
   Assignee|dolphin-bugs-n...@kde.org   |aa...@kde.org
  Component|view-engine: general|general
 CC||sz.rutkow...@protonmail.ch

--- Comment #1 from Szymon Rutkowski  ---
Hello, thanks for reporting.

I think it's clearly a localization issue. I've identified the language as
Punjabi (apologies if this is wrong) and edited the bug name. I'll try to
confirm it later after switching the language pack.

-- 
You are receiving this mail because:
You are watching all bug changes.

[marble] [Bug 449554] Marble "closed unexpectedly" although being closed by user

[Szymon Rutkowski]

https://bugs.kde.org/show_bug.cgi?id=449554

Szymon Rutkowski  changed:

   What|Removed |Added

 CC||sz.rutkow...@protonmail.ch
 Resolution|--- |WAITINGFORINFO
 Status|REPORTED|NEEDSINFO

--- Comment #1 from Szymon Rutkowski  ---
Hello, I have trouble reproducing this bug, though I have the same version of
the software (at least the ones you provided), on Fedora. I am assuming the
issue persists between OS restarts.

If you can, please open Konsole (or another terminal emulator), and run Marble
by writing "marble" and pressing enter. Then perform the steps you describe and
paste the output that appears in the terminal here. Hopefully some useful error
messages will appear.

(Alternatively, if you feel comfortable with this, you can also attempt to
retrieve the backtrace:
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
)

-- 
You are receiving this mail because:
You are watching all bug changes.

[okular] [Bug 449492] Trim margins: When navigating, document acts as if the margins are still present

[Szymon Rutkowski]

https://bugs.kde.org/show_bug.cgi?id=449492

Szymon Rutkowski  changed:

   What|Removed |Added

 Resolution|--- |NOT A BUG
 Status|REPORTED|RESOLVED

--- Comment #3 from Szymon Rutkowski  ---
Alright. This indeed looks like it might be something more involved but
different. Please create a separate bug ticket for convenience of the
maintainers (and also fill the Okular version in the form if you do).
Optionally you could investigate if something like this can happen in similar
circumstances in other KDE suite/Qt programs.

-- 
You are receiving this mail because:
You are watching all bug changes.

[okular] [Bug 449492] Trim margins: When navigating, document acts as if the margins are still present

[Szymon Rutkowski]

https://bugs.kde.org/show_bug.cgi?id=449492

Szymon Rutkowski  changed:

   What|Removed |Added

 Resolution|--- |WAITINGFORINFO
 CC||sz.rutkow...@protonmail.ch
 Status|REPORTED|NEEDSINFO

--- Comment #1 from Szymon Rutkowski  ---
Hello, thanks for reporting. On my end I can kind of reproduce the effect
you're seeing, but this is because the trimmed pages are actually of different
width each. The 6th and 8th page (possibly all the even ones?) seem to be the
widest. If I adjust the width to the widest page, the problem doesn't appear.
Can you confirm this isn't the case on your end?

For reference, I'm on Plasma version 5.22.5, framework 5.85.0, Qt 5.15.2.

-- 
You are receiving this mail because:
You are watching all bug changes.

[gwenview] [Bug 449642] Unable to set keyboard shortcut for Gwenview zooming to +/-

[Szymon Rutkowski]

https://bugs.kde.org/show_bug.cgi?id=449642

Szymon Rutkowski  changed:

   What|Removed |Added

 CC||sz.rutkow...@protonmail.ch

--- Comment #1 from Szymon Rutkowski  ---
Hello, thanks for reporting.

If you don't mind telling, can you confirm that you used the numpad keys (right
edge of the keyboard)? Just to be 100% sure that you don't use some keyboard
layout with other dedicated +/- keys that might be misinterpreted by OS.

Reports about problems with numpad shortcuts that seem to be related:
https://bugs.kde.org/show_bug.cgi?id=430126
https://bugs.kde.org/show_bug.cgi?id=433698 (possibly this is a duplicate of
that)

I'm not able to observe the behavior from #433698 that Alt-Tab'ing causes the
shortcut to be set. However, I noticed the behavior described by a comment at
#430126 that setting a shortcut to a non-numpad number works also with the
numpad one. Otherwise, can replicate. I am on X11, Plasma version 5.22.5,
Gwenview 21.04.1.

-- 
You are receiving this mail because:
You are watching all bug changes.

[Spectacle] [Bug 429390] Screenshot taken on Wayland via keyboard shortcuts is not copied to clipboard

[Szymon Łągiewka]

https://bugs.kde.org/show_bug.cgi?id=429390

Szymon Łągiewka  changed:

   What|Removed |Added

 CC||bugs-...@lagiewka.pl

--- Comment #19 from Szymon Łągiewka  ---
Didn't know this bug was already reported (and fixed!) until I've read Nate's
blog post. Great to see it finally fixed. Was bothering me ever since I've
started using Wayland. This feature is just to good to use other ways :) 

Backport would be awesome to have! 22.04 seems like it's going to be light
years away ;)

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 446948] Qt apps scaling breaks in multi-monitor setup with 90 degree rotation

[Szymon Łągiewka]

https://bugs.kde.org/show_bug.cgi?id=446948

--- Comment #2 from Szymon Łągiewka  ---
Sure. The outputs from 2> in the snippet:
https://invent.kde.org/-/snippets/2010

I've noticed that scaling doesn't break if I move the window directly to
another screen via Move to Screen (from title bar).

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 446894] Dragging maximised window does not un-maximise

[Szymon Łągiewka]

https://bugs.kde.org/show_bug.cgi?id=446894

--- Comment #2 from Szymon Łągiewka  ---
Yes. I will most likely turn it back on. It's just that I've turned it off
because I was trying to get this feature out of the way when using a 90 degree
rotated screen with 3-window stack (snapping in quarters is weird in this
rotation BTW) and decided to report back my impressions.

Never mind the resolution, I still think that it's weird UX to have that toggle
off resulting in windows staying maximised even though they're being dragged
far away from any screen edge. Or at least the title bar is away, other window
edges will obviosly still be touching screen edges since the window is the size
of the screen (minus panels).

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 446948] New: Qt apps scaling breaks in multi-monitor setup with 90 degree rotation

[Szymon Łągiewka]

https://bugs.kde.org/show_bug.cgi?id=446948

Bug ID: 446948
   Summary: Qt apps scaling breaks in multi-monitor setup with 90
degree rotation
   Product: kwin
   Version: 5.23.4
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: wayland-generic
  Assignee: kwin-bugs-n...@kde.org
  Reporter: bugs-...@lagiewka.pl
  Target Milestone: ---

Created attachment 144521
  --> https://bugs.kde.org/attachment.cgi?id=144521=edit
Screen arrangement

SUMMARY
When a scaled display is on the right of another display that is rotated 90
degrees anticlockwise, moving Qt-based apps between them will eventually break
scaling. 

See the attachment for the layout. Happens for both clockwise and
anticlockwise. I've first thought that it might have something to do with the
display's virtual "chin" being in the way (as is in the illustration), but this
is not the case when rotated the other way.  

STEPS TO REPRODUCE
1. Get two displays
2. Rotate the display on the left 90 degrees (anti)clockwise 
3. Scale the display on the right to 200%
4. Open a Qt app on left (100% scale) display 
5. Move the app to the right screen
6. Move the app to the left screen
7. Move the app to the right screen

1. Get two displays
2. Rotate the display on the left 90 degrees (anti)clockwise 
3. Scale the display on the right to 200%
4. Open a Qt app on right (200% scale) display 
5. Move the app to the left screen
6. Move the app to the right screen

OBSERVED RESULT
After each set of steps the Qt app will not keep the scale (will be blurry).

EXPECTED RESULT
Flipping windows back and forth between screens for hours doesn't break
scaling. Amazing. 

It's worth mentioning that this does not happen if the scaled display is on the
left. I have already filed a bug regarding context menu
(https://bugs.kde.org/show_bug.cgi?id=446563) which is subject to the same
layout rules, but is reproducible _without_ any rotation. If one of the
displays is scaled - things on the right display can break.

Tested with scaled display above and below - works. Only when on the right -
this happens.


SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Arch Linux
KDE Plasma Version: 5.23.4
KDE Frameworks Version: 5.88.0
Qt Version: 5.15.2+kde (KDE patches in main repos for some packages)

ADDITIONAL INFORMATION
This doesn't happen for non-Qt apps - Firefox, Electron (Ozone) and other Gtk
apps (I've tested Gnome's Files / Nautilus) work just fine. 

I've no idea whether this is Qt or KWin issue. The fact that this happens only
for certain screen arrangements makes me think this might be KWin as well.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 446563] Context menu flickering/redraw for mixed scale setup (Wayland)

[Szymon Łągiewka]

https://bugs.kde.org/show_bug.cgi?id=446563

--- Comment #4 from Szymon Łągiewka  ---
(In reply to Szymon Łągiewka from comment #3)
> If I drag any KDE app

Forgot to mention - this doesn't happen to Electron apps with Ozone and Firefox
running in native Wayland. They rescale normally.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 446563] Context menu flickering/redraw for mixed scale setup (Wayland)

[Szymon Łągiewka]

https://bugs.kde.org/show_bug.cgi?id=446563

--- Comment #3 from Szymon Łągiewka  ---
(In reply to justinkb from comment #2)
> I should add, if you rearrange the display layout so that the monitor where
> everything is fine is on the right, the bug occurs on the other monitor (the
> 200% scaled one).

Yup, I can observe the same thing. I've rearranged my desk since submitting
this bug and... Now I can say that the context menu is broken on the right
display that is scaled 200%. If I virtually rearrange them so that the scaled
one is back on the left - the issue is gone.

This might be connected with something else I just noticed. If I drag any KDE
app (i.e. KScreen KCM, Dolphin etc., so might be Qt thing...) to non-scaled
display and back to scaled one - scaling doesn't work. If I flip my displays to
be on opposite sides - scaling works when dragging across. I will submit a
separate bug report later today. But I get a feeling that these are connected.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 446894] New: Dragging maximised window does not un-maximise

[Szymon Łągiewka]

https://bugs.kde.org/show_bug.cgi?id=446894

Bug ID: 446894
   Summary: Dragging maximised window does not un-maximise
   Product: kwin
   Version: 5.23.4
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: wayland-generic
  Assignee: kwin-bugs-n...@kde.org
  Reporter: bugs-...@lagiewka.pl
  Target Milestone: ---

SUMMARY
When `Windows dragged to top edge` is off, grabbing the title bar and moving
the window around will not un-maximise it (as in - restore state from before it
was maximised).


STEPS TO REPRODUCE
1. Go to Screen Edges -> Maximise: Windows dragged to top edge - off
2. Maximise a window
3. Drag the window via its title bar (i.e. few inches below)

OBSERVED RESULT
Window stays maximised (w/o borders, shadows etc).

Since the window is in maxmised state still, dragging it to another display
will resize it to the size of that display. So will dragging it back to the
original display.

EXPECTED RESULT
Window should un-maximise (as it does when `Windows dragged to top edge` is
on).

Moving maximised window from one display to another may as well be expected to
keep the window maximised. That would be similar to how one can rearrange
fullscreen apps in multi-monitor setup in macOS. However, placing the window on
the same screen and still having it maximised is counter-intuitive.


SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Arch Linux
KDE Plasma Version: 5.23.4
KDE Frameworks Version: 5.88
Qt Version: 5.15.2

ADDITIONAL INFORMATION
I'm reporting this as wayland-generic. Might as well be the case in X11 -
haven't checked.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 445554] Trying to move the Panel crashes the whole desktop

[Szymon Łągiewka]

https://bugs.kde.org/show_bug.cgi?id=445554

Szymon Łągiewka  changed:

   What|Removed |Added

 CC||bugs-...@lagiewka.pl

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 446563] New: Context menu flickering/redraw for mixed scale setup (Wayland)

[Szymon Łągiewka]

https://bugs.kde.org/show_bug.cgi?id=446563

Bug ID: 446563
   Summary: Context menu flickering/redraw for mixed scale setup
(Wayland)
   Product: plasmashell
   Version: 5.23.4
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: bugs-...@lagiewka.pl
CC: plasma-b...@kde.org
  Target Milestone: 1.0

SUMMARY
I'm having context menu misbehave in my current mixed DPI setup. When a 4K
display (28", display 1, HDMI) has any scale applied and QHD display (27",
display 2, DisplayPort) has no scale applied, the context menus of Plasma are
not showing everything when opened, and show contents on mouse hover.

I've played around with different settings and I was almost convinced that this
will happen on a non-scaled display only. But after I tried the reverse (no
scale on display 1, scale on display 2) I still got this issue on display 2,
but not on display 1.

STEPS TO REPRODUCE
1. Scale display 1 to 200%
2. Scale display 2 to 100% (no scaling)
3. Try context menu on display 2 - will misbehave

1. Scale display 1 to 100% (no scaling)
2. Scale display 2 to 100% (no scaling)
3. Try context menu on either display - all will work correctly

1. Scale display 1 to 200%
2. Scale display 2 to 200% (or 150, 175% - any scale other than 100%)
3. Try context menu on either display - all will work correctly

1. Scale display 1 to 100% (no scaling)
2. Scale display 2 to 125% (or 150, etc.)
3. Try context menu on display 2 - will misbehave

OBSERVED RESULT
Context menu of plasmashell (on widgets, on desktop) flickers and redraws on
mouse hover.

Demonstration: https://youtu.be/--c3om5X3uE
Left screen is scaled 175%, same for 200%. 
Right is not scaled (100%).
Dolphin on right display - context menu is OK.

Applets and desktop context menu are being redrawn (?) and mostly incomplete on
the right screen.

EXPECTED RESULT
Context menu behaves as on the left screen.


SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Arch Linux with Plasma 5.23.4
KDE Plasma Version: 5.23.4
KDE Frameworks Version: 5.88.0
Qt Version: 5.15.2
GPU: AMD RX 550 / open source drivers

ADDITIONAL INFORMATION
Turing bless Plasma Wayland session. It's come a long way since I was first
trying it in 2017. Still some work to do, but right now I'm easily daily
driving it for a week or so.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 446431] Do not disturb reason is confusing (screen sharing)

[Szymon Łągiewka]

https://bugs.kde.org/show_bug.cgi?id=446431

Szymon Łągiewka  changed:

   What|Removed |Added

Summary|Do not disturb reason is|Do not disturb reason is
   |confusing   |confusing (screen sharing)

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 446431] Do not disturb reason is confusing

[Szymon Łągiewka]

https://bugs.kde.org/show_bug.cgi?id=446431

--- Comment #1 from Szymon Łągiewka  ---
Sorry, trying to send attachment with Enter sends the report prematurely.

I just noticed that when screen sharing a window or entire screen in Google
Meet in Firefox causes DND to show reason as `xdg-desktop-portal-kde`. This
will be confusing to any non-technical user. "What is this portal thing?"

I'm not familiar with CreateSession details, but is Firefox registering itself
as a portal? Or it's not, but the inhibition is using wrong description?

On another note: could "Screen sharing in progress" be mentioned first? As a
user I would prefer to have this first and then learn any details - which app,
which process etc. (that's form thinking about the target user ;) )

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 446431] New: Do not disturb reason is confusing

[Szymon Łągiewka]

https://bugs.kde.org/show_bug.cgi?id=446431

Bug ID: 446431
   Summary: Do not disturb reason is confusing
   Product: plasmashell
   Version: 5.23.4
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Severity: minor
  Priority: NOR
 Component: Notifications
  Assignee: k...@privat.broulik.de
  Reporter: bugs-...@lagiewka.pl
CC: plasma-b...@kde.org
  Target Milestone: 1.0

Created attachment 144175
  --> https://bugs.kde.org/attachment.cgi?id=144175=edit
dnd-from-portal

SUMMARY



STEPS TO REPRODUCE
1. 
2. 
3. 

OBSERVED RESULT


EXPECTED RESULT


SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION

-- 
You are receiving this mail because:
You are watching all bug changes.

[lattedock] [Bug 442648] Magic Lamp broken animation ( Wayland )

[Szymon]

https://bugs.kde.org/show_bug.cgi?id=442648

--- Comment #9 from Szymon  ---
Sorry for spam. But I have to add that the alternative animation to "Magic
Lamp" is "Squash" works fine.

The problem was seen on previous versions of latte or KDE, and only on Wayland
and only with the latte dock.

I've never reported it before. So it's definitely not the new version of latte
or KDE. Maybe the effect prescribed for Wayland has some drawbacks.

-- 
You are receiving this mail because:
You are watching all bug changes.

[lattedock] [Bug 442648] Magic Lamp broken animation ( Wayland )

[Szymon]

https://bugs.kde.org/show_bug.cgi?id=442648

--- Comment #8 from Szymon  ---
I can add that the animation looks like it wants to be collapsed from two
points. One goes to a latte dock, and the other to the lower left corner. Then
the animation window intersects.

-- 
You are receiving this mail because:
You are watching all bug changes.

[lattedock] [Bug 442648] Magic Lamp broken animation ( Wayland )

[Szymon]

https://bugs.kde.org/show_bug.cgi?id=442648

--- Comment #7 from Szymon  ---
Version : 0.10.2-1
the problem only occurs with the latte dock. 

When the latte dock is hidden by itself or through a window. The problem is
always there. Sometimes, when the system is turned on, it occurs even with the
visible mode. Then I have to switch the mode from "Always visible" to "dodge
active". Or vice versa.

I would have made a video, but I'm having trouble recording on Wayland.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 442649] Minimize all Windows function does not work in some cases ( mostly ) ( Wayland )

[Szymon]

https://bugs.kde.org/show_bug.cgi?id=442649

--- Comment #3 from Szymon  ---
Example :

Kata -> Dolphin -> Chromium -> Terminal.

The last application is a terminal, if the window activity indicates this
application, the function works correctly with other windows in the background.

If we switch the activity to, for example, Chromium, the function stops working
properly.

But if the terminal is minimized sooner, the Chromium becomes "correct". And
when the activity of the popup indicates chromium, it works fine with other
applications in the background.


To sum up: each newly turned on application is subject to the activity of
itself or the next one. Only then does the function work ( Wow ) .

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 442649] Minimize all Windows function does not work in some cases ( mostly ) ( Wayland )

[Szymon]

https://bugs.kde.org/show_bug.cgi?id=442649

--- Comment #2 from Szymon  ---
ok, i know what is wrong. The function works on the last started application. 

For example, if you turn on kate first and then dolphin. And on the active
dolphin window you can use the functions without any problem. When you change
activity to kate then the function will hide the popups but will not restore
them.

To sum up, the function works correctly only on the last opened application
(window). The problem always occurs with this combination.

By turning on more applications, the previous one that was compatible with the
function stops working. Rule of last run.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 442648] Magic Lamp broken animation ( Wayland )

[Szymon]

https://bugs.kde.org/show_bug.cgi?id=442648

--- Comment #3 from Szymon  ---
Ok do couple of test and problem appear when latte is on hide by some window or
by options "all ways hide". And I want alt+tab to some hidden window, Then
animation going crazy. (on x11 this works normally). I do even test with hidden
panel with active task manager, but works good. So this must be problem only
with latte and wayland.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 442648] Magic Lamp broken animation ( Wayland )

[Szymon]

https://bugs.kde.org/show_bug.cgi?id=442648

--- Comment #2 from Szymon  ---
Only on laptop screen with Intel HD graphics + latte Dock. Wayland platform.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kded-appmenu] [Bug 442646] Some applications do not export menus to the applet (Wayland)

[Szymon]

https://bugs.kde.org/show_bug.cgi?id=442646

Szymon  changed:

   What|Removed |Added

   Platform|Other   |Archlinux Packages

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 442649] New: Minimize all Windows function does not work in some cases ( mostly ) ( Wayland )

[Szymon]

https://bugs.kde.org/show_bug.cgi?id=442649

Bug ID: 442649
   Summary: Minimize all Windows function does not work in some
cases ( mostly ) ( Wayland )
   Product: kwin
   Version: 5.22.90
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: wayland-generic
  Assignee: kwin-bugs-n...@kde.org
  Reporter: szymondud...@gmail.com
  Target Milestone: ---

SUMMARY :
When we change the options "Show Desktop" to "Minimize all Windows" another
problem occurs ( Wayland only ) . Depending on what application is active (
window ) this function works as expected. But when we reshuffle the windows
activity , there is a problem.

STEPS TO REPRODUCE :
1. Launch the Dolphin and Kate applications. 
2. Make sure that the windows are visible on your screen. And then remember
which window was active. 
3. Use the Minimize all Windows function twice via shortcut or applet. 
4. If the windows are still active the second time, change the windows activity
to the other application and use the function twice again.

OBSERVED RESULT :
The windows hide, but after clicking again they do not show up. They are still
hidden and this function does not work until we manually restore the windows
one by one.

EXPECTED RESULT :
The windows should be restored from hiding. No matter the number or type.

SOFTWARE/OS VERSIONS

Linux/KDE Plasma: 5.14.5
(available in About System)
KDE Plasma Version: 5.22.90
KDE Frameworks Version: 5.86.0
Qt Version: 5.15.2

ADDITIONAL INFORMATION :
I am not quite sure if the function error itself occurs only when using it , or
for other reasons. However, if the problem does not appear, please use more
applications, and change their activity, surely it will appear.

The problem also occurs on stable versions of KDE, a long time.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 442648] New: Magic Lamp broken animation ( Wayland )

[Szymon]

https://bugs.kde.org/show_bug.cgi?id=442648

Bug ID: 442648
   Summary: Magic Lamp broken animation ( Wayland )
   Product: kwin
   Version: 5.22.90
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: platform-wayland
  Assignee: kwin-bugs-n...@kde.org
  Reporter: szymondud...@gmail.com
  Target Milestone: ---

SUMMARY
Minimization effects not working properly . The animation looks strange, it is
not a defined form. Complete disaster. 

STEPS TO REPRODUCE
1. Enable Magic Lamp effect
2. Minimize all Windows

OBSERVED RESULT
No problem with speed or performance. It is mainly about Animations. The
animation is not drawn into the icon but disappears next to the window,
sometimes nothing even happens.

EXPECTED RESULT
The animation should "pull in" the application window starting at the bottom of
the window.

SOFTWARE/OS VERSIONS

Linux/KDE Plasma: 5.14.5
(available in About System)
KDE Plasma Version: 5.22.90
KDE Frameworks Version: 5.86.0
Qt Version: 5.15.2

ADDITIONAL INFORMATION
The problem occurs on previous versions of KDE. 5.21, 5.22, etc.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kded-appmenu] [Bug 442646] New: Some applications do not export menus to the applet (Wayland)

[Szymon]

https://bugs.kde.org/show_bug.cgi?id=442646

Bug ID: 442646
   Summary: Some applications do not export menus to the applet
(Wayland)
   Product: kded-appmenu
   Version: 5.22.90
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: export
  Assignee: plasma-b...@kde.org
  Reporter: szymondud...@gmail.com
  Target Milestone: ---

SUMMARY
Some 3rd applications like : inkscape, sublime text, sublime merge and many
others doesn't work with globalmenu in Wayland platform. I think the problem is
due to the presence of GTK2. But I'm not able to verify that. Menus from GTK3
applications export normally.



STEPS TO REPRODUCE
1. Run KDE on Wayland Session
2. Make sure that Globalmenu applet is on Panel
3. Run Application like Inkscape, Sublime Text.

OBSERVED RESULT
All of the above mentioned applications run correctly on Xorg.


EXPECTED RESULT
Application menu on the panel.

SOFTWARE/OS VERSIONS

Linux/KDE Plasma: 5.14.5
(available in About System)
KDE Plasma Version: 5.22.90
KDE Frameworks Version: 5.86.0
Qt Version: 5.15.2

ADDITIONAL INFORMATION

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdeplasma-addons] [Bug 423104] [Wayland] Impossible to drag a widget from Dashboard and drop it on Desktop

[Szymon]

https://bugs.kde.org/show_bug.cgi?id=423104

Szymon  changed:

   What|Removed |Added

 CC||szymondud...@gmail.com

--- Comment #2 from Szymon  ---
The problem also occurs on the default system option "Application Launcher" (
Kickoff) .

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 442518] Screen corner activation stopped working for the "Desktop Grid" effect

[Szymon]

https://bugs.kde.org/show_bug.cgi?id=442518

Szymon  changed:

   What|Removed |Added

 CC||szymondud...@gmail.com

--- Comment #4 from Szymon  ---
I agree, the feature stopped working with version 5.23. On xorg as well as
wayland. The function itself works "correctly" via a shortcut. 

But, there is a problem with "drawing" windows, they are cut, virtual desktops
also. I also noticed a delay when restoring to the desktop. A general
performance problem. Sometimes I have to switch the virtual desktop just to
"unlock" the desktop restore.

KDE : 5.23
Frameworks : 5.86
QT Version : 5.12.2
Linux : 5.14.5
Distro : Arch
Graphics Platform : Wayland & Xorg.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 440751] Opened windows are not getting drawn when 'Show Desktop' is abused in a loop

[Szymon]

https://bugs.kde.org/show_bug.cgi?id=440751

Szymon  changed:

   What|Removed |Added

 CC||szymondud...@gmail.com
   Platform|Other   |Archlinux Packages
Version|5.22.4  |5.22.90

--- Comment #6 from Szymon  ---
When we change the options "Show Desktop" to "Minimize all Windows" another
problem occurs ( Wayland only ) . Depending on what application is active (
window ) this function works as expected. But when we reshuffle the windows
activity , there is a problem.

Description of the Problem : The windows hide, but after clicking again they do
not show up. They are still hidden and this function does not work until we
manually restore the windows one by one.

Opening the Problem : Launch the Dolphin and Kate applications. Make sure that
the windows are visible on your screen. And then remember which window was
active. Use the Minimize all Windows function twice via shortcut or applet. If
the windows are still active the second time, change the windows activity to
the other application and use the function twice again.

PS. I am not quite sure if the function error itself occurs only when using it
, or for other reasons. However, if the problem does not appear, please use
more applications, and change their activity, surely it will appear.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kate] [Bug 425057] When the KDE global theme is Dark Breeze, Kate shows black text on a black background

[Szymon]

https://bugs.kde.org/show_bug.cgi?id=425057

Szymon  changed:

   What|Removed |Added

 CC||kuszek...@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[kopete] [Bug 189815] text in kopete chat input box often switches to black on black background and then can't be switched back

[Szymon]

https://bugs.kde.org/show_bug.cgi?id=189815

Szymon  changed:

   What|Removed |Added

 CC||kuszek...@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kio] [Bug 430374] Dolphin crashed in KIO::RenameDialog::applyAllPressed() while moving and merging folders

[Szymon Kosecki]

https://bugs.kde.org/show_bug.cgi?id=430374

--- Comment #22 from Szymon Kosecki  ---
(In reply to ESSAM BENTALEB from comment #21)
> I have the same problem, trying to overwrite files and folders, crashes as
> soon as I tick apply to all. 
> I'm using OpenSuse tumbleweed, and its up to date.

It has been fixed in arch but they (In reply to Ismael Asensio from comment
#20)
> Git commit 9dc9e26b9196111eeacb5609b36957f74f5a14c4 by Ismael Asensio.
> Committed on 22/12/2020 at 21:29.
> Pushed by ngraham into branch 'master'.
> 
> RenameDialog: Add missing nullptr initialization
> 
> It fixes a crash when pressing `Apply to All` in those cases where
> the action was not present, as the code checks for nullptr
> FIXED-IN: 5.78
> 
> M  +1-0src/widgets/renamedialog.cpp
> 
> https://invent.kde.org/frameworks/kio/commit/
> 9dc9e26b9196111eeacb5609b36957f74f5a14c4

Thank you very much! new arch Kio package released following your fix resolves
the issue for me. Quality fix!

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kio] [Bug 430374] Dolphin crashed in KIO::RenameDialog::applyAllPressed() while moving and merging folders

[Szymon Kosecki]

https://bugs.kde.org/show_bug.cgi?id=430374

Szymon Kosecki  changed:

   What|Removed |Added

 CC||skose...@gmail.com

--- Comment #15 from Szymon Kosecki  ---
I am seeing the same behaviourwhen moving/copying files in Dolphin or Krusader.
As soon as "Apply to all" is clicked, the app initiating the operation will
crash. - Running on Arch linux and up to date.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 377280] plasma crash on startup with external monitor connected

[Szymon Janc]

https://bugs.kde.org/show_bug.cgi?id=377280

Szymon Janc  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |FIXED
 Status|NEEDSINFO   |RESOLVED

--- Comment #15 from Szymon Janc  ---
I can confirm that this is no longer the case

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 386437] plasma crashes on startup

[Szymon Janc]

https://bugs.kde.org/show_bug.cgi?id=386437

Szymon Janc  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|WAITINGFORINFO  |FIXED

--- Comment #3 from Szymon Janc  ---
I've not seen those crashes for some time so it seems to be fixed

-- 
You are receiving this mail because:
You are watching all bug changes.

[yakuake] [Bug 415762] Exiting the session in a Yakuake tab sometimes crash Yakuake

[Szymon Szypulski]

https://bugs.kde.org/show_bug.cgi?id=415762

Szymon Szypulski  changed:

   What|Removed |Added

 CC||s...@gen2.org

-- 
You are receiving this mail because:
You are watching all bug changes.

[dolphin] [Bug 417854] Dolphin or KFind Search Problem (Can't See Files)

[Szymon]

https://bugs.kde.org/show_bug.cgi?id=417854

--- Comment #1 from Szymon  ---
Edit : Search those files work on hidden folder.. Can't even work right know.
So many files to research ...

-- 
You are receiving this mail because:
You are watching all bug changes.

[dolphin] [Bug 417854] New: Dolphin or KFind Search Problem (Can't See Files)

[Szymon]

https://bugs.kde.org/show_bug.cgi?id=417854

Bug ID: 417854
   Summary: Dolphin or KFind Search Problem (Can't See Files)
   Product: dolphin
   Version: 19.12.2
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: search
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: szymondud...@gmail.com
CC: kfm-de...@kde.org
  Target Milestone: ---

Created attachment 126150
  --> https://bugs.kde.org/attachment.cgi?id=126150=edit
LEFT : ./config/48 && RIGHT : /home/48 && KFind : ./config/48 . (Dirs where
find function working on)

SUMMARY
Search in Dolphin (HOME FOLDER) + This EXTRA(TOOLBAR/BAR(NEW FEATURES?)) with
the type of this file... don't work. If i Use function outside HOME folder (all
hidden folder in HOME and root folder this "EXTRA TOOLBAR" toolbar gone and my
Search function work as well. 


STEPS TO REPRODUCE
1. Open Dolphin in Home Folder.
2. use Search of CTRL+F (Search File)
3. And write in my case symbolic / link file.

Don't work on my HOME folder, but for example if i put those folder in .config
then it's work normally . Anyway if i use Find function in Dolphin(HOME FOLDER)
i see new search bar (TYPE FILE,DATE,RATING). When i go to .config folder i
don't see again this bar/toolbar when i use Search function.

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 5.5.4
(available in About System)
KDE Plasma Version: 5.18.1
KDE Frameworks Version: 5.67
Qt Version: 5.14.1

ADDITIONAL INFORMATION
In my opinion if this new feature it's implementation of KFind then KFind it's
the problem, why? cuz only KFIND don't see any files in both places.

-- 
You are receiving this mail because:
You are watching all bug changes.

[klipper] [Bug 417729] Can't paste correctly if history is limited to 1 entry

[Szymon Szypulski]

https://bugs.kde.org/show_bug.cgi?id=417729

Szymon Szypulski  changed:

   What|Removed |Added

 CC||s...@gen2.org

-- 
You are receiving this mail because:
You are watching all bug changes.

[ksmserver] [Bug 381045] Logout greeter gets title bar and breaks background view

[Szymon Łągiewka]

https://bugs.kde.org/show_bug.cgi?id=381045

--- Comment #12 from Szymon Łągiewka  ---
(In reply to Nate Graham from comment #11)
> Is anyone still seeing this with Plasma 5.17 or the upcoming 5.18?

Quick check (I don't use scaling anymore) on Plasma 5.17.5 and Qt 5.14.1 -
everything works great with no artifacts as there were in 5.10.

Feel free to resolve or wait for others to report.

-- 
You are receiving this mail because:
You are watching all bug changes.

[Akonadi] [Bug 386985] akonadi CalDav resource not synching with certain servers

[szymon . pysz]

https://bugs.kde.org/show_bug.cgi?id=386985

szymon.p...@gmail.com  changed:

   What|Removed |Added

 CC||szymon.p...@gmail.com

--- Comment #39 from szymon.p...@gmail.com  ---
Hi,

Today, in the morning I updated kio from version 5.63 to 5.64. 
Problem solved, in my case of course.

Regards,
Simon

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 377308] Notifications from disconnected display appear on primary display

[Szymon Łągiewka]

https://bugs.kde.org/show_bug.cgi?id=377308

Szymon Łągiewka  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |---
 Status|NEEDSINFO   |REPORTED

--- Comment #4 from Szymon Łągiewka  ---
Setting REPORTED the Janitor asked.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 377308] Notifications from disconnected display appear on primary display

[Szymon Łągiewka]

https://bugs.kde.org/show_bug.cgi?id=377308

--- Comment #2 from Szymon Łągiewka  ---
(In reply to Germano Massullo from comment #1)
> Is this bug still happening on newer Plasma versions?

Hey Germano,

Currently I'm not using KDE extensively and this hardware setup has also
changed.

Please mark this as resolved if there are no other cases like this.

-- 
You are receiving this mail because:
You are watching all bug changes.

[krunner] [Bug 412386] New: Krunner crashed when selecten open window

[Szymon Uglis]

https://bugs.kde.org/show_bug.cgi?id=412386

Bug ID: 412386
   Summary: Krunner crashed when selecten open window
   Product: krunner
   Version: 5.16.90
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@privat.broulik.de
  Reporter: szymon.ug...@hotmail.com
  Target Milestone: ---

Application: krunner (5.16.90)

Qt Version: 5.13.1
Frameworks Version: 5.62.0
Operating System: Linux 5.3.1-arch1-1-ARCH x86_64
Distribution: "Arch Linux"

-- Information about the crash:
- What I was doing when the application crashed:
I was reading website in Firefox and my song in spotify changed so I opened
krunner and searched for spotify then selected spotify under open windows
section.

After selecting entry in krunner from `windows` section, nothing happens, then
after about 5 secs notification appears that says that krunner crashed.

The crash can be reproduced every time.

-- Backtrace (Reduced):
#6  0x7f4fa3d8e8bb in KWindowInfo::KWindowInfo(KWindowInfo const&) () at
/usr/lib/libKF5WindowSystem.so.5
#7  0x7f4f9751088f in  () at /usr/lib/qt/plugins/krunner_windows.so
#8  0x7f4f8ee1b0f1 in Plasma::RunnerContext::run(Plasma::QueryMatch const&)
() at /usr/lib/libKF5Runner.so.5
#9  0x7f4f8ee207a7 in Plasma::RunnerManager::run(Plasma::QueryMatch const&)
() at /usr/lib/libKF5Runner.so.5
#10 0x7f4f8ee8e173 in  () at /usr/lib/libmilou.so.5


The reporter indicates this bug may be a duplicate of or related to bug 412109.

Possible duplicates by query: bug 412381, bug 412300, bug 412296, bug 412218,
bug 412123.

Reported using DrKonqi

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 409715] New: KWin crash

[Szymon]

https://bugs.kde.org/show_bug.cgi?id=409715

Bug ID: 409715
   Summary: KWin crash
   Product: kwin
   Version: 5.16.3
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: szymondud...@gmail.com
  Target Milestone: ---

Application: kwin_x11 (5.16.3)

Qt Version: 5.13.0
Frameworks Version: 5.59.0
Operating System: Linux 5.2.0-arch2-1-ARCH x86_64
Distribution: "Arch Linux"

-- Information about the crash:
After Alt + Tab ->  Show All Applications . KWin crashing sometimes in this
combination.

The crash can be reproduced sometimes.

-- Backtrace:
Application: KWin (kwin_x11), signal: Segmentation fault
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f5aa6675880 (LWP 1247))]

Thread 7 (Thread 0x7f59fbfff700 (LWP 7179)):
#0  0x7f5aa8499756 in ppoll () at /usr/lib/libc.so.6
#1  0x7f5aa6fbb913 in qt_safe_poll(pollfd*, unsigned long, timespec const*)
() at /usr/lib/libQt5Core.so.5
#2  0x7f5aa6fbcfa3 in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#3  0x7f5aa6f665ec in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#4  0x7f5aa6d992f5 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#5  0x7f5aa54288f9 in  () at /usr/lib/libQt5Qml.so.5
#6  0x7f5aa6d9a520 in  () at /usr/lib/libQt5Core.so.5
#7  0x7f5aa5ca957f in start_thread () at /usr/lib/libpthread.so.0
#8  0x7f5aa84a40e3 in clone () at /usr/lib/libc.so.6

Thread 6 (Thread 0x7f5a87e7f700 (LWP 4490)):
#0  0x7f5aa8499756 in ppoll () at /usr/lib/libc.so.6
#1  0x7f5aa6fbb913 in qt_safe_poll(pollfd*, unsigned long, timespec const*)
() at /usr/lib/libQt5Core.so.5
#2  0x7f5aa6fbcfa3 in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#3  0x7f5aa6f665ec in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#4  0x7f5aa6d992f5 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#5  0x7f5aa6d9a520 in  () at /usr/lib/libQt5Core.so.5
#6  0x7f5aa5ca957f in start_thread () at /usr/lib/libpthread.so.0
#7  0x7f5aa84a40e3 in clone () at /usr/lib/libc.so.6

Thread 5 (Thread 0x7f5a9cfb7700 (LWP 2940)):
#0  0x7f5aa5caf415 in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f5aa6da05a0 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at
/usr/lib/libQt5Core.so.5
#2  0x7f5aa6da0692 in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#3  0x7f5aa57c77bd in  () at /usr/lib/libQt5Quick.so.5
#4  0x7f5aa57c7a6e in  () at /usr/lib/libQt5Quick.so.5
#5  0x7f5aa6d9a520 in  () at /usr/lib/libQt5Core.so.5
#6  0x7f5aa5ca957f in start_thread () at /usr/lib/libpthread.so.0
#7  0x7f5aa84a40e3 in clone () at /usr/lib/libc.so.6

Thread 4 (Thread 0x7f5a8767e700 (LWP 1441)):
#0  0x7f5aa5caf415 in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f5aa6808edc in  () at /usr/lib/libQt5Script.so.5
#2  0x7f5aa6808ef9 in  () at /usr/lib/libQt5Script.so.5
#3  0x7f5aa5ca957f in start_thread () at /usr/lib/libpthread.so.0
#4  0x7f5aa84a40e3 in clone () at /usr/lib/libc.so.6

Thread 3 (Thread 0x7f5a8700 (LWP 1361)):
#0  0x7f5aa8499756 in ppoll () at /usr/lib/libc.so.6
#1  0x7f5aa6fbb913 in qt_safe_poll(pollfd*, unsigned long, timespec const*)
() at /usr/lib/libQt5Core.so.5
#2  0x7f5aa6fbcfa3 in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#3  0x7f5aa6f665ec in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#4  0x7f5aa6d992f5 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#5  0x7f5aa54288f9 in  () at /usr/lib/libQt5Qml.so.5
#6  0x7f5aa6d9a520 in  () at /usr/lib/libQt5Core.so.5
#7  0x7f5aa5ca957f in start_thread () at /usr/lib/libpthread.so.0
#8  0x7f5aa84a40e3 in clone () at /usr/lib/libc.so.6

Thread 2 (Thread 0x7f5a9e1cf700 (LWP 1309)):
#0  0x7f5aa8499756 in ppoll () at /usr/lib/libc.so.6
#1  0x7f5aa6fbb913 in qt_safe_poll(pollfd*, unsigned long, timespec const*)
() at /usr/lib/libQt5Core.so.5
#2  0x7f5aa6fbcfa3 in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#3  0x7f5aa6f665ec in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#4  0x7f5aa6d992f5 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#5  0x7f5aa4e45b37 in  () at /usr/lib/libQt5DBus.so.5
#6  0x7f5aa6d9a520 in  () at /usr/lib/libQt5Core.so.5
#7  0x7f5aa5ca957f in start_thread () at /usr/lib/libpthread.so.0
#8  0x7f5aa84a40e3 in clone () at /usr/lib/libc.so.6

Thread 1 (Thread 0x7f5aa6675880 (LWP 1247)):
[KCrash Handler]
#6  0x55eb170c6630 in  ()
#7  0x7f5aa81b0d22 in KWin::Workspace::workspaceEvent(xcb_generic_event_t*)
() at /usr/lib/libkwin.so.5
#8  

[korganizer] [Bug 395540] Wrong shown events which end in the next day (UTC timezone)

[szymon . pysz]

https://bugs.kde.org/show_bug.cgi?id=395540

szymon.p...@gmail.com  changed:

   What|Removed |Added

Version|5.8.1   |unspecified

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 401729] Kwin Crash [ When Show All Application ] [ CTRL + F9 ]

[Szymon]

https://bugs.kde.org/show_bug.cgi?id=401729

--- Comment #2 from Szymon  ---
Sorry I can't do this... My system just broken by disable "baloo" by baloo
disable / reboot. Now I can't any login to system / write any file on system
cuz it's "readable only" . Sad …. Anyway Baloo indexing working so bad….

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 401729] New: Kwin Crash [ When Show All Application ] [ CTRL + F9 ]

[Szymon]

https://bugs.kde.org/show_bug.cgi?id=401729

Bug ID: 401729
   Summary: Kwin Crash [ When Show All Application ] [ CTRL + F9 ]
   Product: kwin
   Version: 5.14.4
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: szymondud...@gmail.com
  Target Milestone: ---

Application: kwin_x11 (5.14.4)

Qt Version: 5.11.2
Frameworks Version: 5.52.0
Operating System: Linux 4.19.4-arch1-1-ARCH x86_64
Distribution (Platform): Archlinux Packages

-- Information about the crash:
- What I was doing when the application crashed:

Present Windows - That Effect Sometimes Crash KWin. Not All The Time, but even
if i change my graphics settings and using default ... it's still the same
problem. I think mostly problem with KWIN it's beacuse of Nvidia Drivers. For
example on Nouveau i don't have any Crash on Kwin. But on nvidia it's normal...
When i open , move , minimalize , show window I got KWin crash'es random. 
Mostly it's beacuse of "Window" interaction. On nouveau i don't see any
problem...

The crash can be reproduced sometimes.

-- Backtrace:
Application: KWin (kwin_x11), signal: Segmentation fault
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f83f92cb840 (LWP 2319))]

Thread 7 (Thread 0x7f83dbfff700 (LWP 14261)):
#0  0x7f83f811dafc in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f83f939471c in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7f83f7c6e7ed in  () at /usr/lib/libQt5Quick.so.5
#3  0x7f83f7c6ea5c in  () at /usr/lib/libQt5Quick.so.5
#4  0x7f83f9393f65 in  () at /usr/lib/libQt5Core.so.5
#5  0x7f83f8117a9d in start_thread () at /usr/lib/libpthread.so.0
#6  0x7f83fa9cbb23 in clone () at /usr/lib/libc.so.6

Thread 6 (Thread 0x7f83ea39f700 (LWP 14260)):
#0  0x7f83fa9c0d16 in ppoll () at /usr/lib/libc.so.6
#1  0x7f83f9590e9b in qt_safe_poll(pollfd*, unsigned long, timespec const*)
() at /usr/lib/libQt5Core.so.5
#2  0x7f83f959238b in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#3  0x7f83f95408cc in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#4  0x7f83f9389eb9 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#5  0x7f83f7933859 in  () at /usr/lib/libQt5Qml.so.5
#6  0x7f83f9393f65 in  () at /usr/lib/libQt5Core.so.5
#7  0x7f83f8117a9d in start_thread () at /usr/lib/libpthread.so.0
#8  0x7f83fa9cbb23 in clone () at /usr/lib/libc.so.6

Thread 5 (Thread 0x7f83d8fa7700 (LWP 15703)):
#0  0x7f83f811dafc in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f83f939471c in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7f83f7c6e7ed in  () at /usr/lib/libQt5Quick.so.5
#3  0x7f83f7c6ea5c in  () at /usr/lib/libQt5Quick.so.5
#4  0x7f83f9393f65 in  () at /usr/lib/libQt5Core.so.5
#5  0x7f83f8117a9d in start_thread () at /usr/lib/libpthread.so.0
#6  0x7f83fa9cbb23 in clone () at /usr/lib/libc.so.6

Thread 4 (Thread 0x7f83d3fff700 (LWP 2709)):
#0  0x7f83f811dafc in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f83f8e6920c in  () at /usr/lib/libQt5Script.so.5
#2  0x7f83f8e69229 in  () at /usr/lib/libQt5Script.so.5
#3  0x7f83f8117a9d in start_thread () at /usr/lib/libpthread.so.0
#4  0x7f83fa9cbb23 in clone () at /usr/lib/libc.so.6

Thread 3 (Thread 0x7f83e95cf700 (LWP 2571)):
#0  0x7f83fa9c0d16 in ppoll () at /usr/lib/libc.so.6
#1  0x7f83f9590e9b in qt_safe_poll(pollfd*, unsigned long, timespec const*)
() at /usr/lib/libQt5Core.so.5
#2  0x7f83f959238b in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#3  0x7f83f95408cc in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#4  0x7f83f9389eb9 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#5  0x7f83f7933859 in  () at /usr/lib/libQt5Qml.so.5
#6  0x7f83f9393f65 in  () at /usr/lib/libQt5Core.so.5
#7  0x7f83f8117a9d in start_thread () at /usr/lib/libpthread.so.0
#8  0x7f83fa9cbb23 in clone () at /usr/lib/libc.so.6

Thread 2 (Thread 0x7f83eb5b7700 (LWP 2462)):
#0  0x7f83fa9c0d16 in ppoll () at /usr/lib/libc.so.6
#1  0x7f83f9590e9b in qt_safe_poll(pollfd*, unsigned long, timespec const*)
() at /usr/lib/libQt5Core.so.5
#2  0x7f83f959238b in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#3  0x7f83f95408cc in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#4  0x7f83f9389eb9 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#5  0x7f83f73ecba6 in  () at /usr/lib/libQt5DBus.so.5
#6  0x7f83f9393f65 in  () at /usr/lib/libQt5Core.so.5
#7  0x7f83f8117a9d in start_thread () at 

[systemsettings] [Bug 401002] New: Crash when adding gtk theme manually

[Szymon Żebrowski]

https://bugs.kde.org/show_bug.cgi?id=401002

Bug ID: 401002
   Summary: Crash when adding gtk theme manually
   Product: systemsettings
   Version: unspecified
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: szymon.zebrowsk...@gmail.com
  Target Milestone: ---

Application: systemsettings5 (5.14.3)

Qt Version: 5.11.2
Frameworks Version: 5.51.0
Operating System: Linux 4.18.16-arch1-1-ARCH x86_64
Distribution (Platform): Archlinux Packages

-- Information about the crash:
- What I was doing when the application crashed:

I tried to add manually this: https://store.kde.org/p/1160290 theme, and when i
choosed *.tar.gz archive system settings crashed.

The crash can be reproduced every time.

-- Backtrace:
Application: Ustawienia systemowe (systemsettings5), signal: Segmentation fault
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f5e592b3cc0 (LWP 2246))]

Thread 5 (Thread 0x7f5e4d5e0700 (LWP 2327)):
#0  0x7f5e5c6df6cb in g_main_context_prepare () at
/usr/lib/libglib-2.0.so.0
#1  0x7f5e5c6dfe06 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7f5e5c6dffce in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#3  0x7f5e5f044fe4 in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#4  0x7f5e5eff08cc in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#5  0x7f5e5ee39eb9 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#6  0x7f5e5e254859 in  () at /usr/lib/libQt5Qml.so.5
#7  0x7f5e5ee43f65 in  () at /usr/lib/libQt5Core.so.5
#8  0x7f5e5d3d0a9d in start_thread () at /usr/lib/libpthread.so.0
#9  0x7f5e5eb28b23 in clone () at /usr/lib/libc.so.6

Thread 4 (Thread 0x7f5e4ec36700 (LWP 2324)):
#0  0x7f5e5c68e3a9 in g_mutex_lock () at /usr/lib/libglib-2.0.so.0
#1  0x7f5e5c6dfec5 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7f5e5c6dffce in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#3  0x7f5e5f044fe4 in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#4  0x7f5e5eff08cc in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#5  0x7f5e5ee39eb9 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#6  0x7f5e5e254859 in  () at /usr/lib/libQt5Qml.so.5
#7  0x7f5e5ee43f65 in  () at /usr/lib/libQt5Core.so.5
#8  0x7f5e5d3d0a9d in start_thread () at /usr/lib/libpthread.so.0
#9  0x7f5e5eb28b23 in clone () at /usr/lib/libc.so.6

Thread 3 (Thread 0x7f5e4f5d3700 (LWP 2322)):
#0  0x7f5e5d3d6afc in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f5e4f8221ac in  () at /usr/lib/dri/i965_dri.so
#2  0x7f5e4f821ee8 in  () at /usr/lib/dri/i965_dri.so
#3  0x7f5e5d3d0a9d in start_thread () at /usr/lib/libpthread.so.0
#4  0x7f5e5eb28b23 in clone () at /usr/lib/libc.so.6

Thread 2 (Thread 0x7f5e55c73700 (LWP 2303)):
#0  0x7f5e5c68e3a9 in g_mutex_lock () at /usr/lib/libglib-2.0.so.0
#1  0x7f5e5c6df7b7 in g_main_context_prepare () at
/usr/lib/libglib-2.0.so.0
#2  0x7f5e5c6dfe06 in  () at /usr/lib/libglib-2.0.so.0
#3  0x7f5e5c6dffce in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#4  0x7f5e5f044fe4 in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#5  0x7f5e5eff08cc in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#6  0x7f5e5ee39eb9 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#7  0x7f5e5f296ba6 in  () at /usr/lib/libQt5DBus.so.5
#8  0x7f5e5ee43f65 in  () at /usr/lib/libQt5Core.so.5
#9  0x7f5e5d3d0a9d in start_thread () at /usr/lib/libpthread.so.0
#10 0x7f5e5eb28b23 in clone () at /usr/lib/libc.so.6

Thread 1 (Thread 0x7f5e592b3cc0 (LWP 2246)):
[KCrash Handler]
#6  0x7f5e4c048cbc in  () at /usr/lib/qt/plugins/kcm_kdegtkconfig.so
#7  0x7f5e4c054b75 in  () at /usr/lib/qt/plugins/kcm_kdegtkconfig.so
#8  0x7f5e5f01bbd0 in QMetaObject::activate(QObject*, int, int, void**) ()
at /usr/lib/libQt5Core.so.5
#9  0x7f5e5e958133 in KUrlRequester::textChanged(QString const&) () at
/usr/lib/libKF5KIOWidgets.so.5
#10 0x7f5e5f01bbd0 in QMetaObject::activate(QObject*, int, int, void**) ()
at /usr/lib/libQt5Core.so.5
#11 0x7f5e5fb36b63 in QLineEdit::textChanged(QString const&) () at
/usr/lib/libQt5Widgets.so.5
#12 0x7f5e5fb3d71a in  () at /usr/lib/libQt5Widgets.so.5
#13 0x7f5e5f01ba7c in QMetaObject::activate(QObject*, int, int, void**) ()
at /usr/lib/libQt5Core.so.5
#14 0x7f5e5fb3e2f6 in QWidgetLineControl::textChanged(QString const&) () at
/usr/lib/libQt5Widgets.so.5
#15 0x7f5e5fb41760 in QWidgetLineControl::finishChange(int, bool, bool) ()
at /usr/lib/libQt5Widgets.so.5
#16 0x7f5e5fb41a97 in QWidgetLineControl::internalSetText(QString const&,
int, 

[kwin] [Bug 381040] Spectacle does not capture every desktop

[Szymon Łągiewka]

https://bugs.kde.org/show_bug.cgi?id=381040

--- Comment #3 from Szymon Łągiewka  ---
I have not been testing Plasma on Wayland for quite some time now and I don't
have a multi display setup to test anymore.

You can resolve the issue if you need to.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 351055] Icons are upscaled in "Large Icons" Task Switcher because KWin gets icons from the window rather than the window's application's desktop file

[Szymon]

https://bugs.kde.org/show_bug.cgi?id=351055

Szymon  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
 Resolution|--- |INVALID

--- Comment #50 from Szymon  ---
I managed to fix this error. But this is rather a mistake of my configuration.
I was guided by the name of the .desktop shortcut from the Application Menu
(Edit). However, I went to the path of the. Font file and it was named without
space. It just worked, I'm sorry for unnecessary comments. Everything works as
it should.

-- 
You are receiving this mail because:
You are watching all bug changes.

[korganizer] [Bug 395540] Wrong shown events which end in the next day (UTC timezone)

[szymon . pysz]

https://bugs.kde.org/show_bug.cgi?id=395540

szymon.p...@gmail.com  changed:

   What|Removed |Added

 CC||szymon.p...@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 351055] Icons are upscaled in "Large Icons" Task Switcher because KWin gets icons from the window rather than the window's application's desktop file

[Szymon]

https://bugs.kde.org/show_bug.cgi?id=351055

--- Comment #49 from Szymon  ---
Window Rule don't work for Nvidia Settings / Gravit Designer.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 351055] Icons are upscaled in "Large Icons" Task Switcher because KWin gets icons from the window rather than the window's application's desktop file

[Szymon]

https://bugs.kde.org/show_bug.cgi?id=351055

Szymon  changed:

   What|Removed |Added

 CC||szymondud...@gmail.com

--- Comment #48 from Szymon  ---
Hi, i found new icons to fix, PhpStorm (probably all Jet Brains Apps) and
Gravit Designer . And some WINE apps . It's only one problem icon isn't changed
by .desktop file. On task bar working good as well but on Task Switcher apps
have old / small pix elated icon. I try all possible ways to change that icons
without success.  Funny cuz on Gnome DE my .desktop file working good. Tested
on Xorg / KWayland.

-- 
You are receiving this mail because:
You are watching all bug changes.

[korganizer] [Bug 395540] New: Wrong shown events which end in the next day (UTC timezone)

[szymon . pysz]

https://bugs.kde.org/show_bug.cgi?id=395540

Bug ID: 395540
   Summary: Wrong shown events which end in the next day (UTC
timezone)
   Product: korganizer
   Version: 5.8.1
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: grave
  Priority: NOR
 Component: journalview
  Assignee: kdepim-b...@kde.org
  Reporter: szymon.p...@gmail.com
  Target Milestone: ---

Created attachment 113399
  --> https://bugs.kde.org/attachment.cgi?id=113399=edit
Events view

Dear KDE Developers,

If I add new event in my calendar (caldav) which starts in one day and stops
next day (ex. start 6PM and end 2AM) and if I use UTC timezone the event on
calendar looks like as event which takes one hour - very shortly.

Please noticed that this bug appears only if system timezone is different than
UTC.
Normally if I add an new event with the same timezone as systems everything is
fine.

The event looks like on the screenshot. 

Similar bug which was reported by me: #353531

Many thanks,
Simon

-- 
You are receiving this mail because:
You are watching all bug changes.

[korganizer] [Bug 353531] Wrong shown events that end the next day.

[szymon . pysz]

https://bugs.kde.org/show_bug.cgi?id=353531

--- Comment #9 from szymon.p...@gmail.com  ---
Dear KDE Developers,

Unfortunatelly I don't have good news. I noticed recently that this bug still
exists and shows up every time when event starts one day and stop next day if I
select different timezone what is very often; UTC or other.

The event looks like on the screenshot. 

Any chance to improve that?  

Many thanks,
Simon

-- 
You are receiving this mail because:
You are watching all bug changes.

[korganizer] [Bug 353531] Wrong shown events that end the next day.

[szymon . pysz]

https://bugs.kde.org/show_bug.cgi?id=353531

szymon.p...@gmail.com  changed:

   What|Removed |Added

   Assignee|kdepim-b...@kde.org |szymon.p...@gmail.com
 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1

--- Comment #8 from szymon.p...@gmail.com  ---
Created attachment 112621
  --> https://bugs.kde.org/attachment.cgi?id=112621=edit
Screenshot

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 370975] device notifier pretends it cannot mount usb device while actually mounting it

[Szymon Szypulski]

https://bugs.kde.org/show_bug.cgi?id=370975

Szymon Szypulski <s...@gen2.org> changed:

   What|Removed |Added

 CC||s...@gen2.org

-- 
You are receiving this mail because:
You are watching all bug changes.

[Plasma Vault] [Bug 389276] New: Plasma Vault is incompatible with Vaults created with CryFS 0.9.7 filesystem

[Szymon]

https://bugs.kde.org/show_bug.cgi?id=389276

Bug ID: 389276
   Summary: Plasma Vault is incompatible with Vaults created with
CryFS 0.9.7 filesystem
   Product: Plasma Vault
   Version: unspecified
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: general
  Assignee: ivan.cu...@kde.org
  Reporter: szymon17...@gmail.com
  Target Milestone: ---

If you manually open the vaults using CryFS in terminal (cryfs
yourencryptedfile.enc ~/mountpoint) there's an information that:

This filesystem is for CryFS 0.9.7. It can be migrated to CryFS 0.9.8, but
afterwards couldn't be opened 
anymore with older versions. Do you want to migrate it?
Your choice [y/n]:

If you migrate the filesystem then Plasma Vault will be able to open it without
any problems.

My proposed solution would be to automatically migrate all Vaults to 0.9.8
CryFS filesystem.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 381044] Title bar does not comply to HiDPI scaling

[Szymon Łągiewka]

https://bugs.kde.org/show_bug.cgi?id=381044

--- Comment #4 from Szymon Łągiewka <bugs-...@lagiewka.pl> ---
https://paste.kde.org/pbythjfdw/zwzag5

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 386437] New: plasma crashes on startup

[Szymon Janc]

https://bugs.kde.org/show_bug.cgi?id=386437

Bug ID: 386437
   Summary: plasma crashes on startup
   Product: plasmashell
   Version: 5.10.5
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: szymon.j...@gmail.com
CC: plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.10.5)

Qt Version: 5.7.1
Frameworks Version: 5.38.0
Operating System: Linux 4.13.9-200.fc26.x86_64 x86_64
Distribution: "Fedora release 26 (Twenty Six)"

-- Information about the crash:
This happens occasionally. After crash I'm able to restore desktop by starting
plasmashell (via alt-f2) and it always starts OK.

The crash can be reproduced sometimes.

-- Backtrace:
Application: Plasma (plasmashell), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fc634c9d4c0 (LWP 1364))]

Thread 5 (Thread 0x7fc60eb6a700 (LWP 1719)):
#0  0x7fc63ff4590b in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fc6474d7534 in QTWTF::TCMalloc_PageHeap::scavengerThread() () at
/lib64/libQt5Script.so.5
#2  0x7fc6474d7579 in  () at /lib64/libQt5Script.so.5
#3  0x7fc63ff3f36d in start_thread () at /lib64/libpthread.so.0
#4  0x7fc640c02e1f in clone () at /lib64/libc.so.6

Thread 4 (Thread 0x7fc61dd94700 (LWP 1590)):
#0  0x7fc6399954c4 in g_mutex_unlock () at /lib64/libglib-2.0.so.0
#1  0x7fc639950526 in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#2  0x7fc63995067c in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#3  0x7fc641a12e6b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQt5Core.so.5
#4  0x7fc6419c360a in
QEventLoop::exec(QFlags) () at
/lib64/libQt5Core.so.5
#5  0x7fc64181b99a in QThread::exec() () at /lib64/libQt5Core.so.5
#6  0x7fc644a859b5 in QQmlThreadPrivate::run() () at /lib64/libQt5Qml.so.5
#7  0x7fc64181fc9e in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#8  0x7fc63ff3f36d in start_thread () at /lib64/libpthread.so.0
#9  0x7fc640c02e1f in clone () at /lib64/libc.so.6

Thread 3 (Thread 0x7fc61f5ef700 (LWP 1532)):
#0  0x7fc640bf6d2d in poll () at /lib64/libc.so.6
#1  0x7fc639950569 in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#2  0x7fc63995067c in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#3  0x7fc641a12e6b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQt5Core.so.5
#4  0x7fc6419c360a in
QEventLoop::exec(QFlags) () at
/lib64/libQt5Core.so.5
#5  0x7fc64181b99a in QThread::exec() () at /lib64/libQt5Core.so.5
#6  0x7fc644a859b5 in QQmlThreadPrivate::run() () at /lib64/libQt5Qml.so.5
#7  0x7fc64181fc9e in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#8  0x7fc63ff3f36d in start_thread () at /lib64/libpthread.so.0
#9  0x7fc640c02e1f in clone () at /lib64/libc.so.6

Thread 2 (Thread 0x7fc634c96700 (LWP 1418)):
#0  0x7fc640bf6d2d in poll () at /lib64/libc.so.6
#1  0x7fc639950569 in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#2  0x7fc63995067c in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#3  0x7fc641a12e6b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQt5Core.so.5
#4  0x7fc6419c360a in
QEventLoop::exec(QFlags) () at
/lib64/libQt5Core.so.5
#5  0x7fc64181b99a in QThread::exec() () at /lib64/libQt5Core.so.5
#6  0x7fc641c1ea39 in QDBusConnectionManager::run() () at
/lib64/libQt5DBus.so.5
#7  0x7fc64181fc9e in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#8  0x7fc63ff3f36d in start_thread () at /lib64/libpthread.so.0
#9  0x7fc640c02e1f in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7fc634c9d4c0 (LWP 1364)):
[KCrash Handler]
#6  0x7fc587ed02d0 in  ()
#7  0x7fc64499ff68 in QV4::QmlBindingWrapper::call(QV4::Managed const*,
QV4::CallData*) () at /lib64/libQt5Qml.so.5
#8  0x7fc644a6a725 in QQmlJavaScriptExpression::evaluate(QV4::CallData*,
bool*) () at /lib64/libQt5Qml.so.5
#9  0x7fc644a6ac02 in QQmlJavaScriptExpression::evaluate(bool*) () at
/lib64/libQt5Qml.so.5
#10 0x7fc6449fda61 in QQmlExpressionPrivate::value(bool*) () at
/lib64/libQt5Qml.so.5
#11 0x7fc6449fdc51 in QQmlExpression::evaluate(bool*) () at
/lib64/libQt5Qml.so.5
#12 0x7fc6476069e6 in
PlasmaQuick::AppletQuickItemPrivate::compactRepresentationCheck() () at
/lib64/libKF5PlasmaQuick.so.5
#13 0x7fc647607c12 in PlasmaQuick::AppletQuickItem::init() () at
/lib64/libKF5PlasmaQuick.so.5
#14 0x7fc61dda9914 in AppletInterface::init() () at
/usr/lib64/qt5/plugins/plasma/scriptengines/plasma_appletscript_declarative.so
#15 0x7fc61ddb6373 in ContainmentInterface::init() () at

[kwin] [Bug 376987] On screen display included in window layout

[Szymon Łągiewka]

https://bugs.kde.org/show_bug.cgi?id=376987

Szymon Łągiewka <bugs-...@lagiewka.pl> changed:

   What|Removed |Added

 CC||bugs-...@lagiewka.pl

--- Comment #3 from Szymon Łągiewka <bugs-...@lagiewka.pl> ---
What about notifications? For me in 5.10.5 notifications are still visible in
desktop grid. I can move grab and move them around and so on.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kaffeine] [Bug 368907] kaffeine sometimes uses 100% CPU

[Szymon Stefanek]

https://bugs.kde.org/show_bug.cgi?id=368907

Szymon Stefanek <pra...@kvirc.net> changed:

   What|Removed |Added

 CC||pra...@kvirc.net
 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1

--- Comment #27 from Szymon Stefanek <pra...@kvirc.net> ---
I have the same issue with version 2.0.10. Viewing the same DVB channel
sometimes uses low CPU and sometimes stays almost fixed at 100% (saturating one
core, I guess). Version 2.0.10 installed from
https://launchpad.net/~mtron/+archive/ubuntu/kaffeine-stable seems to be
affected just like the 2.0.5 from the official ubuntu repositories. In addition
2.0.10 also tends to spit out a lot of warnings like the following:

08-07-17 03:55:54.236 [Debug   ] kaffeine.epg: channel invalid
08-07-17 03:55:54.263 [Debug   ] kaffeine.epg: channel invalid
08-07-17 03:55:54.390 [Debug   ] kaffeine.epg: table 0x4f, extension 0x2189,
session 1/1, size 383
08-07-17 03:55:54.392 [Warning ] "2 instead of 1 arguments to message {Country
%1: not rate...} supplied before conversion."

but these might be unrelated as they seem to appear also when CPU usage is low.

Another message I see often (in both versions) is:

[2d6da6e8] core input error: ES_OUT_SET_(GROUP_)PCR  is called too late
(pts_delay increased to 488 ms)
[2d6da6e8] core input error: ES_OUT_RESET_PCR called

Hard to say if it's related.

Profiling shows similar results to the ones obtained by Jan Palus.
Most instruction fetches seem to happen inside src_process in libsamplerate.so.

An interesting fact is that when profiling via valgrind the CPU usage tends to
be lower than when running normally. 100% is very rare. So it's even possible
that the bug is not triggered when running under valgrind.

-- 
You are receiving this mail because:
You are watching all bug changes.

[ksmserver] [Bug 381045] Logout greeter gets title bar and breaks background view

[Szymon Łągiewka]

https://bugs.kde.org/show_bug.cgi?id=381045

--- Comment #3 from Szymon Łągiewka <bugs-...@lagiewka.pl> ---
Yup, it's better now. Though still opens quarterly as I've previously
described.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 360841] Unable to unshow/unpresent windows using the same keyboard shortcut

[Szymon Łągiewka]

https://bugs.kde.org/show_bug.cgi?id=360841

Szymon Łągiewka <bugs-...@lagiewka.pl> changed:

   What|Removed |Added

 CC||bugs-...@lagiewka.pl

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 380902] kwin effects like "present windows" can't be exited with the keyboard

[Szymon Łągiewka]

https://bugs.kde.org/show_bug.cgi?id=380902

Szymon Łągiewka <bugs-...@lagiewka.pl> changed:

   What|Removed |Added

 CC||bugs-...@lagiewka.pl

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 378710] OpenGL visual glitches for task switcher, desktop grid and window tiling.

[Szymon Łągiewka]

https://bugs.kde.org/show_bug.cgi?id=378710

Szymon Łągiewka <bugs-...@lagiewka.pl> changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |WORKSFORME

--- Comment #3 from Szymon Łągiewka <bugs-...@lagiewka.pl> ---
Changing EGL to GLX in kwinrc seems to fix the issue.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 378710] OpenGL visual glitches for task switcher, desktop grid and window tiling.

[Szymon Łągiewka]

https://bugs.kde.org/show_bug.cgi?id=378710

--- Comment #2 from Szymon Łągiewka <bugs-...@lagiewka.pl> ---
I made a quick video that shows all of the issues in one take.
https://youtu.be/tZqx2mgY1Bc

-- 
You are receiving this mail because:
You are watching all bug changes.