[krita] [Bug 430468] New: Ctrl + Alt Color picker malfunction with Wacom tablet

[thiago]

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

Bug ID: 430468
   Summary: Ctrl + Alt Color picker malfunction with Wacom tablet
   Product: krita
   Version: 4.4.1
  Platform: Other
OS: Microsoft Windows
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Color Selectors
  Assignee: krita-bugs-n...@kde.org
  Reporter: tigs.a...@gmail.com
  Target Milestone: ---

SUMMARY
If I use the CTRL + Alt + color picker with the keyboard I get the correct pick
from only the current layer 
If I use the Wacom Tablet keys to press CTRL ALt it doesn't work. 

STEPS TO REPRODUCE

1. Assing both modifiers to the same key, select brush engine, press the tablet
key to call the color picker. 
2. Assing each modifiers to two different tablet keys, select brush engine and
press both keys at the same time.
3. I'm using Wacom Intuos Pro PTH-651.

OBSERVED RESULT
Result is inconsistent and any of the following may happen. 
1-After using the color picker the brush engine turns into a color picker
without any key press and I cannot continue to paint. 
2- Pressing both keys fails to call the corret picker and I pick the combined
color as if only CRTL was pressed.
3- The correct color picker shows up but it after that pressing only CTRL will
call a "color picker from current layer only" tool as if I'm pressing both keys
at the same time.


SOFTWARE/OS VERSIONS
Windows: 10 pro

ADDITIONAL INFORMATION

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

[krita] [Bug 430555] New: Fail preview G'Mic "Color Presets"

[thiago]

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

Bug ID: 430555
   Summary: Fail preview G'Mic "Color Presets"
   Product: krita
   Version: 4.4.1
  Platform: Other
OS: Microsoft Windows
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: G'Mic for Krita
  Assignee: krita-bugs-n...@kde.org
  Reporter: tigs.a...@gmail.com
  Target Milestone: ---

Created attachment 134194
  --> https://bugs.kde.org/attachment.cgi?id=134194&action=edit
Screenshot with error details provided by Gmic

SUMMARY
Fail preview "Color Presets"

STEPS TO REPRODUCE
1. Open G'Mic
2. Select the "Color" then "Color Preset" filter.
3. Select one of the following Lut Packs : "PIXLS.US", "Alex Jordan" or
"Others".
4. Other Lut Packs except of these three work fine.
5. Restarting Krita failed to resolve issue.



OBSERVED RESULT
No preview is displayed

SOFTWARE/OS VERSIONS
Windows: 10 pro

ADDITIONAL INFORMATION
Screenshot error report provided by the program is the same on all failed Lut
packs

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

[krita] [Bug 397427] New: crash while painting on canvas

[thiago]

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

Bug ID: 397427
   Summary: crash while painting on canvas
   Product: krita
   Version: 4.1.1
  Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: General
  Assignee: krita-bugs-n...@kde.org
  Reporter: tigs.a...@gmail.com
  Target Milestone: ---

I am having several crashes but I can`t recreate them. This one happened when I
was using a basic flow brush on canvas. If I can be of further assist please
contact me.

Windows 10 updated yesterday.
Configured to use integrated graphics card. 
After the crash I changed to a dedicated card to see if it will solve the
recurrent crashes.

---

Error occurred on Monday, August 13, 2018 at 09:05:05.

krita.exe caused an Access Violation at location 7FFD5485436F in module
msvcrt.dll Writing to location .

AddrPC   Params
7FFD5485436F  7216EB30  
msvcrt.dll!0x7436f memcpy+0xaf
7FFD16DF2D25 72DD2C18 0001 72DD2C00 
libkritaui.dll!0x162d25 KisTextureTile::update+0x7a5
7FFD16DF0987 0040 0040 0019 
libkritaui.dll!0x160987 KisOpenGLImageTextures::recalculateCache+0xe7
7FFD16DE25FF 0040 0005 7FFD26623298 
libkritaui.dll!0x1525ff KisOpenGLCanvas2::updateCanvasProjection+0x4f
7FFD16C92C07 005FB950 0001 005FB9B0 
libkritaui.dll!0x2c07 KisCanvasWidgetBase::updateCanvasProjection+0xe7
7FFD16DEB821 05139BF5CC74 005FBA58  
libkritaui.dll!0x15b821 KisOpenGLCanvas2::updateCanvasProjection+0x11
7FFD16C99C6B 5A31CFD0 72585540 0061005FBB00 
libkritaui.dll!0x9c6b KisCanvas2::updateCanvasProjection+0x9b
7FFD16FE98D5 5F86B230  72016BA0 
libkritaui.dll!0x3598d5 KisCanvas2::qt_static_metacall+0x105
7FFD262DB42A 5A7248E8 5A31CFD0 5A7248E8 
Qt5Core.dll!0x23b42a QMetaObject::activate+0x7fa
7FFD38858721 58E7C4B0 7FFD262B96A9 6027CA50 
libkritaglobal.dll!0x18721 KisSignalCompressor::start+0xc1
7FFD262DC1AA 005FFBB0  0001 
Qt5Core.dll!0x23c1aa QObject::event+0xda
7FFD19A67B5C 02853CD0 7FFD56641003 71FC0D10 
Qt5Widgets.dll!0x7b5c QApplicationPrivate::notify_helper+0x9c
7FFD19A6EDD0  7FFD260D0DFF 6011E9F0 
Qt5Widgets.dll!0xedd0 QApplication::notify+0x2f0
7FFD16F11E66 0008 00040001 5A6C48A0 
libkritaui.dll!0x281e66 KisApplication::notify+0x16
7FFD262B0778    
Qt5Core.dll!0x210778 QCoreApplication::notifyInternal2+0x198
7FFD262B6375 011E82F0   
Qt5Core.dll!0x216375 QCoreApplicationPrivate::sendPostedEvents+0x1d5
6A8DEF4E 0401 001B0640  
qwindows.dll!0x5ef4e qt_plugin_instance+0x28fe
7FFD26308016 8012 0001  
Qt5Core.dll!0x268016 QEventDispatcherWin32Private::sendTimerEvent+0x666
7FFD56636CC1  7FFD26307AE0 001B0640 
USER32.dll!0x16cc1 UserCallWinProcCheckWow+0x2c1
7FFD56636693 005FC590  005FC590 
USER32.dll!0x16693 DispatchMessageWorker+0x1c3
7FFD2630730B 0286E250 0024 006B09B0 
Qt5Core.dll!0x26730b QEventDispatcherWin32::processEvents+0x5cb
6A8DEF35 0080 0014 5E5E1250 
qwindows.dll!0x5ef35 qt_plugin_instance+0x28e5
7FFD262AEE5F  0001 7FFD26407100 
Qt5Core.dll!0x20ee5f QEventLoop::exec+0x13f
7FFD262B77B7 005FFC00 005FFBB0 005FFB90 
Qt5Core.dll!0x2177b7 QCoreApplication::exec+0x77
000140006641 0001 006B0510 000140FB3980 
krita.exe!0x6641 main+0x17d1
0001400013F7    
krita.exe!0x13f7 __tmainCRTStartup+0x247
0001400014FB    
krita.exe!0x14fb WinMainCRTStartup+0x1b
7FFD564B3034    
KERNEL32.DLL!0x13034 BaseThreadInitThunk+0x14
7FFD56EB1431    
ntdll.dll!0x71431 RtlUserThreadStart+0x21

00014000-000140FC3000 krita.exe
7FFD56E4-7FFD57021000 ntdll.dll 6.2.17134.165
7FFD564A-7FFD56552000 KERNEL32.DLL  6.2.17134.1
7FFD5321-7FFD53483000 KERNELBASE.dll6.2.17134.165
7FFD547E-7FFD5487E000 msvcrt.dll7.0.17134.1
7FFD2B2A-7FFD2B3C1000 libkritawidgetutils.dll
7FFD3884-7FFD38879000 libkritaglobal.dll
6144-

[krita] [Bug 397432] New: OVERVIEW LAG

[thiago]

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

Bug ID: 397432
   Summary: OVERVIEW LAG
   Product: krita
   Version: 4.1.1
  Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: Instant Preview
  Assignee: krita-bugs-n...@kde.org
  Reporter: tigs.a...@gmail.com
  Target Milestone: ---

Overview docker has a significant lag to update. About 2 seconds on a picture
1600 x 1200 pixels. I'm not having other performance issues in Krita. This
happens while changing layer visibility or on brush strokes. While painting 
 sometimes I have to toggle visibility several times to check if the changes
look good so it bothers a little.
 I tried to send the performance log but couldn`t find it.

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

[krita] [Bug 397427] crash while painting on canvas

[thiago]

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

--- Comment #2 from thiago  ---
Canvas Graphics acceleration: checked.
Render: Auto(Open GL)
Scaling: High quality Filtering
Use texture buffer: checked

Before the graphics card change I had 5 crashes in three days. After I only
used for a day but no crashes so far. It seems much more stabe, maybe it is
some incompatibility with the inboard card.

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

[krita] [Bug 382110] Fill tool does not work if brush eraser is selected

[thiago]

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

thiago  changed:

   What|Removed |Added

 CC||tigs.a...@gmail.com

--- Comment #4 from thiago  ---
(In reply to Boudewijn Rempt from comment #3)
> Maybe we should bite the bullet and do for blending mode what I just did for
> opacity; make it a per-tool setting.

I think that would be a nice UI polish. Most people would expect the Fill Tool
to fill with color instead of erasing everything.

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

[krita] [Bug 393116] New: Krita 4.1 fails to load 3.0 build in brush presets

[thiago]

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

Bug ID: 393116
   Summary: Krita 4.1 fails to load 3.0 build in brush presets
   Product: krita
   Version: 4.1
  Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Resource Management
  Assignee: krita-bugs-n...@kde.org
  Reporter: tigs.a...@gmail.com
  Target Milestone: ---

Resource manager fail to load 3.0 brush bundle presets. It does not become an
active bundle and automatically goes back to inactive . This happened in two
different computers, versions 4.0 and 4.1

Another thing I noticed that may help is that if you inspect the resources
contained in each bundle they apear different if it is active or not. 

While on the active side 4.0 bundle appears to have more resource and 3.0
appears to have less.

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

[krita] [Bug 393116] Krita 4.1 fails to load 3.0 build in brush presets

[thiago]

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

--- Comment #1 from thiago  ---
Update: Somehow, without any action, 3.0 brushes are now active. No Idea how or
why that happened. If I can be of assistance please contact me.

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

[krita] [Bug 393116] Krita 4.1 fails to load 3.0 build in brush presets

[thiago]

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

--- Comment #3 from thiago  ---
Not working again.

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

[krita] [Bug 397427] crash while painting on canvas

[thiago]

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

thiago  changed:

   What|Removed |Added

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

--- Comment #4 from thiago  ---
Canvas Graphics acceleration: checked.
Render: Auto(Open GL)
Scaling: High quality Filtering
Use texture buffer: checked

Before the graphics card change I had 5 crashes in three days. After I only
used for a day but no crashes so far. It seems much more stabe, maybe it is
some incompatibility with the inboard card.

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

[krita] [Bug 397427] crash while painting on canvas

[thiago]

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

--- Comment #7 from thiago  ---
Since I discovered I wasn't using the right video card this issue is no longer
a problem for me but it was severe enough that I almost gave up on krita. This
is a serious issue for new users. Krita should auto select the dedicated video
card or give a warning during instalation for users to do so.

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

[krita] [Bug 397427] crash while painting on canvas

[thiago]

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

--- Comment #10 from thiago  ---
INTEL(R) HD GRAPHICS 4600
DRIVER 10.18.15.4248

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

[kdenlive] [Bug 374040] New: Problms in Rendering of Kdenlive with Ubuntu 2016

[Thiago]

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

Bug ID: 374040
   Summary: Problms in Rendering of Kdenlive with Ubuntu 2016
   Product: kdenlive
   Version: unspecified
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Video Display & Export
  Assignee: j...@kdenlive.org
  Reporter: thiago_...@hotmail.com
  Target Milestone: ---

Hello folks recently I made a video of 20 minutes and when I tried to render to
mp4 .. aparesceu a warning of redering Crashed .. I did not understand.
And it has locked and closed constantly, I use many photo files along with mp4
files for video mounts.
  My question is what maximum of minutes that Kdenlive supports. I currently do
videos of 7 minutes and I have no problems

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

[kdenlive] [Bug 374040] Problms in Rendering of Kdenlive with Ubuntu 2016

[Thiago]

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

Thiago  changed:

   What|Removed |Added

URL||https://www.youtube.com/wat
   ||ch?v=xw6wJAWhXJA

--- Comment #1 from Thiago  ---
Produced Kdenlive
https://www.youtube.com/watch?v=xw6wJAWhXJA

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

[krita] [Bug 382110] New: Fill tool does not work if brush eraser is selected

[Thiago]

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

Bug ID: 382110
   Summary: Fill tool does not work if brush eraser is selected
   Product: krita
   Version: 3.1.4
  Platform: Other
OS: MS Windows
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Brush engine
  Assignee: krita-bugs-n...@kde.org
  Reporter: tigs...@gmail.com
  Target Milestone: ---

Fill tool, Fill with foreground color and Fill with background color doesn't
work if the brush tool is set to eraser mode. 

Any eraser preset or any brush with the eraser mode turned on blocks the Fill
Tool functionality.

Actually it does not block the tool, it fills the entire canvas with an eraser
and deletes everything. That could be useful but It is not intuitive nor
productive for the fill tool to behave that way, we already use the delete
shortcut for that. 

Reverting the Brush to normal mode fixes the problem.

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

[krita] [Bug 382110] Fill tool does not work if brush eraser is selected

[Thiago]

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

--- Comment #2 from Thiago  ---
I guess a warning is enough. It took me a while to understand what was
happening as the canvas was already transparent and I had no feedback. 

On a more important topic I had a couple crashes, wish I could help but they
were random and I don't know how to report. Is there a tutorial for that? To
deal with this issue many programs have an option to automatically send a
report with the data you need for debugging.

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

[plasmashell] [Bug 449163] Plasma panel visually freezes after some time under Wayland

[Thiago Sueto]

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

Thiago Sueto  changed:

   What|Removed |Added

 CC||herzensch...@gmail.com

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

[Haruna] [Bug 442132] 4k videos are choppy on Wayland

[Thiago Sueto]

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

--- Comment #3 from Thiago Sueto  ---
Hmm, after taking a look at the VLC comment 

https://github.com/mpv-player/mpv/issues/9417#issuecomment-963132782

it seemed to me like it might be a Qt issue, and I found this:

Suboptimal playback performance with 4K@60fps when using QML MediaPlayer +
VAAPI HW decoding

https://bugreports.qt.io/browse/QTBUG-79301 , closed without any comments. It's
awfully similar, but I'm not sure it's relevant, Haruna doesn't seem to use
QtMultimedia/MediaPlayer.

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

[systemsettings] [Bug 448568] Overview effect can be selected in the screen edges menu even if the effect is disabled

[Thiago Sueto]

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

Thiago Sueto  changed:

   What|Removed |Added

 CC||herzensch...@gmail.com

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

[dolphin] [Bug 421837] Dolphin crash after accidentally renaming an SVG to a nameless file

[Thiago Sueto]

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

Thiago Sueto  changed:

   What|Removed |Added

 CC||herzensch...@gmail.com
Summary|Dolphin se cerró cuando |Dolphin crash after
   |renombraba un archivo svg   |accidentally renaming an
   ||SVG to a nameless file

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

[frameworks-kirigami] [Bug 454999] New: FormLayout adds an extra margin when used in KCMs

[Thiago Sueto]

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

Bug ID: 454999
   Summary: FormLayout adds an extra margin when used in KCMs
   Product: frameworks-kirigami
   Version: Master
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: notm...@gmail.com
  Reporter: herzensch...@gmail.com
  Target Milestone: Not decided

See this thread:
https://invent.kde.org/plasma/plasma-desktop/-/merge_requests/770#note_391758

Relevant code:
https://invent.kde.org/plasma/plasma-desktop/-/blob/work/thiago/morecomponents/kcms/componentchooser/package/contents/ui/main.qml

Top padding by default looks like this:
https://invent.kde.org/plasma/plasma-desktop/uploads/dc4b35dd87c75f52b6d23b5b99ae6c13/Screenshot_20220204_005022.png

When it should look like this:
https://invent.kde.org/plasma/plasma-desktop/uploads/7a4fd46b33211bdd7af2f40a1593d780/Screenshot_20220204_005503.png

Analogously to the Notifications KCM:
https://invent.kde.org/plasma/plasma-desktop/uploads/fa8ec0fb5ab72eb3af898aa69810607e/Screenshot_20220204_005101.png

Code example taken from MR:

```
import QtQuick 2.12
import QtQuick.Layouts 1.15

import org.kde.kirigami 2.7 as Kirigami
import org.kde.kcm 1.5 as KCM

KCM.SimpleKCM {
topPadding: 0
bottomPadding: 0
Kirigami.FormLayout {
id: form

readonly property int longestComboBox:
Math.max(browserCombo.implicitWidth,
   
fileManagerCombo.implicitWidth,
   
textEditorCombo.implicitWidth,
   
pdfViewerCombo.implicitWidth,
   
imageViewerCombo.implicitWidth,
   
musicPlayerCombo.implicitWidth,
   
videoPlayerCombo.implicitWidth,
   
emailCombo.implicitWidth,
   
archiveCombo.implicitWidth,
   
terminalCombo.implicitWidth,
mapCombo.implicitWidth,
   
dialerCombo.implicitWidth)
Item {
Kirigami.FormData.label: i18n("Internet")
Kirigami.FormData.isSection: true
}
ComponentComboBox {
id: browserCombo
Layout.preferredWidth: form.longestComboBox
component: kcm.browsers
label: i18n("Web browser:")
}
[...extracodehere...]
}
```

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

[kdeplasma-addons] [Bug 465553] New: konsoleprofiles widget does not show default readonly profile as an option, only custom ones

[Thiago Sueto]

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

Bug ID: 465553
   Summary: konsoleprofiles widget does not show default readonly
profile as an option, only custom ones
Classification: Plasma
   Product: kdeplasma-addons
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: konsoleprofiles
  Assignee: plasma-b...@kde.org
  Reporter: herzensch...@gmail.com
  Target Milestone: ---

SUMMARY

The widget's list of Konsole profiles does not show the Built-in profile as an
option.

STEPS TO REPRODUCE

1. Add a widget to the panel
2. Click it

OBSERVED RESULT

No profile named "Built-in".

EXPECTED RESULT

The "Built-in" profile should show up.

SOFTWARE/OS VERSIONS
Operating System: openSUSE MicroOS 20230208
KDE Plasma Version: 5.26.5
KDE Frameworks Version: 5.102.0
Qt Version: 5.15.8
Kernel Version: 6.1.10-1-default (64-bit)
Graphics Platform: Wayland
Processors: 4 × Intel® Core™ i5-7200U CPU @ 2.50GHz
Memory: 7.6 GiB of RAM
Graphics Processor: Mesa Intel® HD Graphics 620

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

[frameworks-kconfig] [Bug 460260] On a multi screen setup on Wayland, KDE app windows do not remember the size they had if the primary monitor is not the leftmost one.

[Thiago Sueto]

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

Thiago Sueto  changed:

   What|Removed |Added

 CC||herzensch...@gmail.com

--- Comment #16 from Thiago Sueto  ---
The exact behavior of this bug happens like the following for me:

=
1: Primary monitor on the right : Left is external screen, Right is laptop
screen
Resize in right and close in right = FORGOTTEN
Resize in right and close in left = REMEMBER
Resize in left and close in left = REMEMBER
Resize in left and close in right = REMEMBER

2: Primary monitor on the left : Left is external screen, Right is laptop
screen
Resize in right and close in right = FORGOTTEN
Resize in right and close in left = REMEMBER
Resize in left and close in left = REMEMBER
Resize in left and close in right = REMEMBER

---

1: Primary monitor on the right : Left is laptop screen, Right is external
monitor
Resize in right and close in right = FORGOTTEN
Resize in right and close in left = REMEMBER
Resize in left and close in left = REMEMBER
Resize in left and close in right = REMEMBER

2: Primary monitor on the left : Left is laptop screen, Right is external
monitor
Resize in right and close in right = FORGOTTEN
Resize in right and close in left = REMEMBER
Resize in left and close in left = REMEMBER
Resize in left and close in right = REMEMBER
=

I rebooted every time I changed the primary screen or moved the screen to the
other side.

The conclusion I arrive here is that primary monitor is indeed not what
matters, like deafpolygon noted. Additionally, whether the screen is internal
or external does not matter. In my case, the bug only happens when you resize
and close the app in the right screen, no matter which one it is.

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

[Elisa] [Bug 465716] New: Support for synchronized lyrics file in the same folder

[Thiago Sueto]

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

Bug ID: 465716
   Summary: Support for synchronized lyrics file in the same
folder
Classification: Applications
   Product: Elisa
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: matthieu_gall...@yahoo.fr
  Reporter: herzensch...@gmail.com
  Target Milestone: ---

Currently Elisa already does synchronized lyrics that are embedded into the
Lyrics id3 tag.

Apparently the same formatting used for synchronized lyrics in the Lyrics id3
tag is used for LRC files: https://en.wikipedia.org/wiki/LRC_(file_format), so
if you copy the contents of an LRC file and put it into the song metadata with
Kid3 it shows up in Elisa.

Usually, when a music player supports LRC files, you just need to have an LRC
file in the same folder as the song. It would be nice if Elisa supported this.

If you want to test this with an LRC file, you can use Android's LRC Editor on
a certain song or I can supply one.

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

[kwin] [Bug 461399] In overview effect, Virtual Desktops are shown as flattened arrangement, but spatial arrangement is preserved from the perspective of using the touchpad switching gestures

[Thiago Sueto]

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

Thiago Sueto  changed:

   What|Removed |Added

 CC||herzensch...@gmail.com

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

[systemsettings] [Bug 466325] New: No way to enable/disable apps running in the background

[Thiago Sueto]

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

Bug ID: 466325
   Summary: No way to enable/disable apps running in the
background
Classification: Applications
   Product: systemsettings
   Version: 5.27.0
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: kcm_flatpak
  Assignee: plasma-b...@kde.org
  Reporter: herzensch...@gmail.com
CC: joshiesuha...@gmail.com
  Target Milestone: ---

When a flatpak app is running in the background (e.g. as a tray icon once the
main window is closed) on Wayland, a notification shows up asking if the user
wants to keep it running in the background or not. You can test this with
Telegram or KSnip, a notification shows up once you press the X close button
and it goes to the tray.

If the user disallows the app from running in the background, they can easily
revert this setting using Flatseal (it's one of the last options at the bottom
of the page), but they cannot with the Flatpak KCM.

This is particularly problematic when combined with a separate but destructive
issue where applications notify they're running in the background when they're
actually not (this is the case with Firefox, for instance), so the notification
appears when the window is still in the foreground. Once the user disallows
Firefox from running in the background, the moment they try to open it, it
closes again, making it impossible to use.

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

[docs.kde.org] [Bug 467029] Web-Page part of Website is down! [ 404 Error ]

[Thiago Sueto]

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

Thiago Sueto  changed:

   What|Removed |Added

 CC||herzensch...@gmail.com

--- Comment #2 from Thiago Sueto  ---
develop.kde.org got some major restructuring (it's now flatter and we have no
Use, Extend, Build and Deploy, and this bug report was made after the fact.

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

[systemsettings] [Bug 455394] Vertically-arranged monitors' alignment is off by one pixel

[Thiago Macieira]

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

--- Comment #13 from Thiago Macieira  ---
I've just seen this again in 5.27.2

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

[systemsettings] [Bug 455394] Vertically-arranged monitors' alignment is off by one pixel

[Thiago Macieira]

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

Thiago Macieira  changed:

   What|Removed |Added

 Status|RESOLVED|REOPENED
 Resolution|FIXED   |---

--- Comment #14 from Thiago Macieira  ---
As kscreen set them:

Screen 0: minimum 320 x 200, current 7679 x 2400, maximum 16384 x 16384
eDP-1 connected primary 3840x2400+0+0 (normal left inverted right x axis y
axis) 288mm x 180mm
   3840x2400 59.99*+  48.00  
DP-3-2 connected 3840x2160+3839+0 (normal left inverted right x axis y axis)
597mm x 336mm
   3840x2160 29.98* 

After xrandr --output DP-3-2 --right-of eDP-1:

Screen 0: minimum 320 x 200, current 7680 x 2400, maximum 16384 x 16384
eDP-1 connected primary 3840x2400+0+0 (normal left inverted right x axis y
axis) 288mm x 180mm
   3840x2400 59.99*+  48.00  
DP-3-2 connected 3840x2160+3840+0 (normal left inverted right x axis y axis)
597mm x 336mm
   3840x2160 29.98*

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

[frameworks-kdoctools] [Bug 467128] New: kde-no-chunk.xsl and kde-web.xsl do not work

[Thiago Sueto]

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

Bug ID: 467128
   Summary: kde-no-chunk.xsl and kde-web.xsl do not work
Classification: Frameworks and Libraries
   Product: frameworks-kdoctools
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kde-doc-engl...@kde.org
  Reporter: herzensch...@gmail.com
CC: kdelibs-b...@kde.org
  Target Milestone: ---

Manually setting the --stylesheet used for meinproc5 to these two styles does
not work, the resulting content does not display properly.

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

[frameworks-kwallet] [Bug 458085] Wallet system takes about 1 minute to start

[Thiago Macieira]

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

Thiago Macieira  changed:

   What|Removed |Added

 CC||thi...@kde.org

--- Comment #57 from Thiago Macieira  ---
I disagree that no-allow-external-cache is a proper solution. It's a
workaround, but it prevents one from using GPG/pinentry for other tasks and
saving the credential cache in the KWallet-provided Secret Service. It's
probably the least-intrusive option because gpg-agent does caching on its own
anyway, but it's not a solution.

The solution would be to make kwalletd be able to answer this query coming from
pinentry. To do that, make the kwalletd code asking for the unlocking of GPG
wallet not block - if there's an asynchronous API for that, you can use it,
otherwise move the entire workload to a separate thread. QtDBus is already
threaded, so the query was received by the the process; however, the thread
owning the QObject that would've answered the call was blocked and didn't
answer.

You need to make sure this doesn't loop again: make sure this Secret Service
call isn't going to trigger another call back to pinentry and thus loop again.

This has the added benefit that kwalletd isn't frozen while pinentry is waiting
for the user to type the password. I've seen before that applications waiting
for kwalletd also freeze if kwalletd won't answer, though this particular
change may not affect the applications that are freezing, if kwalletd can't
answer the call in the first place. This benefit comes with its drawback
though: kwalletd needs to know that it's already waiting for the wallet to open
and queue the reply going back to the application.

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

[frameworks-kwallet] [Bug 458085] Wallet system takes about 1 minute to start

[Thiago Macieira]

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

--- Comment #59 from Thiago Macieira  ---
> @Thiago, the issue is bigger than just synchronous vs asynchronous. The
> issue is that if you use a GPG wallet, with Secret Service provided by
> KWallet, and while allowing pinentry to read the key passphrase from Secret
> Service, what ends up happening is that KWallet asks for the key passphrase
> from itself instead of the user. It's like trying to unlock a safe with the
> key that's locked inside that same safe. Not going to work. Even if you
> make this asynchronous, you'll just end up with an infinite recursion.

I understand that we ended up with KWallet asking itself for the password. But
the fact is that if the query was asynchronous, then pinentry would have got
its answer instead of timing out, and then would have prompted the use for the
password. Or maybe not, maybe KWallet is storing the cached answer in memory
and would have provided it to pinentry. But do note I talked about KWallet
ensuring it doesn't recurse infinitely, which is why we'd need to figure out if
where this particular password could be saved if it is provided to KWallet;
refusing to store it is a way to break the chain.

I'm not saying it's easy to implement this.

Your idea from comment 40 -- to tell gpg-agent that we want a password with
no-external-cache -- is a solution too. Probably the Right Solution (with
capital R and S).

But not the way you described it. Modifying ~/.gnupg/gpg-agent.conf is not
acceptable, because it's not atomic. Other passwords may be getting requested
at the same time as KWallet is trying to open. In fact, if we are trying to
open the wallet now because something wants a stored password, then it stands
to reason another program could be trying to do the same. Moreover, because
we're waiting for user interaction, the time during which the gpg-agent.conf
file is modified is measured in human time.

Therefore, this solution requires that we inform gpg-agent that we want a
no-external-auth-cache answer for THIS query only and that it inform the
pinentry tool that it shouldn't query the external auth cache. That requires
those two tools to be updated and their updates deployed; plus probably
libgpgme too. It's probably the right thing to do, so we should interact with
upstream to get them to implement this.

But if there is a KWallet-only solution, we should investigate it.

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

[frameworks-kwallet] [Bug 458085] Wallet system takes about 1 minute to start

[Thiago Macieira]

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

--- Comment #61 from Thiago Macieira  ---
(In reply to michaelk83 from comment #60)
> Pinentry is asking for the passphrase through the same Secret Service API as
> any other client (see comment 31). KWallet has no way to tell it apart from
> any other client, so can't handle it differently. As far as KWallet can tell
> at this point, the passphrase that pinentry wants is inside the same wallet
> (but it's not).

That is understood. I did say that my idea would only work if there were a way
to break the loop. If there isn't, then it doesn't help.

> Currently pinentry's request blocks in the `OpenSession` call because
> KWallet is still waiting for GPG to unlock the wallet (for the original
> request of some other client app). If this was asynchronous, what would
> happen is KWallet would try to unlock the wallet a 2nd time to look for the
> passphrase there, which would invoke GPG and pinentry a 2nd time, which
> would ask KWallet again, and so on and on and on.

Only if it got coded this poorly. A proper implementation would realise that
the request for GPG to open the wallet is still pending and queue the request
to be answered when the wallet got opened. So the loop breaks, but doesn't
solve the problem.

> > But not the way you described it. Modifying ~/.gnupg/gpg-agent.conf is not
> > acceptable, because it's not atomic.
> 
> Yes, as I said, there could be timing issues and maybe other problems. That
> patch is still just an automated and time-limited workaround.
> I'm not aware of any other way to tell pinentry to not use the external
> cache, other than maybe by implementing the Assuan protocol.

It also wouldn't work if I had my ~/.gnupg directory protected against unwanted
reads and writes.

I really think we need to talk to the gpg-agent/pinentry folks.

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

[frameworks-kwallet] [Bug 458085] Wallet system takes about 1 minute to start

[Thiago Macieira]

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

--- Comment #63 from Thiago Macieira  ---
(In reply to michaelk83 from comment #62)
> > It also wouldn't work if I had my ~/.gnupg directory protected against
> > unwanted reads and writes.
> 
> The proposed patch doesn't attempt to write to ~/.gnupg directly. It makes
> calls to gpgconf.

Does it support setting ephemeral settings not saved to disk? I didn't see that
in the documentation.

Otherwise, you're just asking to write to disk, only indirectly. It's like
replacing the KConfig classes with a subprocess call to kwriteconfig5 and say.

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

[frameworks-kwallet] [Bug 458085] Wallet system takes about 1 minute to start

[Thiago Macieira]

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

--- Comment #65 from Thiago Macieira  ---
> I don't know, but if you configure your system such that gpgconf can't do
> its job, then you have a broken configuration, IMO.
> If you really want ephemeral settings without writing to disk, you can mount
> them with overlayfs. But that's really an edge case.

gpgconf can do its job when *I* want to run it. It's a tool for me, not for
other applications. KWallet shouldn't change my GPG settings behind my back.

In any case, this doesn't prevent a race condition anyway. How about we try to
fix it the right way first?

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

[Qt/KDE Flatpak Runtime] [Bug 420529] "Background activity" notification appears while an app installed via flatpak/flathub is running

[Thiago Sueto]

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

Thiago Sueto  changed:

   What|Removed |Added

 CC||herzensch...@gmail.com

--- Comment #22 from Thiago Sueto  ---
https://www.reddit.com/r/kde/comments/11ul75n/comment/jcrlzdu/?utm_source=share&utm_medium=web2x&context=3

> I once had this popup on one of my applications packaged as Flatpak as well.
> From my testing on KDE it seems to get triggered when an application - 
> launched as Flatpak loses focus and / or has a tray icon - doesn't implement 
> the xdg background portal.
> As for my app, I implemented xdg background portal using libportal and that 
> popup went away.

This indeed seems to happen on an individual app basis. Telegram and KSnip work
correctly and only trigger the notification when they're *closed* to the tray.
Other apps do not work correctly.

Additionally, this bug can lead to destructive behavior that I found out in the
MicroOS Desktop channel: Firefox triggers this notification, and if the user
clicks on Learn More and then select the option to stop it from running in the
background, Firefox simply closes, and every time it gets opened again, it's
immediately closed.

The only way to revert the operation is by using Flatseal, going to the app's
Portal settings and either clicking the cleanup/undo icon or allowing the app
to run in the background. The Flatpak KCM lacks these settings, last I saw. So
this is hard for users to find out, and if they cannot find this, they become
incapable of reopening the application.

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

[konsole] [Bug 468391] New: Konsole should be able to switch to/from a distrobox profile

[Thiago Sueto]

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

Bug ID: 468391
   Summary: Konsole should be able to switch to/from a distrobox
profile
Classification: Applications
   Product: konsole
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: konsole-de...@kde.org
  Reporter: herzensch...@gmail.com
  Target Milestone: ---

SUMMARY
Distrobox is a tool used to run podman/docker containers and integrate them in
userspace.

See: https://github.com/89luca89/distrobox

It comes in MicroOS Desktop by default and I think also Fedora Kinoite. In
these distros, you're expected to never install anything to your host root,
only to install userspace applications as flatpaks and using terminal tools
from inside a distrobox container.

One cool thing people can do is to make a custom terminal profile that runs and
enters a distrobox container, then setting it as the default profile, so it's
immediately ready as soon as you open your terminal. I use this with both
Konsole and Yakuake.

See:
https://github.com/89luca89/distrobox/blob/main/docs/useful_tips.md#using-distrobox-as-main-cli

By default, using a distrobox profile breaks the Konsole SSH plugin, but I
managed to work around this by enveloping distrobox in a shell (I use fish in
the container):

/usr/bin/bash -c "distrobox enter mycontainer -- fish --login"

So the only thing that I think is missing from the UX is being able to switch
from/to distrobox profiles, but this doesn't work. Right clicking and
attempting to change the profile does nothing.

This only works if I go to File -> New Tab -> select a different profile, but
this sounds more like a workaround for the fact Konsole can't switch to/from
distrobox.

FWIW, GNOME Terminal isn't able to switch from/to distrobox either, and it
doesn't even have an option to create a new tab running a specific profile, so
Konsole is way better off than it. But it would be great to have this
functionality.

STEPS TO REPRODUCE
1. Install podman + distrobox
2. Create a distrobox container with distrobox create
3. Create a Konsole profile that runs /usr/bin/distrobox enter
4. Right click the terminal and attempt to switch to a distrobox profile

OR

3. Create a Konsole profile that runs /usr/bin/distrobox enter and make it the
default
4. Right click the terminal and attempt to switch away from the distrobox
profile

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

[konsole] [Bug 468393] New: Experimental Konsole flatpak: cannot open a new tab with a different profile

[Thiago Sueto]

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

Bug ID: 468393
   Summary: Experimental Konsole flatpak: cannot open a new tab
with a different profile
Classification: Applications
   Product: konsole
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: konsole-de...@kde.org
  Reporter: herzensch...@gmail.com
  Target Milestone: ---

In the kdeapps flatpak repository, there's an experimental Konsole flatpak that
can be tested.

It runs the host shell just fine, possibly because of
https://invent.kde.org/packaging/flatpak-kde-applications/-/commit/3806b155aace455be639a2cf61d5be271ec24bdf.

It cannot open new tabs with a different profile when I go to File -> New Tab
-> select profile.

This works with non-flatpak Konsole/Yakuake even under weird circumstances like
those mentioned in https://bugs.kde.org/show_bug.cgi?id=468391 where I can run
a different profile that runs distrobox.

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

[Spectacle] [Bug 468077] It's now harder to draw an unfilled circle/ellipse/square/rectangle

[Thiago Sueto]

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

Thiago Sueto  changed:

   What|Removed |Added

 CC||herzensch...@gmail.com

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

[systemsettings] [Bug 468476] New: KCM doesn't show name of third party theme if it uses metadata.json instead of metadata.desktop

[Thiago Sueto]

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

Bug ID: 468476
   Summary: KCM doesn't show name of third party theme if it uses
metadata.json instead of metadata.desktop
Classification: Applications
   Product: systemsettings
   Version: 5.27.0
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: kcm_desktoptheme
  Assignee: plasma-b...@kde.org
  Reporter: herzensch...@gmail.com
  Target Milestone: ---

Very easy to reproduce:

Create a file ~/.local/share/plasma/desktopthemes/electrostorm/metadata.json
with the following contents:


{
"KPlugin": {
"Authors": [
{
"Name": "A Plasma Theme Designer",
"Email": "my@mail.address",
}
],
"Name": "Electrostorm",
"Description": "Brings a very dynamic electrical energy atmosphere to
the desktop",
"Id": "electrostorm",
"Version": "0.1",
"Category": "",
"EnabledByDefault": true,
"License": "GPL",
"Website": ""
},
"X-Plasma-API": "5.0"
}


It will show up with an empty name in System Settings -> Appearance -> Plasma
Style. You don't even need any other file to reproduce.

The equivalent metadata.desktop shows up correctly:


[Desktop Entry]
Name=Electrostorm
Comment=Brings a very dynamic electrical energy atmosphere to the desktop

X-KDE-PluginInfo-Author=A Plasma Theme Designer
X-KDE-PluginInfo-Email=my@mail.address
X-KDE-PluginInfo-Name=electrostorm
X-KDE-PluginInfo-Version=0.1
X-KDE-PluginInfo-Website=
X-KDE-PluginInfo-License=GPL
X-Plasma-API=5.0

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

[systemsettings] [Bug 426047] Various KCMs randomly crash in their destructors when switching to a different KCM

[Thiago Sueto]

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

--- Comment #42 from Thiago Sueto  ---
I haven't been able to reproduce this since 2020 when I reported this if I'm
not misremembering.

Can confirm I can't reproduce this in either X11 or Wayland with current
openSUSE Tumbleweed and on MicroOS Desktop Plasma.

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

[systemsettings] [Bug 455394] Vertically-arranged monitors' alignment is off by one pixel

[Thiago Macieira]

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

--- Comment #17 from Thiago Macieira  ---
(In reply to Harald Sitter from comment #16)
> Are you quite certain the config this happens with is from 5.27 (not older
> and incorrect from before 5.27)? I've been playing with the kcm for a while
> and haven't managed to get incorrect snapping out of it.

Yes, I am quite sure.

My guess is this is related to HighDPI: at 2x, the off-by-1 gets lost in the
rounding.

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

[kasts] [Bug 466855] No option to reverse order

[Thiago Sueto]

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

Thiago Sueto  changed:

   What|Removed |Added

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

--- Comment #1 from Thiago Sueto  ---
Can confirm. Sorting by reverse order is needed to listen to podcasts with
specialized topics (for example, language learning podcasts) or serialized
podcasts (where you follow a story from episode to episode, particularly
popular for criminology podcasts).

Examples:

Deutsche Welle - Warum Nicht? https://www.dw.com/de/deutsch-warum-nicht/s-2235

Good Serialized Podcasts
https://www.podchaser.com/lists/good-serialized-podcasts-107a97Ze7c

True Crime Podcasts
https://www.stylist.co.uk/entertainment/podcasts/best-true-crime-podcasts/244331

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

[Discover] [Bug 469026] Searching for "iso" doesn't find "Popsicle"

[Thiago Sueto]

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

Thiago Sueto  changed:

   What|Removed |Added

 CC||herzensch...@gmail.com

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

[kdevelop] [Bug 469064] New: Add a template for QRC files

[Thiago Sueto]

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

Bug ID: 469064
   Summary: Add a template for QRC files
Classification: Applications
   Product: kdevelop
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: herzensch...@gmail.com
  Target Milestone: ---

In Qt6 there's qt_add_qml_module() which I prefer, but for Qt5 you need to copy
a template for .qrc files every time you need to make one.

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

[NeoChat] [Bug 469066] New: Allow to disable message previews when hovering over groups/contacts list

[Thiago Sueto]

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

Bug ID: 469066
   Summary: Allow to disable message previews when hovering over
groups/contacts list
Classification: Applications
   Product: NeoChat
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: General
  Assignee: fe...@posteo.de
  Reporter: herzensch...@gmail.com
CC: c...@carlschwan.eu
  Target Milestone: ---

I don't really care about hovering over contacts or groups to check the last
message in a conversation most of the time, I just open that conversation
instead.

If the preview has two lines, it blocks view of the contact/group just above in
the list.

And there's a weird bug (probably not in Neochat) where if the previewed last
message is long enough, the tooltip displaying the preview extends behind the
cursor, making opening conversations difficult.

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

[konsole] [Bug 464239] Bookmark menu opens dropdown in a new window if application launcher is open

[Thiago Sueto]

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

Thiago Sueto  changed:

   What|Removed |Added

 CC||herzensch...@gmail.com

--- Comment #3 from Thiago Sueto  ---
To be more precise, this happens when Konsole is not currently focused. Just
having another application open and focused and then clicking on Bookmarks is
enough to trigger the bug.

This seems to only happen with this specific menu.

Given
https://community.kde.org/Guidelines_and_HOWTOs/Wayland_Porting_Notes#Popup_Menus
it might be worth checking how the parent is being set for the bookmark menu
specifically?

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

[Spectacle] [Bug 468077] It's now harder to draw an unfilled circle/ellipse/square/rectangle

[Thiago Sueto]

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

--- Comment #10 from Thiago Sueto  ---
(In reply to Stefan from comment #9)
> If this is something usable, I'd love to finish it. But would need some
> guidance, review and advice. Would that be possible?

Hello Stefan, just send an MR to the Spectacle project. :)

This way

* other people will know there's someone working on this
* the other devs can better assist you by reviewing the code

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

[frameworks-kirigami] [Bug 465440] Using Page.contentItem causes the layout to use the available space behind headerbar

[Thiago Sueto]

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

Thiago Sueto  changed:

   What|Removed |Added

Summary|Cards spawn behind  |Using Page.contentItem
   |headerbar when the Page's   |causes the layout to use
   |contentItem is set  |the available space behind
   ||headerbar

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

[frameworks-kirigami] [Bug 465440] Using Page.contentItem causes the layout to use the available space behind headerbar

[Thiago Sueto]

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

--- Comment #3 from Thiago Sueto  ---
Created attachment 158721
  --> https://bugs.kde.org/attachment.cgi?id=158721&action=edit
Cards go behind the headerbar when using Page.contentItem.

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

[kontact] [Bug 465485] Use OpenURI for attachments

[Thiago Sueto]

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

Thiago Sueto  changed:

   What|Removed |Added

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

--- Comment #3 from Thiago Sueto  ---
Can confirm.

In fact, the clickable attachment text at the top of the email (next to to,
from, date), when clicked, shows this "Open With" window containing only
Kontact apps, whereas the bottom section that is especially made for
attachments simply doesn't do anything when clicked.

Is KMail doing anything different than what's mentioned in
https://docs.flatpak.org/en/latest/portals.html#portal-support-in-qt-and-kde ?

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

[kdeconnect] [Bug 460757] New: Notification drawer shortcut "Send Clipboard" disabled after switching users

[Thiago Santos]

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

Bug ID: 460757
   Summary: Notification drawer shortcut "Send Clipboard" disabled
after switching users
Classification: Applications
   Product: kdeconnect
   Version: unspecified
  Platform: Android
OS: Android 12.x
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: android-application
  Assignee: albertv...@gmail.com
  Reporter: tos.olive...@gmail.com
  Target Milestone: ---

Created attachment 153056
  --> https://bugs.kde.org/attachment.cgi?id=153056&action=edit
After switching users

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
***
When I switch users on my device, the "Send Clipboard" shortcut present in the
notification drawer is got disabled. The only way to enable it again is
rebooting the phone (App version, 1.19.1, haven't found it above)

STEPS TO REPRODUCE
1.  Connect your phone to your computer
2. Switch to a secondary user
3. Switch back to the main user (where Kde is installed

OBSERVED RESULT
The "Send clipboard" shortcut is disabled

EXPECTED RESULT
The "Send clipboard" shortcut remaining enabled

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: Ubuntu 22.04.1 LTS,
(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.

[kdeconnect] [Bug 460757] Notification drawer shortcut "Send Clipboard" disabled after switching users

[Thiago Santos]

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

--- Comment #1 from Thiago Santos  ---
Created attachment 153057
  --> https://bugs.kde.org/attachment.cgi?id=153057&action=edit
aftr rebooting phone

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

[frameworks-kirigami] [Bug 465052] New: CardsGridView has no padding on the left side

[Thiago Sueto]

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

Bug ID: 465052
   Summary: CardsGridView has no padding on the left side
Classification: Frameworks and Libraries
   Product: frameworks-kirigami
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdelibs-b...@kde.org
  Reporter: herzensch...@gmail.com
CC: notm...@gmail.com
  Target Milestone: Not decided

Created attachment 155798
  --> https://bugs.kde.org/attachment.cgi?id=155798&action=edit
CardGridView example from Kirigami Gallery tutorial.

When attempting to reproduce the example in
https://develop.kde.org/docs/use/kirigami/introduction-kirigami-gallery/ , the
result lacks left padding between the cards and the left side of the window.

The code example is added as an attachment. It can be run with qmlscene.

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

[frameworks-kirigami] [Bug 465053] New: Global Drawer gets attached to the mouse after clicking an action that contains nested actions

[Thiago Sueto]

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

Bug ID: 465053
   Summary: Global Drawer gets attached to the mouse after
clicking an action that contains nested actions
Classification: Frameworks and Libraries
   Product: frameworks-kirigami
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdelibs-b...@kde.org
  Reporter: herzensch...@gmail.com
CC: notm...@gmail.com
  Target Milestone: Not decided

Created attachment 155799
  --> https://bugs.kde.org/attachment.cgi?id=155799&action=edit
Global Drawer example from Actions tutorial.

When attempting to reproduce the example from
https://develop.kde.org/docs/use/kirigami/introduction-actions/, I found a bug
in how the global drawer behaves when using actions that contain nested
actions.

The code example is added as an attachment. It can be run with qmlscene.

STEPS TO REPRODUCE

* Open global drawer on the upper left side
* Click View
* Move the mouse from the right to the left

OBSERVED RESULT

* The global drawer opens and attaches to the mouse movement

EXPECTED RESULT

* The global drawer simply opens

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

[frameworks-kirigami] [Bug 465054] New: QtQuick Controls Button does not inherit from Kirigami.Theme

[Thiago Sueto]

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

Bug ID: 465054
   Summary: QtQuick Controls Button does not inherit from
Kirigami.Theme
Classification: Frameworks and Libraries
   Product: frameworks-kirigami
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdelibs-b...@kde.org
  Reporter: herzensch...@gmail.com
CC: notm...@gmail.com
  Target Milestone: Not decided

Created attachment 155800
  --> https://bugs.kde.org/attachment.cgi?id=155800&action=edit
Kirigami.Theme.inherit example from Colors tutorial.

When attempting to reproduce the example from
https://develop.kde.org/docs/use/kirigami/style-colors/#color-set, it seems
QQC2.Buttons don't inherit from Kirigami.Theme.

The code example is added as an attachment. It can be run with qmlscene.

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

[frameworks-kirigami] [Bug 465054] QtQuick Controls Button does not inherit from Kirigami.Theme when using Kirigami.Theme.inherit: true

[Thiago Sueto]

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

Thiago Sueto  changed:

   What|Removed |Added

Summary|QtQuick Controls Button |QtQuick Controls Button
   |does not inherit from   |does not inherit from
   |Kirigami.Theme  |Kirigami.Theme when using
   ||Kirigami.Theme.inherit:
   ||true

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

[frameworks-kirigami] [Bug 465096] New: When GlobalDrawer isMenu: true, calling open() still opens the drawer instead of the menu

[Thiago Sueto]

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

Bug ID: 465096
   Summary: When GlobalDrawer isMenu: true, calling open() still
opens the drawer instead of the menu
Classification: Frameworks and Libraries
   Product: frameworks-kirigami
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdelibs-b...@kde.org
  Reporter: herzensch...@gmail.com
CC: notm...@gmail.com
  Target Milestone: Not decided

This might not be a valid bug since the user is expected to open the drawer by
clicking its button, but I noticed that if a global drawer shows up as a menu,
calling its open() function causes it to still show up as a global drawer, but
in a inactive/disabled state.

The expected behavior would be that the menu is opened instead.

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

[kwin] [Bug 465121] New: Hangs / freeze on Wayland when opening/closing apps

[Thiago Sueto]

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

Bug ID: 465121
   Summary: Hangs / freeze on Wayland when opening/closing apps
Classification: Plasma
   Product: kwin
   Version: 5.26.5
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: wayland-generic
  Assignee: kwin-bugs-n...@kde.org
  Reporter: herzensch...@gmail.com
  Target Milestone: ---

SUMMARY
Since a few versions ago I've been experiencing a few hangs / freezes when
closing apps. Only now did I get logs for it.

Here's the error message from `sudo journalctl -f` (lapinetouch is the machine
hostname):

fev 01 11:12:55 lapinetouch kernel: Asynchronous wait on fence
:00:02.0:kwin_wayland[1936]:6330 timed out (hint:intel_atomic_commit_ready
[i915])
fev 01 11:12:55 lapinetouch kernel: Asynchronous wait on fence
:00:02.0:kwin_wayland[1936]:632e timed out (hint:intel_atomic_commit_ready
[i915])
fev 01 11:12:59 lapinetouch kernel: i915 :00:02.0: [drm] GPU HANG: ecode
8:0:
fev 01 11:12:59 lapinetouch kernel: i915 :00:02.0: [drm] Resetting rcs0 for
stopped heartbeat on rcs0

STEPS TO REPRODUCE

Open or close a lot windows at a time, eventually you can reproduce the issue

SOFTWARE/OS VERSIONS

Operating System: openSUSE Tumbleweed 20230118
KDE Plasma Version: 5.26.5
KDE Frameworks Version: 5.102.0
Qt Version: 5.15.8
Kernel Version: 6.1.6-1-vanilla (64-bit)
Graphics Platform: Wayland
Processors: 4 × Intel® Core™ i7-5500U CPU @ 2.40GHz
Memory: 7.7 GiB of RAM
Graphics Processor: Mesa Intel® HD Graphics 5500
Manufacturer: Dell Inc.
Product Name: Inspiron 7348
System Version: A13

ADDITIONAL INFORMATION

Just today a user on reddit mentioned a similar thing with the same log
message:
https://www.reddit.com/r/kde/comments/10qquun/comment/j6rs0dk/?utm_source=share&utm_medium=web2x&context=3

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

[frameworks-kirigami] [Bug 464429] Kirigami ScrollablePage has empty space above content when refreshing

[Thiago Sueto]

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

Thiago Sueto  changed:

   What|Removed |Added

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

--- Comment #2 from Thiago Sueto  ---
Reproducible with Kirigami 5.102.

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

[frameworks-kirigami] [Bug 450869] PageRow API documentation return 404 on api.kde.org

[Thiago Sueto]

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

Thiago Sueto  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|REPORTED|RESOLVED
 CC||herzensch...@gmail.com

--- Comment #2 from Thiago Sueto  ---
The PageRow API page is now fixed:
https://invent.kde.org/frameworks/kapidox/-/merge_requests/31

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

[frameworks-kirigami] [Bug 465440] New: Cards spawn behind headerbar when the Page's contentItem is set

[Thiago Sueto]

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

Bug ID: 465440
   Summary: Cards spawn behind headerbar when the Page's
contentItem is set
Classification: Frameworks and Libraries
   Product: frameworks-kirigami
   Version: 5.102.0
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdelibs-b...@kde.org
  Reporter: herzensch...@gmail.com
CC: notm...@gmail.com
  Target Milestone: Not decided

See the examples, they can be run with qmlscene.

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

[frameworks-kirigami] [Bug 465440] Cards spawn behind headerbar when the Page's contentItem is set

[Thiago Sueto]

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

--- Comment #1 from Thiago Sueto  ---
Created attachment 156036
  --> https://bugs.kde.org/attachment.cgi?id=156036&action=edit
Card inside a Layout that's inside a Page.contentItem

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

[frameworks-kirigami] [Bug 465440] Cards spawn behind headerbar when the Page's contentItem is set

[Thiago Sueto]

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

--- Comment #2 from Thiago Sueto  ---
Created attachment 156037
  --> https://bugs.kde.org/attachment.cgi?id=156037&action=edit
Card inside a Page.contentItem

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

[frameworks-kirigami] [Bug 465445] New: headerOrientation is missing left margin of header when used in a Kirigami.Card

[Thiago Sueto]

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

Bug ID: 465445
   Summary: headerOrientation is missing left margin of header
when used in a Kirigami.Card
Classification: Frameworks and Libraries
   Product: frameworks-kirigami
   Version: 5.102.0
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdelibs-b...@kde.org
  Reporter: herzensch...@gmail.com
CC: notm...@gmail.com
  Target Milestone: Not decided

Created attachment 156046
  --> https://bugs.kde.org/attachment.cgi?id=156046&action=edit
Image showing how a Card with headerOrientation makes the header lose its left
margin.

The attached file can be run in qmlscene to reproduce the issue.
Just change the Card to an AbstractCard to see how it should look like.

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

[frameworks-kirigami] [Bug 465445] headerOrientation is missing left margin of header when used in a Kirigami.Card

[Thiago Sueto]

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

Thiago Sueto  changed:

   What|Removed |Added

 Attachment #156046|0   |1
is obsolete||

--- Comment #1 from Thiago Sueto  ---
Created attachment 156047
  --> https://bugs.kde.org/attachment.cgi?id=156047&action=edit
Image showing how a Card with headerOrientation makes the header lose its left
margin.

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

[frameworks-kirigami] [Bug 465446] New: Card.banner breaks when using headerOrientation: Qt.Horizontal

[Thiago Sueto]

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

Bug ID: 465446
   Summary: Card.banner breaks when using headerOrientation:
Qt.Horizontal
Classification: Frameworks and Libraries
   Product: frameworks-kirigami
   Version: 5.102.0
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdelibs-b...@kde.org
  Reporter: herzensch...@gmail.com
CC: notm...@gmail.com
  Target Milestone: Not decided

Created attachment 156048
  --> https://bugs.kde.org/attachment.cgi?id=156048&action=edit
Image of a Card with broken banner

See the reproducible example attached.

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

[frameworks-kirigami] [Bug 465445] headerOrientation: Qt.Horizontal is missing left margin of header when used in a Kirigami.Card

[Thiago Sueto]

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

Thiago Sueto  changed:

   What|Removed |Added

Summary|headerOrientation is|headerOrientation:
   |missing left margin of  |Qt.Horizontal is missing
   |header when used in a   |left margin of header when
   |Kirigami.Card   |used in a Kirigami.Card

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

[frameworks-kirigami] [Bug 465446] Card.banner breaks when using headerOrientation: Qt.Horizontal

[Thiago Sueto]

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

--- Comment #1 from Thiago Sueto  ---
It works only with an image. To test, simply add the following to the banner
(or any other icon):

source:
"https://kde.org/stuff/clipart/logo/kde-logo-white-blue-rounded-128x128.png";

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

[kdiff3] [Bug 482590] New: kdiff3 segfaults when used with git mergetool

[Thiago Sueto]

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

Bug ID: 482590
   Summary: kdiff3 segfaults when used with git mergetool
Classification: Applications
   Product: kdiff3
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: application
  Assignee: reeves...@gmail.com
  Reporter: herzensch...@gmail.com
  Target Milestone: ---

Attempting to run git mergetool while having kdiff3 installed to resolve
conflicts for a rebase causes kdiff3 to segfault with output like this:

```
This message is displayed because 'merge.tool' is not configured.
See 'git mergetool --tool-help' or 'git help config' for more details.
'git mergetool' will now attempt to use one of the following tools:
opendiff kdiff3 tkdiff xxdiff meld tortoisemerge gvimdiff diffuse diffmerge
ecmerge p4merge araxis bc codecompare smerge emerge vimdiff nvimdiff
Merging:
README.md

Normal merge conflict for 'README.md':
  {local}: modified file
  {remote}: modified file
Hit return to start merge resolution tool (kdiff3): 
/usr/libexec/git/mergetools/kdiff3: line 11: 22393 Segmentation fault 
(core dumped) "$merge_tool_path" --auto --L1 "$MERGED (Base)" --L2 "$MERGED
(Local)" --L3 "$MERGED (Remote)" -o "$MERGED" "$BASE" "$LOCAL" "$REMOTE" >
/dev/null 2>&1
merge of README.md failed
```

Running kdiff3 separately runs just fine.

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

[kdiff3] [Bug 482590] kdiff3 segfaults when used with git mergetool

[Thiago Sueto]

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

--- Comment #2 from Thiago Sueto  ---
My kdiff3 version is: kdiff3 1.11.70 (64 bit)

I'm on openSUSE Krypton with Plasma 6, but isma mentioned experiencing this bug
in Plasma 5 before.

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

[Akonadi] [Bug 483060] New: Akonadi sending UTC timestamps as local time to MySQL (and this failing around DST change) - QMYSQL bug?

[Thiago Macieira]

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

Bug ID: 483060
   Summary: Akonadi sending UTC timestamps as local time to MySQL
(and this failing around DST change) - QMYSQL bug?
Classification: Frameworks and Libraries
   Product: Akonadi
   Version: 5.24.4
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: server
  Assignee: kdepim-b...@kde.org
  Reporter: thi...@kde.org
CC: c...@carlschwan.eu
  Target Milestone: ---

SUMMARY
KMail started failing to send emails for me with a message saying the item
couldn't be stored. I did find this in the journal:

Mar 09 21:10:09 tjmaciei-mobl5 akonadiserver[745525]:
org.kde.pim.akonadiserver: DATABASE ERROR:
Mar 09 21:10:09 tjmaciei-mobl5 akonadiserver[745525]:
org.kde.pim.akonadiserver:   Error code: "1292"
Mar 09 21:10:09 tjmaciei-mobl5 akonadiserver[745525]:
org.kde.pim.akonadiserver:   DB error:  "Incorrect datetime value: '2024-03-10
02:10:09.341000' for column `akonadi`.`pimitemtable`.`atime` at row 1"
Mar 09 21:10:09 tjmaciei-mobl5 akonadiserver[745525]:
org.kde.pim.akonadiserver:   Error text: "Incorrect datetime value: '2024-03-10
02:10:09.341000' for column `akonadi`.`pimitemtable`.`atime` at row 1 QMYSQL3:
Unable to execute statement"
Mar 09 21:10:09 tjmaciei-mobl5 akonadiserver[745525]:
org.kde.pim.akonadiserver:   Values: QMap((":0", QVariant(QDateTime,
QDateTime(2024-03-10 02:10:09.341 UTC Qt::UTC)))(":1", QVariant(qlonglong,
770803)))
Mar 09 21:10:09 tjmaciei-mobl5 akonadiserver[745525]:
org.kde.pim.akonadiserver:   Query: "UPDATE PimItemTable SET atime = :0 WHERE (
( PimItemTable.id = :1 ) )"
Mar 09 21:10:09 tjmaciei-mobl5 akonadiserver[745525]:
org.kde.pim.akonadiserver: Unable to update item access time

After stressing a bit about whether this was a database or filesystem
corruption, I figured out that the issue was the actual time in that timestamp.
MySQL rejects it:

MariaDB [akonadi]> UPDATE PimItemTable SET atime = timestamp('2024-03-10
02:10:55.625000') WHERE ( ( PimItemTable.id = 770804 ) );
ERROR 1292 (22007): Incorrect datetime value: '2024-03-10 02:10:55.625000' for
column `akonadi`.`pimitemtable`.`atime` at row 1

If you look at the error message in the log, as well as the journalctl
timestamp, 02:10:55 is an UTC time. But when this was sent to the DB server,
there's no information that it is UTC. Thus the server rejects it thinking it's
local time.


STEPS TO REPRODUCE
1. Set your system time such that the universal time, if computed as local
time, would fall into the spring forward gap
2. Try to send an email

OBSERVED RESULT
Email sending fails.

EXPECTED RESULT
Email sending works.

SOFTWARE/OS VERSIONS
KDE Plasma Version: 5.27.10
KDE Frameworks Version: 5.115.0
Qt Version: 5.15.2

ADDITIONAL INFORMATION
This is probably a QMYSQL bug, because the QVariant as printed did have UTC
time. The toMySqlDate() function was added for Qt 6.6, but I don't see a way to
specify the timezone with MYSQL_TIME.

But maybe Akonadi can work around the issue by starting mysqld with TZ=UTC.

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

[Akonadi] [Bug 483060] Akonadi sending UTC timestamps as local time to MySQL (and this failing around DST change) - QMYSQL bug?

[Thiago Macieira]

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

--- Comment #1 from Thiago Macieira  ---
Or use the SET GLOBAL time_zone command.

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

[krunner] [Bug 483164] New: Web shortcuts do not show icons

[Thiago Sueto]

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

Bug ID: 483164
   Summary: Web shortcuts do not show icons
Classification: Plasma
   Product: krunner
   Version: master
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: webshortcuts
  Assignee: plasma-b...@kde.org
  Reporter: herzensch...@gmail.com
CC: alexander.loh...@gmx.de, natalie_clar...@yahoo.de
  Target Milestone: ---

SUMMARY
When attempting to use any web shortcut, the icon that was supposed to show up
in the listing to the left side of the query is missing.

STEPS TO REPRODUCE
1. Alt+Space to open KRunner
2. Try "google: blep"

OBSERVED RESULT
No icon next to query.

SOFTWARE/OS VERSIONS
Operating System: openSUSE Tumbleweed 20240308
KDE Plasma Version: 6.0.80
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2
Kernel Version: 6.7.7-1-default (64-bit)
Graphics Platform: Wayland
Processors: 4 × Intel® Core™ i5-7200U CPU @ 2.50GHz
Memory: 15.5 GiB of RAM
Graphics Processor: Mesa Intel® HD Graphics 620
Manufacturer: Dell Inc.
Product Name: Inspiron 5567

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

[Akonadi] [Bug 483060] Akonadi sending UTC timestamps as local time to MySQL (and this failing around DST change) - QMYSQL bug?

[Thiago Macieira]

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

--- Comment #3 from Thiago Macieira  ---
(In reply to Christophe Marin from comment #2)
> Duplicate of 483061?

Looks like two people experienced the same problem at around the same time,
yes.

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

[Akonadi] [Bug 483061] Akonadi server does not declare UTC times as UTC

[Thiago Macieira]

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

Thiago Macieira  changed:

   What|Removed |Added

 CC||thi...@kde.org
 Resolution|--- |DUPLICATE
 Status|CONFIRMED   |RESOLVED

--- Comment #2 from Thiago Macieira  ---


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

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

[Akonadi] [Bug 483060] Akonadi sending UTC timestamps as local time to MySQL (and this failing around DST change) - QMYSQL bug?

[Thiago Macieira]

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

Thiago Macieira  changed:

   What|Removed |Added

 CC||jos...@joshuakugler.com

--- Comment #4 from Thiago Macieira  ---
*** Bug 483061 has been marked as a duplicate of this bug. ***

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

[Akonadi] [Bug 483060] Akonadi sending UTC timestamps as local time to MySQL (and this failing around DST change) - QMYSQL bug?

[Thiago Macieira]

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

Thiago Macieira  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|REPORTED|CONFIRMED

--- Comment #5 from Thiago Macieira  ---
My reading of the MySQL API is that there's no way to pass the timestamp in
prepared queries as UTC. You can only pass it as a local timestamp. Feels so
1980s...

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

[Akonadi] [Bug 483060] Akonadi sending UTC timestamps as local time to MySQL (and this failing around DST change) - QMYSQL bug?

[Thiago Macieira]

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

Thiago Macieira  changed:

   What|Removed |Added

 CC||ch.ehrlic...@gmx.de

--- Comment #8 from Thiago Macieira  ---
> Another idea: have Akonadi set the client time zone to UTC when it connects. 
> BUT: I don't know what that might do to the times it returns in other 
> queries, so would require investigation, and if code would have to be changed 
> elsewhere.

Applying that fix to QMYSQL instead.
https://codereview.qt-project.org/c/qt/qtbase/+/546954

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

[systemsettings] [Bug 487286] Flatpak KCM does not detect flatpaks installed in another installation

[Thiago Sueto]

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

--- Comment #2 from Thiago Sueto  ---
(In reply to ratijas from comment #1)
> Is this basically a duplicate of https://bugs.kde.org/show_bug.cgi?id=485189
> ? Or maybe that one is for supporting GUI to manually add them, and this one
> is "simply" to work with what's already registered with Flatpak…

Yeah, the other bug report is for the lack of a GUI to set a custom
installation. This one is about the flatpak KCM being unable to detect any
flatpaks from a custom installation that was already set.

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

[kmail2] [Bug 484296] Message header shows time in the sender's timezone, not the reader's

[Thiago Macieira]

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

Thiago Macieira  changed:

   What|Removed |Added

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

--- Comment #1 from Thiago Macieira  ---
Appears to be fixed as of KMail 6.1.0

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

[kmail2] [Bug 484119] Smart dates in message list still show "today" for messages received yesterday

[Thiago Macieira]

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

Thiago Macieira  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|REPORTED|CONFIRMED

--- Comment #2 from Thiago Macieira  ---
Still happening as of KMail 6.1.0.

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

[frameworks-kquickcharts] [Bug 429152] Graphs can consume excessive CPU resources on platforms with weak Intel GPUs and high-resolution displays

[Thiago Sueto]

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

Thiago Sueto  changed:

   What|Removed |Added

 CC||herzensch...@gmail.com

--- Comment #11 from Thiago Sueto  ---
I have the same Intel UHD Graphics 620 and I also have a Radeon R7 M445 as dGPU
on my laptop, and the CPU usage results are still bad for me on Plasma 6:
starts at 15%, stabilizes between 8%-13% with a max peak of 17%.

Reducing the refresh times of all elements on the page does not help.

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

[plasma-systemmonitor] [Bug 482164] New: No way to set a global custom refresh interval

[Thiago Sueto]

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

Bug ID: 482164
   Summary: No way to set a global custom refresh interval
Classification: Applications
   Product: plasma-systemmonitor
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: ksysguard-b...@kde.org
  Reporter: herzensch...@gmail.com
CC: ahiems...@heimr.nl, plasma-b...@kde.org
  Target Milestone: ---

Currently to set the refresh interval on plasma-systemmonitor, you need to go
to Edit Page, click on the graph/table you want to change, and alter "Minimum
time between updates".

The default refresh interval is unreasonably fast (half a second or less?) so I
wanted to decrease its speed, but I had to go to each graph/table on each page
to alter everything. I'd like a global setting for this.

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

[plasma-systemmonitor] [Bug 482167] New: Default refresh interval is too fast

[Thiago Sueto]

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

Bug ID: 482167
   Summary: Default refresh interval is too fast
Classification: Applications
   Product: plasma-systemmonitor
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: ksysguard-b...@kde.org
  Reporter: herzensch...@gmail.com
CC: ahiems...@heimr.nl, plasma-b...@kde.org
  Target Milestone: ---

I'd like a more reasonable refresh interval for plasma-systemmonitor. Currently
it updates at about half a second or less. Or as the "Minimum time between
updates" setting says: "No limit".

Fast graphical refresh intervals are a well known way to get an application to
use too much CPU, and this issue becomes even worse in conjunction with
https://bugs.kde.org/show_bug.cgi?id=429152 (Graphs can consume excessive CPU
resources on platforms with weak Intel GPUs and high-resolution displays).

A system monitor should be lightweight and quick to process, and thus reliable
when the machine is under stress, it shouldn't be using as many hardware
resources as it does.

The default should be something more reasonable, probably something between the
range of 1s to 2s.

1.5s is probably the best compromise.

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

[kwin] [Bug 485353] kwin_wayland forgets the highdpi scaling whenever you connect a new monitor

[Thiago Macieira]

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

--- Comment #5 from Thiago Macieira  ---
(In reply to Zamundaaa from comment #4)
> When you reproduced this issue with a new user account, did you also log
> into Xorg first, or does it even happen if you never do that?

I had used the account first with X, but I did go and delete all the config
files before trying this. I may have missed something, though. Which file is
this stored in? ~/.local/share/kscreen/ ?

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

[kwin] [Bug 485353] kwin_wayland forgets the highdpi scaling whenever you connect a new monitor

[Thiago Macieira]

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

--- Comment #6 from Thiago Macieira  ---
I must have made a mistake in testing previously. After ensuring
~/.local/share/kscreen was deleted, logging out and back in again, kwin_wayland
does not forget the laptop screen's settings when connecting the external
monitor.

PS: in kcm_display, you can't type %

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

[plasma-nm] [Bug 486076] New: [openconnect] crashes inside libopenconnect: ctx->form->opts->_value not set

[Thiago Macieira]

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

Bug ID: 486076
   Summary: [openconnect] crashes inside libopenconnect:
ctx->form->opts->_value not set
Classification: Plasma
   Product: plasma-nm
   Version: 6.0.3
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: thi...@kde.org
  Target Milestone: ---

SUMMARY
When connecting to Palo Alto Network's GlobalProtect, the openconnect plugin
causes a crash inside libopenconnect

STEPS TO REPRODUCE
1. Try to connect to a server that requires OAuth2 authentication (mine is
Microsoft's)
2. Disconnect
3. Connect again

This appears to happen more frequently when some credential is already cached.

OBSERVED RESULT
kded6 crashes

EXPECTED RESULT
Connection is successful

SOFTWARE/OS VERSIONS
KDE Plasma Version: 6.0.4
KDE Frameworks Version: 6.10
Qt Version: 6.7.0

ADDITIONAL INFORMATION
Backtrace:
#3  0x7f0ee2441240 in  () at /lib64/libc.so.6
#4  0x7f0ee257ff6c in __strlen_evex () at /lib64/libc.so.6
#5  0x7f0ee24aa762 in strdup () at /lib64/libc.so.6
#6  0x7f0ebd7bf319 in gpst_login (vpninfo=vpninfo@entry=0x556d4431ef00,
portal=portal@entry=1, ctx=ctx@entry=0x7f0e83dffbd0)
at /usr/src/debug/openconnect-9.12/auth-globalprotect.c:728
#7  0x7f0ebd7bf576 in gpst_obtain_cookie (vpninfo=0x556d4431ef00) at
/usr/src/debug/openconnect-9.12/auth-globalprotect.c:778
#8  0x7f0ebe0bf870 in OpenconnectAuthWorkerThread::run()
(this=0x556d4415dc30)
at
/usr/src/debug/plasma-nm-6.0.4/vpn/openconnect/openconnectauthworkerthread.cpp:125
#9  0x7f0ee2edc1b8 in  () at
/lib64/glibc-hwcaps/x86-64-v4/libQt6Core.so.6.7.0
#10 0x7f0ee2492bb2 in start_thread () at /lib64/libc.so.6
#11 0x7f0ee251400c in clone3 () at /lib64/libc.so.6

In frame 6, line 728

is:
if (!ctx->username)
ctx->username =
strdup(ctx->form->opts->_value);

(gdb) p ctx->form->opts->_value
$6 = 0x0

I can't tell if this is a libopenconnect bug or not. The code in libopenconnect
is hard to debug as it drives the functionality and only calls back into the
plugin for the web display. However, my colleagues using the GNOME counterpart
don't have this issue and this only appears to happen when there's some cookie
stored in kded, so I believe the bug is somehow in the plugin.

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

[plasma-nm] [Bug 485093] openconnect plugin crashes after receiving answer from Palo Alto Networks GlobalProtect auth

[Thiago Macieira]

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

Thiago Macieira  changed:

   What|Removed |Added

 Status|REPORTED|CONFIRMED
 Ever confirmed|0   |1

--- Comment #1 from Thiago Macieira  ---
Still happening on 6.0.4

Backtrace:
#3  0x7f7d3ae41240 in  () at /lib64/libc.so.6
#4  0x7f7d16065a0b in OpenconnectAuthWidget::formLoginClicked()
(this=)
at /usr/src/debug/plasma-nm-6.0.4/vpn/openconnect/openconnectauth.cpp:833
#5  0x7f7d3b7c2c41 in QObject::event(QEvent*) () at
/lib64/glibc-hwcaps/x86-64-v4/libQt6Core.so.6.7.0
#6  0x7f7d3cbc2f1e in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /lib64/libQt6Widgets.so.6
#7  0x7f7d3b77e618 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at /lib64/glibc-hwcaps/x86-64-v4/libQt6Core.so.6.7.0
#8  0x7f7d3b77e95e in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () at /lib64/glibc-hwcaps/x86-64-v4/libQt6Core.so.6.7.0
#9  0x7f7d3b9af653 in  () at
/lib64/glibc-hwcaps/x86-64-v4/libQt6Core.so.6.7.0
#10 0x7f7d3b112710 in  () at /lib64/libglib-2.0.so.0
#11 0x7f7d3b114358 in  () at /lib64/libglib-2.0.so.0
#12 0x7f7d3b114a0c in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#13 0x7f7d3b9ad09c in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/glibc-hwcaps/x86-64-v4/libQt6Core.so.6.7.0
#14 0x7f7d3b78953b in
QEventLoop::exec(QFlags) () at
/lib64/glibc-hwcaps/x86-64-v4/libQt6Core.so.6.7.0
#15 0x7f7d3b782082 in QCoreApplication::exec() () at
/lib64/glibc-hwcaps/x86-64-v4/libQt6Core.so.6.7.0
#16 0x55882d76f532 in  ()
#17 0x7f7d3ae2a1f0 in __libc_start_call_main () at /lib64/libc.so.6
#18 0x7f7d3ae2a2b9 in __libc_start_main_impl () at /lib64/libc.so.6
#19 0x55882d76f895 in  ()

As before, d->passwordFormIndex = 1 and the layout's item list is:
$6 = {
  > = {
> = {}, }, 
  members of QList:
  d = {
d = 0x5588307c9270,
ptr = 0x5588307c9290,
size = 0
  }
}

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

[krdc] [Bug 486178] New: VNC plugin deadlocks on connection

[Thiago Macieira]

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

Bug ID: 486178
   Summary: VNC plugin deadlocks on connection
Classification: Applications
   Product: krdc
   Version: 24.02.2
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: VNC
  Assignee: uwol...@kde.org
  Reporter: thi...@kde.org
  Target Milestone: ---

SUMMARY
VNC plugin deadlocks as soon as you try to connect


STEPS TO REPRODUCE
1. Launch KRDC
2. Attempt to connect to a VNC host
3. Close KRDC

OBSERVED RESULT
KRDC freezes and must be killed

EXPECTED RESULT
KRDC closes. Preferably, the connection does establish.

SOFTWARE/OS VERSIONS
KDE Plasma Version: 6.0.3
KDE Frameworks Version: 6.1.0
Qt Version: 6.7.0

ADDITIONAL INFORMATION
Upon trying to connect, KRDC is still usable, but the debugger shows one thread
to be already frozen:
Thread 30 (Thread 0x7fffb4a006c0 (LWP 497638) "VncClientThread"):
#0  0x75711bcd in syscall () at /lib64/libc.so.6
#1  0x760dcca5 in QBasicMutex::lockInternal() () at
/lib64/glibc-hwcaps/x86-64-v4/libQt6Core.so.6.7.0
#2  0x7fffe341886c in QBasicMutex::lock() (this=0x55b37208) at
/usr/include/qt6/QtCore/qmutex.h:41
#3  QMutexLocker::relock() (this=) at
/usr/include/qt6/QtCore/qmutex.h:257
#4  VncClientThread::run() (this=0x55b37180) at
/usr/src/debug/krdc-24.02.2/vnc/vncclientthread.cpp:521
#5  0x760dc1b8 in  () at
/lib64/glibc-hwcaps/x86-64-v4/libQt6Core.so.6.7.0
#6  0x75692bb2 in start_thread () at /lib64/libc.so.6
#7  0x7571400c in clone3 () at /lib64/libc.so.6

QMutexLocker locker(&mutex);

while (!m_stopped) { // try to connect as long as the server allows
locker.relock();
m_passwordError = false;

This will NEVER EVER work because the mutex is locked by that locker and
nothing can unlock it. This is a difference in behaviour between Qt 5 and Qt 6.
Qt 5:
https://codebrowser.dev/qt5/qtbase/src/corelib/thread/qmutex.h.html#_ZN12QMutexLocker6relockEv
Qt 6:
https://codebrowser.dev/qt6/qtbase/src/corelib/thread/qmutex.h.html#_ZN12QMutexLocker6relockEv

The change happened in Qt 6.4, commit 1b1456975347b044c11169458b53c9f6083dbc59

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

[krdc] [Bug 486178] VNC plugin deadlocks on connection

[Thiago Macieira]

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

Thiago Macieira  changed:

   What|Removed |Added

 Status|REPORTED|CONFIRMED
 Ever confirmed|0   |1
   Severity|normal  |critical

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

[krdc] [Bug 486178] VNC plugin deadlocks on connection

[Thiago Macieira]

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

--- Comment #1 from Thiago Macieira  ---
I'd say "vncplugin doesn't work at all, ever, under any conditions, if you try
to use it" is sufficient for "critical", but ok for "grave"

BTW, I tried to fix that function myself. I can apply a workaround to just
restore the previous behaviour, but that's papering over the sun with a sieve.
I really don't understand what's going on and what is being locked. Is it
trying to protect m_stopped? Why not use an atomic instead? Or, better,
QThread::isInterruptionRequested()? But on line 549, it accesses m_stopped
without a mutex, so I don't know if it needed protecting in the first place.

Ditto for m_passwordError: why not an atomic? Or why not use a local variable
and only lock to save the state when exiting the function? 

This code should be rewritten with closer locks, not that one QMutexLocker at
the top that is used incorrectly.

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

[www.kde.org] [Bug 464394] [develop.kde.org] Breeze icon browser doesn't work

[Thiago Sueto]

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

--- Comment #4 from Thiago Sueto  ---
Alexander did a merge request
(https://invent.kde.org/documentation/develop-kde-org/-/merge_requests/375)
that is now merged, but it didn't cause any changes to
https://develop.kde.org/frameworks/breeze-icons/.

My guess is it's because the CI needs to be updated to run icon_extractor.py
before deploying the website?

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

[plasma-nm] [Bug 439612] plasma-nm Applet does not prompt for login credentials when connecting to GlobalProtect VPN

[Thiago Macieira]

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

Thiago Macieira  changed:

   What|Removed |Added

 CC||thi...@kde.org

--- Comment #1 from Thiago Macieira  ---
Pointing out that this has changed considerably in Plasma 6 because of the
update in qtwebengine. I suggest retrying.

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

[plasma-nm] [Bug 485093] New: openconnect plugin crashes after receiving answer from Palo Alto Networks GlobalProtect auth

[Thiago Macieira]

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

Bug ID: 485093
   Summary: openconnect plugin crashes after receiving answer from
Palo Alto Networks GlobalProtect auth
Classification: Plasma
   Product: plasma-nm
   Version: 6.0.3
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: applet
  Assignee: plasma-b...@kde.org
  Reporter: thi...@kde.org
  Target Milestone: ---

SUMMARY
When trying to authenticate with PAN's GP server, the openconnect plugin
reliably crashes kded6 after receiving the answer. I am unsure if this is a
regression or not: I did manage to log in a few times, initially, but I don't
know if there's some setting stored away that may be influencing the result.

STEPS TO REPRODUCE
1. Start the VPN with PAN GP
2. Perform the OAuth2 authentication (including, in my case, the Microsoft
Authenticator's approval)

OBSERVED RESULT
The dialog disappears, the VPN does not come on, and kded6 has crashed.

EXPECTED RESULT
Connection comes up

SOFTWARE/OS VERSIONS
KDE Plasma Version: 6.0.3
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.3

ADDITIONAL INFORMATION
Backtrace:
#3  0x7f2200241240 in  () at /lib64/libc.so.6
#4  0x7f21db52e67b in OpenconnectAuthWidget::formLoginClicked()
(this=)
at /usr/src/debug/plasma-nm-6.0.3/vpn/openconnect/openconnectauth.cpp:833
#5  0x7f2200bbb441 in QObject::event(QEvent*) () at
/lib64/glibc-hwcaps/x86-64-v4/libQt6Core.so.6.6.3
#6  0x7f2201fc1a7e in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /lib64/libQt6Widgets.so.6
#7  0x7f2200b782f8 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at /lib64/glibc-hwcaps/x86-64-v4/libQt6Core.so.6.6.3
#8  0x7f2200b78635 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () at /lib64/glibc-hwcaps/x86-64-v4/libQt6Core.so.6.6.3
#9  0x7f2200da0c73 in  () at
/lib64/glibc-hwcaps/x86-64-v4/libQt6Core.so.6.6.3
#10 0x7f2200912710 in  () at /lib64/libglib-2.0.so.0
#11 0x7f2200914358 in  () at /lib64/libglib-2.0.so.0
#12 0x7f2200914a0c in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#13 0x7f2200d9e8ec in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/glibc-hwcaps/x86-64-v4/libQt6Core.so.6.6.3
#14 0x7f2200b829bb in
QEventLoop::exec(QFlags) () at
/lib64/glibc-hwcaps/x86-64-v4/libQt6Core.so.6.6.3
#15 0x7f2200b7b752 in QCoreApplication::exec() () at
/lib64/glibc-hwcaps/x86-64-v4/libQt6Core.so.6.6.3
#16 0x55e1abd58522 in  ()
#17 0x7f220022a1f0 in __libc_start_call_main () at /lib64/libc.so.6
#18 0x7f220022a2b9 in __libc_start_main_impl () at /lib64/libc.so.6

Line 833 in this version is
:
QLayout *layout =
d->ui.loginBoxLayout->itemAt(d->passwordFormIndex)->layout();

The debuggers says this is a null pointer dereference. Because both itemAt()
and layout() are virtual functions, it's hard to follow in the disassembly
where exactly we are in this statement. I think it's between itemAt() and
layout().

The d pointer is valid:
(gdb) p d
$3 = {ui = {verticalLayout = 0x55e1ad165530, horizontalLayout_3 =
0x55e1ad7aa670, label_3 = 0x55e1ad102a30, cmbHosts = 0x55e1ad7aa750, 
btnConnect = 0x55e1ad5ff8f0, chkAutoconnect = 0x55e1ad5ff530,
chkStorePasswords = 0x55e1ad5ff560, loginBox = 0x55e1ad110820, 
loginBoxLayout = 0x55e1ad5ff590, serverLogBox = 0x55e1ad602df0, logLayout =
0x55e1ad602e20, horizontalLayout_2 = 0x55e1ad603140, 
viewServerLog = 0x55e1ad603330, lblLogLevel = 0x55e1ad5b9f30, cmbLogLevel =
0x55e1ad5b9f90, serverLog = 0x55e1ad5b6bd0}, setting = {
value = 0x55e1ad14b320, d = 0x55e1ad4050a0}, vpninfo = 0x55e1ad7ab500,
secrets = {d = {d = 0x55e1ad5ff1b0}}, tmpSecrets = {d = {d = 0x0}}, 
  mutex = { = {d_ptr = {_q_value = std::atomic =
{ 0x0 }}}, }, workerWaiting = {d = 0x55e1ad5bb230}, 
  worker = 0x55e1ad5fa120, 
  hosts = { >> =
{ >> = {}, }, d = {
  d = 0x55e1ad5ff150, ptr = 0x55e1ad5ff160, size = 1}}, userQuit = false,
formGroupChanged = true, cancelPipes = {48, 52}, 
  serverLog = { >> =
{ >> = {}, }, d = {d = 0x55e1ade09460, ptr = 0x55e1ade09470, size = 49}},
passwordFormIndex = 1, tokenMode = {d = {d = 0x55e1ad7ac500, 
  ptr = 0x55e1ad7ac510 "disabled", size = 8}}, token = {tokenMode =
OC_TOKEN_MODE_NONE, tokenSecret = {d = {d = 0x0, ptr = 0x0, size = 0}}}, 
  waitForWebEngineFinish = {> = {_q_value =
std::atomic = { 0x0 }}, }}

and so is d->ui.loginBoxLayout:
(gdb) p *d->ui.loginBoxLayout
$2 = { = { = { = {},
 = {_vptr.QLayoutItem = 0x7f2202534268 , 
align = {i = 0}}, }, }, }

It says QObject has no data fields because I didn't have the debugging info for
QtCore installed during this. But decoding memory shows its d pointer to be
0x55e1ad0cbe10, which is valid and decodes to:

$3 = { = { = {}

[Discover] [Bug 485189] New: Provide GUI method to define a custom installation following flatpak-installation

[Thiago Sueto]

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

Bug ID: 485189
   Summary: Provide GUI method to define a custom installation
following flatpak-installation
Classification: Applications
   Product: Discover
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: Flatpak Backend
  Assignee: plasma-b...@kde.org
  Reporter: herzensch...@gmail.com
CC: aleix...@kde.org, jgrul...@redhat.com,
trav...@redhat.com
  Target Milestone: ---

I am on a Steam Deck with 64 GB of storage running default Plasma 5 and I have
an external SD card with 512 GB. My flatpaks take a substantial amount of space
and I'd like to move the place where they're stored to the SD card
(/dev/mmcblk0p1).

But according to
https://docs.flatpak.org/en/latest/tips-and-tricks.html#adding-a-custom-installation
and https://man7.org/linux/man-pages/man5/flatpak-installation.5.html this
needs root, which is discouraged to do manually.

I'd like Discover to have a setting option for this as suggested here by a
flatpak contributor:
https://github.com/flatpak/flatpak/issues/1224#issuecomment-1310764573

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

[Discover] [Bug 485189] Provide GUI method to define a custom installation following flatpak-installation

[Thiago Sueto]

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

--- Comment #2 from Thiago Sueto  ---
> Where do the manpages say that?

"more system-wide installations can be defined via configuration files
/etc/flatpak/installations.d/"

A user path like ~/.local/share/flatpak/installations.d doesn't seem to work.
See: https://github.com/flatpak/flatpak/issues/4403

> And how would it be any different to what discover would do under the hood?

I don't know. I'm not familiar with how root files persist in immutable distros
yet.

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

[Discover] [Bug 485189] Provide GUI method to define a custom installation following flatpak-installation

[Thiago Sueto]

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

--- Comment #4 from Thiago Sueto  ---
> But where is it discouraged?

Sorry, I meant to say it's generally discouraged to do root operations *in
immutable distributions*.

SteamOS is one, and they caution the user (twice) that they should know what
they're doing and that their changes might be reset, and they don't have a sudo
password by default, as mentioned in
https://help.steampowered.com/en/faqs/view/671A-4453-E8D2-323C.

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

[kwin] [Bug 459161] Inconsistent cursor size on Wayland

[Thiago Macieira]

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

Thiago Macieira  changed:

   What|Removed |Added

 CC||thi...@kde.org

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

[kwin] [Bug 485353] New: kwin_wayland forgets the highdpi scaling whenever you connect a new monitor

[Thiago Macieira]

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

Bug ID: 485353
   Summary: kwin_wayland forgets the highdpi scaling whenever you
connect a new monitor
Classification: Plasma
   Product: kwin
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: wayland-generic
  Assignee: kwin-bugs-n...@kde.org
  Reporter: thi...@kde.org
  Target Milestone: ---

SUMMARY
Whenever you connect a new monitor (not a previously connected one), KWin
forgets the scaling for the monitor it is in. The physical size of existing
monitors does not change when you connect new outputs

STEPS TO REPRODUCE
1. Configure one monitor to something other than 100% (for example, laptop
display panel to 200% or 250%)
2. Connect another monitor

OBSERVED RESULT
The first-connected monitor goes back to 100%

EXPECTED RESULT
The first-connected monitor's scaling remains as it was configured

SOFTWARE/OS VERSIONS
KDE Plasma Version: 6.0.3
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.3

ADDITIONAL INFORMATION

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