[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets

2023-06-03 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=470114

Bug Janitor Service  changed:

   What|Removed |Added

   Severity|crash   |wishlist

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

[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets

2023-06-03 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=470114

Bug Janitor Service  changed:

   What|Removed |Added

   Severity|wishlist|crash

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

[konsole] [Bug 470100] cannot select and copy text on git log

2023-06-03 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=470100

greenscarf...@gmail.com changed:

   What|Removed |Added

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

--- Comment #2 from greenscarf...@gmail.com ---
my bad, i was wrongly adding ' --mouse' option to LESS variable in my
.gitconfig like:

[core]
  pager = less -LRc --mouse
[pager]
diff = LESS='LRc --mouse' delta
show = LESS='LRc --mouse' delta
stash = LESS='LRc --mouse' delta
log = LESS='LRc --mouse' delta
reflog = LESS='LRc --mouse' delta

after removing '--mouse', it works as intended.

[core]
  pager = delta
[pager]
diff = LESS=LRc delta
show = LESS=LRc delta
stash = LESS=LRc delta
log = LESS=LRc delta
reflog = LESS=LRc delta
  blame = LESS=LRc delta

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

[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets

2023-06-03 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=470114

Bug Janitor Service  changed:

   What|Removed |Added

   Severity|crash   |wishlist

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

[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets

2023-06-03 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=470114

Bug Janitor Service  changed:

   What|Removed |Added

   Severity|wishlist|crash

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

[plasmashell] [Bug 470533] Feature request: Click & drag on panel to move maximised window that touches it

2023-06-03 Thread Aurora Robb Kristiansen
https://bugs.kde.org/show_bug.cgi?id=470533

Aurora Robb Kristiansen  changed:

   What|Removed |Added

 CC||td21rz...@mozmail.com

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

[plasmashell] [Bug 469192] Plasmashell frequently starts up with no wallpaper (black background) nor desktop folder view until plasmashell is restarted.

2023-06-03 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=469192

--- Comment #7 from Bug Janitor Service  ---
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

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

[krita] [Bug 469389] Window flickers sporadically

2023-06-03 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=469389

Bug Janitor Service  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|WAITINGFORINFO  |WORKSFORME

--- Comment #4 from Bug Janitor Service  ---
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!

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

[kate] [Bug 468638] kate crashed while moving tab

2023-06-03 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=468638

--- Comment #4 from Bug Janitor Service  ---
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

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

[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets

2023-06-03 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=470114

Bug Janitor Service  changed:

   What|Removed |Added

   Severity|crash   |wishlist

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

[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets

2023-06-03 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=470114

Bug Janitor Service  changed:

   What|Removed |Added

   Severity|wishlist|crash

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

[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets

2023-06-03 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=470114

Bug Janitor Service  changed:

   What|Removed |Added

   Severity|crash   |wishlist

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

[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets

2023-06-03 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=470114

Bug Janitor Service  changed:

   What|Removed |Added

   Severity|wishlist|crash

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

[plasmashell] [Bug 470620] New: Clipboard filled with image URIs can cause severe performance problems

2023-06-03 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=470620

Bug ID: 470620
   Summary: Clipboard filled with image URIs can cause severe
performance problems
Classification: Plasma
   Product: plasmashell
   Version: master
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Clipboard
  Assignee: plasma-b...@kde.org
  Reporter: annasonoh...@gmail.com
  Target Milestone: 1.0

SUMMARY
The clipboard can cause plasmashell to use a lot of disk transfers and memory
if it is filled with lots of image URIs
This persists across system restarts, until the relevant images are removed.
May be related to the previews.


STEPS TO REPRODUCE
1. select around 50k images in dolphin
2. press ctrl+C
3. wait a few minutes. I/O usage and memory will increase over time.

OBSERVED RESULT
8GiB of memory, some more in swap, 100% disk read, plasmashell freezing, other
programs encountering long disk waits

EXPECTED RESULT
Some sort of cap prevents the system from becoming unusable

SOFTWARE/OS VERSIONS
Linux kernel: 6.1.31-1-MANJARO (64 bit)
KDE Plasma Version: 5.27.4
KDE Frameworks Version: 5.105.0
Qt Version: 5.15.9
Graphics platform: X11

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

[kwin] [Bug 458446] Menus Start Showing behind Windows

2023-06-03 Thread Pedro Rosado
https://bugs.kde.org/show_bug.cgi?id=458446

--- Comment #9 from Pedro Rosado  ---
(In reply to Nate Graham from comment #7)
> See Comment 3

Please find below the result from running the command - 'qdbus-qt5 org.kde.KWin
/KWin supportInformation"
Version
===
KWin version: 5.27.5
Qt Version: 5.15.9
Qt compile version: 5.15.9
XCB compile version: 1.15

Operation Mode: Xwayland

Build Options
=
KWIN_BUILD_DECORATIONS: yes
KWIN_BUILD_TABBOX: yes
KWIN_BUILD_ACTIVITIES: yes
HAVE_X11_XCB: yes
HAVE_EPOXY_GLX: yes

X11
===
Vendor: SUSE LINUX
Vendor Release: 12301001
Protocol Version/Revision: 11/0
SHAPE: yes; Version: 0x11
RANDR: yes; Version: 0x14
DAMAGE: yes; Version: 0x11
Composite: yes; Version: 0x4
RENDER: yes; Version: 0xb
XFIXES: yes; Version: 0x50
SYNC: yes; Version: 0x31
GLX: yes; Version: 0x0

Decoration
==
Plugin: org.kde.breeze
Theme: 
Plugin recommends border size: None
onAllDesktopsAvailable: true
alphaChannelSupported: true
closeOnDoubleClickOnMenu: false
decorationButtonsLeft: 0, 2
decorationButtonsRight: 6, 3, 4, 5
borderSize: 0
gridUnit: 10
font: Noto Sans,10,-1,0,50,0,0,0,0,0
smallSpacing: 2
largeSpacing: 10

Output backend
==
Name: DRM
Active: true
Atomic Mode Setting on GPU 0: true

Cursor
==
themeName: breeze_cursors
themeSize: 24

Options
===
focusPolicy: 0
xwaylandCrashPolicy: 
xwaylandMaxCrashCount: 3
nextFocusPrefersMouse: false
clickRaise: true
autoRaise: false
autoRaiseInterval: 0
delayFocusInterval: 0
shadeHover: false
shadeHoverInterval: 250
separateScreenFocus: false
activeMouseScreen: true
placement: 
activationDesktopPolicy: 0
focusPolicyIsReasonable: true
borderSnapZone: 10
windowSnapZone: 10
centerSnapZone: 0
snapOnlyWhenOverlapping: false
rollOverDesktops: false
focusStealingPreventionLevel: 1
operationTitlebarDblClick: 5000
operationMaxButtonLeftClick: 5000
operationMaxButtonMiddleClick: 5015
operationMaxButtonRightClick: 5014
commandActiveTitlebar1: 0
commandActiveTitlebar2: 28
commandActiveTitlebar3: 2
commandInactiveTitlebar1: 4
commandInactiveTitlebar2: 28
commandInactiveTitlebar3: 2
commandWindow1: 7
commandWindow2: 8
commandWindow3: 8
commandWindowWheel: 28
commandAll1: 10
commandAll2: 3
commandAll3: 14
keyCmdAllModKey: 16777250
condensedTitle: false
electricBorderMaximize: true
electricBorderTiling: true
electricBorderCornerRatio: 0.25
borderlessMaximizedWindows: false
killPingTimeout: 5000
hideUtilityWindowsForInactive: true
compositingMode: 1
useCompositing: true
hiddenPreviews: 1
glSmoothScale: 2
glStrictBinding: false
glStrictBindingFollowsDriver: true
glPreferBufferSwap: 101
glPlatformInterface: 2
windowsBlockCompositing: true
latencyPolicy: 
renderTimeEstimator: 
allowTearing: true

Screen Edges

desktopSwitching: false
desktopSwitchingMovingClients: false
cursorPushBackDistance: 1x1
timeThreshold: 225
reActivateThreshold: 400
actionTopLeft: 0
actionTop: 0
actionTopRight: 0
actionRight: 0
actionBottomRight: 0
actionBottom: 0
actionBottomLeft: 0
actionLeft: 0

Screens
===
Active screen follows mouse:  yes
Number of Screens: 2

Screen 0:
-
Name: eDP-1
Enabled: 1
Geometry: 0,0,1920x1080
Scale: 1
Refresh Rate: 60006
Adaptive Sync: incapable
Screen 1:
-
Name: VGA-1
Enabled: 1
Geometry: 1920,0,1440x900
Scale: 1
Refresh Rate: 59887
Adaptive Sync: incapable

Compositing
===
Compositing is active
Compositing Type: OpenGL
OpenGL vendor string: Intel
OpenGL renderer string: Mesa Intel(R) HD Graphics 4600 (HSW GT2)
OpenGL version string: 4.6 (Core Profile) Mesa 23.0.3
OpenGL platform interface: EGL
OpenGL shading language version string: 4.60
Driver: Intel
GPU class: Haswell
OpenGL version: 4.6
GLSL version: 4.60
Mesa version: 23.0.3
Linux kernel version: 6.3.4
Direct rendering: Requires strict binding: no
GLSL shaders:  yes
Texture NPOT support:  yes
Virtual Machine:  no
OpenGL 2 Shaders are used

Loaded Effects:
---
colorpicker
outputlocator
screenshot
screenedge
zoom
blur
contrast
kwin4_effect_sessionquit
kwin4_effect_logout
kwin4_effect_login
slidingpopups
kwin4_effect_windowaperture
magiclamp
slide
slideback
kwin4_effect_fullscreen
kwin4_effect_scale
kwin4_effect_morphingpopups
kwin4_effect_maximize
kwin4_effect_frozenapp
kwin4_effect_fadingpopups
kwin4_effect_dimscreen
kwin4_effect_dialogparent
desktopgrid
highlightwindow
overview
tileseditor
windowview
wobblywindows
blendchanges
startupfeedback
kscreen
screentransform

Currently Active Effects:
-
blur
contrast

Effect Settings:

colorpicker:

outputlocator:

screenshot:

screenedge:

zoom:
zoomFactor: 1.2
mousePointer: 0
mouseTracking: 0
focusTrackingEnabled: false
textCaretTrackingEnabled: false
focusDelay: 350
moveFactor: 20
targetZoom: 1

blur:

contrast:

kwin4_effect_sessionquit:
pluginId: kwin4_effect_sessionquit
isActiveFullScreenEffect: false

kwin4_effect_logout:
pluginId: kwin4_effect_logout
isActiveFullScreenEffect: false

kwin4_effect_login:
pluginId: kwin4_effect_login

[plasmashell] [Bug 470604] Desktop icon positions reset when plasmashell is restarted

2023-06-03 Thread Justin Zobel
https://bugs.kde.org/show_bug.cgi?id=470604

Justin Zobel  changed:

   What|Removed |Added

 CC||justin.zo...@gmail.com

--- Comment #1 from Justin Zobel  ---
I have plasmashell running in a terminal because well, it's Plasma 6 and it's
janky.

If I Ctrl C the plasmashell process and start it again it won't remember the
icon placement
If I open a new tab and plasmashell --replace it will remember the placement.

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

[plasmashell] [Bug 470606] Save/discard/cancel dialogs for Plasma config dialogs are unstyled QML now

2023-06-03 Thread Justin Zobel
https://bugs.kde.org/show_bug.cgi?id=470606

Justin Zobel  changed:

   What|Removed |Added

 Status|REPORTED|CONFIRMED
 CC||justin.zo...@gmail.com
 Ever confirmed|0   |1

--- Comment #1 from Justin Zobel  ---
Can confirm same issue.

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

[plasmashell] [Bug 470573] cannot select items with selection rectangle on desktop in folder view

2023-06-03 Thread Justin Zobel
https://bugs.kde.org/show_bug.cgi?id=470573

Justin Zobel  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |WORKSFORME
 Status|NEEDSINFO   |RESOLVED

--- Comment #2 from Justin Zobel  ---
I reported this on my old install on my portable SSD, a fresh install to my
internal SSD all seems to be fine, closing.

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

[konsole] [Bug 470575] incorrect text selected, offset

2023-06-03 Thread Justin Zobel
https://bugs.kde.org/show_bug.cgi?id=470575

Justin Zobel  changed:

   What|Removed |Added

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

--- Comment #2 from Justin Zobel  ---
No scaling, Konsole says built against Qt 6.5.1. I'd upload a screen recording
but Spectacle isn't finishing/saving recordings :D

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

[ark] [Bug 470577] [feature request] 7z additional options

2023-06-03 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=470577

--- Comment #1 from 2wxsy5823...@opayq.com ---
Regarding those new compression methods, the official 7-Zip by Igor Pavlov does
not support them, so they are not official / standard yet.

Also, even though some distros have switched to the new p7zip fork (which
supports those new compression methods), I wonder whether distros will
eventually switch to the official 7-Zip, since it now also supports Linux.

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

[ark] [Bug 435874] Ark should warn about closing its window while an extraction is in progress

2023-06-03 Thread Fabian Arndt
https://bugs.kde.org/show_bug.cgi?id=435874

Fabian Arndt  changed:

   What|Removed |Added

 CC||fabian.ar...@root-core.net

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

[ark] [Bug 435874] Ark should warn about closing its window while an extraction is in progress

2023-06-03 Thread Fabian Arndt
https://bugs.kde.org/show_bug.cgi?id=435874

Fabian Arndt  changed:

   What|Removed |Added

 CC||orakmoyaoffic...@gmail.com

--- Comment #3 from Fabian Arndt  ---
*** Bug 461447 has been marked as a duplicate of this bug. ***

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

[ark] [Bug 461447] Provide warning upon trying to close program while it's extracting contents.

2023-06-03 Thread Fabian Arndt
https://bugs.kde.org/show_bug.cgi?id=461447

Fabian Arndt  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
 Resolution|--- |DUPLICATE

--- Comment #1 from Fabian Arndt  ---


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

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

[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets

2023-06-03 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=470114

Bug Janitor Service  changed:

   What|Removed |Added

   Severity|crash   |wishlist

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

[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets

2023-06-03 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=470114

Bug Janitor Service  changed:

   What|Removed |Added

   Severity|wishlist|crash

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

[ark] [Bug 459359] Unhelpful ping-pong 'progress' bar during creation / extraction of an single-file archive

2023-06-03 Thread Fabian Arndt
https://bugs.kde.org/show_bug.cgi?id=459359

Fabian Arndt  changed:

   What|Removed |Added

Summary|Unhelpful ping-pong |Unhelpful ping-pong
   |'progress' bar when I   |'progress' bar during
   |create a .tar or .arj   |creation / extraction of an
   |archive with a single file  |single-file archive
   |via context menu of Dolphin |

--- Comment #3 from Fabian Arndt  ---
This seems to be independent of the choosen format and it also happens if you
create an archive via. Ark itself - not only via context menu.

The problem with progress bars is how you calculate them. In this case ark uses
the file count, but this is cumbersome with big files or a mixed set with small
and big files. File size might be a better option, but could be misleading if
lots of small files slow down the process.

- At least for a single file operation the filesize would be helpful
- A data transfer rate would make a good addition
- One good solution might be to show two progress bars: current file and
overall progress

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

[systemsettings] [Bug 470619] All fonts except for "Window title" don't obey an unchecked "Anti-Aliasing" setting

2023-06-03 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=470619

--- Comment #1 from sunsp...@gmail.com ---
Incidentally, there may be some interplay with QT here for apps like System
Settings, Dolphin, etc. who do not respect the settings. In Windows, I stopped
updating qBittorrent past a certain version because an update to QT caused the
app to enforce anti-aliasing when previously it respected the OS setting to
have it disabled.

Should this bug be properly filed against QT? It is a regression, since it was
working correctly before a certain version number.

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

[systemsettings] [Bug 470619] New: All fonts except for "Window title" don't obey an unchecked "Anti-Aliasing" setting

2023-06-03 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=470619

Bug ID: 470619
   Summary: All fonts except for "Window title" don't obey an
unchecked "Anti-Aliasing" setting
Classification: Applications
   Product: systemsettings
   Version: 5.26.1
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: kcm_fonts
  Assignee: plasma-b...@kde.org
  Reporter: sunsp...@gmail.com
  Target Milestone: ---

SUMMARY
If the "Anti-Aliasing" option is unchecked, only "Window Title" correctly
renders as aliased. All other elements on the panel continue rendering as
anti-aliased. 

STEPS TO REPRODUCE
1. Uncheck "Anti-Aliasing"
2. Open an app like Dolphin

OBSERVED RESULT
Using Dolphin as an example, the window titlebar will be correctly aliased, but
everything else in the window will be anti-aliased.

EXPECTED RESULT
For everything to be completely aliased, however if there has to be a bug, it
should be a consistent bug.. the window title should also be anti-aliased in
that situation.

SOFTWARE/OS VERSIONS
Operating System: SteamOS 3.4.6
KDE Plasma Version: 5.26.1
KDE Frameworks Version: 5.99.0
Qt Version: 5.15.6
Kernel Version: 5.13.0-valve36-1-neptune (64-bit)
Graphics Platform: X11

ADDITIONAL INFORMATION
I actually often do use truetype fonts that have been hinted to work properly
aliased. I feel the need to make this comment because I've seen a number of
comments in bug reports saying "why would you want ugly fonts?". My response to
that is, if you use a properly hinted font designed for 1-bit, it'll be crisp
and clear just like bitmapped fonts in the console. It is correct that if the
font is not hinted and AA is turned off, it will look bad on a lower resolution
display. Also, the higher resolution a display is, the less and less you need
anti-aliasing, in other words, if you're on 4K, 5K, 6K, 8K, etc. resolution
displays, you will actually WANT to have anti-aliasing (and hinting) turned
off. In any case, the bug should demonstrate a consistent behaviour with the
rest of the screen elements.

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

[Spectacle] [Bug 470618] Command line option to take screenshot instantly

2023-06-03 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=470618

--- Comment #1 from deresi...@protonmail.ch ---
> I think none of the above work on KDE plasma for different reasons (maim is
> x11 only, grim uses a wlroots extension, and I think gnome-screenshot only
> works with gnome's compositor)

Oops, I meant that none of those work on plasma wayland. I know that KDE plasma
has X11, but I was only thinking in the context of plasma wayland.

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

[Spectacle] [Bug 470618] New: Command line option to take screenshot instantly

2023-06-03 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=470618

Bug ID: 470618
   Summary: Command line option to take screenshot instantly
Classification: Applications
   Product: Spectacle
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: General
  Assignee: noaha...@gmail.com
  Reporter: deresi...@protonmail.ch
CC: k...@david-redondo.de
  Target Milestone: ---

SUMMARY
Currently spectacle can select a region to screenshot and take an image of it
through `spectacle -b -r -o filename.png`. But it always has the UI for "save,
save as , copy, export etc..." on the region select screen and it always
requires either double clicking or pressing enter to save finish taking the
screenshot.

I'm looking for a way to use spectacle with *just*
1. execute spectacle through command line with cli parameters
2. region selection without any other UI elements
3. immediately finish taking screenshot after letting go of left mouse button

For reference, what I'm talking about is like:
`grim -g "$(slurp)"` using https://git.sr.ht/~emersion/grim in combination with
https://github.com/emersion/slurp
and gnome-screenshot's `gnome-screenshot -a -f file.png`
and `maim --select file.png` with https://github.com/naelstrof/maim

I think none of the above work on KDE plasma for different reasons (maim is x11
only, grim uses a wlroots extension, and I think gnome-screenshot only works
with gnome's compositor)

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

[konsole] [Bug 462615] Use KActionCollection::setDefaultShortcut(s) instead

2023-06-03 Thread Guilherme Silva
https://bugs.kde.org/show_bug.cgi?id=462615

Guilherme Silva  changed:

   What|Removed |Added

 CC||oguilhe...@protonmail.com

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

[kalendar] [Bug 470592] Kalendar crashes during launch.

2023-06-03 Thread Carl Schwan
https://bugs.kde.org/show_bug.cgi?id=470592

Carl Schwan  changed:

   What|Removed |Added

 Resolution|--- |DOWNSTREAM
 Status|REPORTED|RESOLVED

--- Comment #1 from Carl Schwan  ---
This is a packaging issue

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

[ark] [Bug 459359] Unhelpful ping-pong 'progress' bar when I create a .tar or .arj archive with a single file via context menu of Dolphin

2023-06-03 Thread Fabian Arndt
https://bugs.kde.org/show_bug.cgi?id=459359

Fabian Arndt  changed:

   What|Removed |Added

 CC||fabian.ar...@root-core.net

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

[ark] [Bug 461447] Provide warning upon trying to close program while it's extracting contents.

2023-06-03 Thread Fabian Arndt
https://bugs.kde.org/show_bug.cgi?id=461447

Fabian Arndt  changed:

   What|Removed |Added

 CC||fabian.ar...@root-core.net

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

[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets

2023-06-03 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=470114

Bug Janitor Service  changed:

   What|Removed |Added

   Severity|crash   |wishlist

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

[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets

2023-06-03 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=470114

Bug Janitor Service  changed:

   What|Removed |Added

   Severity|wishlist|crash

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

[KClock] [Bug 470580] Stopwatch does not correctly show hours

2023-06-03 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=470580

648j...@gmail.com changed:

   What|Removed |Added

   Platform|Debian testing  |Flatpak

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

[krita] [Bug 470617] Screen glitches out when I move my mouse/stylus. The window flashes black and white boxes repeatedly across the screen. I've tried both my mousepad and stylus but both cause the f

2023-06-03 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=470617

--- Comment #1 from sebstrider...@gmail.com ---
*** Bug 470616 has been marked as a duplicate of this bug. ***

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

[krita] [Bug 470616] Screen glitches out when I move my mouse/stylus. The window flashes black and white boxes repeatedly across the screen. I've tried both my mousepad and stylus but both cause the f

2023-06-03 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=470616

sebstrider...@gmail.com changed:

   What|Removed |Added

 Status|REPORTED|NEEDSINFO
 Resolution|--- |DUPLICATE

--- Comment #1 from sebstrider...@gmail.com ---
Sorry about the missing info, I accidentally submitted the bug report wrong. I
resubmitted the report with the correct info. The Report ID is 470617.

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

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

[krita] [Bug 470617] New: Screen glitches out when I move my mouse/stylus. The window flashes black and white boxes repeatedly across the screen. I've tried both my mousepad and stylus but both cause

2023-06-03 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=470617

Bug ID: 470617
   Summary: Screen glitches out when I move my mouse/stylus. The
window flashes black and white boxes repeatedly across
the screen. I've tried both my mousepad and stylus but
both cause the flashes, mostly when they move around
the edges of the screen.
Classification: Applications
   Product: krita
   Version: unspecified
  Platform: Microsoft Windows
OS: Microsoft Windows
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: General
  Assignee: krita-bugs-n...@kde.org
  Reporter: sebstrider...@gmail.com
  Target Milestone: ---

SUMMARY
***
Screen glitches out when I move my mouse/stylus. The window flashes black and
white boxes repeatedly across the screen. I've tried both my mousepad and
stylus but both cause the flashes, mostly when they move around the edges of
the screen.
***


STEPS TO REPRODUCE
1. Open application
2. move mose/stylus around the screen, especially the edges
3. 

OBSERVED RESULT
Window flashes black and white glitches

EXPECTED RESULT


SOFTWARE/OS VERSIONS
Windows: 11 Home
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.

[krita] [Bug 470616] New: Screen glitches out when I move my mouse/stylus. The window flashes black and white boxes repeatedly across the screen. I've tried both my mousepad and stylus but both cause

2023-06-03 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=470616

Bug ID: 470616
   Summary: Screen glitches out when I move my mouse/stylus. The
window flashes black and white boxes repeatedly across
the screen. I've tried both my mousepad and stylus but
both cause the flashes, mostly when they move around
the edges of the screen.
Classification: Applications
   Product: krita
   Version: unspecified
  Platform: Microsoft Windows
OS: Microsoft Windows
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: General
  Assignee: krita-bugs-n...@kde.org
  Reporter: sebstrider...@gmail.com
  Target Milestone: ---

SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug
symbols.
See
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***


STEPS TO REPRODUCE
1. 
2. 
3. 

OBSERVED RESULT


EXPECTED RESULT


SOFTWARE/OS VERSIONS
Windows: 11 Home
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 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets

2023-06-03 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=470114

Bug Janitor Service  changed:

   What|Removed |Added

   Severity|crash   |wishlist

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

[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets

2023-06-03 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=470114

Bug Janitor Service  changed:

   What|Removed |Added

   Severity|wishlist|crash

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

[krfb] [Bug 470615] no mouse or keyboard control

2023-06-03 Thread Nicolas Fella
https://bugs.kde.org/show_bug.cgi?id=470615

Nicolas Fella  changed:

   What|Removed |Added

 CC||nicolas.fe...@gmx.de
   Severity|critical|normal

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

[frameworks-baloo] [Bug 470443] Baloo crash indexing

2023-06-03 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=470443

tagwer...@innerjoin.org changed:

   What|Removed |Added

 CC||tagwer...@innerjoin.org

--- Comment #2 from tagwer...@innerjoin.org ---
> ... On resume Baloo seems to work, but monitor shows nothing ...
Have a look at Bug 470382

There's been a recent change that limits the memory that baloo can use to 512
Mbyte, this issue sounds similar. You would need to edit the systemd service
file for kde-baloo, following the description.

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

[yakuake] [Bug 392626] Tab changes when an unselected tab is closed

2023-06-03 Thread Nicolas Fella
https://bugs.kde.org/show_bug.cgi?id=392626

Nicolas Fella  changed:

   What|Removed |Added

 CC||nicolas.fe...@gmx.de
   Version Fixed In||23.04.3

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

[yakuake] [Bug 392626] Tab changes when an unselected tab is closed

2023-06-03 Thread Nicolas Fella
https://bugs.kde.org/show_bug.cgi?id=392626

Nicolas Fella  changed:

   What|Removed |Added

 Resolution|--- |FIXED
  Latest Commit||https://invent.kde.org/util
   ||ities/yakuake/-/commit/baaa
   ||c15a8f52d044dc6a712c96e2c68
   ||fc4209315
 Status|ASSIGNED|RESOLVED

--- Comment #6 from Nicolas Fella  ---
Git commit baaac15a8f52d044dc6a712c96e2c68fc4209315 by Nicolas Fella, on behalf
of Teague Millette.
Committed on 03/06/2023 at 22:41.
Pushed by nicolasfella into branch 'release/23.04'.

Prevent unnecessary tab switching on tab close
(cherry picked from commit 5797a3fe00a859ad185c7b53c273e468db813b3f)

M  +3-1app/tabbar.cpp

https://invent.kde.org/utilities/yakuake/-/commit/baaac15a8f52d044dc6a712c96e2c68fc4209315

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

[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets

2023-06-03 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=470114

Bug Janitor Service  changed:

   What|Removed |Added

   Severity|crash   |wishlist

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

[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets

2023-06-03 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=470114

Bug Janitor Service  changed:

   What|Removed |Added

   Severity|wishlist|crash

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

[krfb] [Bug 470615] New: no mouse or keyboard control

2023-06-03 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=470615

Bug ID: 470615
   Summary: no mouse or keyboard control
Classification: Applications
   Product: krfb
   Version: 23.04.1
  Platform: Ubuntu
OS: Linux
Status: REPORTED
  Severity: critical
  Priority: NOR
 Component: general
  Assignee: grundleb...@googlemail.com
  Reporter: fjfel...@gmail.com
  Target Milestone: ---

No mouse clicks or keyboard stokes possible.
I used Tight VNC Viewer and real VNC Viewer.
The xcb plug draws just a tiny window on my VNC software on my windows PC.
The QT plug shows only a black screen.
Only the PW plug shows the video.
I have the checkboxes to allow control set correctly.

thank you.

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

[systemsettings] [Bug 186996] Keyboard & Mouse System Settings - keyboard (DualKit: keyboard+mouse) info in mouse section

2023-06-03 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=186996

fjfel...@gmail.com changed:

   What|Removed |Added

 CC||fjfel...@gmail.com

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

[kscreenlocker] [Bug 470376] kscreenlocker uses discrete GPU when integrated GPU is available

2023-06-03 Thread David Koppelman
https://bugs.kde.org/show_bug.cgi?id=470376

--- Comment #5 from David Koppelman  ---
I meant that it's *not* likely I missed anything, due to the multi-second
inactivity to suspend time.

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

[kscreenlocker] [Bug 470376] kscreenlocker uses discrete GPU when integrated GPU is available

2023-06-03 Thread David Koppelman
https://bugs.kde.org/show_bug.cgi?id=470376

--- Comment #4 from David Koppelman  ---
(In reply to Nate Graham from comment #3)
> Thanks. Out of curiosity, does the discrete GPU also render the logout
> screen? The thing that appears when you click "Shut Down." If so, then I'm
> guessing the shader-based blur effects they both use are triggering the
> behavior.

The discrete GPU remains suspended after selecting both shut-down and
logout. When I select either of these I get a confirmation screen. The
confirmation screen has a black background and no obvious blur
effect. After selecting cancel I check the output a GPU status logger
which had been checking every half second, and it shows that the GPU
remained suspended. (After being used the discrete GPU remains active
for several seconds before suspending, so it's likely I missed
anything.)

BTW, I have the wobbly windows effect active and composited window
shadows, and neither results in the discrete GPU being activated.

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

[plasmashell] [Bug 470606] Save/discard/cancel dialogs for Plasma config dialogs are unstyled QML now

2023-06-03 Thread Patrick Silva
https://bugs.kde.org/show_bug.cgi?id=470606

Patrick Silva  changed:

   What|Removed |Added

 CC||bugsefor...@gmx.com

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

[frameworks-kirigami] [Bug 470612] SwipeListItem action buttons lack icons in KF6

2023-06-03 Thread Patrick Silva
https://bugs.kde.org/show_bug.cgi?id=470612

Patrick Silva  changed:

   What|Removed |Added

 CC||bugsefor...@gmx.com

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

[systemsettings] [Bug 466781] Systemsettings crashes when switching KCMs

2023-06-03 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=466781

Nate Graham  changed:

   What|Removed |Added

 Status|REPORTED|CONFIRMED
 Ever confirmed|0   |1
Summary|Systemsettings crashed when |Systemsettings crashes when
   |switching KCMs  |switching KCMs
URL||https://bugreports.qt.io/br
   ||owse/QTBUG-112306
 CC||n...@kde.org

--- Comment #7 from Nate Graham  ---
Keeping open for tracking purposes, since the upstream Qt issue isn't fixed
yet.

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

[plasmashell] [Bug 470528] "Choose Style…" button in configuration dialog does nothing when clicked in Plasma 6

2023-06-03 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=470528

Nate Graham  changed:

   What|Removed |Added

   Severity|normal  |major

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

[dolphin] [Bug 470570] After dragging an item from dolphin to the desktop the plus symbol remains on the cursor in dolphin

2023-06-03 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=470570

Nate Graham  changed:

   What|Removed |Added

   Severity|normal  |minor
 CC||n...@kde.org

--- Comment #1 from Nate Graham  ---
Cannot reproduce with those steps.

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

[xdg-desktop-portal-kde] [Bug 470476] File portal uses an incorrect too-small font size

2023-06-03 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=470476

--- Comment #3 from sunsp...@gmail.com ---
(In reply to Nate Graham from comment #2)
> > The logical DPI on this system is already set to 144.
> Note that this isn't a supported way to do scaling in a KDE environment. If
> you want everything on the screen to be bigger, the expected UX is to use
> the global scaling slider in System Settings > Display and Monitor. If yo
> just want the text to be a bit bigger for readability's take, the expected
> UX is to increase the font sizes in System Settings > Appearance > Fonts. In
> no case should it be necessary to change the Font DPI, and we're actually
> removing the ability to do so in Plasma 6.
> 
> Does the global scale slider help?

Hi Nate,

Actually, the slider is what I have used the whole time. It is set for 150%.
Where I got the 144 logical dpi information from is from the fonts panel where
it shows checkbox "force font dpi" and 144 is listed there and also in "xrdb
-query | grep -i xft". The number makes sense to me, since it is scaling. The
true DPI of the physical display is something like 102 PPI, and of course X
likes 96 as a base. 

It's not a big issue because the rest of the UI seems to be working, I just
feel the portal behaviour should be consistent with the rest of the UI. I tried
changing the font for "Small" to a different face to test, nothing changed.

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

[frameworks-kxmlgui] [Bug 470345] Configuring toolbars in KF6-ported apps fails

2023-06-03 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=470345

Nate Graham  changed:

   What|Removed |Added

   Severity|normal  |major

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

[konsole] [Bug 470572] double clicking on the empty area next to tabs no longer opens a new tab

2023-06-03 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=470572

Nate Graham  changed:

   What|Removed |Added

   Severity|normal  |minor

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

[plasmashell] [Bug 448078] Global Menu does not work in Qt6

2023-06-03 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=448078

Nate Graham  changed:

   What|Removed |Added

   Severity|normal  |major

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

[frameworks-kuserfeedback] [Bug 468446] Cannot load User Feedback KCM due to cmake/soname diff - "plugin KUserFeedbackQml" not found.

2023-06-03 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=468446

Nate Graham  changed:

   What|Removed |Added

   Severity|normal  |grave
Summary|cannot load KCM due to  |Cannot load User Feedback
   |cmake/soname diff - |KCM due to cmake/soname
   |"plugin KUserFeedbackQml"   |diff -  "plugin
   |not found.  |KUserFeedbackQml" not
   ||found.

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

[kwin] [Bug 470603] bb8e5458a748ea922c19294a38026cfeb48ddb02 breaks Overview effect when activated via keyboard shortcut

2023-06-03 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=470603

Nate Graham  changed:

   What|Removed |Added

   Severity|normal  |major

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

[frameworks-kxmlgui] [Bug 470574] Custom keyboard shortcuts are forgotten on quit in KF6-ported apps

2023-06-03 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=470574

Nate Graham  changed:

   What|Removed |Added

   Severity|normal  |major

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

[plasmashell] [Bug 470604] Desktop icon positions reset when plasmashell is restarted

2023-06-03 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=470604

Nate Graham  changed:

   What|Removed |Added

   Severity|normal  |major

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

[systemsettings] [Bug 470609] Updates KCM not built for Qt 6

2023-06-03 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=470609

Nate Graham  changed:

   What|Removed |Added

   Severity|normal  |grave

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

[systemsettings] [Bug 470611] Date & Time KCM not built for Qt 6

2023-06-03 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=470611

Nate Graham  changed:

   What|Removed |Added

   Severity|normal  |grave

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

[Discover] [Bug 470614] New: App list page sort order is reversed

2023-06-03 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=470614

Bug ID: 470614
   Summary: App list page sort order is reversed
Classification: Applications
   Product: Discover
   Version: master
  Platform: Other
OS: Linux
Status: REPORTED
  Keywords: qt6
  Severity: normal
  Priority: NOR
 Component: discover
  Assignee: plasma-b...@kde.org
  Reporter: n...@kde.org
CC: aleix...@kde.org
  Target Milestone: ---

See attached screenshot. The apps shown on top should be on the bottom. If I
scroll all the way to the bottom, I see the apps I expect to be on top.

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

[Discover] [Bug 470613] Discover's PackageKit backend barely works in Qt6

2023-06-03 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=470613

Nate Graham  changed:

   What|Removed |Added

Version|5.27.4  |master

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

[Discover] [Bug 470613] New: Discover's PackageKit backend barely works in Qt6

2023-06-03 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=470613

Bug ID: 470613
   Summary: Discover's PackageKit backend barely works in Qt6
Classification: Applications
   Product: Discover
   Version: 5.27.4
  Platform: Other
OS: Linux
Status: REPORTED
  Keywords: qt6
  Severity: grave
  Priority: NOR
 Component: PackageKit
  Assignee: plasma-b...@kde.org
  Reporter: n...@kde.org
CC: aleix...@kde.org
  Target Milestone: ---

With Discover built against Qt6, its PackageKit backend does not seem to work
properly. When I run `plasma-discover --backends packagekit`, I see only 3 apps
(see attached screenshot) and it never finds any updates. It is essentially
non-functional.

Note: this is using AppStream and AppStreamQt 1.0 built from source, so it
might be a Nate problem or an AppStream integration issue. But I'm not sure how
to debug that.

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

[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets

2023-06-03 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=470114

Bug Janitor Service  changed:

   What|Removed |Added

   Severity|crash   |wishlist

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

[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets

2023-06-03 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=470114

Bug Janitor Service  changed:

   What|Removed |Added

   Severity|wishlist|crash

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

[kwin] [Bug 156155] effects->grabKeyboard() disables global shortcuts

2023-06-03 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=156155

Nate Graham  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|REPORTED|RESOLVED
   Severity|wishlist|normal

--- Comment #15 from Nate Graham  ---
This has been working for a while.

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

[digikam] [Bug 470566] Metadata not updated

2023-06-03 Thread maison
https://bugs.kde.org/show_bug.cgi?id=470566

--- Comment #25 from maison  ---
No, I don’t use extra metadata files. Most of the photographs are JPEG,
therefore there is no need for xmp files since metadata can stay in the very
file.

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

[frameworks-kirigami] [Bug 470612] SwipeListItem action buttons lack icons in KF6

2023-06-03 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=470612

Nate Graham  changed:

   What|Removed |Added

   Severity|normal  |major

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

[frameworks-kirigami] [Bug 470612] New: SwipeListItem action buttons lack icons in KF6

2023-06-03 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=470612

Bug ID: 470612
   Summary: SwipeListItem action buttons lack icons in KF6
Classification: Frameworks and Libraries
   Product: frameworks-kirigami
   Version: Master
  Platform: Other
OS: Linux
Status: REPORTED
  Keywords: qt6
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdelibs-b...@kde.org
  Reporter: n...@kde.org
CC: m...@ratijas.tk, notm...@gmail.com
  Target Milestone: Not decided

Created attachment 159455
  --> https://bugs.kde.org/attachment.cgi?id=159455=edit
ToolButtons with no icons

See attached screenshot of the Virtual Desktops KCM.

SwipeListItem.qml has the following code to draw the toolbuttons:

> delegate: QQC2.ToolButton {
> icon.name: modelData.iconName !== "" ? modelData.iconName : ""
> icon.source: modelData.iconSource !== "" ? 
> modelData.iconSource : ""

Use of iconName seems fishy since that's no longer in Qt6, but I tried changing
it to icon.name and it didn't fix the problem.

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

[digikam] [Bug 470566] Metadata not updated

2023-06-03 Thread Maik Qualmann
https://bugs.kde.org/show_bug.cgi?id=470566

--- Comment #24 from Maik Qualmann  ---
Are sidecars possibly involved? Do you have sidecar reading enabled? Note that
GPS coordinates from XMP in digiKam take precedence over EXIF metadata.

Maik

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

[systemsettings] [Bug 470611] Date & Time KCM not built for Qt 6

2023-06-03 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=470611

Nate Graham  changed:

   What|Removed |Added

Summary|Date & Time not built for   |Date & Time KCM not built
   |Qt 6|for Qt 6

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

[systemsettings] [Bug 470611] New: Date & Time not built for Qt 6

2023-06-03 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=470611

Bug ID: 470611
   Summary: Date & Time not built for Qt 6
Classification: Applications
   Product: systemsettings
   Version: master
  Platform: Other
OS: Linux
Status: REPORTED
  Keywords: qt6
  Severity: normal
  Priority: NOR
 Component: kcm_clock
  Assignee: plasma-b...@kde.org
  Reporter: n...@kde.org
  Target Milestone: ---

Because it hasn't even been ported away from KDELibs4Support!

This is already known to various people, but I'm making a Bugzilla ticket for
it so we can track it among all other Qt6 issues in a central location.

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

[KScreen] [Bug 469160] kscreen-doctor segmentation faults in KIconLoader::~KIconLoader() when exiting

2023-06-03 Thread mooodyhunter
https://bugs.kde.org/show_bug.cgi?id=469160

--- Comment #5 from mooodyhun...@outlook.com  ---
Tested with `KSCREEN_BACKEND=KWayland` vs QScreen... and yes the problem has
never occurred with QScreen backend.

> i feel like our backtraces are maybe a red herring?

Yes so do I

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

[plasmashell] [Bug 470610] New: Not enough contrast between breeze and overview effect background

2023-06-03 Thread Andres Betts
https://bugs.kde.org/show_bug.cgi?id=470610

Bug ID: 470610
   Summary: Not enough contrast between breeze and overview effect
background
Classification: Plasma
   Product: plasmashell
   Version: master
  Platform: Other
OS: Other
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: anditosan1...@gmail.com
CC: k...@davidedmundson.co.uk
  Target Milestone: 1.0

Overview effect background should use more contrast to make windows more
visible. Notice the contrast ratio fail that we see in the attached images.
Also, for people with blurry vision, it's harder to make out what you see on
the screen when you have too much of one color.

Solutions are to change the background to a tint of black or use more
transparency.

Images:
https://ibb.co/2yyv1Qf
https://ibb.co/WyGgYfr

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

[systemsettings] [Bug 470609] New: Updates KCM not built for Qt 6

2023-06-03 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=470609

Bug ID: 470609
   Summary: Updates KCM not built for Qt 6
Classification: Applications
   Product: systemsettings
   Version: master
  Platform: Other
OS: Linux
Status: REPORTED
  Keywords: qt6
  Severity: normal
  Priority: NOR
 Component: kcm_updates
  Assignee: plasma-b...@kde.org
  Reporter: n...@kde.org
CC: aleix...@kde.org
  Target Milestone: ---

Because Discover's CMakeLists.txt file has this in it:

option(WITH_KCM "Build and install the updates KCM" ON)
if(WITH_KCM)
# add_subdirectory(kcm)
endif()

No comment explaining why, even! If I uncomment it and try to build, I get the
following error:

> Make Error at kcm/CMakeLists.txt:33 (kpackage_install_package):
>   Unknown CMake command "kpackage_install_package".

So I guess that's why.

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

[digikam] [Bug 470566] Metadata not updated

2023-06-03 Thread maison
https://bugs.kde.org/show_bug.cgi?id=470566

--- Comment #23 from maison  ---
Yes we are coming back to the same report: remember I used many ways to force
digiKam to update its data (probably all the possible imaginable ways).
Remember also that it did read the metadata after the external update since it
presents it in the panel. But it only half updates it, because there is no
globe and it confuses other functions (like update to iNaturalist), by letting
them think there is no geo‐location.
And the log provided didn’t seem to show where in digiKam the bug is located.

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

[digikam] [Bug 470566] Metadata not updated

2023-06-03 Thread Maik Qualmann
https://bugs.kde.org/show_bug.cgi?id=470566

--- Comment #22 from Maik Qualmann  ---
Reread the metadata in the item menu still doesn't show a geolocation icon? If
not, please create a log with this reread metadata action.

Note that the metadata option "Rescan file when files are modified" should be
enabled if you want digiKam's initial start scan to already update the GPS
information.

Maik

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

[krename] [Bug 470608] New: Doesn't build with podofo 0.10.0

2023-06-03 Thread Robert Scott
https://bugs.kde.org/show_bug.cgi?id=470608

Bug ID: 470608
   Summary: Doesn't build with podofo 0.10.0
Classification: Applications
   Product: krename
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: minor
  Priority: NOR
 Component: general
  Assignee: heiko.bec...@kde.org
  Reporter: b...@humanleg.org.uk
  Target Milestone: ---

Hi,

Just to let you know that podofo 0.10.0 has some API-breaking changes and
krename doesn't currently build with it. This wouldn't normally be important,
but the 0.9.x series has some open CVEs on it that don't look like they're
going to get fixes backported to them. There's some helpful porting information
here https://github.com/podofo/podofo/wiki/PoDoFo-API-migration-guide

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

[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets

2023-06-03 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=470114

Bug Janitor Service  changed:

   What|Removed |Added

   Severity|crash   |wishlist

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

[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets

2023-06-03 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=470114

Bug Janitor Service  changed:

   What|Removed |Added

   Severity|wishlist|crash

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

[digikam] [Bug 470566] Metadata not updated

2023-06-03 Thread maison
https://bugs.kde.org/show_bug.cgi?id=470566

--- Comment #21 from maison  ---
(In reply to Maik Qualmann from comment #14)
> When adding GPS information to an image, it is important to set all of the
> following tags: GPSLatitude, GPSLatitudeRef, GPSLongitude, GPSLongitudeRef,
> and GPSAltitude and GPSAltitudeRef if the altitude is known.
> ---
> 
> Also read this thread:
> 
> https://exiftool.org/forum/index.php?topic=8443.0
> 
> Without this information it is not a valid GPS. digiKam does nothing wrong
> here.

As an irrelevant reply for this side subject, I update my files externally with
exiftool because I geo‐locate them with a .nmea file which is not supported by
digiKam (only gpx, although it shouldn’t make any difference for digiKam if it
only transfers it to exiftool in the back). For someone who doesn’t know, nmea
is the most complete GPS capture, therefore all the possible information is
there and the relevant ones are then transferred to the photographs. OK, let’s
go back to the bug.

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

[kwin] [Bug 470607] New: When using Wobbly Windows on Plasma 6 Wayland with 200% scale, windows blur/de-scale when dragged

2023-06-03 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=470607

Bug ID: 470607
   Summary: When using Wobbly Windows on Plasma 6 Wayland with
200% scale, windows blur/de-scale when dragged
Classification: Plasma
   Product: kwin
   Version: master
  Platform: Other
OS: Linux
Status: REPORTED
  Keywords: qt6, regression, wayland
  Severity: minor
  Priority: NOR
 Component: effects-various
  Assignee: kwin-bugs-n...@kde.org
  Reporter: n...@kde.org
  Target Milestone: ---

STEPS TO REPRODUCE
1. Use Plasma 6 Wayland session
2. Turn on scaling; I use 200%
3. Turn on Wobbly Windows effect
4. Drag a window, or even just click and hold and don't move it anywhere

OBSERVED RESULT
The window contents stop being rendered at 200% scale while dragged; instead it
visibly blurs or pixelates

EXPECTED RESULT
Window contents remain drawn at high DPI while being dragged

ADDITIONAL INFORMATION
- Did not happen in the Plasma 6 Wayland session
- Does not happen in the Plasma 6 X11 session

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

[KScreen] [Bug 469160] kscreen-doctor segmentation faults in KIconLoader::~KIconLoader() when exiting

2023-06-03 Thread Ryan Rix
https://bugs.kde.org/show_bug.cgi?id=469160

--- Comment #4 from Ryan Rix  ---
```
~ $ KSCREEN_BACKEND=QScreen kscreen-doctor --json | jq .outputs[0].name
kscreen.qscreen: Screen added QScreen(0x12e4010, name="DSI-1") "DSI-1"
warning: queue 0x12f48e0 destroyed while proxies still attached:
  wl_display@1 still attached
"DSI-1"
~ $ KSCREEN_BACKEND=KWayland kscreen-doctor --json | jq .outputs[0].name
warning: queue 0x1bc6880 destroyed while proxies still attached:
  wl_display@1 still attached
corrupted double-linked list
parse error: Invalid numeric literal at line 1, column 8
```

seems like the issue is specific to the KWayland backend, i feel like our
backtraces are maybe a red herring?

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

[plasmashell] [Bug 470606] New: Save/discard/cancel dialogs for Plasma config dialogs are unstyled QML now

2023-06-03 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=470606

Bug ID: 470606
   Summary: Save/discard/cancel dialogs for Plasma config dialogs
are unstyled QML now
Classification: Plasma
   Product: plasmashell
   Version: master
  Platform: Other
OS: Linux
Status: REPORTED
  Keywords: qt6
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: n...@kde.org
CC: k...@davidedmundson.co.uk
  Target Milestone: 1.0

Created attachment 159453
  --> https://bugs.kde.org/attachment.cgi?id=159453=edit
Looks slightly sub-optimal

They look pretty bad. See attached screenshot. We'll need to style them at the
minimum, if not find a way to force them to go back to their prior
separate-window styling.

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

[digikam] [Bug 470566] Metadata not updated

2023-06-03 Thread maison
https://bugs.kde.org/show_bug.cgi?id=470566

--- Comment #20 from maison  ---
Created attachment 159454
  --> https://bugs.kde.org/attachment.cgi?id=159454=edit
Screen capture with a new digikam profile, therefore every file is new,
therefore file updates haven’t been performed, therefore the same “faulty”
files are not a problem at all

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

[digikam] [Bug 470566] Metadata not updated

2023-06-03 Thread maison
https://bugs.kde.org/show_bug.cgi?id=470566

--- Comment #19 from maison  ---
Created attachment 159452
  --> https://bugs.kde.org/attachment.cgi?id=159452=edit
Screen capture with main software profile, a file that digiKam doesn’t update
because it’s been updated externally

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

[digikam] [Bug 470566] Metadata not updated

2023-06-03 Thread maison
https://bugs.kde.org/show_bug.cgi?id=470566

maison  changed:

   What|Removed |Added

 Attachment #159451|0   |1
is obsolete||

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

[systemsettings] [Bug 470605] Firewall KCM broken in Plasma 6 due to use of QQC1 TableView, which doesn't exist anymore

2023-06-03 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=470605

Nate Graham  changed:

   What|Removed |Added

   Keywords||qt6

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

[systemsettings] [Bug 470605] New: Firewall KCM broken in Plasma 6 due to use of QQC1 TableView, which doesn't exist anymore

2023-06-03 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=470605

Bug ID: 470605
   Summary: Firewall KCM broken in Plasma 6 due to use of QQC1
TableView, which doesn't exist anymore
Classification: Applications
   Product: systemsettings
   Version: 5.27.4
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: grave
  Priority: NOR
 Component: kcm_firewall
  Assignee: plasma-b...@kde.org
  Reporter: n...@kde.org
CC: lucas.bia...@kde.org, tcanabr...@kde.org
  Target Milestone: ---

$ systemsettings kcm_firewall
"file:///home/nate/kde/usr6/share/kpackage/kcms/kcm_firewall/contents/ui/main.qml"
 
 "Error loading QML file.\n9: module \"QtQuick.Controls\" version 1.4 is not
installed\n"

It needs that import because it uses the QQC1 TableView. We need to port this
to the new QQC2 one in Qt 6--or something else.

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

[digikam] [Bug 470566] Metadata not updated

2023-06-03 Thread maison
https://bugs.kde.org/show_bug.cgi?id=470566

--- Comment #18 from maison  ---
Created attachment 159451
  --> https://bugs.kde.org/attachment.cgi?id=159451=edit
Screen capture with main software profile, a file that digiKam doesn’t update
because it’s been updated externally

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

[plasmashell] [Bug 470604] New: Desktop icon positions reset when plasmashell is restarted

2023-06-03 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=470604

Bug ID: 470604
   Summary: Desktop icon positions reset when plasmashell is
restarted
Classification: Plasma
   Product: plasmashell
   Version: master
  Platform: Other
OS: Linux
Status: REPORTED
  Keywords: qt6
  Severity: normal
  Priority: NOR
 Component: Folder
  Assignee: plasma-b...@kde.org
  Reporter: n...@kde.org
CC: h...@kde.org
  Target Milestone: 1.0

STEPS TO REPRODUCE
1. Have any desktop icons
2. Move one of them anywhere
3. Restart plasmashell or reboot the computer

OBSERVED RESULT
The icon you moved has returned to where it was before

EXPECTED RESULT
The icon stays where you moved it

ADDITIONAL INFORMATION
100% reproducible for me in all cases even with a simple single-screen setup;
so this isn't a complex multi-screen multi-containment issue. Saving desktop
icons positions simply appears to be 100% broken.

To my knowledge it never worked at all in Plasma 6, so it's a Qt 6 or porting
issue, not a recently introduced regression in Folder View itself.

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

[digikam] [Bug 470566] Metadata not updated

2023-06-03 Thread maison
https://bugs.kde.org/show_bug.cgi?id=470566

--- Comment #17 from maison  ---
Created attachment 159450
  --> https://bugs.kde.org/attachment.cgi?id=159450=edit
Screen capture with main software profile, a file that has been accepted

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

  1   2   3   >