from:"Elias"

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

Vincenc Elias  changed:

   What|Removed |Added

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

--- Comment #4 from Vincenc Elias  ---
Yeah, it's fine. It is important to report bugs.

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

[plasma-wayland-protocols] [Bug 478526] "Alt + Shift + Tab" task switcher doesn't work

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

Vincenc Elias  changed:

   What|Removed |Added

 CC||vinca.ostrav...@gmail.com

--- Comment #1 from Vincenc Elias  ---
Thanks for your report!
I tried it in the latest tumbleweed version of openSUSE 20231213 and it worked
as intended. Try switching to the latest version. 
There is a newer version of plasma so it may help.

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

[konsole] [Bug 478524] Konsole is not allowing me to write scripts/programs that print the standard output to a file. I'm writing a program that includes

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

Vincenc Elias  changed:

   What|Removed |Added

 CC||vinca.ostrav...@gmail.com
 Resolution|--- |NOT A BUG
 Status|REPORTED|RESOLVED

--- Comment #1 from Vincenc Elias  ---
Thanks for your report!
Any bug reports are appreciated but the syntax of your command is wrong. If you
want search for multiple strings use: grep "string1\|string2\|string3". If you
write it like this: grep "string1" "string2", it will look for string1 in file
named string2. It will basically return an error.

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

[kde] [Bug 478522] application menu doesnt open when i press on it and when i use the super key

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

Vincenc Elias  changed:

   What|Removed |Added

 Resolution|--- |WAITINGFORINFO
 CC||vinca.ostrav...@gmail.com
 Status|REPORTED|NEEDSINFO

--- Comment #2 from Vincenc Elias  ---
And did you make any changes to the system?

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

[kde] [Bug 478522] application menu doesnt open when i press on it and when i use the super key

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

--- Comment #1 from Vincenc Elias  ---
Thanks for your report!
Can you tell us more information about this problem? What exact distro are you
using? When it happens? Does it happen every time? Did you install  anything?
Are you using Waylad or X11? And a video of this bug would be appreciated.

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

[Breeze] [Bug 478493] The default folder icon has a slightly different shape than all other folder icons

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

Vincenc Elias  changed:

   What|Removed |Added

 Status|REPORTED|CONFIRMED
 Ever confirmed|0   |1
   Keywords||junior-jobs

--- Comment #2 from Vincenc Elias  ---
Thanks for your report!
Yes, icons are different.
Tested on the latest KDE neon unstable edition.

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

[Breeze] [Bug 478493] The default folder icon has a slightly different shape than all other folder icons

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

Vincenc Elias  changed:

   What|Removed |Added

 CC||vinca.ostrav...@gmail.com

--- Comment #1 from Vincenc Elias  ---
Created attachment 164167
  --> https://bugs.kde.org/attachment.cgi?id=164167&action=edit
different icons

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

[dolphin] [Bug 478482] Folders named "?" can't be accessed in Dolphin.

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

Vincenc Elias  changed:

   What|Removed |Added

 CC||vinca.ostrav...@gmail.com

--- Comment #5 from Vincenc Elias  ---
It seems fine on Manjaro 23.0.04 with Dolphin 23.08.1. I tried creating it on
different places and also using terminal but I didn't find anything unusual.

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

[plasmashell] [Bug 478498] Global Menu disappears when menu is clicked

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

Vincenc Elias  changed:

   What|Removed |Added

 CC||vinca.ostrav...@gmail.com

--- Comment #2 from Vincenc Elias  ---
Thanks for your report!
I tried but I can't reproduce it.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: KDE Neon Unstable
KDE Plasma Version: 5.90.90
KDE Frameworks Version: 5.246.0
Qt Version: 6.6.0

STEPS THAT I DID
1. I set up a panel with global menu widget
2. I used the system for a while and opened various apps and tried to reproduce
it
3. I did everything in the attached video but I couldn't reproduce it

SUMMARY
Please add additional info or what you did before it happened

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

[kwin] [Bug 343690] Missing windows tabbing

2023-09-30 Thread Elias Probst

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

Elias Probst  changed:

   What|Removed |Added

 CC||m...@eliasprobst.eu

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

[layer-shell-qt] [Bug 472994] How to use layer-shell-qt in an application

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

Elias Steurer  changed:

   What|Removed |Added

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

--- Comment #5 from Elias Steurer  ---
Ok I have read about the thing with gnome not supporting layer-shell. At least
it works on kde now. Thanks!

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

[layer-shell-qt] [Bug 472994] How to use layer-shell-qt in an application

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

--- Comment #4 from Elias Steurer  ---
I have now running on KDE. This should also work on Gnome, right? When testing
with Gnome (Wayland) 42.9 it displays the window as regular window and not as
background when setting it to LayerBackground

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

[layer-shell-qt] [Bug 472994] How to use layer-shell-qt in an application

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

--- Comment #3 from Elias Steurer  ---
Update: I have managed to install ecm and layer-shell-qt via the regular
configure, make and make install. Now on to integration with
ScreenPlayWallpaper. I do have to link to LayerShellQtInterface right?

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

[layer-shell-qt] [Bug 472994] How to use layer-shell-qt in an application

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

--- Comment #2 from Elias Steurer  ---
I'm trying to do exactly that. For this, I added ECM and the layer-shell-qt via
CMake FetchContent. CMake/layer-shell-qt then either complains about not
finding ecm or finding not a suitable version, see
https://gitlab.com/kelteseth/ScreenPlay/-/merge_requests/106/diffs#236c5f57741468d5819178c066ff5fe6e5a31092_21_22
any idea what I can try to do different?

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

[layer-shell-qt] [Bug 472994] New: How to use layer-shell-qt in an application

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

Bug ID: 472994
   Summary: How to use layer-shell-qt in an application
Classification: Frameworks and Libraries
   Product: layer-shell-qt
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: aleix...@kde.org
  Reporter: i...@kelteseth.net
  Target Milestone: ---

SUMMARY
My goal is to add Wayland support to ScreenPlay. ScreenPlay is an Open Source
Live-Wallpaper app for Windows and OSX written in Qt 6.5 and qml. 

STEPS TO REPRODUCE
1.  Clone ScreenPlay and check out this MR
https://gitlab.com/kelteseth/ScreenPlay/-/merge_requests/106#b7045c08a6069f1f5456dfd608d3c8385402338c
2. cd Tools
3.  python -m  pip install -r requirements.txt
4.  python3 setup.py
5. CMake configure via VSCode or QtCreator CMakePresets.json

OBSERVED RESULT
CMake is unable to configure because of ECM dependencies

EXPECTED RESULT
To be able to configure and run wallpaper

SOFTWARE/OS VERSIONS
Linux/KDE Plasma:  Kubuntu 22.04 
(available in About System)
KDE Plasma Version: KDE 5.24.7
KDE Frameworks Version:  5.92.0
Qt Version: 5.15.3

ADDITIONAL INFORMATION

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

[Elisa] [Bug 472284] New: Modifying the playlist while Elisa is playing results in a wrong playing order

2023-07-15 Thread Elias

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

Bug ID: 472284
   Summary: Modifying the playlist while Elisa is playing results
in a wrong playing order
Classification: Applications
   Product: Elisa
   Version: 23.04.2
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: matthieu_gall...@yahoo.fr
  Reporter: mosa...@posteo.de
  Target Milestone: ---

SUMMARY
When a song from above the currently playing position is moved to the position
after the currently playing, Elisa does not play this song next. Instead the
next song playing is one from above the current position or the current
position again.

STEPS TO REPRODUCE
1. Create a playlist with three songs.
2. Play the last (third) song by double clicking it.
3. Drag the first song to the last position.
4. The next song that will be played is not the expected (just dragged) one.

OBSERVED RESULT
The next song playing will be song two of the playlist (the one, you just
listened to). In longer playlists it could be another one from above the
current position, but it will never be the recently dragged song.

EXPECTED RESULT
The now third (former fist) song should be played. After the dragging the song
this is the next song in the list, thus it should be played next.

SOFTWARE/OS VERSIONS
Operating System: Fedora Linux 38
KDE Plasma Version: 5.27.6
KDE Frameworks Version: 5.107.0
Qt Version: 5.15.10
Kernel Version: 6.3.12-200.fc38.x86_64 (64-bit)
Graphics Platform: Wayland

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

[plasmashell] [Bug 471168] New: se bloqueo al usar la linea de comando obs-studio instalando linuxgsm

2023-06-17 Thread elias

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

Bug ID: 471168
   Summary: se bloqueo al usar la linea de comando obs-studio
instalando linuxgsm
Classification: Plasma
   Product: plasmashell
   Version: 5.27.5
  Platform: Debian stable
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: eliascura1...@gmail.com
CC: k...@davidedmundson.co.uk
  Target Milestone: 1.0

Application: plasmashell (5.27.5)

Qt Version: 5.15.8
Frameworks Version: 5.103.0
Operating System: Linux 6.1.0-9-amd64 x86_64
Windowing System: Wayland
Distribution: Debian GNU/Linux 12 (bookworm)
DrKonqi: 5.27.5 [CoredumpBackend]

-- Information about the crash:
se bloqueo al usar la linea de comando obs-studio instalando linuxgsm

The reporter is unsure if this crash is reproducible.

-- Backtrace:
Application: Plasma (plasmashell), signal: Segmentation fault

   PID: 1118 (plasmashell)
   UID: 1001 (steam)
   GID: 1001 (steam)
Signal: 11 (SEGV)
 Timestamp: Sat 2023-06-17 14:48:40 -03 (53s ago)
  Command Line: /usr/bin/plasmashell --no-respawn
Executable: /usr/bin/plasmashell
 Control Group:
/user.slice/user-1001.slice/user@1001.service/session.slice/plasma-plasmashell.service
  Unit: user@1001.service
 User Unit: plasma-plasmashell.service
 Slice: user-1001.slice
 Owner UID: 1001 (steam)
   Boot ID: 884cd4f2740d41f3ac023552bccd4709
Machine ID: a6e8f61da4f744fe969582ea42c8ab37
  Hostname: e1189
   Storage:
/var/lib/systemd/coredump/core.plasmashell.1001.884cd4f2740d41f3ac023552bccd4709.1118.168702412000.zst
(present)
  Size on Disk: 6.7M
   Message: Process 1118 (plasmashell) of user 1001 dumped core.

Module libsystemd.so.0 from deb systemd-252.6-1.amd64
Module libudev.so.1 from deb systemd-252.6-1.amd64
Stack trace of thread 1426:
#0  0x7efd280a9ccc n/a (libc.so.6 + 0x8accc)
#1  0x7efd2805aef2 raise (libc.so.6 + 0x3bef2)
#2  0x7efd2a7aab46 _ZN6KCrash19defaultCrashHandlerEi
(libKF5Crash.so.5 + 0x5b46)
#3  0x7efd2805af90 n/a (libc.so.6 + 0x3bf90)
#4  0x7efd280a9ccc n/a (libc.so.6 + 0x8accc)
#5  0x7efd2805aef2 raise (libc.so.6 + 0x3bef2)
#6  0x7efd2805af90 n/a (libc.so.6 + 0x3bf90)
#7  0x7efd280a4d36 n/a (libc.so.6 + 0x85d36)
#8  0x7efd280a76dc pthread_cond_timedwait (libc.so.6 +
0x886dc)
#9  0x7efd282d19bc
_ZN14QWaitCondition4waitEP6QMutex14QDeadlineTimer (libQt5Core.so.5 + 0xd19bc)
#10 0x7efd282cf0a5 n/a (libQt5Core.so.5 + 0xcf0a5)
#11 0x7efd282cbd43 n/a (libQt5Core.so.5 + 0xcbd43)
#12 0x7efd280a7fd4 n/a (libc.so.6 + 0x88fd4)
#13 0x7efd281285bc n/a (libc.so.6 + 0x1095bc)

Stack trace of thread 1425:
#0  0x7efd2811afff __poll (libc.so.6 + 0xfbfff)
#1  0x7efd26fb89ae n/a (libglib-2.0.so.0 + 0x549ae)
#2  0x7efd26fb8acc g_main_context_iteration
(libglib-2.0.so.0 + 0x54acc)
#3  0x7efd2850984e
_ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE
(libQt5Core.so.5 + 0x30984e)
#4  0x7efd284b017b
_ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 +
0x2b017b)
#5  0x7efd282cab87 _ZN7QThread4execEv (libQt5Core.so.5 +
0xcab87)
#6  0x7efd2a1566d6 n/a (libQt5Quick.so.5 + 0x1566d6)
#7  0x7efd282cbd43 n/a (libQt5Core.so.5 + 0xcbd43)
#8  0x7efd280a7fd4 n/a (libc.so.6 + 0x88fd4)
#9  0x7efd281285bc n/a (libc.so.6 + 0x1095bc)

Stack trace of thread 1121:
#0  0x7efd2811afff __poll (libc.so.6 + 0xfbfff)
#1  0x7efd29f2fcd6 n/a (libQt5WaylandClient.so.5 + 0x7acd6)
#2  0x7efd282cbd43 n/a (libQt5Core.so.5 + 0xcbd43)
#3  0x7efd280a7fd4 n/a (libc.so.6 + 0x88fd4)
#4  0x7efd281285bc n/a (libc.so.6 + 0x1095bc)

Stack trace of thread 1245:
#0  0x7efd2811afff __poll (libc.so.6 + 0xfbfff)
#1  0x7efd26fb89ae n/a (libglib-2.0.so.0 + 0x549ae)
#2  0x7efd26fb8acc g_main_context_iteration
(libglib-2.0.so.0 + 0x54acc)
#3  0x7efd2850984e
_ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE
(libQt5Core.so.5 + 0x30984e)
#4  0x7efd284b017b
_ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 +
0x2

[gwenview] [Bug 468677] New: Window title doesn't change after renaming operation (only when opening rename dialog again)

2023-04-19 Thread Elias Probst

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

Bug ID: 468677
   Summary: Window title doesn't change after renaming operation
(only when opening rename dialog again)
Classification: Applications
   Product: gwenview
   Version: 22.12.3
  Platform: NixOS
OS: Linux
Status: REPORTED
  Severity: minor
  Priority: NOR
 Component: general
  Assignee: gwenview-bugs-n...@kde.org
  Reporter: m...@eliasprobst.eu
  Target Milestone: ---

SUMMARY
After renaming an image in Gwenview, the window title isn't updated to reflect
the new name.
Only after opening (and immediately closing it again) the rename dialog again,
the window title is updated.


STEPS TO REPRODUCE
1. Open any local image in Gwenview
2. Open the rename dialog (F2 or "Operations → Rename")
3. Define a new name and close the dialog via "Rename"

OBSERVED RESULT
The window title doesn't change to show the new image name

EXPECTED RESULT
The window title changes to show the new image name


SOFTWARE/OS VERSIONS
Linux/KDE Plasma:
  KDE Plasma Version: 5.27.3
  KDE Frameworks Version: 5.104.0
  Qt Version: 5.15.8
  Graphics Platform: Wayland

ADDITIONAL INFORMATION
When opening the rename dialog again (without doing anything further), the
window title is updated immediately.

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

[frameworks-baloo] [Bug 468337] New: Baloo ignores corrupted DB

2023-04-09 Thread Elias Probst

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

Bug ID: 468337
   Summary: Baloo ignores corrupted DB
Classification: Frameworks and Libraries
   Product: frameworks-baloo
   Version: 5.104.0
  Platform: NixOS
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Engine
  Assignee: baloo-bugs-n...@kde.org
  Reporter: m...@eliasprobst.eu
  Target Milestone: ---

SUMMARY
For reasons unknown, my Baloo DB got corrupted - but I had no clue until I
wondered why I got no results from Baloo and started to investigate using
Baloo's CLI tools.
At no point did Baloo's KCM or any of the Plasma tooling let me know, that
Baloo might have a problem with its DB.


STEPS TO REPRODUCE
1. Corrupt your DB (procedure unknown)
2. Index a file
3. Execute a query which should return the file

OBSERVED RESULT
- Baloo acts on the surface, as if nothing happened
- Baloo only hints at a problem, when manually executing "balooctl index
$PathToFile"

The following steps demonstrate the problem:
- Create a testfile:
  ```
  echo "This is my testfile. Unique term is: joo0theg8Vai2agh8wah" >
~/Documents/my-testfile.txt
  ```
- Query Baloo for the unique term in it (no results returned):
  ```
  baloosearch joo0theg8Vai2agh8wah
  Elapsed: 1.47841 msecs
  ```
- Ask Baloo explicitly to index the file (it sends mixed signals - on the one
hand it claims to have indexed the file, on the other hand a huge number of
errors):
  ```
  balooctl index ~/Documents/my-testfile.txt
  kf.baloo.engine: IdTreeDB::put MDB_CORRUPTED: Located page was wrong type
  kf.baloo.engine: IdFilenameDB::put MDB_BAD_TXN: Transaction must abort, has a
child, or is invalid
  kf.baloo.engine: IdTreeDB::put MDB_BAD_TXN: Transaction must abort, has a
child, or is invalid
  kf.baloo.engine: IdFilenameDB::put MDB_BAD_TXN: Transaction must abort, has a
child, or is invalid
  kf.baloo.engine: IdTreeDB::put MDB_BAD_TXN: Transaction must abort, has a
child, or is invalid
  kf.baloo.engine: IdFilenameDB::put MDB_BAD_TXN: Transaction must abort, has a
child, or is invalid
  kf.baloo.engine: IdTreeDB::put MDB_BAD_TXN: Transaction must abort, has a
child, or is invalid
  kf.baloo.engine: IdFilenameDB::put MDB_BAD_TXN: Transaction must abort, has a
child, or is invalid
  kf.baloo.engine: DocumentDB::put MDB_BAD_TXN: Transaction must abort, has a
child, or is invalid
  kf.baloo.engine: DocumentDB::put MDB_BAD_TXN: Transaction must abort, has a
child, or is invalid
  kf.baloo.engine: DocumentTimeDB::put 25335805920738816 MDB_BAD_TXN:
Transaction must abort, has a child, or is invalid
  kf.baloo.engine: MTimeDB::put MDB_BAD_TXN: Transaction must abort, has a
child, or is invalid
  kf.baloo.engine: DocumentDataDB::put MDB_BAD_TXN: Transaction must abort, has
a child, or is invalid
  kf.baloo.engine: PostingDB::put MDB_BAD_TXN: Transaction must abort, has a
child, or is invalid
  kf.baloo.engine: PositionDB::put MDB_BAD_TXN: Transaction must abort, has a
child, or is invalid
  kf.baloo.engine: PostingDB::put MDB_BAD_TXN: Transaction must abort, has a
child, or is invalid
  kf.baloo.engine: PositionDB::put MDB_BAD_TXN: Transaction must abort, has a
child, or is invalid
  kf.baloo.engine: PostingDB::put MDB_BAD_TXN: Transaction must abort, has a
child, or is invalid
  kf.baloo.engine: PositionDB::put MDB_BAD_TXN: Transaction must abort, has a
child, or is invalid
  kf.baloo.engine: PostingDB::put MDB_BAD_TXN: Transaction must abort, has a
child, or is invalid
  kf.baloo.engine: PositionDB::put MDB_BAD_TXN: Transaction must abort, has a
child, or is invalid
  kf.baloo.engine: PostingDB::put MDB_BAD_TXN: Transaction must abort, has a
child, or is invalid
  kf.baloo.engine: PositionDB::put MDB_BAD_TXN: Transaction must abort, has a
child, or is invalid
  kf.baloo.engine: PostingDB::put MDB_BAD_TXN: Transaction must abort, has a
child, or is invalid
  kf.baloo.engine: PostingDB::put MDB_BAD_TXN: Transaction must abort, has a
child, or is invalid
  kf.baloo.engine: PositionDB::put MDB_BAD_TXN: Transaction must abort, has a
child, or is invalid
  kf.baloo.engine: PostingDB::put MDB_BAD_TXN: Transaction must abort, has a
child, or is invalid
  kf.baloo.engine: PositionDB::put MDB_BAD_TXN: Transaction must abort, has a
child, or is invalid
  kf.baloo.engine: PostingDB::put MDB_BAD_TXN: Transaction must abort, has a
child, or is invalid
  kf.baloo.engine: PostingDB::put MDB_BAD_TXN: Transaction must abort, has a
child, or is invalid
  kf.baloo.engine: PositionDB::put MDB_BAD_TXN: Transaction must abort, has a
child, or is invalid
  kf.baloo.engine: PostingDB::put MDB_BAD_TXN: Transaction must abort, has a
child, or is invalid
  kf.baloo.engine: PositionDB::put MDB_BAD_TXN: Transaction must abort, has a
child, or is invalid
  kf.baloo.engine: PostingDB::put MDB_BAD_TXN: Transaction must abort, has a
child, or is invalid
  kf.baloo.engine: PositionDB::put MDB_BAD_TXN: Tra

[plasmashell] [Bug 451449] Wayland desktop panel doesn't follow primary screen when external primary screen is turned off and back on again

2023-02-18 Thread Elias Probst

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

Elias Probst  changed:

   What|Removed |Added

   See Also||https://bugs.kde.org/show_b
   ||ug.cgi?id=465756

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

[plasmashell] [Bug 459082] Wayland - Notification on primary monitor in wrong place

2023-02-18 Thread Elias Probst

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

Elias Probst  changed:

   What|Removed |Added

   See Also||https://bugs.kde.org/show_b
   ||ug.cgi?id=465756

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

[plasmashell] [Bug 465756] Plasma panel items showing up on the wrong screen

2023-02-18 Thread Elias Probst

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

Elias Probst  changed:

   What|Removed |Added

   See Also||https://bugs.kde.org/show_b
   ||ug.cgi?id=459082,
   ||https://bugs.kde.org/show_b
   ||ug.cgi?id=451449
 CC||m...@eliasprobst.eu
 Status|REPORTED|CONFIRMED
 Ever confirmed|0   |1

--- Comment #1 from Elias Probst  ---
Potentially related bugs:
- #451449 - Wayland desktop panel doesn't follow primary screen when external
primary screen is turned off and back on again
(https://bugs.kde.org/show_bug.cgi?id=451449)
- #459082 - Wayland - Notification on primary monitor in wrong place
(https://bugs.kde.org/show_bug.cgi?id=459082)

I'm seeing the same here.

I wouldn't say it's not strictly, that items show up on the wrong screen, but
that the panel on the primary screen somehow messes up its screen coordinates,
as some elements appear on the right screen, but in the wrong place, some are
shown on the adjacent screen, some don't show up at all.

My primary screen is (2560x1440, external display) located centered above the
secondary screen (1920x1080, laptop built-in). Each screen has a panel at the
bottom edge at full width.

Things I can observe here:
- The Kickoff menu (button located at default position, the very left edge of
the bottom panel) is shown overlaying the panel at the bottom edge of the
screen and moved to the right, as if it would use the secondary screen's
geometry to define its X position.
- Panel tooltips use seemingly random positions, either misplaced similarly as
the Kickoff menu, or moved downwards to the built-in laptop screen where they
appear at the upper edge.
- Right aligned popups from the systray behave similar to what I described for
Kickoff (not taking the panel height into account, aligning with the screen's
bottom edge instead and not being placed above the systray, being moved to the
left as if they'd use the built-in screen's right edge as their maximum for X
positioning)
- I have next to the Kickoff button the "Activities" applet, which is supposed
to show the Activity Manager on the corresponding screen when clicked. It works
just fine, until the screen is re-connected, then clicking on the applet on the
primary (external) screen does nothing, clicking on it on the secondary
(built-in) screen works just fine. Using the Meta+Q shortcut always triggers it
on the secondary (built-in) screen, even when the focus is on the primary
(external) screen.

- NixOS unstable
- Plasma 5.27
- KF5 5.103
- Qt 5.15.8
- Kernel 5.15.94

$ kscreen-doctor -o
Output: 1 eDP-1 enabled connected priority 2 Panel Modes: 0:1920x1080@60*!
1:1920x1080@48 2:1280x1024@60 3:1024x768@60 4:1280x800@60 5:1920x1080@60
6:1600x900@60 7:1368x768@60 8:1280x720@60 Geometry: 359,1440 1920x1080 Scale: 1
Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: Automatic
Output: 2 DP-1 enabled connected priority 1 DisplayPort Modes: 0:2560x1440@60*!
1:2048x1080@60 10:1600x1200@60 11:1280x1024@75 12:1280x1024@60 13:1152x864@75
14:1280x720@60 15:1280x720@60 16:1280x720@60 17:1280x720@50 18:1024x768@75
19:1024x768@60 2:2048x1080@24 20:800x600@75 21:800x600@60 22:720x576@50
23:720x576@50 24:720x480@60 25:720x480@60 26:720x480@60 27:720x480@60
28:640x480@75 29:640x480@60 3:1920x1080@60 30:640x480@60 31:640x480@60
32:720x400@70 33:1600x1200@60 34:1280x1024@60 35:1024x768@60 36:1920x1200@60
37:1280x800@60 38:1920x1080@60 39:1600x900@60 4:1920x1080@60 40:1368x768@60
41:1280x720@60 5:1920x1080@60 6:1920x1080@60 7:1920x1080@60 8:1920x1080@50
9:1920x1080@50 Geometry: 0,0 2560x1440 Scale: 1 Rotation: 1 Overscan: 0 Vrr:
incapable RgbRange: Automatic

$ kscreen-console
START: Requesting Config
Received config. Took 32 milliseconds
Screen:
maxSize: QSize(64000, 64000)
minSize: QSize(0, 0)
currentSize: QSize(2560, 2520)

-

Id:  1
Name:  "eDP-1"
Type:  "Panel (Laptop)"
Connected:  true
Enabled:  true
Priority:  2
Rotation:  KScreen::Output::None
Pos:  QPoint(359,1440)
MMSize:  QSize(310, 170)
FollowPreferredMode:  false
Size:  QSize(1920, 1080)
Scale:  1
Clones:  None
Mode:  "0"
Preferred Mode:  "0"
Preferred modes:  ("0")
Modes:
"0""1920x1080@60"   QSize(1920, 1080)   60.02
"1""1920x1080@48"   QSize(1920, 1080)   47.999
"2""1280x1024@60"   QSize(1280, 1024)   59.895
"3""1024x768@60"   QSize(1024, 768)   59.92
"4""1280x800@60"   QSize(1280, 800)   59.81
"5""1920x1080@60&q

[filelight] [Bug 464114] Alt + TAB'ing out of filelight whilist hovering over a address makes the info pop-up stuck to the screen.

2023-01-10 Thread Elias

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

--- Comment #2 from Elias  ---
Created attachment 155189
  --> https://bugs.kde.org/attachment.cgi?id=155189&action=edit
The correct Image of my desktop after alt+tabbing out of filelight when
hoverning over the piechart.

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

[filelight] [Bug 464114] Alt + TAB'ing out of filelight whilist hovering over a address makes the info pop-up stuck to the screen.

2023-01-10 Thread Elias

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

--- Comment #1 from Elias  ---
(In reply to Elias from comment #0)
And I managed to attach the wrong image..
Sorry, first time here.

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

[filelight] [Bug 464114] New: Alt + TAB'ing out of filelight whilist hovering over a address makes the info pop-up stuck to the screen.

2023-01-10 Thread Elias

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

Bug ID: 464114
   Summary: Alt + TAB'ing out of filelight whilist hovering over a
address makes the info pop-up stuck to the screen.
Classification: Applications
   Product: filelight
   Version: 22.12.0
  Platform: Manjaro
OS: Linux
Status: REPORTED
  Severity: minor
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: elpi2...@gmail.com
CC: martin.sandsm...@kde.org
  Target Milestone: ---

Created attachment 155188
  --> https://bugs.kde.org/attachment.cgi?id=155188&action=edit
Image of the pop-up being stuck. As an example I Alt + Tabbed out and closed
everything to view the desktop.

SUMMARY


STEPS TO REPRODUCE
1. Open Filelight to a drive/folder piechart
2. Hover your mouse over a chunk of the pie so a little pop-up gives the
address, size and amount of files
3. Alt + TAB out of filelight

OBSERVED RESULT
The pop-up gets stuck with its info still on it.

EXPECTED RESULT
It would be expected that the pop-up doesn't stay on after tabbing out.

It can be easily fixed when going back to Filelight, and hovering over another
address chunk, then taking your mouse off of Filelight before Alt + Tabbing

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Manjaro Linux
KDE Plasma Version: 5.26.4
KDE Frameworks Version: 5.101.0
Qt Version: 5.15.7

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

[systemsettings] [Bug 424597] Night color is not activated if display output is changed

2022-12-21 Thread Elias

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

Elias  changed:

   What|Removed |Added

 CC||supg...@gmail.com

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

[systemsettings] [Bug 450288] Night colors aren't applied if login takes place during the "night"

2022-12-21 Thread Elias

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

--- Comment #5 from Elias  ---
(In reply to Elias from comment #4)
> For me, deleting the autostart entry (on Fedora:
> `/etc/xdg/autostart/nvidia-settings-user.desktop`) (filename could be
> different depending on distribution, look in your `/etc/xdg/autostart`) did
> help.

...However keep in mind this is only a workaround and may have side effects
(your custom nvidia config won't load anymore, if you have one). Ideally Plasma
should wait until the `nvidia-settings --load-config-only` command (run by the
autostart entry) finished executing and only after that activate Night Color.

An alternative workaround:
Add a script to your autostart which toggles Night Color two times, with a
little delay, after login. Example:
```
#!/bin/bash
sleep 2
qdbus org.kde.kglobalaccel /component/kwin
org.kde.kglobalaccel.Component.invokeShortcut "Toggle Night Color"
sleep 1
qdbus org.kde.kglobalaccel /component/kwin
org.kde.kglobalaccel.Component.invokeShortcut "Toggle Night Color"
```

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

[systemsettings] [Bug 450288] Night colors aren't applied if login takes place during the "night"

2022-12-21 Thread Elias

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

Elias  changed:

   What|Removed |Added

 CC||supg...@gmail.com

--- Comment #4 from Elias  ---
Hi, I noticed one thing that contributes to the problem on Nvidia systems. Some
distributions (Fedora, Ubuntu, Pop,...) package an auto start entry which
executes the command
`nvidia-settings --load-config-only`
after every user login. This should load the nvidia configuration file (if you
have one) but unfortunately at the same time resets your color profile.

What happens is that Night Color activates on login, works for about one
second, but shortly after the autostart command is run, nvidia config is loaded
and colors are reset.

For me, deleting the autostart entry (on Fedora:
`/etc/xdg/autostart/nvidia-settings-user.desktop`) (filename could be different
depending on distribution, look in your `/etc/xdg/autostart`) did help.
Now Night Color works at least most of the time after login.
But it still sometimes fails to activate after first login after boot, so there
seems yet something else involved.

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

2022-10-12 Thread Elias

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

Elias  changed:

   What|Removed |Added

 CC||mosa...@posteo.de

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

[plasma-pa] [Bug 435142] Toggle microphone only changes default microphone

2022-09-14 Thread Elias

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

Elias  changed:

   What|Removed |Added

 CC||supg...@gmail.com

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

[plasmashell] [Bug 428757] Microphone tray applet's mute toggle function doesn't always mute the selected microphones; consider making it mute ALL microphones

2022-09-14 Thread Elias

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

Elias  changed:

   What|Removed |Added

 CC||supg...@gmail.com

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

[plasma-systemmonitor] [Bug 444323] Memory usage is not shown for processes owned by other users

2022-07-21 Thread Elias

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

Elias  changed:

   What|Removed |Added

 CC||mosa...@posteo.de

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

[plasmashell] [Bug 456720] New: Plasma crashes when trying to show more information about a network

2022-07-14 Thread Elias

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

Bug ID: 456720
   Summary: Plasma crashes when trying to show more information
about a network
   Product: plasmashell
   Version: 5.25.3
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: elbert.le...@outlook.de
CC: k...@davidedmundson.co.uk
  Target Milestone: 1.0

Application: plasmashell (5.25.3)

Qt Version: 5.15.5
Frameworks Version: 5.96.0
Operating System: Linux 5.15.0-41-generic x86_64
Windowing System: Wayland
Distribution: KDE neon User - 5.25
DrKonqi: 5.25.3 [KCrashBackend]

-- Information about the crash:
I am connected to a LAN connection and to a Wifi connection. When I open the
network panel in the taskbar and click at the arrow next to each available
connection, it firsts expands the box of the specific network but with nothing
in it. Then my whole PC freezes for a few seconds. After that The network panel
gets white (I am using dark mode) and blurred out. Then Plasma chrashes and the
taskbar disappears, after a further few seconds, it's there again.

The crash can be reproduced every time.

-- Backtrace:
Application: Plasma (plasmashell), signal: Aborted

[New LWP 1311]
[New LWP 1312]
[New LWP 1342]
[New LWP 1493]
[New LWP 1495]
[New LWP 1621]
[New LWP 1976]
[New LWP 2062]
[New LWP 2063]
[New LWP 2064]
[New LWP 2183]
[New LWP 2184]
[New LWP 2185]
[New LWP 3393]
[New LWP 3394]
[New LWP 3395]
[New LWP 3414]
[New LWP 3416]
[New LWP 3417]
[New LWP 6301]
[New LWP 6302]
[New LWP 6303]
[New LWP 6304]
[New LWP 6305]
[New LWP 6306]
[New LWP 6307]
[New LWP 6308]
[New LWP 6309]
[New LWP 6310]
[New LWP 6311]
[New LWP 6336]
[New LWP 7444]
[New LWP 7445]
[New LWP 7446]
[New LWP 7517]
[New LWP 7518]
[New LWP 7519]
[New LWP 7527]
[New LWP 7528]
[New LWP 7529]
[New LWP 13639]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
futex_wait_cancelable (private=, expected=0,
futex_word=0x5647911aa1c4) at ../sysdeps/nptl/futex-internal.h:183
__preamble__
[Current thread is 1 (Thread 0x7f365cbc99c0 (LWP 1290))]

Thread 42 (Thread 0x7f35a57fa700 (LWP 13639)):
#0  0x7f3660aac46e in epoll_wait (epfd=57, events=0x7f35a57f97f0,
maxevents=32, timeout=-1) at ../sysdeps/unix/sysv/linux/epoll_wait.c:30
#1  0x7f36145cf27b in  () at
/usr/lib/x86_64-linux-gnu/spa-0.2/support/libspa-support.so
#2  0x7f36145c16f4 in  () at
/usr/lib/x86_64-linux-gnu/spa-0.2/support/libspa-support.so
#3  0x7f361461c0e0 in  () at /lib/x86_64-linux-gnu/libpipewire-0.3.so.0
#4  0x7f36607c2609 in start_thread (arg=) at
pthread_create.c:477
#5  0x7f3660aac133 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 41 (Thread 0x7f359d0ab700 (LWP 7529)):
#0  futex_wait_cancelable (private=, expected=0,
futex_word=0x564790bce1b0) at ../sysdeps/nptl/futex-internal.h:183
#1  __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x564790bce160,
cond=0x564790bce188) at pthread_cond_wait.c:508
#2  __pthread_cond_wait (cond=0x564790bce188, mutex=0x564790bce160) at
pthread_cond_wait.c:647
#3  0x7f3660e355fb in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at
/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f3662acf2f4 in  () at /lib/x86_64-linux-gnu/libQt5Quick.so.5
#5  0x7f3662acf769 in  () at /lib/x86_64-linux-gnu/libQt5Quick.so.5
#6  0x7f3660e2f553 in  () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f36607c2609 in start_thread (arg=) at
pthread_create.c:477
#8  0x7f3660aac133 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 40 (Thread 0x7f359e4ec700 (LWP 7528)):
#0  futex_wait_cancelable (private=, expected=0,
futex_word=0x56479324fc30) at ../sysdeps/nptl/futex-internal.h:183
#1  __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x56479324fbe0,
cond=0x56479324fc08) at pthread_cond_wait.c:508
#2  __pthread_cond_wait (cond=0x56479324fc08, mutex=0x56479324fbe0) at
pthread_cond_wait.c:647
#3  0x7f364a63a5eb in  () at /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
#4  0x7f364a63a1eb in  () at /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
#5  0x7f36607c2609 in start_thread (arg=) at
pthread_create.c:477
#6  0x7f3660aac133 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 39 (Thread 0x7f359d8ac700 (LWP 7527)):
#0  futex_wait_cancelable (private=, expected=0,
futex_word=0x5647931aca00) at ../sysdeps/nptl/futex-internal.h:183
#1  __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x5647931ac9b0,
cond=0x5647931ac9d8) at pthread_cond_wait.c:508
#2  __pthread_cond_wait (cond=0x5647931ac9d8, mutex=0x5647931ac9b0) at
pthread_cond_wait.c:647
#3  0x7f364a63a5eb in  () at /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
#4  0x7f364a63a1eb in  () at /usr/lib/x86_64-l

[kwin] [Bug 443410] Please restore the Desktop Cube switching effect

2022-05-31 Thread Elias

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

Elias  changed:

   What|Removed |Added

 CC||el...@kesh.com

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

[frameworks-kconfig] [Bug 427875] On a multi screen setup, KDE app windows do not remember size, position, or the screen they were last opened on. For X11 when the left-most display is not the primary

2022-04-06 Thread Elias

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

Elias  changed:

   What|Removed |Added

 CC||mosa...@posteo.de

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

[kwin] [Bug 448839] [NVIDIA Wayland] Screen recording and task manager's window thumbnails are black

2022-03-30 Thread Elias

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

Elias  changed:

   What|Removed |Added

 CC||supg...@gmail.com

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

[kwin] [Bug 451906] Blackscreen with mouse pointer only on wayland when multiple displays are connected

2022-03-29 Thread Elias

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

Elias  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED

--- Comment #3 from Elias  ---
> Elias, does this affect all screens, or only one?

It did affect all screens, so it is not a duplicate. However the issue is no
more since I recreated my user account. Seems there was a problem with some
config or cache. I now created a new user and set up most of my stuff again and
it still works. (Well, despite of some graphical glichtes, but it is not black
anymore.)

I'm sorry to tell you that I forgot to take a backup of the old users dotfiles.
(Didn't really think that this would fix it, was just about resetting my user
anyway.) So we can't figure out what exactly caused the problem :/

I will mark this as resolved for now. Will see if the problem comes up again
after more configuration.

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

[kwin] [Bug 451906] New: Blackscreen with mouse pointer only on wayland when multiple displays are connected

2022-03-25 Thread Elias

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

Bug ID: 451906
   Summary: Blackscreen with mouse pointer only on wayland when
multiple displays are connected
   Product: kwin
   Version: 5.24.3
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: wayland-generic
  Assignee: kwin-bugs-n...@kde.org
  Reporter: supg...@gmail.com
  Target Milestone: ---

SUMMARY

When starting a Wayland session and multiple displays are connected to the gpu,
only a black screen is rendered with only the mouse pointer visible and
moveable.
When only one display is connected to the gpu, the wayland session correctly
renders the desktop.

STEPS TO REPRODUCE

1. Start KDE Wayland session

OBSERVED RESULT

Only black screen with mouse pointer is shown.

EXPECTED RESULT

Desktop should render correctly.

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: Arch Linux / KDE 5.24.3
KDE Plasma Version: 5.24.3
KDE Frameworks Version:  5.92.0
Qt Version: 5.15.3

ADDITIONAL INFORMATION
GPU: Nvidia GTX 1060, using nvidia v510.54 driver
Kernel: default 'linux' package from Arch, version 5.16.16-arch1-1

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

[xdg-desktop-portal-kde] [Bug 448944] xdg-desktop-portal only shows a black screen when trying to screenshare a whole screen in Wayland with Pipewire (NVIDIA GBM)

2022-03-25 Thread Elias

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

--- Comment #4 from Elias  ---
Lately (or only in my case?) this is not KDE specific. I tested on Gnome on
Fedora 36. Screencapture is also black there.

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

[kwin] [Bug 449797] Plasma 5.24 and nvidia GPU: segfault in KWin::GbmSurface::swapBuffersForDrm()

2022-02-26 Thread Elias

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

Elias  changed:

   What|Removed |Added

 CC||supg...@gmail.com

--- Comment #41 from Elias  ---
(In reply to Stefan from comment #34)
> So affected are KDE neon and openSUSE Tumbleweed but not Arch?

Can't confirm this. I'm on Archlinux and while Wayland session started with
Plasma 5.23, since 5.24 it is broken, I only see the login/start animation but
then it freezes on that and I can only move the mouse but no desktop showing
up.
Not sure if this is the exact same issue as described here, since I don't get
thrown back to sddm.

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

[xdg-desktop-portal-kde] [Bug 448944] xdg-desktop-portal only shows a black screen when trying to screenshare a whole screen in Wayland with Pipewire (NVIDIA GBM)

2022-02-10 Thread Elias

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

--- Comment #3 from Elias  ---
This is still broken with new Plasma 5.24.0 update and Nvidia drivers
v510.47.03 :/

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

[xdg-desktop-portal-kde] [Bug 448944] xdg-desktop-portal only shows a black screen when trying to screenshare a whole screen in Wayland with Pipewire (NVIDIA GBM)

2022-01-31 Thread Elias

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

Elias  changed:

   What|Removed |Added

 CC||supg...@gmail.com

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

[kmymoney] [Bug 448013] New: Unresponsive UI elements in "New File Setup" > "Select Accounts"

2022-01-06 Thread Elias Probst

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

Bug ID: 448013
   Summary: Unresponsive UI elements in "New File Setup" > "Select
Accounts"
   Product: kmymoney
   Version: 5.1.1
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: minor
  Priority: NOR
 Component: ux-ui
  Assignee: kmymoney-de...@kde.org
  Reporter: m...@eliasprobst.eu
  Target Milestone: ---

Created attachment 145151
  --> https://bugs.kde.org/attachment.cgi?id=145151&action=edit
Screenshot showing a vertically resized "Select Accounts" dialog

SUMMARY
When increasing the vertical window size in the "Select Accounts" dialog of the
"New File Setup" to get a better overview of the available account types, none
of the UI elements scale accordingly.

STEPS TO REPRODUCE
1. Start KMyMoney for the 1st time
2. Proceed in the wizard until the the "Select Accounts" dialog
3. Increase the vertical window size to get a better overview of the available
account types 

OBSERVED RESULT
The list of account types doesn't resize vertically together with the window
The vertically resized window leaves a lot of unused whitespace at its bottom 

EXPECTED RESULT
The list of account types increases its height when resizing the window
vertically.

SOFTWARE/OS VERSIONS
Windows: -
macOS: -
Linux/KDE Plasma: 
  KDE Plasma Version: 5.23.4 
  KDE Frameworks Version: 5.87.0
  Qt Version: 5.15.3

ADDITIONAL INFORMATION

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

[Discover] [Bug 447546] Immutable unattended updates UX

2021-12-29 Thread Elias

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

--- Comment #4 from Elias  ---
Since I'm not able to get this working reliably, I also created this reddit
post, in case someone has an idea over there:
https://www.reddit.com/r/kde/comments/rra0xe/need_help_setting_global_immutable_settings_kiosk/

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

[Discover] [Bug 447546] Immutable unattended updates UX

2021-12-28 Thread Elias

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

Elias  changed:

   What|Removed |Added

 Resolution|WORKSFORME  |WAITINGFORINFO

--- Comment #3 from Elias  ---
Noticed that this is not yet really a good solution. At least /etc/xdg.
Problem is that distributions already pack default kde settings into /etc/xdg
and if I put in my custom ones (auto and offline updates) they will get
overwritten by updates.
Would need another directory to load config files from which gets prioritized
over /etc/xdg, so that I can safely overwrite distributions defaults without
losing my settings after updates. How to add a path for kde configs between
/home/.config and /etc/xdg?

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

[Discover] [Bug 447546] Immutable unattended updates UX

2021-12-28 Thread Elias

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

Elias  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |WORKSFORME
 Status|NEEDSINFO   |RESOLVED

--- Comment #2 from Elias  ---
Put it in /etc/xdg/PlasmaDiscoverUpdates.
This worked, thanks.

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

[Discover] [Bug 447546] New: Feature: Global unattended updates

2021-12-26 Thread Elias

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

Bug ID: 447546
   Summary: Feature: Global unattended updates
   Product: Discover
   Version: 5.23.4
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: discover
  Assignee: lei...@leinir.dk
  Reporter: supg...@gmail.com
CC: aleix...@kde.org
  Target Milestone: ---

SUMMARY

There is an option in system settings for automatic updates. However this
option is only set for the current user (saved in
`~/.config/PlasmaDiscoverUpdates`). I want to enable auto updates for the whole
system. Users should not be able to disable auto updates by accident. I want to
have this setting somewhere in for example `/etc/PlasmaDiscoverUpdates`, not
writable for normal users.


STEPS TO REPRODUCE
1. Enable automatic updates for one user
2. Create a new user and see that automatic updates are disabled again

OBSERVED RESULT
Automatic updates do not work for new users and users can disable them by
accident.

EXPECTED RESULT
Automatic updates should be a system wide setting that only administrators can
change.

ADDITIONAL INFORMATION

A possible short solution would be (pseudo code):

if (file.exists("/etc/PlasmaDiscoverUpdates")) {
// load settings from /etc/PlasmaDiscoverUpdates
} else {
// load settings from ~/.config/PlasmaDiscoverUpdates`
}

And an alternative idea, would take longer to implement:
a whole new system wide service which runs as root and performs the updates,
not depending on user sessions or user settings at all.
This would also make auto updates more reliable in general, for example if
users are switched often (current idle timeout never runs out), multiple users
are logged in (conflicting auto updates run multiple times), and would make it
work even in cases where users do not have admin privileges to perform updates,
like in case of ubuntu, auto updates currently don't work at all because of
this:
https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1955489

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

[Discover] [Bug 447245] Auto updates do not work

2021-12-21 Thread Elias

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

--- Comment #1 from Elias  ---
Btw. on Debian+Ubuntu there is an addational bug wich prevents auto updates
from working. Not Discovers fault, but wanted to note that, for anyone testing.
The deb/ubuntu package for packagekit currently contains a patch which
disallows offline updates for non admin users and without a password prompt.
This makes offline updates never get triggered. You have to change
`/usr/share/polkit-1/actions/org.freedesktop.packagekit.policy` to get it
working.
See:
https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1955489

---

Also, adding to this I wrote before:

> If my assumption is true, this could be fixed by changing from 15 minutes of 
> idle to for example just 15 minutes after boot.

Instead of 'xx minutes after boot' maybe 'xx minutes after updates were found'
would be the better choice here.

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

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

2021-12-20 Thread Elias

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

Elias  changed:

   What|Removed |Added

 CC||supg...@gmail.com

--- Comment #18 from Elias  ---
(In reply to Méven Car from comment #16)
> It could be adapted somewhat with #ifdef based on KF version, but expect
> from rolling distro that should not reach many users.

This is not true. The upcoming Ubuntu 22.04 LTS will have KDE Gears 21.12 in
repos and already offers KF 5.89 (will most likely be updated again before
release, feature freeze is in february).
Ubuntu is a very well known distro, not rolling release and since the next
release is a LTS one, this is what many user over many years will get.
Please reconsider backporting in some form.

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

[Discover] [Bug 447245] Auto updates do not work

2021-12-19 Thread Elias

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

Elias  changed:

   What|Removed |Added

Version|unspecified |5.23.4

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

[Discover] [Bug 447245] New: Auto updates do not work

2021-12-19 Thread Elias

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

Bug ID: 447245
Summary: Auto updates do not work
Product: Discover
Version: unspecified
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: discover
Assignee: lei...@leinir.dk
Reporter: supg...@gmail.com
CC: aleix...@kde.org
Target Milestone: ---

Hi, I try to get auto updates working on a machine that I don't want to babysit
that often. The problem is that they work very unreliable. I had them working
only once in all the time I have the auto update setting enabled in the system
settings. But most times, the machine ends up on very old software, because the
auto updates do not get run.

STEPS TO REPRODUCE
1. Use Kubuntu 21.10 or 22.04 (dev branch)
2. Enable auto updates in system settings
3. Use the machine for work

OBSERVED RESULT

Auto updates nearly never get run.

EXPECTED RESULT

Auto updates should work reliably.

SOFTWARE/OS VERSIONS
Windows:
macOS:
Linux/KDE Plasma: Kubuntu 22.04
(available in About System)
KDE Plasma Version: 5.23.4
KDE Frameworks Version: 5.89
Qt Version: 5.15.2

ADDITIONAL INFORMATION

I already have a guess why this works so bad. Haven't found documentation for
how exactly this works (should be added btw) so I had a look at the source
code.
Here:
https://invent.kde.org/plasma/discover/-/blob/5ad26c9c66cd2b8913e2ee8bfaa93f9fa76d65c0/notifier/UnattendedUpdates.cpp#L33-36

It seems that it waits for an idle moment of 15 minutes (even tho the comment
says 1 hour, should be corrected and also made configurable).
I don't know what exactly "an idle moment" is. But if it means something like
no user input (no mouse movement or keyboard presses) for 15 minutes then this
may be the reason for my problem.
The machine I try to get auto updates working on is nearly never that long
unused while powered on. Usually it is booted, someone gets work done, and it
gets shut down again. Yeah, sometimes we get something to drink/eat in between
or go to the toilet, but this never takes 15 minutes, so there are no 15
minutes idles and this is most likely why auto updates never get triggered.

If my assumption is true, this could be fixed by changing from 15 minutes of
idle to for example just 15 minutes after boot.
Also, I think 15 minutes is a little long. Would recommend changing it to 10
minutes as default to make it more reliable in more cases, and also make it
configurable for those who have to adopt it to their usage.

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

[Discover] [Bug 416193] Expose update check interval as a configurable setting

2021-12-19 Thread Elias

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

Elias  changed:

   What|Removed |Added

 CC||supg...@gmail.com

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

[kwin] [Bug 442846] Plasma Wayland Freezes upon unlocking screen after leaving laptop with intel graphics idle for long time when using Firefox in XWayland mode

2021-12-02 Thread Elias

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

Elias  changed:

   What|Removed |Added

 CC||mosa...@posteo.de

--- Comment #13 from Elias  ---
I can reproduce this bug. But I think the reason for this happening has nothing
to do with the screen locker itself. The freeze happens just in the moment when
the monitor is sent to sleep (default after 10 min). So if you set this to 1
minute and de-activate screen locking the bug happens without a lock screen
involved. Everything freezes, mouse cursor is still movable.

The strange thing is that it does not happen on all monitors:
- I can reproduce this problem on a DELL S2421HN connected via HDMI to an AMD
graphics card. 
- On an older DELL model everything is fine. Also on a very old Fujitsu screen
connected with DVI.

Workaround:
De-activate automatic monitor power saving.

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

[plasmashell] [Bug 420160] Plasma crashes when monitor goes into standby

2021-09-22 Thread Elias

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

Elias  changed:

   What|Removed |Added

 CC||mosa...@posteo.de

--- Comment #58 from Elias  ---
(In reply to Leyenda from comment #57)

> > turned off screen
> > turned on screen
> > 
> > firefox still runs
> > only wallpaper and desktop icons on place

I can confirm that bahaviour on Fedora 34 with Plasma 2.22.90. My monitor is a
Dell UltraSharp U3417W.

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

[yakuake] [Bug 440128] Yakuake sticks on the activity it was started first

2021-08-27 Thread Elias Probst

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

Elias Probst  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 CC||m...@eliasprobst.eu
 Status|REPORTED|CONFIRMED

--- Comment #3 from Elias Probst  ---
I can confirm this, using:
- Gear/Yakuake 21.04.0
- Plasma 5.22.4
- Frameworks 5.84.0
- Qt 5.15.2
- Display server: X11
- OS: NixOS 21.11 (nixos-unstable-small)

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

[plasmashell] [Bug 439580] New: Localised button text truncated

2021-07-07 Thread Elias

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

Bug ID: 439580
   Summary: Localised button text truncated
   Product: plasmashell
   Version: 5.22.2
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Application Launcher (Kickoff)
  Assignee: k...@davidedmundson.co.uk
  Reporter: mosa...@posteo.de
CC: mikel5...@gmail.com, plasma-b...@kde.org
  Target Milestone: 1.0

Created attachment 139915
  --> https://bugs.kde.org/attachment.cgi?id=139915&action=edit
Plasmashell 5.22.2 Kickoff with German translation

In Kickoff 2.0 with German localisation enabled the text of the main action
buttons on the bottom of the menu is often truncated. 

Sometimes only one letter is hidden. But that could lead to misunderstanding
and looks awful. See screenshot attached.

It would be expected that the buttons expand in size so that the translated
text fits in completely. This could be an issue in other translations as well.

Reproduced with:
Fedora 34
KDE Plasma Version: 5.22.2
KDE Frameworks Version: 5.83.0
Qt Version: 5.15.2

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

[digikam] [Bug 433183] Migrate from "MySQL Server" database corrupts face/people metadata.

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

--- Comment #2 from Elias Gabrielsson  ---

I have tested the following cases which both produces a corrupted migration:
"MySQL Server" -> "SQLite"
"MySQL Server" -> "MySQL Server"

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

[digikam] [Bug 433183] Migrate from "MySQL Server" database corrupts face/people metadata.

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

Elias Gabrielsson  changed:

   What|Removed |Added

Summary|Migrate from "MySQL Server" |Migrate from "MySQL Server"
   |to "SQLite" corrupts|database corrupts
   |face/people metadata.   |face/people metadata.

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

[digikam] [Bug 433183] Migrate from "MySQL Server" to "SQLite" corrupts face/people metadata.

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

--- Comment #1 from Elias Gabrielsson  ---
Created attachment 135859
  --> https://bugs.kde.org/attachment.cgi?id=135859&action=edit
Wrong tag shown

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

[digikam] [Bug 433183] New: Migrate from "MySQL Server" to "SQLite" corrupts face/people metadata.

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

Bug ID: 433183
   Summary: Migrate from "MySQL Server" to "SQLite" corrupts
face/people metadata.
   Product: digikam
   Version: 7.2.0
  Platform: Microsoft Windows
OS: Microsoft Windows
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Database-Migration
  Assignee: digikam-bugs-n...@kde.org
  Reporter: elias.gabriels...@gmail.com
  Target Milestone: ---

SUMMARY:
Migration from "MySQL Server" to "SQLite" corrupts faces / people metadata.
- The face tag is stored as "IIM Application 2" -> "Keywords" in the IPTC
metadata tab. 
- All people are removed in people list. 
- The images will also be marked with "Scanned for Faces".


STEPS TO REPRODUCE
1. Setup MySQL Server and connect digikam.
2. Add image, tag face in image.
3. Scan databases for faces.
4. Add another image (will not be tagged "Scanned for Faces".
5. Open Migration tool, migrate "MySQL Server" to "SQLite".
6. Change database to internal "SQLite".
7. Restart Digikam to flush cache.
8. Open image and observe result.

OBSERVED RESULT


EXPECTED RESULT:
- Face and people tags should persist between migrations.  

SOFTWARE/OS VERSIONS
Windows: Windows 10
MariaDB 10.2, Digikam 7.2.0-RC

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

[Plasma Vault] [Bug 410457] System Integration for cloud usage (mounting/unlocking)

2021-02-07 Thread Elias

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

--- Comment #5 from Elias  ---
(In reply to Ivan Čukić from comment #4)
> To repeat, if you want encryption just for the cloud sync, which is unlocked 
> while you're logged in, Vault is not the solution. It is not Vault's 
> use-case. Vault is *not* going to support use-cases which blur the best 
> practices for its use-case.

Why is this not a use-case for plasma-vault?

This makes no sense because the default backend (cryfs) is mainly made for
exactly this purpose.
The first sentence on its website (https://www.cryfs.org/) is:

"Keep your data safe in the cloud"

So while cryfs is especially made for the cloud, it seems really off for
plasma-vault as a frontend to not support its main functionality.

In fact, cryfs and gocryptfs are perfect solutions to encrypt cloud storage.
EncFS was too in the past, but is not recommended anymore due to found security
issues.


> One of the interesting things I've been researching recently (which might end 
> up as a new KDE project at one point) is git+gpg which provides a nice 
> end-to-end encryption. The local files are not encrypted, but they are sent 
> properly encrypted to a git server. This would be a good tool for your 
> use-case.

While I think this would be an interesting project, it doesn't fit my use case.
My cloud is a simple file storage. The client just copies the files over. This
simple filesystem is just right, so I don't need a more complicated setup like
a git server. Also, I guess you can't just setup a git server on Dropbox or
Google Drive anyway, so this won't work.


> As mentioned before, the alternative is to set up the usual encrypted $HOME 
> (or some other directory) and sync the encrypted data with your cloud 
> provider. This would have the benefit of gpg+git with added protection 
> against device theft if it is stolen while powered off.

Also as mentioned before, this is not the solution for my use-case. The only
thing I want to prevent is that the people having access to the server my data
is stored on can not read it unencrypted.

Encrypting home will bring zero benefit for this. Since the cloud sync software
runs under my user after login, it will see the decrypted files and so upload
them unencrypted. This does not help at all in this use-case.

Also I'm already using Full Disk Encryption, so I'm already safe against device
theft.

---

I do not sacrifice security if the password is stored on my machine. This is
fine, since the cloud provider can't access my machine where the key is, they
will only get the encrypted vault / files which they can't ready without the
key.

Also, implementing a "save password" option would be good for consistency.

Plasma does already support saving the password for for example external
encrypted disks / storage.
Now imagine the cloud as another "external storage" since it is exactly this.

It would make sense for plasma to be consistent and support the same
functionality (in this case saving the password) for all encrypted external
storages the same.

---

And, just to be complete, here is one last reason to implement a password save
option:

Linux and Plasma are all about freedom and giving the options.
To refuse users use-cases seems off in this philosophy.

Nobody will be force to use this option when it is there, so it won't hurt
anyone, but only help some :)

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

[plasmashell] [Bug 432592] System monitor Sensor widget does not work well in text only mode in a panel

2021-02-06 Thread Elias

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

Elias  changed:

   What|Removed |Added

 CC||supg...@gmail.com

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

[plasmashell] [Bug 432592] New: System monitor Sensor widget does not work well in text only mode in a panel

2021-02-06 Thread Elias

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

Bug ID: 432592
Summary: System monitor Sensor widget does not work well in
text only mode in a panel
Product: plasmashell
Version: 5.20.5
Platform: Manjaro
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: System Monitor
Assignee: plasma-b...@kde.org
Reporter: supg...@gmail.com
CC: ahiems...@heimr.nl, notm...@gmail.com
Target Milestone: 1.0

SUMMARY

Hi, I want to see my current network up/down activity as text (something like 5
Mb/s down, 20 Kb/s up).
Luckily there is a widget called "System monitor Sensor".

It does exactly what I need. I just put it on the desktop and set it to text
only mode. It looks fine there:
https://invent.kde.org/plasma/plasma-desktop/uploads/c3f52c38887a41fdbc181d1850846f2b/image.png

However I want to see this information also while running maximized windows. So
I put the widget in my panel at the top of the screen so that is is always
visible. I also set it to display text only.

STEPS TO REPRODUCE
1. Add the widget "System monitor Sensor" configured to display network
activity on a panel
2. Change the display type to text only

OBSERVED RESULT

This is what it looks like, not displaying any text, looking broken:
https://invent.kde.org/plasma/plasma-desktop/uploads/34eeabad6056af714f9f3bfa78189e63/image.png

EXPECTED RESULT

And this is how I imagine it should look like:
https://invent.kde.org/plasma/plasma-desktop/uploads/b0ba9fd6e118c2a454ccbe00d30c432e/image.png

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Manjaro / Plasma 5.20.5
KDE Frameworks Version: 5.79.0
Qt Version: 5.15.2

ADDITIONAL INFORMATION

Here is a video of it:
https://www.youtube.com/watch?v=pS9qNQOzNh0

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

[Plasma Vault] [Bug 410457] System Integration for cloud usage (mounting/unlocking)

2021-02-06 Thread Elias

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

Elias  changed:

   What|Removed |Added

 Status|RESOLVED|REOPENED
 Ever confirmed|0   |1
 Resolution|INTENTIONAL |---

--- Comment #3 from Elias  ---
> Integration with KWallet is out of the question as it would render Vaults 
> useless.

Not in the use case of a cloud, not wanting to give unencrypted files to the
cloud provider.

> There is no point in keeping something encrypted if the encryption key is 
> easily accessible.

This is no problem since the encrypting key will only be stored on my machine
and will not be accessible by the cloud provider.

---

I use a plasma vault for encrypting my files before they are seen by the cloud
client so that it uploads the files encrypted. I do not care about locally
encrypting the files. The whole purpose of this is that the cloud provider /
server does only get encrypted versions of the files.

For this usecase storing the password unencrypted on my computer is okay. It
will not destroy the purpose of the vault and will still do the job.

> There are already better tools for this use-case. You should encrypt user's 
> home directory, or better, create an encrypted /home partition.

Encrypting the /home directory will not help at all with this. (I'm already
using FDE anyway.)
The cloud client runs after user login and syncs the files it sees in its
directory. They will be unlocked at that time, even with encrypted /home. So
the cloud client would upload the unencrypted files. This would solve nothing.
Another layer in between is needed. For example by using plasma-vault ;)

---

> Vaults are meant and designed to be small encrypted containers [...] that are 
> in the locked state for as much as they can be.

Yes I would want to keep them closed while not used. (I have multiple vaults on
my cloud for different things.)
This way, they eat up less memory of my machine and I'm a little more safe
against accidental changes by me.

But currently, closing and later reopening a vault is not very user friendly. I
always have to type my password, which is not very fun when your password is
mad of many random chars/symbols.
It would be much faster if I could just open/close vaults with one click.
For that, an option to remeber the password is required.

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

[Plasma Vault] [Bug 410457] System Integration for cloud usage (mounting/unlocking)

2021-02-06 Thread Elias

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

Elias  changed:

   What|Removed |Added

 CC||supg...@gmail.com

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

[Plasma Vault] [Bug 410457] System Integration for cloud usage (mounting/unlocking)

2021-02-06 Thread Elias

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

Elias  changed:

   What|Removed |Added

 CC|eliassicher...@gmail.com|

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

[Plasma Vault] [Bug 410457] System Integration for cloud usage (mounting/unlocking)

2021-02-06 Thread Elias

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

Elias  changed:

   What|Removed |Added

 CC||eliassicher...@gmail.com

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

[Plasma Vault] [Bug 410457] System Integration for cloud usage (mounting/unlocking)

2021-02-06 Thread Elias

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

Elias  changed:

   What|Removed |Added

 CC|eliassicher...@gmail.com|

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

[Plasma Vault] [Bug 410457] System Integration for cloud usage (mounting/unlocking)

2021-02-06 Thread Elias

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

Elias  changed:

   What|Removed |Added

 CC||eliassicher...@gmail.com

--- Comment #1 from Elias  ---
This would be very useful. Are there any news about this?

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

[kmymoney] [Bug 430163] KMyMoney crash on opening

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

--- Comment #10 from Daniel Elias  ---
Created attachment 134299
  --> https://bugs.kde.org/attachment.cgi?id=134299&action=edit
Image03

Error that occurs after entering currency information.

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

[kmymoney] [Bug 430163] KMyMoney crash on opening

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

--- Comment #9 from Daniel Elias  ---
Created attachment 134298
  --> https://bugs.kde.org/attachment.cgi?id=134298&action=edit
Image02

Second screen, when I select the currency information and confirm.

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

[kmymoney] [Bug 430163] KMyMoney crash on opening

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

--- Comment #8 from Daniel Elias  ---
Created attachment 134297
  --> https://bugs.kde.org/attachment.cgi?id=134297&action=edit
Image01

First screen, when I enter the information about connecting to the database.

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

[kmymoney] [Bug 430163] KMyMoney crash on opening

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

Daniel Elias  changed:

   What|Removed |Added

 Status|NEEDSINFO   |REPORTED
 Resolution|WAITINGFORINFO  |---
 Ever confirmed|1   |0

--- Comment #7 from Daniel Elias  ---
I added screenshots of the screens, following the steps until the error
occurred.
In fact, this error occurs in any type of database.

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

[kmymoney] [Bug 430163] KMyMoney crash on opening

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

--- Comment #5 from Daniel Elias  ---
(In reply to Jack from comment #3)
> What do you mean "currency configuration is requested?"  Is this trying to
> set up a new instance of KMM using Postgres or are you trying to access an
> already set up database?
> If you invoke KMM from command line, is there any other output to console
> that might be useful in tracking down the cause?

Hello!
1. I'm trying access a new instance of KMM using Postgres. I think the currency
configuration is the last step before configuration accounts, which I haven't
yet reached.
2. When I invoke KMM from the terminal (Linux), and follow the same procedure
(currency configuration), I get this:

terminate called after throwing an instance of 'MyMoneyException'
  what():  Unknown account id 'AStd::Asset'
/build/kmymoney-wh5VtB/kmymoney-5.1.0/kmymoney/mymoney/storage/mymoneystoragemgr.cpp:142
KCrash: crashing... crashRecursionCounter = 2
KCrash: Application Name = kmymoney path = /usr/bin pid = 291268
KCrash: Arguments: /usr/bin/kmymoney 
KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi from
kdeinit
sock_file=/run/user/1000/kdeinit5__0

It should be noted that the error occurs in both cases: when I select the
currency and close the window, or when I simply close the currency selection
window without defining it.

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

[kmymoney] [Bug 430163] KMyMoney crash on opening

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

--- Comment #2 from Daniel Elias  ---
Qt5 lib versions:

libqt5core5a:amd64 (5.11.3+dfsg1-1+deb10u4)
libqt5sql5:amd64 (5.11.3+dfsg1-1+deb10u4)
libqt5sql5-psql:amd64 (5.11.3+dfsg1-1+deb10u4)

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

[kmymoney] [Bug 430163] KMyMoney crash on opening

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

Daniel Elias  changed:

   What|Removed |Added

   Platform|unspecified |Debian stable

--- Comment #1 from Daniel Elias  ---
PostgreSQL 12.5 (Debian 12.5-1.pgdg100+1) on x86_64-pc-linux-gnu, compiled by
gcc (Debian 8.3.0-6) 8.3.0, 64-bit

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

[kde] [Bug 430163] New: KMyMoney crash on opening