from:"thiago"

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.

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

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?

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 483061] Akonadi server does not declare UTC times as UTC

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?

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.

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

2024-03-10 Thread 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?

2024-03-09 Thread 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.

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

2024-03-09 Thread 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.

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

2024-03-07 Thread 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.

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

2024-03-06 Thread 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.

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

2024-03-01 Thread 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.

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

2024-03-01 Thread 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.

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

2024-03-01 Thread 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.

[systemsettings] [Bug 480737] Crash upon running kcm_lookandfeel on openSUSE Krypton (Plasma 6)

2024-02-02 Thread Thiago Sueto

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

Thiago Sueto  changed:

   What|Removed |Added

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

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

[systemsettings] [Bug 480737] New: Crash upon running kcm_lookandfeel on openSUSE Krypton (Plasma 6)

2024-02-02 Thread Thiago Sueto

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

Bug ID: 480737
   Summary: Crash upon running kcm_lookandfeel on openSUSE Krypton
(Plasma 6)
Classification: Applications
   Product: systemsettings
   Version: master
  Platform: openSUSE
OS: Linux
Status: REPORTED
  Severity: crash
  Priority: NOR
 Component: kcm_lookandfeel
  Assignee: plasma-b...@kde.org
  Reporter: herzensch...@gmail.com
  Target Milestone: ---

SUMMARY

Segmentation fault when running systemsettings kcm_lookandfeel

SOFTWARE/OS VERSIONS

Operating System: openSUSE Tumbleweed 20240131
KDE Plasma Version: 6.0.80
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.1
Kernel Version: 6.7.2-1-default (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

BACKTRACE

Thread 15 (Thread 0x7fffe34006c0 (LWP 12956) "QQmlThread"):
#0  QQmlPropertyCacheCreator::propertyCacheForObject
(error=0x7fffe33feaf8, context=..., obj=0x7fffc052e948, this=0x7fffe33ff1d0) at
/usr/src/debug/qtdeclarative-everywhere-src-6.6.1/build/include/QtQml/6.6.1/QtQml/private/../../../../../../src/qml/jsruntime/qv4resolvedtypereference_p.h:90
#1  QQmlPropertyCacheCreator::buildMetaObjectRecursively
(this=this@entry=0x7fffe33ff1d0, objectIndex=22, context=...,
isVMERequired=isVMERequired@entry=QQmlPropertyCacheCreator::VMEMetaObjectIsRequired::Maybe)
at
/usr/src/debug/qtdeclarative-everywhere-src-6.6.1/build/include/QtQml/6.6.1/QtQml/private/../../../../../../src/qml/qml/qqmlpropertycachecreator_p.h:277
#2  0x7635d297 in
QQmlPropertyCacheCreator::buildMetaObjectRecursively
(this=this@entry=0x7fffe33ff1d0, objectIndex=20, context=...,
isVMERequired=isVMERequired@entry=QQmlPropertyCacheCreator::VMEMetaObjectIsRequired::Maybe)
at /usr/include/qt6/QtCore/qendian.h:258
#3  0x7635d297 in
QQmlPropertyCacheCreator::buildMetaObjectRecursively
(this=this@entry=0x7fffe33ff1d0, objectIndex=13, context=...,
isVMERequired=isVMERequired@entry=QQmlPropertyCacheCreator::VMEMetaObjectIsRequired::Maybe)
at /usr/include/qt6/QtCore/qendian.h:258
#4  0x7635d297 in
QQmlPropertyCacheCreator::buildMetaObjectRecursively
(this=this@entry=0x7fffe33ff1d0, objectIndex=1, context=...,
isVMERequired=isVMERequired@entry=QQmlPropertyCacheCreator::VMEMetaObjectIsRequired::Maybe)
at /usr/include/qt6/QtCore/qendian.h:258
#5  0x7635d297 in
QQmlPropertyCacheCreator::buildMetaObjectRecursively
(this=0x7fffe33ff1d0, objectIndex=0, context=..., isVMERequired=) at /usr/include/qt6/QtCore/qendian.h:258
#6  0x763535ef in
QQmlPropertyCacheCreator::buildMetaObjectsIncrementally
(this=0x7fffe33ff1d0) at
/usr/src/debug/qtdeclarative-everywhere-src-6.6.1/build/include/QtQml/6.6.1/QtQml/private/../../../../../../src/qml/qml/qqmlpropertycachecreator_p.h:223
#7  QQmlTypeCompiler::compile (this=0x7fffe33ff440) at
/usr/src/debug/qtdeclarative-everywhere-src-6.6.1/src/qml/qml/qqmltypecompiler.cpp:62
#8  0x763638f0 in
QQmlTypeData::compile(QQmlRefPointer const&,
QV4::ResolvedTypeReferenceMap*, std::function const&)
(dependencyHasher=..., resolvedTypeCache=0x7fffe33ff370, typeNameCache=...,
this=) at
/usr/src/debug/qtdeclarative-everywhere-src-6.6.1/src/qml/qml/qqmltypedata.cpp:852
#9  QQmlTypeData::done (this=) at
/usr/src/debug/qtdeclarative-everywhere-src-6.6.1/src/qml/qml/qqmltypedata.cpp:502
#10 0x762a8f3b in QQmlDataBlob::tryDone (this=0x5588b390) at
/usr/src/debug/qtdeclarative-everywhere-src-6.6.1/src/qml/qml/qqmldatablob.cpp:485
#11 QQmlDataBlob::tryDone (this=0x5588b390) at
/usr/src/debug/qtdeclarative-everywhere-src-6.6.1/src/qml/qml/qqmldatablob.cpp:476
#12 0x76371410 in QQmlTypeLoader::setData
(this=this@entry=0x559b28b0, blob=..., d=...) at
/usr/src/debug/qtdeclarative-everywhere-src-6.6.1/src/qml/qml/qqmltypeloader.cpp:415
#13 0x76371c1a in QQmlTypeLoader::setData
(this=this@entry=0x559b28b0, blob=..., fileName=...) at
/usr/src/debug/qtdeclarative-everywhere-src-6.6.1/src/qml/qml/qqmltypeloader.cpp:395
#14 0x76375655 in QQmlTypeLoader::loadThread (this=0x559b28b0,
blob=...) at
/usr/src/debug/qtdeclarative-everywhere-src-6.6.1/src/qml/qml/qqmltypeloader.cpp:260
#15 0x763796c5 in QQmlThread::createMessageFromMethod const&),
QQmlRefPointer const&>(void
(QQmlTypeLoaderThread::*&&)(QQmlRefPointer const&),
QQmlRefPointer const&)::I::call(QQmlThread*) () at
/usr/include/c++/13/bits/invoke.h:71
#16 0x76279054 in QQmlThreadPrivate::threadEvent (this=0x557fa1e0)
at
/usr/src/debug/qtdeclarative-everywhere-src-6.6.1/src/qml/qml/ftw/qqmlthread.cpp:148
#17 QQmlThreadPrivate::event (this=0x557fa1e0, e=0x55e61320) at
/usr/src/debug/qtdeclarative-everywhere-src-6.6.1/src/qml/qml/ftw/qqmlthread.cpp:105
#18

[dolphin] [Bug 479841] Remaining disk space is not detected properly on Btrfs disks

2024-01-25 Thread Thiago Macieira

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

--- Comment #6 from Thiago Macieira  ---
(In reply to Thiago Macieira from comment #4)
> Fixing in Qt.

Upstream fix landed in 6.7 as f3782300d2ebd4a70c594f1eb12a7d79de4b9602

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

[dolphin] [Bug 479841] Remaining disk space is not detected properly on Btrfs disks

2024-01-17 Thread Thiago Macieira

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

Thiago Macieira  changed:

   What|Removed |Added

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

--- Comment #4 from Thiago Macieira  ---
Fixing in Qt.

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

[frameworks-kio] [Bug 191632] It should be easier to add a template to "Create New..." menu (e.g. look into ~/Templates)

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

Thiago Sueto  changed:

   What|Removed |Added

 CC||codestr...@posteo.org

--- Comment #11 from Thiago Sueto  ---
*** Bug 412657 has been marked as a duplicate of this bug. ***

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

[frameworks-kio] [Bug 412657] Make it easier to add new items to the File > "Create New" menu

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

Thiago Sueto  changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 Status|CONFIRMED   |RESOLVED
 CC||herzensch...@gmail.com

--- Comment #2 from Thiago Sueto  ---


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

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

[frameworks-kio] [Bug 191632] It should be easier to add a template to "Create New..." menu (e.g. look into ~/Templates)

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

Thiago Sueto  changed:

   What|Removed |Added

 CC||jagannatha...@gmail.com

--- Comment #10 from Thiago Sueto  ---
*** Bug 400263 has been marked as a duplicate of this bug. ***

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

[frameworks-kio] [Bug 400263] Better workflow for creating template files

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

Thiago Sueto  changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 Status|CONFIRMED   |RESOLVED
 CC||herzensch...@gmail.com

--- Comment #3 from Thiago Sueto  ---


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

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

[systemsettings] [Bug 476166] Unable to change user avatar in Plasma 6

2023-10-27 Thread Thiago Sueto

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

Thiago Sueto  changed:

   What|Removed |Added

   Keywords||qt6

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

[systemsettings] [Bug 476166] New: Unable to change user avatar in Plasma 6

2023-10-27 Thread Thiago Sueto

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

Bug ID: 476166
   Summary: Unable to change user avatar in Plasma 6
Classification: Applications
   Product: systemsettings
   Version: master
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: kcm_users
  Assignee: plasma-b...@kde.org
  Reporter: herzensch...@gmail.com
CC: uhh...@gmail.com
  Target Milestone: ---

SUMMARY
Attempting to change the user avatar fails.

STEPS TO REPRODUCE
1. Go to the Users KCM
2. Click on the current avatar icon
3. Click on the option to select a new file
4. Choose the file and confirm the dialog

OBSERVED RESULT
The dialog closes as though nothing happened, showing the avatar icon list.

EXPECTED RESULT
The avatar should be updated.

SOFTWARE/OS VERSIONS
Operating System: Arch Linux 
KDE Plasma Version: 5.27.80
KDE Frameworks Version: 5.240.0
Qt Version: 6.6.0
Kernel Version: 6.5.8-arch1-1 (64-bit)
Graphics Platform: Wayland

ADDITIONAL INFORMATION
Plasma 6 was compiled with kdesrc-build. This is a clean compile, from scratch,
using simple kdesrc-build workspace.

Running System Settings from the terminal, I see two relevant errors.

The first when opening the avatar list:

qrc:/qt/qml/org/kde/kirigamiaddons/components/Avatar.qml:201:9: QML
QQuickImage: Cannot open: file:///home/blumen/.face?0

The second after clicking ok in the dialog:

qrc:/kcm/kcm_users/PicturesSheet.qml:137: Error: Cannot assign [undefined] to
QUrl

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

[frameworks-kglobalaccel] [Bug 475056] [Plasma 6] Deleting and recreating a command keyboard shortcut generates a new .desktop file every time

2023-09-30 Thread Thiago Sueto

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

Thiago Sueto  changed:

   What|Removed |Added

Summary|Deleting and recreating a   |[Plasma 6] Deleting and
   |command keyboard shortcut   |recreating a command
   |generates a new .desktop|keyboard shortcut generates
   |file every time |a new .desktop file every
   ||time

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

[frameworks-kglobalaccel] [Bug 475056] Deleting and recreating a command keyboard shortcut generates a new .desktop file every time

2023-09-30 Thread Thiago Sueto

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

Thiago Sueto  changed:

   What|Removed |Added

   Keywords||qt6

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

[frameworks-kglobalaccel] [Bug 475056] New: Deleting and recreating a command keyboard shortcut generates a new .desktop file every time

2023-09-30 Thread Thiago Sueto

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

Bug ID: 475056
   Summary: Deleting and recreating a command keyboard shortcut
generates a new .desktop file every time
Classification: Frameworks and Libraries
   Product: frameworks-kglobalaccel
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdelibs-b...@kde.org
  Reporter: herzensch...@gmail.com
  Target Milestone: ---

SUMMARY
If you create a new keyboard shortcut that triggers a command, assign it a
shortcut (so it appears in ~/.config/kglobalshortcutsrc), delete it, and
recreate it, it generates a new .desktop file in ~/.local/share/applications
following the naming scheme executable{,-1,-2,-3,...,-n}.desktop.

The curious thing is that the entries in ~/.config/kglobalshortcutsrc do
disappear fine when you delete a shortcut, it's just the .desktop file that
doesn't.

So if the user keeps testing to figure whether a command works well or not,
they might end up with several redundant .desktop files.

STEPS TO REPRODUCE
1. Go to Shortcuts -> Add Command...
2. Create a new command /usr/bin/kdialog --msgbox "Sup"
3. Assign a shortcut to it, for example, Meta+K
4. Click Apply
5. Verify that ~/.config/kglobalshortcutsrc contains a kdialog entry, it should
point to kdialog.desktop
6. Delete the shortcut via System Settings
7. Create a new one that also uses kdialog
8. Verify that ~/.config/kglobalshortcutsrc contains a kdialog entry, it should
point to kdialog-2.desktop

OBSERVED RESULT
Every time you recreate the shortcut, a new desktop entry gets added to
~/.local/share/applications without removing the original.

EXPECTED RESULT
Every time you delete the shortcut, the original desktop entry gets deleted,
and every time you create a new shortcut using the same executable, the new
desktop entry reuses its name.

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

[systemsettings] [Bug 472114] The sidebar doesn't show subcategories or it gets too small depending on window size

2023-09-28 Thread Thiago Sueto

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

Thiago Sueto  changed:

   What|Removed |Added

 CC||herzensch...@gmail.com

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

[tellico] [Bug 231867] Group view should allow a field other than the title to be shown

2023-09-10 Thread Thiago Sueto

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

Thiago Sueto  changed:

   What|Removed |Added

 CC||herzensch...@gmail.com

--- Comment #4 from Thiago Sueto  ---
I recently created a custom collection with Tellico and removed the Title
field, instead using a more descriptive field called Repository. Now the Group
view will show groups but not the name of each record, showing a list filled
with empty items.

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

[plasmashell] [Bug 473922] Meta+number does not work on Plasma 6

2023-08-29 Thread Thiago Sueto

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

Thiago Sueto  changed:

   What|Removed |Added

   Keywords||qt6

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

[plasmashell] [Bug 473922] New: Meta+number does not work on Plasma 6

2023-08-29 Thread Thiago Sueto

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

Bug ID: 473922
   Summary: Meta+number does not work on Plasma 6
Classification: Plasma
   Product: plasmashell
   Version: master
  Platform: Archlinux
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Task Manager and Icons-Only Task Manager
  Assignee: plasma-b...@kde.org
  Reporter: herzensch...@gmail.com
CC: qydwhotm...@gmail.com
  Target Milestone: 1.0

Trying to open/go to applications pinned to the panel does not work with the
Meta/Super/Win + number shortcut.

Running:

qdbus6 org.kde.kglobalaccel /component/plasmashell
org.kde.kglobalaccel.Component.invokeShortcut "activate task manager entry 1"

Also does not work, for any entry, despite the fact that something like:

qdbus6 org.kde.kglobalaccel /component/plasmashell
org.kde.kglobalaccel.Component.invokeShortcut "show-on-mouse-pos"

Does work.

I also noticed that the new kglobalacceld is not actually running as a systemd
service or directly from the command line, it just exits normally immediately
after execution, with no stdout.

systemctl status --user plasma-kglobalaccel.service (which is supposed to run
kglobalacceld) says Active: inactive (dead), despite its logs saying:

Starting KDE Global Shortcuts Server...
Started KDE Global Shortcuts Server.

Deleting kglobalshortcutsrc, khotkeysrc or kwinrc and restarting makes no
difference.

This is from Plasma 6 compiled with kdesrc-build yesterday (28/08). I compiled
both kglobalaccel and kglobalacceld for good measure, no difference.

I'm not sure if this is a bug in plasmashell or kglobalacceld.

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

[plasmashell] [Bug 470900] "More options" menu does not fit to 1366x768 screen

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

--- Comment #7 from Thiago Sueto  ---
Created attachment 160410
  --> https://bugs.kde.org/attachment.cgi?id=160410=edit
Panel on the side.

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

[plasmashell] [Bug 470900] "More options" menu does not fit to 1366x768 screen

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

--- Comment #6 from Thiago Sueto  ---
Created attachment 160409
  --> https://bugs.kde.org/attachment.cgi?id=160409=edit
Panel at the top.

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

[plasmashell] [Bug 470900] "More options" menu does not fit to 1366x768 screen

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

--- Comment #5 from Thiago Sueto  ---
Created attachment 160408
  --> https://bugs.kde.org/attachment.cgi?id=160408=edit
Panel at the bottom.

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

[plasmashell] [Bug 470900] "More options" menu does not fit to 1366x768 screen

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

Thiago Sueto  changed:

   What|Removed |Added

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

--- Comment #4 from Thiago Sueto  ---
This isn't fixed for me. Just compiled Plasma 6 the other day.

The additional options available when in Edit Mode are unusable in 1366x768
screens unless you use the panel on the sides.

I'll add screenshots.

When at the top, it's impossible to see anything useful in the options menu.
When at the bottom, it's impossible to delete panels.
When on the sides, the options dialog (?) unnecessarily takes all available
space.

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

[plasma-systemmonitor] [Bug 468403] The system monitor crashes when navigating between pages

2023-06-21 Thread Thiago Motta

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

--- Comment #2 from Thiago Motta  ---
Created attachment 159805
  --> https://bugs.kde.org/attachment.cgi?id=159805=edit
New crash information added by DrKonqi

plasma-systemmonitor (5.27.5) using Qt 5.15.8

O monitor do sistema quebra ao navegar em qualuer janela

-- Backtrace (Reduced):
#7  0x7fa9cdfc1dc2 in QAccessibleQuickItem::role() const () from
/lib/x86_64-linux-gnu/libQt5Quick.so.5
[...]
#11 0x7fa9cde4d6d3 in QQuickItemPrivate::setEffectiveVisibleRecur(bool) ()
from /lib/x86_64-linux-gnu/libQt5Quick.so.5
#12 0x7fa9cde55ffd in QQuickItem::setParentItem(QQuickItem*) () from
/lib/x86_64-linux-gnu/libQt5Quick.so.5
#13 0x7fa9cde5650d in QQuickItem::~QQuickItem() () from
/lib/x86_64-linux-gnu/libQt5Quick.so.5
[...]
#15 0x7fa9cd4c3357 in
QQmlTableInstanceModel::destroyModelItem(QQmlDelegateModelItem*,
QQmlTableInstanceModel::DestructionMode) () from
/lib/x86_64-linux-gnu/libQt5QmlModels.so.5

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

[plasma-systemmonitor] [Bug 468403] The system monitor crashes when navigating between pages

2023-06-21 Thread Thiago Motta

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

Thiago Motta  changed:

   What|Removed |Added

 CC||motta.sys...@gmail.com

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

[kontact] [Bug 465485] Use OpenURI for attachments

2023-05-05 Thread 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.

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

2023-05-05 Thread 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=edit
Cards go behind the headerbar when using Page.contentItem.

-- 
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

2023-05-05 Thread 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.

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

2023-05-03 Thread 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.

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

2023-04-28 Thread 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.

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

2023-04-27 Thread 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.

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

2023-04-27 Thread 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.

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

2023-04-26 Thread 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.

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

2023-04-19 Thread 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.

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

2023-04-17 Thread 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.

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

2023-04-15 Thread 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 468476] New: KCM doesn't show name of third party theme if it uses metadata.json instead of metadata.desktop

2023-04-13 Thread 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.

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

2023-04-11 Thread 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.

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

2023-04-11 Thread 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.

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

2023-04-11 Thread 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

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.

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

2023-03-29 Thread 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_medium=web2x=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.

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

2023-03-13 Thread 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.

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

2023-03-12 Thread 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

2023-03-12 Thread 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

2023-03-12 Thread 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

2023-03-10 Thread 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-kdoctools] [Bug 467128] New: kde-no-chunk.xsl and kde-web.xsl do not work

2023-03-09 Thread 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.

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

2023-03-09 Thread 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.

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

2023-03-09 Thread 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.

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

2023-03-08 Thread 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 466325] New: No way to enable/disable apps running in the background

2023-02-23 Thread 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.

[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

2023-02-15 Thread 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.

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

2023-02-14 Thread 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.

[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.

2023-02-13 Thread 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.

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

2023-02-10 Thread 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-kirigami] [Bug 465446] Card.banner breaks when using headerOrientation: Qt.Horizontal

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.

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

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] New: Card.banner breaks when using headerOrientation: Qt.Horizontal

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=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 is missing left margin of header when used in a Kirigami.Card

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=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 465445] New: headerOrientation is missing left margin of header when used in a Kirigami.Card

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=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 465440] Cards spawn behind headerbar when the Page's contentItem is set

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=edit
Card 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

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=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] New: Cards spawn behind headerbar when the Page's contentItem is set

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 450869] PageRow API documentation return 404 on api.kde.org