[kmymoney] [Bug 479131] Scheduled transactions always have one month frequency regardless of the set value

[Szőts Ákos]

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

Szőts Ákos  changed:

   What|Removed |Added

 Status|RESOLVED|REPORTED
 Resolution|WORKSFORME  |---

--- Comment #4 from Szőts Ákos  ---
I did some more financial accounting in KMyMoney which involved scheduled
transactions and I figured out what is the issue.

When you create a new scheduled transaction, the window has the defaults
already filled out. This includes the one month frequency setting  and the T+1
month as the next occurrence date pre-filled.

However, when you change the frequency to something else than exactly one
month, e.g. to one year, the next occurrence date won't change, it still stays
as today + 1 month.

The problem is that the correction from the user side is not automatic (and
also not apparent that it has to be made; this is why this bug report was born
in the first place).

The user has the following choices:
- Calculate themselves manually when the next occurrence will happen, including
bank holidays, etc and put that value in. This can be done by KMyMoney in other
cases.
- Set the next occurrence date back to today, and cancel today's event manually
in the ledger. This way the next real occurrence will be automatic (my
solution).

All of these depend on that the user noticed that the next occurrence date
became invalid at the point when they changed the frequency or the frequency
value.

If the next occurrence is in less than one month, KMyMoney will probably skip
that, too, until T+1 month kicks in.

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

[systemsettings] [Bug 368063] NumLock is not turned on at start, although the preference for it is set to `on` in kcm_keyboard

[Szőts Ákos]

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

--- Comment #62 from Szőts Ákos  ---
This is a 2016 bug which was marked as fixed on an unspecified date.

485940, which was marked as a duplicate of this, is fairly new. In order not to
close a valid bug as "fixed", "duplicate", may I ask when was this bug fixed?
If you take a look at 485940, multiple people are still bumping into this issue
in 6.0.4.

If you think 485940 is a still valid and new bug, please, reopen it as such.

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

[plasmashell] [Bug 486128] New: Plasma floating panel sometimes goes to top

[Szőts Ákos]

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

Bug ID: 486128
   Summary: Plasma floating panel sometimes goes to top
Classification: Plasma
   Product: plasmashell
   Version: 6.0.4
  Platform: openSUSE
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Panel
  Assignee: plasma-b...@kde.org
  Reporter: szots...@gmail.com
CC: niccolo.venera...@gmail.com
  Target Milestone: 1.0

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

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

SUMMARY

My panel (which shows the running applications) is normally in the bottom.
However, sometimes, seemingly randomly, it goes to top and I cannot move it
back down with anything obvious. It covers the top of every windows, too.

"plasmashell --replace" fixes it.

STEPS TO REPRODUCE (randomly)
1. Minimise all windows
2. Scroll on the background to get to another virtual desktop

OBSERVED RESULT

Plasma panel goes to top

EXPECTED RESULT

Panel stays wherever it was at that time.

SOFTWARE/OS VERSIONS

Operating System: openSUSE Tumbleweed 20240418
KDE Plasma Version: 6.0.4
KDE Frameworks Version: 6.1.0
Qt Version: 6.7.0
Kernel Version: 6.8.6-1-default (64-bit)
Graphics Platform: X11

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

[Spectacle] [Bug 484597] Print screen button doesn't start Spectacle

[Szőts Ákos]

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

--- Comment #7 from Szőts Ákos  ---
No, I have only one monitor with multiple inputs. Spectacle starts for both
kinds of invocation.

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

[systemsettings] [Bug 485941] New: Caps Lock works even though it supposed to be disabled

[Szőts Ákos]

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

Bug ID: 485941
   Summary: Caps Lock works even though it supposed to be disabled
Classification: Applications
   Product: systemsettings
   Version: 6.0.4
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: kcm_keyboard
  Assignee: plasma-b...@kde.org
  Reporter: szots...@gmail.com
CC: butir...@gmail.com, natalie_clar...@yahoo.de
  Target Milestone: ---

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

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

STEPS TO REPRODUCE
1. System Settings > Keyboard > Model: Generic 105 keys
2. Advanced > Caps Lock behaviour > enable "Disable Caps Lock"
3. Reboot

OBSERVED RESULT

When I press Caps Lock, it turns on, despite its setting to be turned off. Even
the notifier tray icon appears that it's on.

EXPECTED RESULT

Caps Lock remains disabled.

SOFTWARE/OS VERSIONS
Operating System: openSUSE Tumbleweed 20240418
KDE Plasma Version: 6.0.4
KDE Frameworks Version: 6.1.0
Qt Version: 6.7.0
Kernel Version: 6.8.6-1-default (64-bit)
Graphics Platform: X11

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

[systemsettings] [Bug 485940] New: NumLock is off when Plasma starts (even though it's configured to be on)

[Szőts Ákos]

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

Bug ID: 485940
   Summary: NumLock is off when Plasma starts (even though it's
configured to be on)
Classification: Applications
   Product: systemsettings
   Version: 6.0.4
  Platform: openSUSE
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: kcm_keyboard
  Assignee: plasma-b...@kde.org
  Reporter: szots...@gmail.com
CC: butir...@gmail.com, natalie_clar...@yahoo.de
  Target Milestone: ---

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

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

STEPS TO REPRODUCE
1. System Settings > Keyboard > Model: Generic 105 keys
2. NumLock on Plasma Startup: Turn on
3. Reboot

OBSERVED RESULT

NumLock is off

EXPECTED RESULT

NumLock is on.

Keyboard: Logitech MX Keys



SOFTWARE/OS VERSIONS

Operating System: openSUSE Tumbleweed 20240418
KDE Plasma Version: 6.0.4
KDE Frameworks Version: 6.1.0
Qt Version: 6.7.0
Kernel Version: 6.8.6-1-default (64-bit)
Graphics Platform: X11

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

[Spectacle] [Bug 484597] Print screen button doesn't start Spectacle

[Szőts Ákos]

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

Szőts Ákos  changed:

   What|Removed |Added

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

--- Comment #5 from Szőts Ákos  ---
This is the relevant section for Spectacle from the file:

[services][org.kde.spectacle.desktop]
ActiveWindowScreenShot=none
FullScreenScreenShot=none
RectangularRegionScreenShot=none
_launch=Meta+Shift+Print

Apart from it, do you need the full config file?

I remember Print Screen disappeared (or never appeared) during the change of
KSnapshot -> Spectacle change. If I recall correctly, during KSnapshot time it
wasn't always bound to start that application and I think I never received this
functionality.

I can, of course, bind it, but that won't help for the other long-time users
who have the same problem and therefore I don't want alter the current
debuggable configuration.

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

[Spectacle] [Bug 484597] Print screen button doesn't start Spectacle

[Szőts Ákos]

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

Szőts Ákos  changed:

   What|Removed |Added

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

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

[Spectacle] [Bug 484597] Print screen button doesn't start Spectacle

[Szőts Ákos]

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

--- Comment #3 from Szőts Ákos  ---
Created attachment 167855
  --> https://bugs.kde.org/attachment.cgi?id=167855=edit
Shortcuts screenshot

It says Meta+Shift+Print. I'm 99% sure that I haven't set this shortcut.

I'm sorry that it's in Hungarian, but for some reason `LC_ALL=C.UTF-8
systemsettings` doesn't change the individual KCM pages to English (just the
main window). I hope that the localisation doesn't change the order and you can
match with your setup.

This is what xev reports back for pressing and releasing the print screen
button:

KeyPress event, serial 41, synthetic NO, window 0x441,
root 0x1e1, subw 0x0, time 60011851, (1094,485), root:(1097,521),
state 0x10, keycode 107 (keysym 0xff61, Print), same_screen YES,
XLookupString gives 0 bytes: 
XmbLookupString gives 0 bytes: 
XFilterEvent returns: False

KeyRelease event, serial 41, synthetic NO, window 0x441,
root 0x1e1, subw 0x0, time 60011971, (1094,485), root:(1097,521),
state 0x10, keycode 107 (keysym 0xff61, Print), same_screen YES,
XLookupString gives 0 bytes: 
XFilterEvent returns: False

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

[Spectacle] [Bug 484597] Print screen button doesn't start Spectacle

[Szőts Ákos]

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

--- Comment #1 from Szőts Ákos  ---
I came from an old KDE installation, so it's not a fresh install.

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

[Spectacle] [Bug 484597] New: Print screen button doesn't start Spectacle

[Szőts Ákos]

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

Bug ID: 484597
   Summary: Print screen button doesn't start Spectacle
Classification: Applications
   Product: Spectacle
   Version: 24.02.0
  Platform: openSUSE
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: General
  Assignee: noaha...@gmail.com
  Reporter: szots...@gmail.com
CC: k...@david-redondo.de
  Target Milestone: ---

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

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

SUMMARY

If I press the "Print screen" button on my keyboard, nothing happens.

EXPECTED RESULT

Spectacle starts

SOFTWARE/OS VERSIONS
Operating System: openSUSE Tumbleweed 20240318
KDE Plasma Version: 6.0.2
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2
Kernel Version: 6.7.9-1-default (64-bit)
Graphics Platform: X11

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

[dolphin] [Bug 484596] New: Shift+Ins doesn't work in Dolphin Konsole part

[Szőts Ákos]

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

Bug ID: 484596
   Summary: Shift+Ins doesn't work in Dolphin Konsole part
Classification: Applications
   Product: dolphin
   Version: 24.02.0
  Platform: openSUSE
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: panels: terminal
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: szots...@gmail.com
CC: kfm-de...@kde.org
  Target Milestone: ---

Created attachment 167844
  --> https://bugs.kde.org/attachment.cgi?id=167844=edit
Keyboard shortcuts view

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

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

SUMMARY

"Paste" shortcut is ambiguous in Dolphin for Shift+Ins.

STEPS TO REPRODUCE
1. Open Dolphin Konsole view (F4)
2. Try to paste something from the clipboard with Shift+Ins


OBSERVED RESULT

"The key sequence 'Shift+Ins' is ambiguous. Use 'Configure Keyboard Shortcuts'
from the 'Settings' menu to solve the ambiguity.
No action will be triggered."

EXPECTED RESULT

Paste happens

SOFTWARE/OS VERSIONS
Operating System: openSUSE Tumbleweed 20240318
KDE Plasma Version: 6.0.2
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2
Kernel Version: 6.7.9-1-default (64-bit)
Graphics Platform: X11

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

[plasma-systemmonitor] [Bug 484595] New: Ctrl+Esc doesn't invoke System monitor anymore

[Szőts Ákos]

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

Bug ID: 484595
   Summary: Ctrl+Esc doesn't invoke System monitor anymore
Classification: Applications
   Product: plasma-systemmonitor
   Version: 6.0.2
  Platform: openSUSE
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: ksysguard-b...@kde.org
  Reporter: szots...@gmail.com
CC: ahiems...@heimr.nl, plasma-b...@kde.org
  Target Milestone: ---

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

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

SUMMARY

In KDE 5 Ctrl+Esc invoked system monitor (similarly to Windows). With Plasma 6
this shortcut doesn't work anymore and nothing happens.

Please, restore this behaviour, it was very comfortable. Probably, I could look
around in system settings hotkeys section but that won't help the other users.


SOFTWARE/OS VERSIONS
Operating System: openSUSE Tumbleweed 20240318
KDE Plasma Version: 6.0.2
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2
Kernel Version: 6.7.9-1-default (64-bit)
Graphics Platform: X11

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

[kwin] [Bug 479250] Brief screen freeze when opening Thumbnail Grid tabbox

[Szőts Ákos]

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

Szőts Ákos  changed:

   What|Removed |Added

 CC||szots...@gmail.com

--- Comment #8 from Szőts Ákos  ---
*** Bug 484134 has been marked as a duplicate of this bug. ***

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

[systemsettings] [Bug 484134] Quick Alt+Tabbing has a big delay when the QML tab switcher visualisation is enabled

[Szőts Ákos]

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

Szőts Ákos  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |DUPLICATE
 Status|NEEDSINFO   |RESOLVED

--- Comment #3 from Szőts Ákos  ---
It is indeed the same bug; thanks for the hint.

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

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

[systemsettings] [Bug 484134] New: Quick Alt+Tabbing has a big delay when the QML tab switcher visualisation is enabled

[Szőts Ákos]

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

Bug ID: 484134
   Summary: Quick Alt+Tabbing has a big delay when the QML tab
switcher visualisation is enabled
Classification: Applications
   Product: systemsettings
   Version: 6.0.2
  Platform: openSUSE
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: kcm_kwintabbox
  Assignee: kwin-bugs-n...@kde.org
  Reporter: szots...@gmail.com
CC: plasma-b...@kde.org
  Target Milestone: ---

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

Previously, in KDE 5, when I pressed Alt+Tab+Tab very quickly (and released
it), then I have the second window in front of me, effectively immediately.

Now, in KDE 6, after the same sequence, I have a ~700 ms delay before the
window is shown and after that the tab box visualisation is even flashed for
some ms (basically, just its borders are drawn, its content I can't see because
it disappears very quickly).

Simple Alt+Tab is also very slow and suffers from the same.

If I turn off the tab box visualisation in system settings, this delay is gone.

This is the default tab switcher which comes with KDE 6 (first item in the
list; I have it in another language).

EXPECTED RESULT

Either the tab switcher is displayed immediately and introduces no delay or not
displayed at all and, again, introducing no delay.

SOFTWARE/OS VERSIONS
Operating System: openSUSE Tumbleweed 20240318
KDE Plasma Version: 6.0.2
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2
Kernel Version: 6.7.9-1-default (64-bit)
Graphics Platform: X11
Graphics Processor: NVIDIA GeForce RTX
System Version: 1.0

ADDITIONAL INFORMATION

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

[kwin] [Bug 484132] New: Night color is not applied until KWin is restarted

[Szőts Ákos]

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

Bug ID: 484132
   Summary: Night color is not applied until KWin is restarted
Classification: Plasma
   Product: kwin
   Version: 6.0.2
  Platform: openSUSE
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: szots...@gmail.com
  Target Milestone: ---

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

I configured KDE night colour to be always have an effect during daytime (and
stronger effect during night time).

When KDE starts and the splash screen appears on X11 I see that the KDE logo is
tinted yellow which means that the night colour is on. However, during this
start-up sequence it suddenly changes to white and night colour gets turned off
until I restart kwin with "kwin_x11 --replace".

The same happens after a suspend/resume cycle: night colour is lost until KWin
is restarted.

SOFTWARE/OS VERSIONS
Operating System: openSUSE Tumbleweed 20240318
KDE Plasma Version: 6.0.2
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2
Kernel Version: 6.7.9-1-default (64-bit)
Graphics Platform: X11
Graphics Processor: NVIDIA GeForce RTX (driver: 550.54.14)
System Version: 1.0

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

[plasmashell] [Bug 484129] New: KDE turns down my screen brightness to 9%

[Szőts Ákos]

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

Bug ID: 484129
   Summary: KDE turns down my screen brightness to 9%
Classification: Plasma
   Product: plasmashell
   Version: 6.0.2
  Platform: openSUSE
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Brightness Control
  Assignee: plasma-b...@kde.org
  Reporter: szots...@gmail.com
CC: natalie_clar...@yahoo.de
  Target Milestone: 1.0

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

After resuming from sleep or when I switch to a different input on my monitor,
the screen brightness is down to 9%. I have to manually align it on my monitor
back to 20-something just to notice that KDE didn't check its current value and
sets it to 9% again.

So in the applet I set it to 20% but after a suspend/resume cycle or when I
switch to a different input with my KDE PC is still on, I see _on the other
input_ that my screen brightness is down again.

In "Power saving" module the "Change screen brightness" option is off, so I
don't know where else to turn it off within KDE.

Anyhow, I switched off DDC/CI inside my monitor which breaks some of other
stuff but it's still less annoying that way.

SOFTWARE/OS VERSIONS
Operating System: openSUSE Tumbleweed 20240318
KDE Plasma Version: 6.0.2
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2
Kernel Version: 6.7.9-1-default (64-bit)
Graphics Platform: X11
Graphics Processor: NVIDIA GeForce RTX
System Version: 1.0

ADDITIONAL INFORMATION

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

[kmymoney] [Bug 479131] New: Scheduled transactions always have one month frequency regardless of the set value

[Szőts Ákos]

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

Bug ID: 479131
   Summary: Scheduled transactions always have one month frequency
regardless of the set value
Classification: Applications
   Product: kmymoney
   Version: 5.1.3
  Platform: openSUSE
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kmymoney-de...@kde.org
  Reporter: szots...@gmail.com
  Target Milestone: ---

Create a new scheduled transaction with other than "1 month" schedule. My
examples are "1 year" and "28 days".

No matter what I set in the frequency drop-down, in the ledger the next
instance appears exactly one month later anyway.

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

[plasmashell] [Bug 465441] plasmashell leaks memory after each resume (currently around 23 GB) [with heaptrack] in plasmadesktoptheme.cpp:231

[Szőts Ákos]

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

--- Comment #5 from Szőts Ákos  ---
Created attachment 160131
  --> https://bugs.kde.org/attachment.cgi?id=160131=edit
30 GB Plasma leak

Just wanted to confirm that in the latest version it's still an issue.

Operating System: openSUSE Tumbleweed 20230603
KDE Plasma Version: 5.27.5
KDE Frameworks Version: 5.106.0
Qt Version: 5.15.9
Kernel Version: 6.3.4-1-default (64-bit)
Graphics Platform: X11
Processors: 16 × AMD Ryzen 7 3700X 8-Core Processor

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

[kwin] [Bug 471976] New: KWin crashed after returning from sleep

[Szőts Ákos]

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

Bug ID: 471976
   Summary: KWin crashed after returning from sleep
Classification: Plasma
   Product: kwin
   Version: 5.27.5
  Platform: openSUSE
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: szots...@gmail.com
  Target Milestone: ---

Application: kwin_x11 (5.27.5)

Qt Version: 5.15.9
Frameworks Version: 5.106.0
Operating System: Linux 6.3.4-1-default x86_64
Windowing System: X11
Distribution: "openSUSE Tumbleweed"
DrKonqi: 5.27.5 [KCrashBackend]

-- Information about the crash:
My PC returned from sleep and KWin crashed.

I'm sorry for a possible duplicate, the new Konqi tool unfortunately makes it
impossible to compare backtraces unless you memorise it beforehand.

The reporter is unsure if this crash is reproducible.

-- Backtrace:
Application: KWin (kwin_x11), signal: Segmentation fault
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = }
[KCrash Handler]
#6  0x in  ()
#7  0x7fd8b32ee495 in
std::default_delete::operator()(KWin::EffectWindowImpl*)
const (__ptr=0x55b23cfb29d0, this=) at
/usr/include/c++/13/bits/unique_ptr.h:99
#8  std::__uniq_ptr_impl >::reset(KWin::EffectWindowImpl*)
(__p=0x0, this=0x55b23d0d9718) at /usr/include/c++/13/bits/unique_ptr.h:211
#9  std::unique_ptr >::reset(KWin::EffectWindowImpl*)
(__p=0x0, this=0x55b23d0d9718) at /usr/include/c++/13/bits/unique_ptr.h:509
#10 KWin::Window::finishCompositing(KWin::ReleaseReason) (this=0x55b23d0d95f0,
releaseReason=) at /usr/src/debug/kwin-5.27.5/src/window.cpp:370
#11 0x7fd8b31c5b25 in
KWin::X11Window::finishCompositing(KWin::ReleaseReason)
(releaseReason=KWin::ReleaseReason::Release, this=0x55b23d0d95f0) at
/usr/src/debug/kwin-5.27.5/src/x11window.cpp:1491
#12 KWin::Compositor::stop() (this=0x55b23d04b7e0) at
/usr/src/debug/kwin-5.27.5/src/composite.cpp:523
#13 KWin::Compositor::stop() (this=0x55b23d04b7e0) at
/usr/src/debug/kwin-5.27.5/src/composite.cpp:505
#14 0x7fd8b31be873 in KWin::Compositor::reinitialize()
(this=0x55b23d04b7e0) at /usr/src/debug/kwin-5.27.5/src/composite.cpp:628
#15 0x7fd8b31c80b2 in KWin::X11Compositor::composite(KWin::RenderLoop*)
(this=0x55b23d04b7e0, renderLoop=) at
/usr/src/debug/kwin-5.27.5/src/composite.cpp:961
#16 0x7fd8b1925232 in QtPrivate::QSlotObjectBase::call(QObject*, void**)
(a=0x7ffeeff2a060, r=0x55b23d04b7e0, this=0x55b23d076bd0) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#17 doActivate(QObject*, int, void**) (sender=0x55b23cc48860,
signal_index=5, argv=0x7ffeeff2a060) at kernel/qobject.cpp:3923
#18 0x7fd8b191de2f in QMetaObject::activate(QObject*, QMetaObject const*,
int, void**) (sender=, m=m@entry=0x7fd8b35c1100,
local_signal_index=local_signal_index@entry=2, argv=argv@entry=0x7ffeeff2a060)
at kernel/qobject.cpp:3983
#19 0x7fd8b317b1f2 in KWin::RenderLoop::frameRequested(KWin::RenderLoop*)
(this=, _t1=) at
/usr/src/debug/kwin-5.27.5/build/src/kwin_autogen/TAC5DWH4SE/moc_renderloop.cpp:206
#20 0x7fd8b31cd9c3 in KWin::RenderLoopPrivate::dispatch()
(this=0x55b23cc29a60) at /usr/src/debug/kwin-5.27.5/src/core/renderloop.cpp:157
#21 0x7fd8b1925232 in QtPrivate::QSlotObjectBase::call(QObject*, void**)
(a=0x7ffeeff2a180, r=0x55b23cc48860, this=0x55b23cc48940) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#22 doActivate(QObject*, int, void**) (sender=0x55b23cc29a78,
signal_index=3, argv=0x7ffeeff2a180) at kernel/qobject.cpp:3923
#23 0x7fd8b191de2f in QMetaObject::activate(QObject*, QMetaObject const*,
int, void**) (sender=, m=m@entry=0x7fd8b1bc69a0,
local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffeeff2a180)
at kernel/qobject.cpp:3983
#24 0x7fd8b192900a in QTimer::timeout(QTimer::QPrivateSignal)
(this=, _t1=...) at .moc/moc_qtimer.cpp:205
#25 0x7fd8b1918b5b in QObject::event(QEvent*) (this=0x55b23cc29a78,
e=0x7ffeeff2a2d0) at kernel/qobject.cpp:1369
#26 0x7fd8b0ba51ae in QApplicationPrivate::notify_helper(QObject*, QEvent*)
(this=, receiver=0x55b23cc29a78, e=0x7ffeeff2a2d0) at
kernel/qapplication.cpp:3640
#27 0x7fd8b18ec978 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
(receiver=0x55b23cc29a78, event=0x7ffeeff2a2d0) at
kernel/qcoreapplication.cpp:1064
#28 0x7fd8b1945319 in QTimerInfoList::activateTimers()
(this=0x55b23ca914b0) at kernel/qtimerinfo_unix.cpp:643
#29 0x7fd8b1945bc4 in timerSourceDispatch(GSource*, GSourceFunc, gpointer)
(source=) at kernel/qeventdispatcher_glib.cpp:183
#30 0x7fd8af1168d8 in g_main_dispatch (context=0x7fd8a4000ee0) at
../glib/gmain.c:3460
#31 g_main_context_dispatch (context=context@entry=0x7fd8a4000ee0) at
../glib/gmain.c:4200
#32 0x7fd8af116ce8 in g_main_context_iterate
(context=context@entry=0x7fd8a4000ee0, 

[KDE Itinerary] [Bug 470643] After importing a PDF ticket, KDE Itinerary freezes when station coordinates cannot be found

[Szőts Ákos]

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

--- Comment #2 from Szőts Ákos  ---
Nice catch, thank you for the fix!

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

[krunner] [Bug 471376] KRunner crashed when typed in a calculation

[Szőts Ákos]

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

--- Comment #1 from Szőts Ákos  ---
Created attachment 159853
  --> https://bugs.kde.org/attachment.cgi?id=159853=edit
New crash information added by DrKonqi

DrKonqi auto-attaching complete backtrace.

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

[krunner] [Bug 471376] New: KRunner crashed when typed in a calculation

[Szőts Ákos]

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

Bug ID: 471376
   Summary: KRunner crashed when typed in a calculation
Classification: Plasma
   Product: krunner
   Version: 5.27.5
  Platform: unspecified
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: szots...@gmail.com
CC: alexander.loh...@gmx.de, natalie_clar...@yahoo.de
  Target Milestone: ---

Application: krunner (5.27.5)

Qt Version: 5.15.9
Frameworks Version: 5.106.0
Operating System: Linux 6.3.4-1-default x86_64
Windowing System: X11
Distribution: "openSUSE Tumbleweed"
DrKonqi: 5.27.5 [KCrashBackend]

-- Information about the crash:
Sorry, this new DrKonqi is very sluggishj when typiong , not allow to view the
backtrace comparison. Hopefully, no duplicaplce.

The reporter is unsure if this crash is reproducible.

-- Backtrace (Reduced):
#6  0x7f32f365fce0 in MathStructure::clear(bool)
(this=this@entry=0x7f32767fb9, preserve_precision=false) at
/usr/src/debug/libqalculate-4.6.1/libqalculate/MathStructure.cc:565
#7  0x7f32f36602b2 in MathStructure::setAborted(bool) (this=0x7f32767fb9,
preserve_precision=) at
/usr/src/debug/libqalculate-4.6.1/libqalculate/MathStructure.cc:453
#8  0x7f32f35d8c97 in CalculateThread::run() (this=0x7f32642a90c0) at
/usr/src/debug/libqalculate-4.6.1/libqalculate/Calculator-calculate.cc:77
#9  0x7f32f3671dcf in Thread::doRun(void*) (data=0x7f32642a90c0) at
/usr/src/debug/libqalculate-4.6.1/libqalculate/util.cc:1078
#10 0x7f332f090c24 in start_thread (arg=) at
pthread_create.c:444


Reported using DrKonqi

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

[KDE Itinerary] [Bug 470644] New: Calendar list is empty when trying to add a booking to calendar

[Szőts Ákos]

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

Bug ID: 470644
   Summary: Calendar list is empty when trying to add a booking to
calendar
Classification: Applications
   Product: KDE Itinerary
   Version: unspecified
  Platform: Android
OS: Android 12.x
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: vkra...@kde.org
  Reporter: szots...@gmail.com
  Target Milestone: ---

I have a booking in Itinerary which I would like to add to one of my calendars.
When I click on "Add to calendar...", only the title, "Select Calendar" is
shown, but the body of that form is missing.

I have multiple calendars configured in my Android system (via DAVx5) and
another calendar program can see them correctly.

The "Calendar" permission is granted for the application.

In ADB logs I see the following:

06-04 23:37:45.145 29330 29356 W itinerary:
qrc:/android_rcc_bundle/qml/org/kde/kirigami.2/PromptDialog.qml:113:22: QML
SelectableLabel: Binding loop detected for property "implicitWidth"
06-04 23:37:45.177 29330 29356 W itinerary:
qrc:/android_rcc_bundle/qml/org/kde/kirigami.2/PromptDialog.qml:113:22: QML
SelectableLabel: Binding loop detected for property "implicitWidth"
06-04 23:37:45.246 29330 29356 W itinerary: qrc:/TicketTokenDelegate.qml:54:5:
QML BarcodeContainer: Binding loop detected for property "implicitHeight"
06-04 23:37:45.254 29330 29356 W itinerary: qrc:/FormPlaceDelegate.qml:159:
TypeError: Cannot read property 'connected' of null
06-04 23:37:45.254 29330 29356 W itinerary: qrc:/FormPlaceDelegate.qml:159:
TypeError: Cannot read property 'connected' of null
06-04 23:37:50.355 29330 29356 D itinerary: Permission::WriteCalendar

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

[KDE Itinerary] [Bug 470643] New: After importing a PDF ticket, KDE Itinerary freezes when station coordinates cannot be found

[Szőts Ákos]

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

Bug ID: 470643
   Summary: After importing a PDF ticket, KDE Itinerary freezes
when station coordinates cannot be found
Classification: Applications
   Product: KDE Itinerary
   Version: unspecified
  Platform: Android
OS: Android 12.x
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: vkra...@kde.org
  Reporter: szots...@gmail.com
  Target Milestone: ---

I imported a ticket into Itinerary, but it completely froze right after. After
a restart it displayed the imported ticket normally.

What I observed is that Itinerary tries to search for coordinates for stations.
If it could not find them, it freezes. When it could find them, I didn't notice
a freeze.

Something similar appeared in the logs:

Non-working condition logs:
itinerary: "Station 1" nan nan
itinerary: "Station 2" nan nan

Working condition logs:
itinerary: "Station 1" Coord1_1 Coord1_2
itinerary: "Station 2 with track info" Coord2_1 Coord2_2

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

[plasmashell] [Bug 403563] Memory leak in plasma desktop (plasmashell)

[Szőts Ákos]

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

Szőts Ákos  changed:

   What|Removed |Added

 CC||szots...@gmail.com

--- Comment #21 from Szőts Ákos  ---
I don't know whether it's related, but Bug 465441 has heaptrack report attached
with specific line number causing the leak.

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

[KDE Itinerary] [Bug 470578] KDE Itinerary doesn't draw the bottom part of the screen

[Szőts Ákos]

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

--- Comment #1 from Szőts Ákos  ---
Created attachment 159430
  --> https://bugs.kde.org/attachment.cgi?id=159430=edit
Main screen with the drawer open showing the bottom part is missing

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

[KDE Itinerary] [Bug 470578] New: KDE Itinerary doesn't draw the bottom part of the screen

[Szőts Ákos]

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

Bug ID: 470578
   Summary: KDE Itinerary doesn't draw the bottom part of the
screen
Classification: Applications
   Product: KDE Itinerary
   Version: unspecified
  Platform: Android
OS: Android 12.x
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: vkra...@kde.org
  Reporter: szots...@gmail.com
  Target Milestone: ---

Created attachment 159429
  --> https://bugs.kde.org/attachment.cgi?id=159429=edit
Main screen with weather showing the bottom part is missing

Just start the application and see that the bottom half is not drawn.

Logs from ADB:
06-03 10:28:09.070 15387 15387 W QtThread: type=1400 audit(0.0:324779): avc:
denied { ioctl } for path="socket:[69337054]" dev="sockfs" ino=69337054
ioctlcmd=0x8927 scontext=u:r:untrusted_app:s0:c103,c257,c512,c768
tcontext=u:r:untrusted_app:s0:c103,c257,c512,c768 tclass=tcp_socket
permissive=0 app=org.kde.itinerary
06-03 10:28:09.070 15387 15387 W QtThread: type=1400 audit(0.0:324780): avc:
denied { ioctl } for path="socket:[69337054]" dev="sockfs" ino=69337054
ioctlcmd=0x8927 scontext=u:r:untrusted_app:s0:c103,c257,c512,c768
tcontext=u:r:untrusted_app:s0:c103,c257,c512,c768 tclass=tcp_socket
permissive=0 app=org.kde.itinerary
06-03 10:28:09.070 15387 15387 W QtThread: type=1400 audit(0.0:324781): avc:
denied { ioctl } for path="socket:[69337054]" dev="sockfs" ino=69337054
ioctlcmd=0x8927 scontext=u:r:untrusted_app:s0:c103,c257,c512,c768
tcontext=u:r:untrusted_app:s0:c103,c257,c512,c768 tclass=tcp_socket
permissive=0 app=org.kde.itinerary
06-03 10:28:09.077 15387 15412 D itinerary:
QUrl("https://api.met.no/weatherapi/locationforecast/2.0/classic?lat=35.9=14.5;)
06-03 10:28:09.073 15387 15387 W QtThread: type=1400 audit(0.0:324782): avc:
denied { ioctl } for path="socket:[69337055]" dev="sockfs" ino=69337055
ioctlcmd=0x8927 scontext=u:r:untrusted_app:s0:c103,c257,c512,c768
tcontext=u:r:untrusted_app:s0:c103,c257,c512,c768 tclass=tcp_socket
permissive=0 app=org.kde.itinerary
06-03 10:28:09.073 15387 15387 W QtThread: type=1400 audit(0.0:324783): avc:
denied { ioctl } for path="socket:[69337055]" dev="sockfs" ino=69337055
ioctlcmd=0x8927 scontext=u:r:untrusted_app:s0:c103,c257,c512,c768
tcontext=u:r:untrusted_app:s0:c103,c257,c512,c768 tclass=tcp_socket
permissive=0 app=org.kde.itinerary
[...]
06-03 10:28:09.163 15387 15412 D itinerary: weather recomputation done
06-03 10:28:09.167 15387 15412 D itinerary: 0 pending download requests
SolidExtras::NetworkStatus::Yes SolidExtras::NetworkStatus::No
06-03 10:28:09.659 15387 15412 W itinerary: QFont::setPointSize: Point size <=
0 (-3), must be greater than 0
06-03 10:28:09.659 15387 15412 W itinerary:
qrc:/android_rcc_bundle/qml/org/kde/kirigami.2/styles/Material/Theme.qml:14:1:
QML Theme: Binding loop detected for property "disabledTextColor"
06-03 10:28:09.659 15387 15412 W itinerary:
qrc:/android_rcc_bundle/qml/org/kde/kirigami.2/styles/Material/Theme.qml:14:1:
QML Theme: Binding loop detected for property "disabledTextColor"
06-03 10:28:09.659 15387 15412 W itinerary:
qrc:/android_rcc_bundle/qml/org/kde/kirigami.2/styles/Material/Theme.qml:14:1:
QML Theme: Binding loop detected for property "disabledTextColor"
06-03 10:28:09.664 15387 15412 W itinerary: kf.kirigami: Failed to find a
Kirigami platform plugin
06-03 10:28:09.740 15387 15412 W itinerary:
qrc:/android_rcc_bundle/qml/org/kde/kirigami.2/ScrollablePage.qml:215:13: QML
QQuickItem*: ScrollBar must be attached to a Flickable or ScrollView
06-03 10:28:09.744 15387 15412 W itinerary:
qrc:/android_rcc_bundle/qml/org/kde/kirigami.2/PromptDialog.qml:113:22: QML
SelectableLabel: Binding loop detected for property "implicitWidth"
06-03 10:28:09.853 15387 15412 W itinerary:
qrc:/android_rcc_bundle/qml/org/kde/kirigami.2/private/BannerImage.qml:135:5:
QML RowLayout: Binding loop detected for property "height"
06-03 10:28:09.911 15387 15412 W itinerary:
qrc:/android_rcc_bundle/qml/org/kde/kirigami.2/ContextDrawer.qml:135:9: QML
ListView: Binding loop detected for property "topMargin"
06-03 10:28:10.335 15387 15412 W itinerary:
qrc:/LocationInfoDelegate.qml:19:35: QML LocationInformationDelegateController:
Binding loop detected for property "performCurrencyConversion"
06-03 10:28:10.335 15387 15412 W itinerary: org.kde.itinerary: Imminent
KUnitConversion deadlock detected, skipping currency conversion!
06-03 10:28:10.349 15387 15412 W itinerary: qrc:/TimelinePage.qml:100:5: QML
PromptDialog: Binding loop detected for property "implicitHeight"
06-03 10:28:10.601 15387 15412 D itinerary: 359 145
06-03 10:28:10.601 15387 15412 D itinerary: (QPair("Server","nginx/1.18.0
(Ubuntu)"), QPair("Date","Sat, 03 Jun 2023 08:28:10 GMT"),
QPair("Content-Type","application/xml"), QPair("Content-Length","6301"),
QPair("Connection","keep-alive"), QPair("Expires","Sat, 03 Jun 

[kwin] [Bug 466380] kwin_x11 crashes in KWin::X11Window::finishCompositing() when disabling compositing

[Szőts Ákos]

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

--- Comment #7 from Szőts Ákos  ---
I've through many sleep-resume cycles but unfortunately, I could not reproduce
the issue more times.

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

[KDE Itinerary] [Bug 469562] New: KDE Itinerary on Android freezes during start-up

[Szőts Ákos]

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

Bug ID: 469562
   Summary: KDE Itinerary on Android freezes during start-up
Classification: Applications
   Product: KDE Itinerary
   Version: unspecified
  Platform: Other
OS: Android 12.x
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: vkra...@kde.org
  Reporter: szots...@gmail.com
  Target Milestone: ---

I started using the program but now it fails to react to any interactions right
after start-up; the application seems completely frozen. Just the first station
is loaded in the list, the rest of the journeys are not displayed.

Here are the logs from ADB:

05-10 08:50:46.066  2020  5764 I ActivityTaskManager: START u0
{act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER]
flg=0x1000 pkg=org.kde.itinerary cmp=org.kde.itinerary/.Activity} from uid
1000
05-10 08:50:46.066  2020  5764 I ActivityTaskManager: executeMessage package=
org.kde.itinerary displayId= -1 calling package=com.android.settings
05-10 08:50:46.067  2020  5764 I ActivityTaskManager: executeMessage task=null
eph intent=Intent { act=android.intent.action.MAIN
cat=[android.intent.category.LAUNCHER] flg=0x1000 pkg=org.kde.itinerary
cmp=org.kde.itinerary/.Activity } isHomeActivity:false
05-10 08:50:46.099  2020  2077 I ActivityManager: Start proc
8399:org.kde.itinerary/u0a359 for pre-top-activity
{org.kde.itinerary/org.kde.itinerary.Activity}
05-10 08:50:46.114  2020  2058 I WindowManager: SURFACE SHOW
Surface(name=Splash Screen org.kde.itinerary)/@0x242eaca on display:0
05-10 08:50:46.136  8399  8399 V GraphicsEnvironment: ANGLE Developer option
for 'org.kde.itinerary' set to: 'default'
05-10 08:50:46.224  2020  2722 V WindowManager: Changing focus of displayId=0
to Window{386222b u0 org.kde.itinerary/org.kde.itinerary.Activity} from null
05-10 08:50:46.250  2020  2058 I LaunchCheckinHandler: MotoDisplayed
org.kde.itinerary/.Activity,cp,ca,166
05-10 08:50:46.251  2020  2058 I WindowManager: SURFACE SHOW
Surface(name=org.kde.itinerary/org.kde.itinerary.Activity)/@0x172361e on
display:0
05-10 08:50:46.254  2020  2054 I ActivityTaskManager: Displayed
org.kde.itinerary/.Activity: +184ms
05-10 08:50:46.260  2020  2058 I WindowManager: SURFACE hide
Surface(name=Splash Screen org.kde.itinerary)/@0x242eaca on display:0
05-10 08:50:46.263  2020  2722 W InputManager-JNI: Input channel object
'532f80e Splash Screen org.kde.itinerary (client)' was disposed without first
being removed with the input manager!
05-10 08:50:46.271  7663  7663 I GoogleInputMethodService:
GoogleInputMethodService.onStartInput():1898
onStartInput(EditorInfo{inputType=0x0(NULL) imeOptions=0x0
privateImeOptions=null actionName=UNSPECIFIED actionLabel=null actionId=0
initialSelStart=-1 initialSelEnd=-1 initialCapsMode=0x0 hintText=null
label=null packageName=org.kde.itinerary fieldId=-1 fieldName=null extras=null
hintLocales=[]}, false)
05-10 08:50:46.311  8399  8424 D itinerary: starting scan at "STATION_1"
05-10 08:50:46.311  8399  8424 D itinerary:   aborting search, maximum trip
duration reached
05-10 08:50:46.311  8399  8424 D itinerary: nothing found
05-10 08:50:46.311  8399  8424 D itinerary: starting scan at "STATION_1"
05-10 08:50:46.311  8399  8424 D itinerary:   aborting search, maximum trip
duration reached
05-10 08:50:46.311  8399  8424 D itinerary: nothing found
05-10 08:50:46.311  8399  8424 D itinerary: starting scan at "STATION_2"
05-10 08:50:46.311  8399  8424 D itinerary:   current transition goes from
"STATION_1.1" to "STATION_2.1"
05-10 08:50:46.311  8399  8424 D itinerary:   aborting connectivity search,
arrived at the start again "STATION_2.1"
05-10 08:50:46.311  8399  8424 D itinerary:   considering transition to
"STATION_2.1" as part of trip despite unknown reservation number
05-10 08:50:46.311  8399  8424 D itinerary:   current transition goes from
"STATION_2.1" to "STATION_3"
05-10 08:50:46.311  8399  8424 D itinerary:   aborting reservation number
search due to mismatch
05-10 08:50:46.311  8399  8424 D itinerary: existing group unchanged
"STATION_1.1 (április 2023)"
05-10 08:50:46.311  8399  8424 D itinerary: starting scan at "STATION_2.1"
05-10 08:50:46.311  8399  8424 D itinerary:   current transition goes from
"STATION_3" to "STATION_4"
05-10 08:50:46.311  8399  8424 D itinerary:   aborting connectivity search, not
an adjacent transition from "STATION_3" to "STATION_2.2"
05-10 08:50:46.311  8399  8424 D itinerary:   aborting reservation number
search due to mismatch
05-10 08:50:46.311  8399  8424 D itinerary: nothing found
05-10 08:50:46.311  8399  8424 D itinerary: starting scan at "STATION_2.2"
05-10 08:50:46.311  8399  8424 D itinerary: nothing found
05-10 08:50:46.312  8399  8424 W itinerary: org.kde.kpublictransport: Unknown
backend setting: "supportedOutputFormats"
05-10 08:50:46.313  8399  8424 W itinerary: 

[kwin] [Bug 466380] kwin_x11 crashed on disabling compositing

[Szőts Ákos]

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

Szőts Ákos  changed:

   What|Removed |Added

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

--- Comment #5 from Szőts Ákos  ---
It's a bit erratic. What I observed is that after I did a "kwin_x11 --replace"
after the first resume, the subsequent ones had higher probability of crashing.
Since I discovered it only yesterday, unfortunately, I cannot say a ratio.
Today's resume was fine.

I'll try a --replace before resume tomorrow.

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

[kwin] [Bug 466380] kwin_x11 crashed on disabling compositing

[Szőts Ákos]

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

--- Comment #4 from Szőts Ákos  ---
$> qdbus-qt5 org.kde.KWin /KWin org.kde.KWin.supportInformation

Version
===
KWin version: 5.27.4
Qt Version: 5.15.8
Qt compile version: 5.15.8
XCB compile version: 1.15

Operation Mode: X11 only

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

X11
===
Vendor: The X.Org Foundation
Vendor Release: 12101008
Protocol Version/Revision: 11/0
SHAPE: yes; Version: 0x11
RANDR: yes; Version: 0x14
DAMAGE: yes; Version: 0x11
Composite: yes; Version: 0x4
RENDER: yes; Version: 0xb
XFIXES: yes; Version: 0x50
SYNC: yes; Version: 0x31
GLX: yes; Version: 0x0

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

Output backend
==
Name: KWin::X11StandaloneBackend

Cursor
==
themeName: breeze_cursors
themeSize: 24

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

Screen Edges

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

Screens
===
Active screen follows mouse:  no
Number of Screens: 1

Screen 0:
-
Name: DP-0
Enabled: 1
Geometry: 0,0,3440x1440
Scale: 1
Refresh Rate: 59972
Adaptive Sync: incapable

Compositing
===
Compositing is active
Compositing Type: OpenGL
OpenGL vendor string: NVIDIA Corporation
OpenGL renderer string: NVIDIA GeForce GTX 960/PCIe/SSE2
OpenGL version string: 3.1.0 NVIDIA 525.105.17
OpenGL platform interface: GLX
OpenGL shading language version string: 1.40 NVIDIA via Cg compiler
Driver: NVIDIA
Driver version: 525.105.17
GPU class: Unknown
OpenGL version: 3.1
GLSL version: 1.40
X server version: 1.21.1
Linux kernel version: 6.2.9
Direct rendering: Requires strict binding: no
GLSL shaders:  yes
Texture NPOT support:  yes
Virtual Machine:  no
OpenGL 2 Shaders are used

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

Currently Active Effects:
-
blur
contrast

Effect Settings:

colorpicker:

outputlocator:

screenshot:

screenedge:

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

blur:

contrast:

kwin4_effect_login:
pluginId: kwin4_effect_login
isActiveFullScreenEffect: false

kwin4_effect_sessionquit:
pluginId: kwin4_effect_sessionquit
isActiveFullScreenEffect: false

kwin4_effect_logout:
pluginId: kwin4_effect_logout
isActiveFullScreenEffect: false

slidingpopups:
slideInDuration: 75
slideOutDuration: 125

kwin4_effect_windowaperture:
pluginId: kwin4_effect_windowaperture
isActiveFullScreenEffect: false

slide:
horizontalGap: 45
verticalGap:

[kwin] [Bug 466380] kwin_x11 crashed on disabling compositing

[Szőts Ákos]

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

Szőts Ákos  changed:

   What|Removed |Added

 CC||szots...@gmail.com

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

[kwin] [Bug 466380] kwin_x11 crashed on disabling compositing

[Szőts Ákos]

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

--- Comment #2 from Szőts Ákos  ---
Created attachment 158455
  --> https://bugs.kde.org/attachment.cgi?id=158455=edit
New crash information added by DrKonqi

kwin_x11 (5.27.4) using Qt 5.15.8

Unfortuately, in the new Konqi I cannot directly compare the the backtraces but
if my memory serves me well the parameter of the top frame function was the
same.

In my case the system came back from sleep. Waited a bit and KWin crashed. I
didn't disable compositing.

-- Backtrace (Reduced):
#6  0x7f4b5ecee1f1 in
std::default_delete::operator()(KWin::EffectWindowImpl*)
const (__ptr=0x55ab5977cb50, this=) at
/usr/include/c++/13/bits/unique_ptr.h:94
#7  std::__uniq_ptr_impl >::reset(KWin::EffectWindowImpl*)
(__p=0x0, this=0x55ab59966678) at /usr/include/c++/13/bits/unique_ptr.h:212
#8  std::unique_ptr >::reset(KWin::EffectWindowImpl*)
(__p=0x0, this=0x55ab59966678) at /usr/include/c++/13/bits/unique_ptr.h:510
#9  KWin::Window::finishCompositing(KWin::ReleaseReason) (this=0x55ab59966550,
releaseReason=) at /usr/src/debug/kwin-5.27.4/src/window.cpp:370
#10 0x7f4b5ebc5ba5 in
KWin::X11Window::finishCompositing(KWin::ReleaseReason)
(releaseReason=KWin::ReleaseReason::Release, this=0x55ab59966550) at
/usr/src/debug/kwin-5.27.4/src/x11window.cpp:1491

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

[plasmashell] [Bug 445664] Cannot move tasks to activities from the panel

[Szőts Ákos]

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

Szőts Ákos  changed:

   What|Removed |Added

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

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

[plasmashell] [Bug 445664] Cannot move tasks to activities from the panel

[Szőts Ákos]

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

--- Comment #8 from Szőts Ákos  ---
Created attachment 158060
  --> https://bugs.kde.org/attachment.cgi?id=158060=edit
KDE activity move bug

I upgraded to 5.27.4 from 5.26 and unfortunately, the same issue remains.
Moving any (KDE or non-KDE) window to a new activity in the title bar works,
but not in the panel.

I created a short video about it. Sorry, it's in Hungarian, but hopefully you
can see the point.

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

[plasmashell] [Bug 465441] plasmashell leaks memory after each resume (currently around 23 GB) [with heaptrack]

[Szőts Ákos]

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

--- Comment #3 from Szőts Ákos  ---
Created attachment 156041
  --> https://bugs.kde.org/attachment.cgi?id=156041=edit
Top-down

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

[plasmashell] [Bug 465441] plasmashell leaks memory after each resume (currently around 23 GB) [with heaptrack]

[Szőts Ákos]

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

--- Comment #2 from Szőts Ákos  ---
Created attachment 156040
  --> https://bugs.kde.org/attachment.cgi?id=156040=edit
Top leakers

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

[plasmashell] [Bug 465441] plasmashell leaks memory after each resume (currently around 23 GB) [with heaptrack]

[Szőts Ákos]

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

--- Comment #1 from Szőts Ákos  ---
Created attachment 156039
  --> https://bugs.kde.org/attachment.cgi?id=156039=edit
Flame graph

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

[plasmashell] [Bug 465441] New: plasmashell leaks memory after each resume (currently around 23 GB) [with heaptrack]

[Szőts Ákos]

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

Bug ID: 465441
   Summary: plasmashell leaks memory after each resume (currently
around 23 GB) [with heaptrack]
Classification: Plasma
   Product: plasmashell
   Version: 5.26.5
  Platform: openSUSE
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: generic-performance
  Assignee: plasma-b...@kde.org
  Reporter: szots...@gmail.com
  Target Milestone: 1.0

Created attachment 156038
  --> https://bugs.kde.org/attachment.cgi?id=156038=edit
23 GB leak

Plasmashell, after 3-4 sleep resume cycles, starts leaking memory. In the first
3-4 cycles just some hundred MBs but then after +5 GB, then +15 GB.

Heaptrack shows the following backtrace as one of the culprits:

main in plasmashell
QCoreApplication::exec() in libQt5Core.so.5
QEventLoop::exec(QFlags) in libQt5Core.so.5
QEventDispatcherGlib::processEvents(QFlags) in
libQt5Core.so.5
g_main_context_iteration in libglib-2.0.so.0
g_main_context_iterate in libglib-2.0.so.0
g_main_context_dispatch in libglib-2.0.so.0
g_main_dispatch in libglib-2.0.so.0
postEventSourceDispatch in libQt5Core.so.5
QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) in
libQt5Core.so.5
QCoreApplication::notifyInternal2(QObject*, QEvent*) in libQt5Core.so.5
QApplicationPrivate::notify_helper(QObject*, QEvent*) in libQt5Widgets.so.5
QObject::event(QEvent*) in libQt5Core.so.5
PlasmaDesktopTheme::syncWindow() in org.kde.desktop.so
QMetaObject::Connection QObject::connect(QtPrivate::FunctionPointer::Object const*, void (QQuickWindow::*)(),
QtPrivate::FunctionPointer::Object const*, void
(PlasmaDesktopTheme::*)(), Qt::ConnectionType) in org.kde.desktop.so
QObject::connectImpl(QObject const*, void**, QObject const*, void**,
QtPrivate::QSlotObjectBase*, Qt::ConnectionType, int const*, QMetaObject
const*) in libQt5Core.so.5
QObjectPrivate::connectImpl(QObject const*, int, QObject const*, void**,
QtPrivate::QSlotObjectBase*, Qt::ConnectionType, int const*, QMetaObject
const*) in libQt5Core.so.5

According to it, the leaking line is plasmadesktoptheme.cpp:231:

if (qw) {
connect(qw, ::sceneGraphInitialized, this,
::syncWindow);
}

Heaptrack file:
https://mega.nz/file/lRJFmSCC#olTMN_Kqf8Cv1l2OlKDzZ_lYoQSWkSisL2JGQ_z7j3I

Please, take a look whether you can find other problems, too. Thank you!

Operating System: openSUSE Tumbleweed 20230130
KDE Plasma Version: 5.26.5
KDE Frameworks Version: 5.102.0
Qt Version: 5.15.8
Kernel Version: 6.1.8-1-default (64-bit)
Graphics Platform: X11
Memory: 78.5 GiB of RAM

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

[plasmashell] [Bug 464425] New: Plasma crashes when plasmoid removal undo notifications are closed

[Szőts Ákos]

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

Bug ID: 464425
   Summary: Plasma crashes when plasmoid removal undo
notifications are closed
Classification: Plasma
   Product: plasmashell
   Version: 5.26.3
  Platform: OpenSUSE
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Notifications
  Assignee: plasma-b...@kde.org
  Reporter: szots...@gmail.com
CC: k...@privat.broulik.de
  Target Milestone: 1.0

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


STEPS TO REPRODUCE
1. Add multiple sticky note plasmoids to the desktop
2. Remove at least two of them one after each other
3. Click on the closing "X"es of the undo notifications in the order of
appearance

OBSERVED RESULT

Plasma crashes

SOFTWARE/OS VERSIONS
Operating System: openSUSE Tumbleweed 20221128
KDE Plasma Version: 5.26.3
KDE Frameworks Version: 5.100.0
Qt Version: 5.15.7
Kernel Version: 6.0.8-1-default (64-bit)
Graphics Platform: X11

ADDITIONAL INFORMATION

For some reason it doesn't pop up a DrKonqi dialogue, therefore I manually
attached GDB to it:

$ gdb -p $(pidof plasmashell)
GNU gdb (GDB; openSUSE Tumbleweed) 12.1
Copyright (C) 2022 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
[ Legend: Modified register | Code | Heap | Stack | String ]

registers 
$rax   : 0xfdfc
$rbx   : 0x9
$rcx   : 0x007f36da30bb7f  →  0x3177f0003d48 ("H="?)
$rdx   : 0x22af
$rsp   : 0x007fff681109b0  →  0x007f36d0005010  →  0x
$rbp   : 0x007f36d0005010  →  0x
$rsi   : 0x9
$rdi   : 0x00558a3ba80770  →  0x00010004
$rip   : 0x007f36da30bb7f  →  0x3177f0003d48 ("H="?)
$r8: 0x0
$r9: 0x007f36daca76c0  →  0x0008
$r10   : 0x007fff68171080  →  0x007fff68171080
$r11   : 0x293
$r12   : 0x00558a3ba80770  →  0x00010004
$r13   : 0x007f36d8b2c790  →   mov esi, esi
$r14   : 0x22af
$r15   : 0xf
$eflags: [zero CARRY parity ADJUST SIGN trap INTERRUPT direction overflow
resume virtualx86 identification]
$cs: 0x33 $ss: 0x2b $ds: 0x00 $es: 0x00 $fs: 0x00 $gs: 0x00

stack 
0x007fff681109b0│+0x: 0x007f36d0005010  →  0x← $rsp
0x007fff681109b8│+0x0008: 0x00558a3ba80770  →  0x00010004
0x007fff681109c0│+0x0010: 0x09 ("\t"?)
0x007fff681109c8│+0x0018: 0x22af0001
0x007fff681109d0│+0x0020: 0x000f
0x007fff681109d8│+0x0028: 0x007f36d8b1cdbe  → 
 mov r13d, eax
0x007fff681109e0│+0x0030: 0x007fff68110ae8  →  0x508ad777e0b53700
0x007fff681109e8│+0x0038: 0x0001daac7c04
──
code:x86:64 
   0x7f36da30bb73 movrdi, QWORD PTR [rsp+0x8]
   0x7f36da30bb78 moveax, 0x7
   0x7f36da30bb7d syscall
 → 0x7f36da30bb7f cmprax, 0xf000
   0x7f36da30bb85 ja 0x7f36da30bbb8 <__GI___poll+138>
   0x7f36da30bb87 movedi, r8d
   0x7f36da30bb8a movDWORD PTR [rsp+0x8], eax
   0x7f36da30bb8e call   0x7f36da28f7ee
<__GI___pthread_disable_asynccancel>
   0x7f36da30bb93moveax, DWORD PTR [rsp+0x8]
─
source:../sysdeps/unix[...].c+29 
 24
 25  int
 26  __poll (struct pollfd *fds, nfds_t nfds, int timeout)
 27  {
 28  #ifdef __NR_poll
   // fds=0x007fff681109b8  →  [...]  →  0x00010004,
timeout=0x22af
 →   29return SYSCALL_CANCEL (poll, fds, nfds, timeout);
 30  #else
 31struct timespec timeout_ts;
 32struct timespec *timeout_ts_p = NULL;
 33
 34if (timeout >= 0)
──
threads 
[#0] Id 1, Name: "plasmashell", stopped 0x7f36da30bb7f in __GI___poll (),
reason: STOPPED
[#1] Id 2, Name: "QDBusConnection", stopped 0x7f36da30bb7f in __GI___poll (),
reason: STOPPED
[#2] Id 3, Name: "QXcbEventQueue", stopped 0x7f36da30bb7f in __GI___poll (),
reason: STOPPED
[#3] Id 4, 

[valgrind] [Bug 462958] New: ARMv8: Unrecognised instruction: _armv8_sha512_probe

[Szőts Ákos]

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

Bug ID: 462958
   Summary: ARMv8: Unrecognised instruction: _armv8_sha512_probe
Classification: Developer tools
   Product: valgrind
   Version: 3.17.0
  Platform: Other
OS: Other
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: jsew...@acm.org
  Reporter: szots...@gmail.com
  Target Milestone: ---

When I run an application in Valgrind on an ARMv8 CPU Valgrind dies with the
following error message which comes from libcrypto.so:

valgrind: Unrecognised instruction at address 0xxx.
   at 0: _armv8_sha512_probe (in /[...]/libcrypto.so)

Valgrind version is: valgrind-3.17.0.GIT

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

[systemsettings] [Bug 423091] System Setting App crashes when deleting a duplicated line in virtual screen settings

[Szőts Ákos]

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

Szőts Ákos  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |---
Version|5.18.5  |5.26.3
 Status|NEEDSINFO   |REPORTED
   Platform|Fedora RPMs |OpenSUSE

--- Comment #20 from Szőts Ákos  ---
Operating System: openSUSE Tumbleweed 20221128
KDE Plasma Version: 5.26.3
KDE Frameworks Version: 5.100.0
Qt Version: 5.15.7
Kernel Version: 6.0.8-1-default (64-bit)
Graphics Platform: X11
Graphics Processor: NVIDIA GeForce GTX 960/PCIe/SSE2

This time only system settings crashed.

Application: Rendszerbeállítások (systemsettings), signal: Segmentation fault

[KCrash Handler]
#6  std::__atomic_base::load (__m=std::memory_order::relaxed,
this=) at /usr/include/c++/12/bits/atomic_base.h:486
#7  QAtomicOps::loadRelaxed (_q_value=...) at
/usr/include/qt5/QtCore/qatomic_cxx11.h:239
#8  QBasicAtomicInteger::loadRelaxed (this=) at
/usr/include/qt5/QtCore/qbasicatomic.h:107
#9  QtPrivate::RefCount::ref (this=) at
/usr/include/qt5/QtCore/qrefcount.h:55
#10 QString::QString (other=..., this=0x7ffcb4e851c0) at
/usr/include/qt5/QtCore/qstring.h:1094
#11 KWin::DesktopsModel::syncWithServer (this=0x561d7f0f92c0) at
/usr/src/debug/kwin-5.26.3/src/kcmkwin/kwindesktop/desktopsmodel.cpp:305
#12 0x7f952c0e3ecf in KWin::VirtualDesktops::save (this=0x561d7f0f3980) at
/usr/src/debug/kwin-5.26.3/src/kcmkwin/kwindesktop/virtualdesktops.cpp:80
#13 0x7f9545d263f2 in KCModuleQml::save (this=0x561d7f190730) at
/usr/src/debug/kcmutils-5.100.0/src/kcmoduleqml.cpp:299
#14 0x7f9545d2e327 in KCModuleProxy::save (this=) at
/usr/src/debug/kcmutils-5.100.0/src/kcmoduleproxy.cpp:279
#15 0x7f95462d8751 in ModuleView::moduleSave (this=0x561d7ea54ab0,
module=) at
/usr/src/debug/systemsettings-5.26.3/core/ModuleView.cpp:369
#16 0x7f95462d8a8e in ModuleView::moduleSave (this=) at
/usr/src/debug/systemsettings-5.26.3/core/ModuleView.cpp:360
#17 0x7f95462daebe in ModuleView::qt_static_metacall (_o=,
_c=, _id=, _a=0x7ffcb4e85440) at
/usr/src/debug/systemsettings-5.26.3/build/core/systemsettingsview_autogen/EWIEGA46WW/moc_ModuleView.cpp:133
#18 0x7f9544b1354c in doActivate (sender=0x561d7e6de590,
signal_index=9, argv=0x7ffcb4e85440) at kernel/qobject.cpp:3931
#19 0x7f9544b0c74f in QMetaObject::activate
(sender=sender@entry=0x561d7e6de590, m=m@entry=0x7f9545cbe160
,
local_signal_index=local_signal_index@entry=2, argv=argv@entry=0x7ffcb4e85440)
at kernel/qobject.cpp:3979
#20 0x7f9545897072 in QAbstractButton::clicked
(this=this@entry=0x561d7e6de590, _t1=) at
.moc/moc_qabstractbutton.cpp:308
#21 0x7f95458972da in QAbstractButtonPrivate::emitClicked
(this=0x561d7e480c00) at widgets/qabstractbutton.cpp:416
#22 0x7f9545898b78 in QAbstractButtonPrivate::click (this=0x561d7e480c00)
at widgets/qabstractbutton.cpp:409
#23 0x7f9545898d97 in QAbstractButton::mouseReleaseEvent
(this=0x561d7e6de590, e=0x7ffcb4e859c0) at widgets/qabstractbutton.cpp:1045
#24 0x7f95457e6c38 in QWidget::event (this=0x561d7e6de590,
event=0x7ffcb4e859c0) at kernel/qwidget.cpp:9043
#25 0x7f95457a53fe in QApplicationPrivate::notify_helper
(this=this@entry=0x561d7e3aa6e0, receiver=receiver@entry=0x561d7e6de590,
e=e@entry=0x7ffcb4e859c0) at kernel/qapplication.cpp:3637
#26 0x7f95457ad922 in QApplication::notify (this=,
receiver=0x561d7e6de590, e=) at kernel/qapplication.cpp:3081
#27 0x7f9544adc128 in QCoreApplication::notifyInternal2
(receiver=0x561d7e6de590, event=0x7ffcb4e859c0) at
kernel/qcoreapplication.cpp:1064
#28 0x7f95457aba9e in QApplicationPrivate::sendMouseEvent
(receiver=receiver@entry=0x561d7e6de590, event=event@entry=0x7ffcb4e859c0,
alienWidget=, nativeWidget=0x561d7e8a4610,
buttonDown=buttonDown@entry=0x7f9545cf0330 ,
lastMouseReceiver=..., spontaneous=true, onlyDispatchEnterLeave=false) at
kernel/qapplication.cpp:2619
#29 0x7f95457ffa58 in QWidgetWindow::handleMouseEvent (this=0x561d7e8f21a0,
event=0x7ffcb4e85c70) at kernel/qwidgetwindow.cpp:683
#30 0x7f9545802fb0 in QWidgetWindow::event (this=0x561d7e8f21a0,
event=0x7ffcb4e85c70) at kernel/qwidgetwindow.cpp:300
#31 0x7f95457a53fe in QApplicationPrivate::notify_helper (this=, receiver=0x561d7e8f21a0, e=0x7ffcb4e85c70) at
kernel/qapplication.cpp:3637
#32 0x7f9544adc128 in QCoreApplication::notifyInternal2
(receiver=0x561d7e8f21a0, event=0x7ffcb4e85c70) at
kernel/qcoreapplication.cpp:1064
#33 0x7f9544f7b9ad in QGuiApplicationPrivate::processMouseEvent
(e=0x561d7e9d16c0) at kernel/qguiapplication.cpp:2285
#34 0x7f9544f4f37c in QWindowSystemInterface::sendWindowSystemEvents
(flags=flags@entry=...) at kernel/qwindowsysteminterface.cpp:1169
#35 0x7f953f51a0fa in xcbSourceDispatch (source=) at
qxcbeventdispatcher.cpp:105
#36 0x7f954331ca90 in g_main_dispatch (context

[systemsettings] [Bug 423091] System Setting App crashes when deleting a duplicated line in virtual screen settings

[Szőts Ákos]

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

--- Comment #18 from Szőts Ákos  ---
Created attachment 151712
  --> https://bugs.kde.org/attachment.cgi?id=151712=edit
KWin GDB full backtrace

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

[systemsettings] [Bug 423091] System Setting App crashes when deleting a duplicated line in virtual screen settings

[Szőts Ákos]

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

--- Comment #17 from Szőts Ákos  ---
I tried to reproduce it. Now, what happens is, instead of a crash when I click
Apply, the whole desktop is rendered unusable by kwin_x11 which starts spinning
X11 and doesn't repaint windows anymore.

In another terminal (without X11) I could attach KWin to GDB and I saw the
following:

#0  __futex_abstimed_wait_common64 (private=0, cancel=true, abstime=0x0,
op=393, expected=0, futex_word=0x7ffcd9a04b9c) at futex-internal.c:57
#1  __futex_abstimed_wait_common (futex_word=futex_word@entry=0x7ffcd9a04b9c,
expected=expected@entry=0, clockid=clockid@entry=0, abstime=abstime@entry=0x0,
private=private@entry=0, cancel=cancel@entry=true) at futex-internal.c:87
#2  0x7ff3610a3e6f in __GI___futex_abstimed_wait_cancelable64
(futex_word=futex_word@entry=0x7ffcd9a04b9c, expected=expected@entry=0,
clockid=clockid@entry=0, abstime=abstime@entry=0x0, private=private@entry=0) at
futex-internal.c:139
#3  0x7ff3610a6ab0 in __pthread_cond_wait_common (abstime=0x0, clockid=0,
mutex=0x5568e55e0dd8, cond=0x7ffcd9a04b70) at pthread_cond_wait.c:503
#4  ___pthread_cond_wait (cond=cond@entry=0x7ffcd9a04b70,
mutex=mutex@entry=0x5568e55e0dd8) at pthread_cond_wait.c:618
#5  0x7ff362f3cf25 in _xcb_conn_wait (count=0x0, vector=0x0,
cond=0x7ffcd9a04b70, c=0x5568e55e0dc0) at
/usr/src/debug/libxcb-1.15-1.3.x86_64/src/xcb_conn.c:476
#6  wait_for_reply (c=c@entry=0x5568e55e0dc0, request=263708, e=e@entry=0x0) at
/usr/src/debug/libxcb-1.15-1.3.x86_64/src/xcb_in.c:522
#7  0x7ff362f3de01 in xcb_wait_for_reply (c=0x5568e55e0dc0, request=263708,
e=0x0) at /usr/src/debug/libxcb-1.15-1.3.x86_64/src/xcb_in.c:538
#8  0x7ff3634d1a1e in get_stringlist_reply(xcb_connection_t*,
xcb_get_property_cookie_t, xcb_atom_t) (c=, cookie=...,
cookie@entry=..., type=322) at
/usr/src/debug/kwindowsystem-5.96.0-1.1.x86_64/src/platforms/xcb/netwm.cpp:242
#9  0x7ff3634d1fb8 in NETRootInfo::update(QFlags,
QFlags) (this=0x5568e5b403c0, properties=..., properties2=...)
at
/usr/src/debug/kwindowsystem-5.96.0-1.1.x86_64/src/platforms/xcb/netwm.cpp:2120
#10 0x7ff3634d3b72 in NETRootInfo::event(xcb_generic_event_t*,
QFlags*, QFlags*)
(this=this@entry=0x5568e5b403c0, event=event@entry=0x5568e6079fc0,
properties=properties@entry=0x7ffcd9a05200,
properties2=properties2@entry=0x7ffcd9a051f8) at
/usr/src/debug/kwindowsystem-5.96.0-1.1.x86_64/src/platforms/xcb/netwm.cpp:1870
#11 0x7ff3523f10a6 in
NETEventFilter::nativeEventFilter(xcb_generic_event_t*) (this=0x5568e5b403c0,
ev=0x5568e6079fc0) at
/usr/src/debug/kwindowsystem-5.96.0-1.1.x86_64/src/platforms/xcb/kwindowsystem.cpp:250
#12 0x7ff3624d952f in
QAbstractEventDispatcher::filterNativeEvent(QByteArray const&, void*, long*)
(this=, eventType=..., message=message@entry=0x5568e6079fc0,
result=result@entry=0x7ffcd9a052b8) at kernel/qabstracteventdispatcher.cpp:495
#13 0x7ff35c6f447f in QXcbConnection::handleXcbEvent(xcb_generic_event_t*)
(this=this@entry=0x5568e55df790, event=event@entry=0x5568e6079fc0) at
qxcbconnection.cpp:536
#14 0x7ff35c6f5b16 in
QXcbConnection::processXcbEvents(QFlags)
(this=0x5568e55df790, flags=...) at qxcbconnection.cpp:1020
#15 0x7ff35c71bbbc in
QXcbUnixEventDispatcher::processEvents(QFlags)
(this=0x5568e568c490, flags=...) at qxcbeventdispatcher.cpp:61
#16 0x7ff3624daa2b in
QEventLoop::exec(QFlags)
(this=this@entry=0x7ffcd9a05400, flags=..., flags@entry=...) at
../../include/QtCore/../../src/corelib/global/qflags.h:69
#17 0x7ff3624e2b96 in QCoreApplication::exec() () at
../../include/QtCore/../../src/corelib/global/qflags.h:121
#18 0x7ff36296ee0c in QGuiApplication::exec() () at
kernel/qguiapplication.cpp:1867
#19 0x7ff3619a5395 in QApplication::exec() () at
kernel/qapplication.cpp:2829
#20 0x5568e467c08d in main(int, char**) (argc=,
argv=0x7ffcd9a056c8) at
/usr/src/debug/kwin5-5.25.3-1.1.x86_64/src/main_x11.cpp:501

I attach the full backtrace of all threads.

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

[plasmashell] [Bug 456062] Plasma crashed when returned from sleep (with NVIDIA backtraces)

[Szőts Ákos]

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

--- Comment #2 from Szőts Ákos  ---
Thank you for your quick respone; I've just reported the bug to them.

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

[plasmashell] [Bug 456062] New: Plasma crashed when returned from sleep (with NVIDIA backtraces)

[Szőts Ákos]

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

Bug ID: 456062
   Summary: Plasma crashed when returned from sleep (with NVIDIA
backtraces)
   Product: plasmashell
   Version: 5.25.1
  Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: szots...@gmail.com
CC: k...@davidedmundson.co.uk
  Target Milestone: 1.0

Application: plasmashell (5.25.1)

Qt Version: 5.15.2
Frameworks Version: 5.95.0
Operating System: Linux 5.18.6-1-default x86_64
Windowing System: X11
Distribution: "openSUSE Tumbleweed"
DrKonqi: 5.25.1 [KCrashBackend]

-- Information about the crash:
Plasma crashed when it returned from sleep (without any interaction; I just
turned on the machine). It is perhaps an NVIDIA issue.

Unfortunately, new Dr. Konqi doesn't show in the bug list their states (NEW,
DUPLICATE, WORKSFORME, etc.) and also cannot let me compare the backtraces,
therefore I opened a new report.

Sorry, if it's an already reported duplicate.

The reporter is unsure if this crash is reproducible.

-- Backtrace:
Application: Plasma (plasmashell), signal: Segmentation fault
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = 0x0}
[KCrash Handler]
#6  0x7ff4be8d024b in  () at /lib64/libnvidia-glcore.so.515.48.07
#7  0x7ff4be8d5d74 in  () at /lib64/libnvidia-glcore.so.515.48.07
#8  0x7ff4be8db9af in  () at /lib64/libnvidia-glcore.so.515.48.07
#9  0x7ff4be56fb5d in  () at /lib64/libnvidia-glcore.so.515.48.07
#10 0x7ff4be570892 in  () at /lib64/libnvidia-glcore.so.515.48.07
#11 0x7ff4d7fc90bd in QOpenGLFunctions::glBufferData(unsigned int, long,
void const*, unsigned int) (usage=, data=,
size=, target=34962, this=0x7ff448125d80) at
/usr/include/qt5/QtGui/qopenglfunctions.h:1218
#12 QSGBatchRenderer::Renderer::unmap(QSGBatchRenderer::Buffer*, bool)
(this=0x7ff448125c10, buffer=0x7ff44823aa68, isIndexBuf=) at
/usr/src/debug/libqt5-qtdeclarative-5.15.2+kde43-2.3.x86_64/src/quick/scenegraph/coreapi/qsgbatchrenderer.cpp:1222
#13 0x7ff4d7fcae6b in
QSGBatchRenderer::Renderer::uploadBatch(QSGBatchRenderer::Batch*)
(this=this@entry=0x7ff448125c10, b=b@entry=0x7ff44823aa40) at
/usr/src/debug/libqt5-qtdeclarative-5.15.2+kde43-2.3.x86_64/src/quick/scenegraph/coreapi/qsgbatchrenderer.cpp:2384
#14 0x7ff4d7fdc636 in QSGBatchRenderer::Renderer::render() (this=) at
/usr/src/debug/libqt5-qtdeclarative-5.15.2+kde43-2.3.x86_64/src/quick/scenegraph/coreapi/qsgbatchrenderer.cpp:4352
#15 0x7ff4d7fc4160 in QSGRenderer::renderScene(QSGBindable const&)
(bindable=, this=0x7ff448125c10) at
/usr/src/debug/libqt5-qtdeclarative-5.15.2+kde43-2.3.x86_64/src/quick/scenegraph/coreapi/qsgrenderer.cpp:264
#16 QSGRenderer::renderScene(QSGBindable const&) (this=0x7ff448125c10,
bindable=) at
/usr/src/debug/libqt5-qtdeclarative-5.15.2+kde43-2.3.x86_64/src/quick/scenegraph/coreapi/qsgrenderer.cpp:220
#17 0x7ff4d7fc4613 in QSGRenderer::renderScene(unsigned int)
(this=, fboId=) at
/usr/src/debug/libqt5-qtdeclarative-5.15.2+kde43-2.3.x86_64/src/quick/scenegraph/coreapi/qsgrenderer.cpp:212
#18 0x7ff4d8026513 in
QSGDefaultRenderContext::renderNextFrame(QSGRenderer*, unsigned int)
(this=0x7ff464188850, renderer=0x7ff448125c10, fboId=) at
/usr/src/debug/libqt5-qtdeclarative-5.15.2+kde43-2.3.x86_64/src/quick/scenegraph/qsgdefaultrendercontext.cpp:228
#19 0x7ff4d8092bd9 in QQuickWindowPrivate::renderSceneGraph(QSize const&,
QSize const&) (this=0x55fa541021e0, size=,
surfaceSize=) at
/usr/src/debug/libqt5-qtdeclarative-5.15.2+kde43-2.3.x86_64/src/quick/items/qquickwindow.cpp:616
#20 0x7ff4d80343a7 in QSGRenderThread::syncAndRender(QImage*)
(this=0x55fa54b96170, grabImage=0x0) at
/usr/src/debug/libqt5-qtdeclarative-5.15.2+kde43-2.3.x86_64/src/quick/scenegraph/qsgthreadedrenderloop.cpp:837
#21 0x7ff4d803527f in QSGRenderThread::run() (this=0x55fa54b96170) at
/usr/src/debug/libqt5-qtdeclarative-5.15.2+kde43-2.3.x86_64/src/quick/scenegraph/qsgthreadedrenderloop.cpp:1043
#22 0x7ff4d62f5d4d in QThreadPrivate::start(void*) (arg=0x55fa54b96170) at
thread/qthread_unix.cpp:331
#23 0x7ff4d5aa in start_thread (arg=) at
pthread_create.c:442
#24 0x7ff4d5b31c10 in clone3 () at
../sysdeps/unix/sysv/linux/x86_64/clone3.S:81

Thread 10 (Thread 0x7ff46159d640 (LWP 15953) "KCupsConnection"):
#1  0x7ff4d486c6ae in g_main_context_prepare
(context=context@entry=0x7ff454000c30, priority=priority@entry=0x7ff46159ca40)
at ../glib/gmain.c:3746
#2  0x7ff4d486d0fb in g_main_context_iterate
(context=context@entry=0x7ff454000c30, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at ../glib/gmain.c:4191
#3  0x7ff4d486d2ec in g_main_context_iteration (context=0x7ff454000c30,
may_block=1) at ../glib/gmain.c:4276
#4  0x7ff4d653311e in

[kalendar] [Bug 455369] Calendar event notifications lead to segfault if closed by notification button

[Szőts Ákos]

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

--- Comment #2 from Szőts Ákos  ---
Created attachment 150170
  --> https://bugs.kde.org/attachment.cgi?id=150170=edit
New crash information added by DrKonqi

kalendarac (5.20.2) using Qt 5.15.2

Perhaps a duplicate. New Dr. Konqui doesn't let me compare the backtraces,
unfortunately.

-- Backtrace (Reduced):
#6  _mm_packus_epi16(long long __vector(2), long long __vector(2)) (__B=, __A=) at
/usr/lib64/gcc/x86_64-suse-linux/12/include/emmintrin.h:1000
#7  simdEncodeAscii (end=, src=,
nextAscii=, dst=) at codecs/qutfcodec.cpp:90
#8  QUtf8::convertFromUnicode (uc=, len=32712) at
codecs/qutfcodec.cpp:383
#9  0x7fc8ff57bc75 in qt_convert_to_utf8 (str=...) at text/qstring.cpp:5376
#10 QString::toUtf8_helper (str=...) at text/qstring.cpp:5368

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

[kalendar] [Bug 455369] Calendar event notifications lead to segfault if closed by notification button

[Szőts Ákos]

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

Szőts Ákos  changed:

   What|Removed |Added

 CC||szots...@gmail.com

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

[kleopatra] [Bug 450824] crash when closing kleopatra

[Szőts Ákos]

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

--- Comment #1 from Szőts Ákos  ---
Created attachment 149538
  --> https://bugs.kde.org/attachment.cgi?id=149538=edit
New crash information added by DrKonqi

kleopatra (3.1.21.220401 (22.04.1)) using Qt 5.15.2

- What I was doing when the application crashed:

Choose File > Quit (exit from program).

The backtrace is similar to OP's but complete.

-- Backtrace (Reduced):
#6  __pthread_kill_implementation (threadid=,
signo=signo@entry=6, no_tid=no_tid@entry=0) at pthread_kill.c:44
#7  0x7fdb744a9733 in __pthread_kill_internal (signo=6, threadid=) at pthread_kill.c:78
#8  0x7fdb744566f6 in __GI_raise (sig=sig@entry=6) at
../sysdeps/posix/raise.c:26
#9  0x7fdb7443f814 in __GI_abort () at abort.c:79
#10 0x7fdb7443f72b in __assert_fail_base (fmt=,
assertion=, file=, line=,
function=) at assert.c:92

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

[kleopatra] [Bug 450824] crash when closing kleopatra

[Szőts Ákos]

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

Szőts Ákos  changed:

   What|Removed |Added

 CC||szots...@gmail.com

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

[systemsettings] [Bug 433299] [systemd] Applications meant to autostart do not start after switching to systemd

[Szőts Ákos]

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

Szőts Ákos  changed:

   What|Removed |Added

 Resolution|UPSTREAM|---
 Status|RESOLVED|REOPENED

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

[systemsettings] [Bug 433299] [systemd] Applications meant to autostart do not start after switching to systemd

[Szőts Ákos]

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

Szőts Ákos  changed:

   What|Removed |Added

   Platform|Fedora RPMs |openSUSE RPMs

--- Comment #10 from Szőts Ákos  ---
I have now systemd 250.4 and unfortunately this bug is still there. Are you
sure it's an upstream issue?

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

[plasmashell] [Bug 445664] Cannot move tasks to activities from the panel

[Szőts Ákos]

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

Szőts Ákos  changed:

   What|Removed |Added

 Status|RESOLVED|REOPENED
   Version Fixed In|5.24|
 Ever confirmed|0   |1
 Resolution|FIXED   |---

--- Comment #5 from Szőts Ákos  ---
I tested it in 5.24.1, but unfortunately even with the new menu structure this
issue still remains.

I cannot move an activity to another one from the task manager either by using
the checkboxes or the "Move to ..." menu entry. The window stays on the current
activity and the checkboxes don't get changed either.

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

[kwin] [Bug 414805] Crash in QScreen::handle() after QXcbIntegration::createPlatformOpenGLContext()

[Szőts Ákos]

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

--- Comment #41 from Szőts Ákos  ---
Created attachment 146271
  --> https://bugs.kde.org/attachment.cgi?id=146271=edit
New crash information added by DrKonqi

plasmashell (5.23.4) using Qt 5.15.2

Unfortunately, it seems that the very same crash happens with the Qt patch
applied (my libqt5-base version is 5.15.2+kde268). Once after each monitor
input change I can reproduce it.

I understand that this is a Qt problem (presumably), however, the number of
duplicates tells that it widely affects KDE users.

My question is, despite that this is an external problem, should we reopen it?
Do other people face the same problem also with KDE-patched Qt?

-- Backtrace (Reduced):
#6  0x7f32b4a46794 in QScreen::handle() const (this=0x559f268d9ca0) at
kernel/qscreen.cpp:182
#7  0x7f32aec95150 in
QXcbGlxIntegration::createPlatformOpenGLContext(QOpenGLContext*) const
(this=, context=0x7f32a80043b0) at qxcbglxintegration.cpp:195
#8  0x7f32b4a63bed in QOpenGLContext::create() (this=0x7f32a80043b0) at
kernel/qopenglcontext.cpp:612
#9  0x7f32b60924b8 in QSGRenderThread::sync(bool, bool)
(this=this@entry=0x559f29d4a650, inExpose=inExpose@entry=true,
inGrab=inGrab@entry=false) at
/usr/src/debug/libqt5-qtdeclarative-5.15.2+kde36-1.3.x86_64/src/quick/scenegraph/qsgthreadedrenderloop.cpp:620
#10 0x7f32b609425c in QSGRenderThread::syncAndRender(QImage*)
(this=0x559f29d4a650, grabImage=0x0) at
/usr/src/debug/libqt5-qtdeclarative-5.15.2+kde36-1.3.x86_64/src/quick/scenegraph/qsgthreadedrenderloop.cpp:778

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

[kwin] [Bug 449270] Crash in QXcbScreen::surfaceFormatFor() after QXcbGlxIntegration::createPlatformOpenGLContext)

[Szőts Ákos]

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

--- Comment #3 from Szőts Ákos  ---
Here are the ~previous minute debug logs from "KWIN_GL_DEBUG=1
QT_LOGGING_RULES="kwin_*.debug=true" kwin_x11 --replace&".

Let me know if I can help you debugging this further.

kwin_platform_x11_standalone: Using FBConfig 0x108 for visual 0x84
kwin_tabbox: 0 : keySymX=0x "ffe9"  i= 8  mask=0x "1"  keymap[i]=0x "1"
kwin_core: Failed to create window pixmap for window 0x2e6 (error code 8)
kwin_core: KWin::X11Client(0x55a45907b7e0, windowId=0x3ae,
caption="Munkaasztal — Plasma") true false false
kwin_core: PERMITTED KWin::X11Client(0x55a45907b7e0, windowId=0x3ae,
caption="Munkaasztal — Plasma") true
file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/windowswitcher/WindowSwitcher.qml:30:19:
QML ScrollArea: Binding loop detected for property "height"
file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/windowswitcher/WindowSwitcher.qml:30:19:
QML ScrollArea: Binding loop detected for property "height"
kwin_core: KWin::X11Client(0x55a45a38a460, windowId=0x3a00018,
caption="Plasma") true false false
kwin_core: PERMITTED KWin::X11Client(0x55a45a38a460, windowId=0x3a00018,
caption="Plasma") true
trying to show an empty dialog
kwin_core: KWin::X11Client(0x55a458dc7fe0, windowId=0x2e6, caption="DB
Browser") true true true
kwin_core: DENIED
kwin_core: KWin::X11Client(0x55a458dc7fe0, windowId=0x2e6, caption="DB
Browser") true true true
kwin_core: DENIED
kwin_core: Failed to update gamma ramp for output
KWin::X11PlaceholderOutput(0x55a4599b3d70, name="Placeholder-0",
geometry=QRect(0,0 8x8), scale=1)
kwin_core: KWin::X11Client(0x55a45907b7e0, windowId=0x3ae,
caption="Munkaasztal — Plasma") true false false
kwin_core: PERMITTED KWin::X11Client(0x55a45907b7e0, windowId=0x3ae,
caption="Munkaasztal — Plasma") true
kwin_core: KWin::X11Client(0x55a458dc7fe0, windowId=0x2e6, caption="DB
Browser") true true true
kwin_core: DENIED
kwin_core: User timestamp, ASN: 230459706
kwin_core: User timestamp, final: KWin::X11Client(0x55a45936e270,
windowId=0x3a0012e, caption="Munkaasztal — Plasma") : 230459706
kwin_core: Activation, compared: KWin::X11Client(0x55a45936e270,
windowId=0x3a0012e, caption="Munkaasztal — Plasma") : 230459706 : 230444965 :
true
kwin_core: XCB error: 3 (BadWindow), sequence: 52444, resource id: 60817710,
major code: 129 (SHAPE), minor code: 3 (Combine)
kwin_core: XCB error: 3 (BadWindow), sequence: 52445, resource id: 60817710,
major code: 129 (SHAPE), minor code: 3 (Combine)
kwin_core: XCB error: 3 (BadWindow), sequence: 52464, resource id: 60817710,
major code: 129 (SHAPE), minor code: 3 (Combine)
kwin_core: XCB error: 3 (BadWindow), sequence: 52465, resource id: 60817710,
major code: 129 (SHAPE), minor code: 3 (Combine)
trying to show an empty dialog
kwin_core: User timestamp, ASN: 229479439
kwin_core: User timestamp, final: KWin::X11Client(0x55a45a4246d0,
windowId=0x1a6, caption="KDE Daemon") : 229479439
kwin_core: Activation, compared: KWin::X11Client(0x55a45a4246d0,
windowId=0x1a6, caption="KDE Daemon") : 229479439 : 230444965 : false
kwin_core: KWin::X11Client(0x55a45a38a460, windowId=0x3a00018,
caption="Plasma") true false false
kwin_core: PERMITTED KWin::X11Client(0x55a45a38a460, windowId=0x3a00018,
caption="Plasma") true
kwin_core: XCB error: 152 (BadDamage), sequence: 53305, resource id: 134503031,
major code: 143 (DAMAGE), minor code: 2 (Destroy)
kwin_core: XCB error: 3 (BadWindow), sequence: 53306, resource id: 134503025,
major code: 129 (SHAPE), minor code: 6 (Input)
kwin_core: User timestamp, ASN: 23044
kwin_core: User timestamp, final: KWin::X11Client(0x55a45a4246d0,
windowId=0x3a00137, caption="Plasma") : 23044
kwin_core: Activation, compared: KWin::X11Client(0x55a45a4246d0,
windowId=0x3a00137, caption="Plasma") : 23044 : 230878384 : false
kwin_core: KWin::X11Client(0x55a45a4246d0, windowId=0x3a00137,
caption="Plasma") true false false
kwin_core: PERMITTED KWin::X11Client(0x55a45a4246d0, windowId=0x3a00137,
caption="Plasma") true
kwin_core: User timestamp, ASN: 23044
kwin_core: User timestamp, final: KWin::X11Client(0x55a4593b6570,
windowId=0x3a00139, caption="Plasma") : 23044
kwin_core: Activation, compared: KWin::X11Client(0x55a4593b6570,
windowId=0x3a00139, caption="Plasma") : 23044 : 230878384 : false
kwin_core: KWin::X11Client(0x55a4593b6570, windowId=0x3a00139,
caption="Plasma") true false false
kwin_core: PERMITTED KWin::X11Client(0x55a4593b6570, windowId=0x3a00139,
caption="Plasma") true
kwin_core: KWin::X11Client(0x55a4593b6570, windowId=0x3a00139,
caption="Plasma") true false fals

[kwin] [Bug 449270] Crash in QXcbScreen::surfaceFormatFor() after QXcbGlxIntegration::createPlatformOpenGLContext)

[Szőts Ákos]

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

--- Comment #2 from Szőts Ákos  ---
I don't know if it's in connection or not but when I start kwin in debug mode
every time I get the following error message:

kwin_core: XCB error: 152 (BadDamage), sequence: 32772, resource id: 35675075,
major code: 143 (DAMAGE), minor code: 3 (Subtract)

after a really quick Alt+Tab+Tab sequence.

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

[krunner] [Bug 449427] KRunner crashed after external monitor input change on Alt+F2 in QXcbConnection::hasDefaultVisualId()

[Szőts Ákos]

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

--- Comment #1 from Szőts Ákos  ---
I see many NVIDIA-originated error messages in dmesg (though I think crash is
not a desired reaction):

[jan31 08:54] NVRM: Xid (PCI::2d:00): 13, pid=1222, Graphics Exception on
GPC 0: 3D HEIGHT CT Violation. Coordinates: (0x0, 0x80)
[  +0,11] NVRM: Xid (PCI::2d:00): 13, pid=1222, Graphics Exception: ESR
0x500420=0x8020 0x500434=0x80 0x500438=0x2a00 0x50043c=0x0
[  +0,14] NVRM: Xid (PCI::2d:00): 13, pid=1222, Graphics Exception on
GPC 1: 3D HEIGHT CT Violation. Coordinates: (0x10, 0x80)
[  +0,06] NVRM: Xid (PCI::2d:00): 13, pid=1222, Graphics Exception: ESR
0x508420=0x8020 0x508434=0x800010 0x508438=0x2a00 0x50843c=0x0
[  +0,000164] NVRM: Xid (PCI::2d:00): 13, pid=4849, Graphics Exception:
ChID 0068, Class b197, Offset 0f80, Data 

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

[krunner] [Bug 449427] New: KRunner crashed after external monitor input change on Alt+F2 in QXcbConnection::hasDefaultVisualId()

[Szőts Ákos]

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

Bug ID: 449427
   Summary: KRunner crashed after external monitor input change on
Alt+F2 in QXcbConnection::hasDefaultVisualId()
   Product: krunner
   Version: 5.23.4
  Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: alexander.loh...@gmx.de
  Reporter: szots...@gmail.com
CC: plasma-b...@kde.org
  Target Milestone: ---

Application: krunner (5.23.4)

Qt Version: 5.15.2
Frameworks Version: 5.89.0
Operating System: Linux 5.15.12-1-default x86_64
Windowing System: X11
Distribution: "openSUSE Tumbleweed"
DrKonqi: 5.23.4 [KCrashBackend]

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

1. Monitor input has changed while KDE was running
2. Alt+F2 -> KRunner crashed.

Qt version:
libqt5-qtbase: 5.15.2+kde268

The crash can be reproduced sometimes.

-- Backtrace:
Application: krunner (krunner), signal: Segmentation fault
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = 0x0}
[KCrash Handler]
#6  0x7f90dcd57173 in QXcbConnection::hasDefaultVisualId (this=) at
/usr/src/debug/libqt5-qtbase-5.15.2+kde268-1.1.x86_64/src/plugins/platforms/xcb/qxcbconnection.h:169
#7  QXcbVirtualDesktop::surfaceFormatFor (this=0x31, format=...) at
qxcbscreen.cpp:425
#8  0x7f90dcd57752 in QXcbScreen::surfaceFormatFor
(this=this@entry=0x55b182954780, format=...) at qxcbscreen.cpp:653
#9  0x7f90dc04316c in QXcbGlxIntegration::createPlatformOpenGLContext
(this=, context=0x7f90d8008ce0) at qxcbglxintegration.cpp:196
#10 0x7f90e2259bed in QOpenGLContext::create (this=0x7f90d8008ce0) at
kernel/qopenglcontext.cpp:612
#11 0x7f90e37344b8 in QSGRenderThread::sync
(this=this@entry=0x7f90d8009710, inExpose=inExpose@entry=true,
inGrab=inGrab@entry=false) at
/usr/src/debug/libqt5-qtdeclarative-5.15.2+kde36-1.3.x86_64/src/quick/scenegraph/qsgthreadedrenderloop.cpp:620
#12 0x7f90e373625c in QSGRenderThread::syncAndRender (this=0x7f90d8009710,
grabImage=0x0) at
/usr/src/debug/libqt5-qtdeclarative-5.15.2+kde36-1.3.x86_64/src/quick/scenegraph/qsgthreadedrenderloop.cpp:778
#13 0x7f90e3736f97 in QSGRenderThread::run (this=0x7f90d8009710) at
/usr/src/debug/libqt5-qtdeclarative-5.15.2+kde36-1.3.x86_64/src/quick/scenegraph/qsgthreadedrenderloop.cpp:1043
#14 0x7f90e1a3bdf1 in QThreadPrivate::start (arg=0x7f90d8009710) at
thread/qthread_unix.cpp:329
#15 0x7f90e15a23d7 in start_thread (arg=) at
pthread_create.c:435
#16 0x7f90e162b6e0 in clone3 () at
../sysdeps/unix/sysv/linux/x86_64/clone3.S:81

Thread 4 (Thread 0x7f90cf5ef640 (LWP 2599) "QQmlThread"):
#1  0x7f90e00f50be in g_main_context_poll (priority=,
n_fds=1, fds=0x7f90c8004a60, timeout=, context=0x7f90c8000c20)
at ../glib/gmain.c:4478
#2  g_main_context_iterate (context=context@entry=0x7f90c8000c20,
block=block@entry=1, dispatch=dispatch@entry=1, self=) at
../glib/gmain.c:4170
#3  0x7f90e00f51df in g_main_context_iteration (context=0x7f90c8000c20,
may_block=1) at ../glib/gmain.c:4240
#4  0x7f90e1c78276 in QEventDispatcherGlib::processEvents
(this=0x7f90c8000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#5  0x7f90e1c1f72b in QEventLoop::exec (this=this@entry=0x7f90cf5eeb60,
flags=..., flags@entry=...) at
../../include/QtCore/../../src/corelib/global/qflags.h:69
#6  0x7f90e1a3acbe in QThread::exec (this=this@entry=0x55b182243600) at
../../include/QtCore/../../src/corelib/global/qflags.h:121
#7  0x7f90e33a0cc5 in QQmlThreadPrivate::run (this=0x55b182243600) at
/usr/src/debug/libqt5-qtdeclarative-5.15.2+kde36-1.3.x86_64/src/qml/qml/ftw/qqmlthread.cpp:155
#8  0x7f90e1a3bdf1 in QThreadPrivate::start (arg=0x55b182243600) at
thread/qthread_unix.cpp:329
#9  0x7f90e15a23d7 in start_thread (arg=) at
pthread_create.c:435
#10 0x7f90e162b6e0 in clone3 () at
../sysdeps/unix/sysv/linux/x86_64/clone3.S:81

Thread 3 (Thread 0x7f90d7f7c640 (LWP 2397) "QDBusConnection"):
#1  0x7f90e00f4592 in g_main_context_prepare
(context=context@entry=0x7f90dc20, priority=priority@entry=0x7f90d7f7ba10)
at ../glib/gmain.c:3697
#2  0x7f90e00f4feb in g_main_context_iterate
(context=context@entry=0x7f90dc20, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at ../glib/gmain.c:4155
#3  0x7f90e00f51df in g_main_context_iteration (context=0x7f90dc20,
may_block=1) at ../glib/gmain.c:4240
#4  0x7f90e1c78276 in QEventDispatcherGlib::processEvents
(this=0x7f90db60, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#5  0x7f90e1c1f72b in QEventLoop::exec (this=this@entry=0x7f90d7f7bb50,
flags=..., flags@entry=...) at
../../include/QtCore/../../src/corelib/global/qflags.h:69
#6  0x7f90e1a3acbe in QThread::exec (this=this@entry=0x7f90e2039440
<(anonymous 

[kwin] [Bug 414805] Crash in QScreen::handle() after QXcbIntegration::createPlatformOpenGLContext()

[Szőts Ákos]

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

--- Comment #39 from Szőts Ákos  ---
I reported the phenomenon I referred above in Bug 449270 separately to be able
to track it independently.

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

[kwin] [Bug 449270] New: Crash in QXcbScreen::surfaceFormatFor() after QXcbGlxIntegration::createPlatformOpenGLContext)

[Szőts Ákos]

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

Bug ID: 449270
   Summary: Crash in QXcbScreen::surfaceFormatFor() after
QXcbGlxIntegration::createPlatformOpenGLContext)
   Product: kwin
   Version: 5.23.4
  Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: szots...@gmail.com
  Target Milestone: ---

Application: kwin_x11 (5.23.4)

Qt Version: 5.15.2
Frameworks Version: 5.89.0
Operating System: Linux 5.15.12-1-default x86_64
Windowing System: X11
Distribution: "openSUSE Tumbleweed"
DrKonqi: 5.23.4 [KCrashBackend]

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

I pressed Alt+Tab when KWin crashed.

Similar crash happens after I change monitor inputs and then I start KRunner or
click on a taskbar icon. I'll try to gather more backtraces from those
occasions.

KDE Qt version:
libqt5-qtbase-devel: 5.15.2+kde268

The reporter is unsure if this crash is reproducible.

-- Backtrace:
Application: KWin (kwin_x11), signal: Segmentation fault
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = 0x0}
[KCrash Handler]
#6  0x7f23a72bc739 in QXcbScreen::surfaceFormatFor(QSurfaceFormat const&)
const (this=this@entry=0x0, format=...) at qxcbscreen.cpp:653
#7  0x7f23a660116c in
QXcbGlxIntegration::createPlatformOpenGLContext(QOpenGLContext*) const
(this=, context=0x55faa641b5a0) at qxcbglxintegration.cpp:196
#8  0x7f23ae29bbed in QOpenGLContext::create() (this=0x55faa641b5a0) at
kernel/qopenglcontext.cpp:612
#9  0x7f23ac32b4b8 in QSGRenderThread::sync(bool, bool)
(this=this@entry=0x55faa6461680, inExpose=inExpose@entry=true,
inGrab=inGrab@entry=false) at
/usr/src/debug/libqt5-qtdeclarative-5.15.2+kde36-1.3.x86_64/src/quick/scenegraph/qsgthreadedrenderloop.cpp:620
#10 0x7f23ac32d25c in QSGRenderThread::syncAndRender(QImage*)
(this=0x55faa6461680, grabImage=0x0) at
/usr/src/debug/libqt5-qtdeclarative-5.15.2+kde36-1.3.x86_64/src/quick/scenegraph/qsgthreadedrenderloop.cpp:778
#11 0x7f23ac32df97 in QSGRenderThread::run() (this=0x55faa6461680) at
/usr/src/debug/libqt5-qtdeclarative-5.15.2+kde36-1.3.x86_64/src/quick/scenegraph/qsgthreadedrenderloop.cpp:1043
#12 0x7f23adc14df1 in QThreadPrivate::start(void*) (arg=0x55faa6461680) at
thread/qthread_unix.cpp:329
#13 0x7f23acef93d7 in start_thread (arg=) at
pthread_create.c:435
#14 0x7f23acf826e0 in clone3 () at
../sysdeps/unix/sysv/linux/x86_64/clone3.S:81

Thread 5 (Thread 0x7f235cbb9640 (LWP 12743) "FreezeDetector"):
#1  0x7f23ade4d2b9 in ppoll (__ss=, __timeout=, __nfds=, __fds=) at
/usr/include/bits/poll2.h:81
#2  qt_ppoll (timeout_ts=0x0, nfds=1, fds=0x55faa5cffce8) at
kernel/qcore_unix.cpp:132
#3  qt_ppoll (timeout_ts=0x0, nfds=1, fds=0x55faa5cffce8) at
kernel/qcore_unix.cpp:129
#4  qt_safe_poll(pollfd*, unsigned long, timespec const*) (fds=0x55faa5cffce8,
nfds=1, timeout_ts=timeout_ts@entry=0x0) at kernel/qcore_unix.cpp:155
#5  0x7f23ade4e963 in
QEventDispatcherUNIX::processEvents(QFlags)
(this=, flags=...) at kernel/qeventdispatcher_unix.cpp:502
#6  0x7f23addf872b in
QEventLoop::exec(QFlags)
(this=this@entry=0x7f235cbb8b80, flags=..., flags@entry=...) at
../../include/QtCore/../../src/corelib/global/qflags.h:69
#7  0x7f23adc13cbe in QThread::exec() (this=) at
../../include/QtCore/../../src/corelib/global/qflags.h:121
#8  0x7f23adc14df1 in QThreadPrivate::start(void*) (arg=0x55faa596d020) at
thread/qthread_unix.cpp:329
#9  0x7f23acef93d7 in start_thread (arg=) at
pthread_create.c:435
#10 0x7f23acf826e0 in clone3 () at
../sysdeps/unix/sysv/linux/x86_64/clone3.S:81

Thread 4 (Thread 0x7f233500f640 (LWP 32050) "CPMMListener"):
#1  0x7f239eba3b51 in  () at /lib64/libnvidia-glcore.so.495.46
#2  0x7f239eba15e8 in  () at /lib64/libnvidia-glcore.so.495.46
#3  0x7f23acef93d7 in start_thread (arg=) at
pthread_create.c:435
#4  0x7f23acf826e0 in clone3 () at
../sysdeps/unix/sysv/linux/x86_64/clone3.S:81

Thread 3 (Thread 0x7f235e3fb640 (LWP 32040) "QQmlThread"):
#1  0x7f23ade4d2b9 in ppoll (__ss=, __timeout=, __nfds=, __fds=) at
/usr/include/bits/poll2.h:81
#2  qt_ppoll (timeout_ts=0x0, nfds=1, fds=0x7f234c000d78) at
kernel/qcore_unix.cpp:132
#3  qt_ppoll (timeout_ts=0x0, nfds=1, fds=0x7f234c000d78) at
kernel/qcore_unix.cpp:129
#4  qt_safe_poll(pollfd*, unsigned long, timespec const*) (fds=0x7f234c000d78,
nfds=1, timeout_ts=timeout_ts@entry=0x0) at kernel/qcore_unix.cpp:155
#5  0x7f23ade4e963 in
QEventDispatcherUNIX::processEvents(QFlags)
(this=, flags=...) at kernel/qeventdispatcher_unix.cpp:502
#6  0x7f23addf872b in
QEventLoop::exec(QFlags)
(this=this@entry=0x7f235e3fab60, flags=..., flags@entry=...) at
../../include/QtCore/../../src/corelib/global/qflags.h:69
#7  0x7f23adc13cbe in QThread::exec() 

[krunner] [Bug 416145] Krunner doesn't immediately intercept keystrokes, leading the user to accidentally type text into whatever app is open

[Szőts Ákos]

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

--- Comment #57 from Szőts Ákos  ---
Yes, what I always do in all my KDE installs is to autostart "/usr/bin/krunner
--daemon". This causes KRunner to be loaded during KDE start-up and not to wait
for it until the first time it's needed. I think it'd be nice to include it
into default KDE installs, too.

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

[kwin] [Bug 414805] Crash in QScreen::handle() after QXcbIntegration::createPlatformOpenGLContext()

[Szőts Ákos]

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

--- Comment #38 from Szőts Ákos  ---
I see the backport was merged into KDE Qt repos 6 months ago. I use openSUSE
Tumbleweed 20220103 with libqt5 5.15.2+kde268-1.1 (so its seems it has KDE
patches).

For some reason I still daily meet this crash after I change monitor outputs
(once for KWin after an Alt+Tab, then in Krunner when I press Alt+F2, finally
in plasmashell when I click on volume slider).

In the distro libqt5 changelog
(https://build.opensuse.org/package/view_file/openSUSE:Factory/libqt5-qtbase/libqt5-qtbase.changes?expand=1
) I don't see the explicit mentioning of this backport fix, however, I do see
that it's getting the sources from invent.kde
(https://build.opensuse.org/package/view_file/openSUSE:Factory/libqt5-qtbase/_service?expand=1
)

My question is, how certain you are that this patch fixed the issue or should I
post some backtraces to verify whether we're talking about the same crash?

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

[systemsettings] [Bug 433299] [systemd] Applications meant to autostart do not start after switching to systemd

[Szőts Ákos]

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

--- Comment #8 from Szőts Ákos  ---
Just last week I thought I give systemd Plasma another spin, but unfortunately
this feature still doesn't work for me either so I reverted back.

I have the xbindkeys program mentioned above and a manual bash script which
starts redshift, but none of them gets started.

I used the latest Tumbleweed for testing (now I don't have it handy but
supposedly it has systemd 249 in it).

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

[korganizer] [Bug 444543] KOrganizer crashes when adding new event

[Szőts Ákos]

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

--- Comment #1 from Szőts Ákos  ---
Created attachment 143782
  --> https://bugs.kde.org/attachment.cgi?id=143782=edit
New crash information added by DrKonqi

kontact (5.18.3 (21.08.3)) using Qt 5.15.2

- What I was doing when the application crashed:

I created a new task (with recurrency). When I clicked OK, KOrganizer crashed.
The event had been created successfully before, though.

-- Backtrace (Reduced):
#6  QSortFilterProxyModelPrivate::proxy_to_source (this=0x56554185b0d0,
proxy_index=...) at itemmodels/qsortfilterproxymodel.cpp:571
#7  0x7f7138b6b2c9 in QSortFilterProxyModel::mapToSource (proxyIndex=...,
this=0x5655419cc2c0) at itemmodels/qsortfilterproxymodel.cpp:3171
#8  QSortFilterProxyModelPrivate::store_persistent_indexes (this=) at itemmodels/qsortfilterproxymodel.cpp:1248
#9  0x7f7138b6cd5b in
QSortFilterProxyModelPrivate::_q_sourceLayoutAboutToBeChanged
(this=0x56554185b0d0, sourceParents=..., hint=) at
itemmodels/qsortfilterproxymodel.cpp:1639
#10 0x7f7138bd5078 in doActivate (sender=0x5655419cb430,
signal_index=9, argv=0x7fff36d06a30) at kernel/qobject.cpp:3898

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

[korganizer] [Bug 444543] KOrganizer crashes when adding new event

[Szőts Ákos]

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

Szőts Ákos  changed:

   What|Removed |Added

 CC||szots...@gmail.com

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

[kwin] [Bug 445664] New: Cannot move tasks to activities from the panel

[Szőts Ákos]

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

Bug ID: 445664
   Summary: Cannot move tasks to activities from the panel
   Product: kwin
   Version: 5.23.2
  Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: activities
  Assignee: kwin-bugs-n...@kde.org
  Reporter: szots...@gmail.com
  Target Milestone: ---

STEPS TO REPRODUCE
1. Have a non-KDE/CSD window (like a browser) open
2. Have multiple activities available
3. Right click on the task manager entry of that window and choose "Show on
activity", then choose a different activity to current one

OBSERVED RESULT

Nothing happens, when you right click again, the tick mark remains next to the
same activity name as before and the window didn't get moved to the selected
activity.

Interestingly, it works for KDE/non-CSD windows when the same is tried from the
title bar.

EXPECTED RESULT

Can move a CSD window to the selected activity.

SOFTWARE/OS VERSIONS

Operating System: openSUSE Tumbleweed 2021
KDE Plasma Version: 5.23.2
KDE Frameworks Version: 5.87.0
Qt Version: 5.15.2
Kernel Version: 5.14.6-1-default (64-bit)
Graphics Platform: X11

ADDITIONAL INFORMATION

Btw. I like the non-CSD title-bar solution much better because the local menu
stays open during activity manipulation.

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

[kontact] [Bug 444909] New: KOrganizer crashed when changed the URL and look-back interval of a calendar

[Szőts Ákos]

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

Bug ID: 444909
   Summary: KOrganizer crashed when changed the URL and look-back
interval of a calendar
   Product: kontact
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: szots...@gmail.com
  Target Milestone: ---

Application: kontact (5.18.2 (21.08.2))

Qt Version: 5.15.2
Frameworks Version: 5.87.0
Operating System: Linux 5.14.6-1-default x86_64
Windowing System: X11
Distribution: "openSUSE Tumbleweed"
DrKonqi: 5.23.2 [KCrashBackend]

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

1. I opened the calendar properties in KOrganizer and changed the URL. The new
URL pointed to the very same physical destination, but it was an external
address to the same DAV resource.
2. I modified the look-back interval from 2 years to infinite (so I turned off
the limitation).
3. I clicked OK.

First, KOrganizer shown a random calendar (or perhaps a to-do) entry for today
and some seconds later it crashed completely.

The reporter is unsure if this crash is reproducible.

-- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = }
[KCrash Handler]
#6  0x7f47ed959878 in QDateTime::operator= (this=this@entry=0x55fb745ba130,
other=...) at time/qdatetime.cpp:3781
#7  0x7f478ad94228 in KCalendarCore::Event::Private::operator=
(this=0x55fb745ba130) at
/usr/src/debug/kcalendarcore-5.87.0-1.1.x86_64/src/event.cpp:33
#8  KCalendarCore::Event::assign (other=..., this=0x55fb73ab4270) at
/usr/src/debug/kcalendarcore-5.87.0-1.1.x86_64/src/event.cpp:75
#9  KCalendarCore::Event::assign (this=0x55fb73ab4270, other=...) at
/usr/src/debug/kcalendarcore-5.87.0-1.1.x86_64/src/event.cpp:70
#10 0x7f478adb1ea2 in KCalendarCore::IncidenceBase::operator=
(this=this@entry=0x55fb73ab4270, other=...) at
/usr/src/debug/kcalendarcore-5.87.0-1.1.x86_64/src/incidencebase.cpp:134
#11 0x7f478a838358 in Akonadi::ETMCalendarPrivate::updateItem
(this=0x55fb72260e60, item=...) at
/usr/include/qt5/QtCore/qsharedpointer_impl.h:301
#12 0x7f478a839099 in
Akonadi::ETMCalendarPrivate::onDataChangedInFilteredModel (this=0x55fb72260e60,
topLeft=..., bottomRight=...) at
/usr/src/debug/akonadi-calendar-21.08.2-1.1.x86_64/src/etmcalendar.cpp:365
#13 0x7f47edaab013 in QtPrivate::QSlotObjectBase::call (a=0x7ffe274b79a0,
r=0x55fb72260e60, this=0x55fb72295350) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#14 doActivate (sender=0x55fb72233820, signal_index=3,
argv=0x7ffe274b79a0) at kernel/qobject.cpp:3886
#15 0x7f47edaa44df in QMetaObject::activate
(sender=sender@entry=0x55fb72233820, m=m@entry=0x7f47edd48fa0
,
local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffe274b79a0)
at kernel/qobject.cpp:3946
#16 0x7f47eda0ed85 in QAbstractItemModel::dataChanged
(this=this@entry=0x55fb72233820, _t1=..., _t2=..., _t3=...) at
.moc/moc_qabstractitemmodel.cpp:557
#17 0x7f47eda4a921 in QSortFilterProxyModelPrivate::_q_sourceDataChanged
(this=0x55fb73029410, source_top_left=..., source_bottom_right=..., roles=...)
at itemmodels/qsortfilterproxymodel.cpp:1539
#18 0x7f47edaab048 in doActivate (sender=0x55fb72233310,
signal_index=3, argv=0x7ffe274b7c50) at kernel/qobject.cpp:3898
#19 0x7f47edaa44df in QMetaObject::activate
(sender=sender@entry=0x55fb72233310, m=m@entry=0x7f47edd48fa0
,
local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffe274b7c50)
at kernel/qobject.cpp:3946
#20 0x7f47eda0ed85 in QAbstractItemModel::dataChanged
(this=this@entry=0x55fb72233310, _t1=..., _t2=..., _t3=...) at
.moc/moc_qabstractitemmodel.cpp:557
#21 0x7f47eda4a921 in QSortFilterProxyModelPrivate::_q_sourceDataChanged
(this=0x55fb72e00140, source_top_left=..., source_bottom_right=..., roles=...)
at itemmodels/qsortfilterproxymodel.cpp:1539
#22 0x7f47edaab048 in doActivate (sender=0x55fb72233760,
signal_index=3, argv=0x7ffe274b7f00) at kernel/qobject.cpp:3898
#23 0x7f47edaa44df in QMetaObject::activate
(sender=sender@entry=0x55fb72233760, m=m@entry=0x7f47edd48fa0
,
local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffe274b7f00)
at kernel/qobject.cpp:3946
#24 0x7f47eda0ed85 in QAbstractItemModel::dataChanged
(this=this@entry=0x55fb72233760, _t1=..., _t2=..., _t3=...) at
.moc/moc_qabstractitemmodel.cpp:557
#25 0x7f47eda4a921 in QSortFilterProxyModelPrivate::_q_sourceDataChanged
(this=0x55fb70ff2d30, source_top_left=..., source_bottom_right=..., roles=...)
at itemmodels/qsortfilterproxymodel.cpp:1539
#26 0x7f47edaab048 in doActivate (sender=0x55fb722337e0,
signal_index=3, argv=0x7ffe274b81b0) at kernel/qobject.cpp:3898
#27 0x7f47edaa44df 

[drkonqi] [Bug 443517] Cannot submit a bug report with Dr. Konqi

[Szőts Ákos]

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

Szőts Ákos  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |WORKSFORME
 Status|NEEDSINFO   |RESOLVED

--- Comment #3 from Szőts Ákos  ---
That makes sense.

Since the report I haven't met a crashing application but when I will have,
I'll update this bug report.

Until then I'm closing it appropriately.

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

[systemsettings] [Bug 443541] New: KWin rules window by default hides the "Add property" footer

[Szőts Ákos]

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

Bug ID: 443541
   Summary: KWin rules window by default hides the "Add property"
footer
   Product: systemsettings
   Version: 5.22.4
  Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: kcm_kwinrules
  Assignee: kwin-bugs-n...@kde.org
  Reporter: szots...@gmail.com
CC: isma...@gmail.com, plasma-b...@kde.org
  Target Milestone: ---

Created attachment 142294
  --> https://bugs.kde.org/attachment.cgi?id=142294=edit
KWin rules settings - invisible footer (note the missing "Add property" button
in the bottom)

SUMMARY

1. Open the context menu of a window title bar
2. Choose "Configure Special Window/Application Settings"
3. When you'd like to add a new property, the "Add property" button is missing
4. Resize the window down and up
5. The button appears

Errors what I get when I open the window:

okt 10 11:12:34 openSUSE kwin_rules_dialog[27559]: kf.kirigami:
Units.devicePixelRatio is deprecated (since 5.86 ): This returns 1 when using
Qt HiDPI scaling.
okt 10 11:12:34 openSUSE kwin_rules_dialog[27559]:
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/Page.qml:448: TypeError: Cannot
read property 'globalToolBar' of null
okt 10 11:12:34 openSUSE kwin_rules_dialog[27559]:
file:///usr/share/kpackage/kcms/kcm_kwinrules/contents/ui/RulesList.qml:60:
ReferenceError: units is not defined
okt 10 11:12:34 openSUSE kwin_rules_dialog[27559]:
file:///usr/share/kpackage/kcms/kcm_kwinrules/contents/ui/RulesList.qml:60:
ReferenceError: units is not defined
okt 10 11:12:34 openSUSE kwin_rules_dialog[27559]:
file:///usr/share/kpackage/kcms/kcm_kwinrules/contents/ui/RulesList.qml:60:
ReferenceError: units is not defined
okt 10 11:12:35 openSUSE kwin_rules_dialog[27559]:
file:///usr/share/kpackage/kcms/kcm_kwinrules/contents/ui/RulesList.qml:60:
ReferenceError: units is not defined
okt 10 11:12:35 openSUSE kwin_rules_dialog[27559]:
file:///usr/share/kpackage/kcms/kcm_kwinrules/contents/ui/RulesList.qml:60:
ReferenceError: units is not defined
okt 10 11:12:35 openSUSE kwin_rules_dialog[27559]:
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/templates/InlineMessage.qml:261:9:
QML ActionToolBar: Binding loop detected for property "atBottom"
okt 10 11:12:35 openSUSE kwin_rules_dialog[27559]: Retrieved properties for
window QUuid("{8b217033-50d1-4019-8840-9fa29e096ed8}")
okt 10 11:12:35 openSUSE kwin_rules_dialog[27559]:
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/templates/SwipeListItem.qml:170:9:
Unable to assign DelegateRecycler to QQuickFlickable
okt 10 11:12:35 openSUSE kwin_rules_dialog[27559]:
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/templates/SwipeListItem.qml:170:9:
Unable to assign DelegateRecycler to QQuickFlickable
okt 10 11:12:35 openSUSE kwin_rules_dialog[27559]:
file:///usr/share/kpackage/kcms/kcm_kwinrules/contents/ui/RulesEditor.qml:107:9:
QML SpinBox: Binding loop detected for property "implicitWidth"
okt 10 11:12:35 openSUSE kwin_rules_dialog[27559]:
file:///usr/share/kpackage/kcms/kcm_kwinrules/contents/ui/RulesEditor.qml:107:9:
QML SpinBox: Binding loop detected for property "implicitWidth"
okt 10 11:12:35 openSUSE kwin_rules_dialog[27559]:
file:///usr/share/kpackage/kcms/kcm_kwinrules/contents/ui/RulesEditor.qml:107:9:
QML SpinBox: Binding loop detected for property "implicitHeight"
okt 10 11:12:35 openSUSE kwin_rules_dialog[27559]:
file:///usr/share/kpackage/kcms/kcm_kwinrules/contents/ui/RulesEditor.qml:107:9:
QML SpinBox: Binding loop detected for property "implicitWidth"
okt 10 11:12:35 openSUSE kwin_rules_dialog[27559]:
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/Page.qml:448: TypeError: Cannot
read property 'globalToolBar' of null
okt 10 11:12:35 openSUSE kwin_rules_dialog[27559]:
file:///usr/share/kpackage/kcms/kcm_kwinrules/contents/ui/RulesEditor.qml:62:
ReferenceError: units is not defined
okt 10 11:12:35 openSUSE kwin_rules_dialog[27559]:
file:///usr/share/kpackage/kcms/kcm_kwinrules/contents/ui/RulesEditor.qml:62:
ReferenceError: units is not defined
okt 10 11:12:35 openSUSE kwin_rules_dialog[27559]:
file:///usr/share/kpackage/kcms/kcm_kwinrules/contents/ui/RulesEditor.qml:62:
ReferenceError: units is not defined
okt 10 11:12:35 openSUSE kwin_rules_dialog[27559]:
file:///usr/share/kpackage/kcms/kcm_kwinrules/contents/ui/RulesEditor.qml:62:
ReferenceError: units is not defined
okt 10 11:12:35 openSUSE kwin_rules_dialog[27559]:
file:///usr/share/kpackage/kcms/kcm_kwinrules/contents/ui/RulesEditor.qml:69:13:
QML ColumnLayout: Cannot anchor to an item that isn't a parent or sibling.
okt 10 11:12:35 openSUSE kwin_rules_dialog[27559]:
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/templates/SwipeListItem.qml:170:9:
Unable to assign DelegateRecycler to QQuickFlickable
okt 10 11:12:35 openSUSE kwin_rules_dialog[27559]:

[frameworks-kactivities] [Bug 443537] Activity settings window has no labels in it

[Szőts Ákos]

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

--- Comment #2 from Szőts Ákos  ---
When I open System settings and click on the main menu which leads to the
Activity submenu, I get the following error messages:

okt 10 10:11:43 openSUSE systemsettings5[10188]: kf.kirigami:
Units.devicePixelRatio is deprecated (since 5.86 ): This returns 1 when using
Qt HiDPI scaling.
okt 10 10:11:43 openSUSE systemsettings5[10188]:
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/Page.qml:448: TypeError: Cannot
read property 'globalToolBar' of null
okt 10 10:11:43 openSUSE systemsettings5[10188]:
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/templates/OverlaySheet.qml:220:38:
QML FocusScope: Binding loop detected for property "contentItemMaximumWidth"
okt 10 10:11:43 openSUSE systemsettings5[10188]: QCoreApplication::postEvent:
Unexpected null receiver
okt 10 10:11:43 openSUSE systemsettings5[10188]:
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/Page.qml:448: TypeError: Cannot
read property 'globalToolBar' of null
okt 10 10:11:43 openSUSE systemsettings5[10188]:
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/AbstractApplicationItem.qml:94:
TypeError: Cannot read property 'position' of null
okt 10 10:11:43 openSUSE systemsettings5[10188]:
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/AbstractApplicationItem.qml:93:
TypeError: Cannot read property 'background' of null
okt 10 10:11:43 openSUSE systemsettings5[10188]:
file:///usr/lib64/qt5/qml/org/kde/newstuff/qml/Page.qml:155: TypeError: Cannot
read property 'useLabel' of null
okt 10 10:11:43 openSUSE systemsettings5[10188]:
file:///usr/lib64/qt5/qml/org/kde/newstuff/qml/Dialog.qml:129: TypeError:
Cannot read property 'uploadEnabled' of null
okt 10 10:11:43 openSUSE systemsettings5[10188]: kf.coreaddons: "Could not load
plugin from "
okt 10 10:11:43 openSUSE systemsettings5[10188]: kf.coreaddons: "Could not load
plugin from "
okt 10 10:11:43 openSUSE systemsettings5[10188]:
file:///usr/share/kpackage/kcms/kcm_screenlocker/contents/ui/main.qml:83:13:
QML SpinBox: Binding loop detected for property "implicitWidth"
okt 10 10:11:43 openSUSE systemsettings5[10188]:
file:///usr/share/kpackage/kcms/kcm_screenlocker/contents/ui/main.qml:83:13:
QML SpinBox: Binding loop detected for property "implicitWidth"
okt 10 10:11:43 openSUSE systemsettings5[10188]:
file:///usr/share/kpackage/kcms/kcm_screenlocker/contents/ui/main.qml:83:13:
QML SpinBox: Binding loop detected for property "implicitHeight"
okt 10 10:11:43 openSUSE systemsettings5[10188]:
file:///usr/share/kpackage/kcms/kcm_screenlocker/contents/ui/main.qml:50:17:
QML SpinBox: Binding loop detected for property "implicitWidth"
okt 10 10:11:43 openSUSE systemsettings5[10188]:
file:///usr/share/kpackage/kcms/kcm_screenlocker/contents/ui/main.qml:50:17:
QML SpinBox: Binding loop detected for property "implicitWidth"
okt 10 10:11:43 openSUSE systemsettings5[10188]:
file:///usr/share/kpackage/kcms/kcm_screenlocker/contents/ui/main.qml:50:17:
QML SpinBox: Binding loop detected for property "implicitHeight"
okt 10 10:11:43 openSUSE systemsettings5[10188]:
file:///usr/share/kpackage/kcms/kcm_screenlocker/contents/ui/main.qml:83:13:
QML SpinBox: Binding loop detected for property "implicitWidth"
okt 10 10:11:43 openSUSE systemsettings5[10188]:
file:///usr/share/kpackage/kcms/kcm_screenlocker/contents/ui/main.qml:50:17:
QML SpinBox: Binding loop detected for property "implicitWidth"
okt 10 10:11:43 openSUSE systemsettings5[10188]:
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/Page.qml:448: TypeError: Cannot
read property 'globalToolBar' of null
okt 10 10:11:43 openSUSE systemsettings5[10188]:
file:///usr/share/kpackage/kcms/kcm_kwin_virtualdesktops/contents/ui/main.qml:262:17:
QML SpinBox: Binding loop detected for property "implicitWidth"
okt 10 10:11:43 openSUSE systemsettings5[10188]:
file:///usr/share/kpackage/kcms/kcm_kwin_virtualdesktops/contents/ui/main.qml:262:17:
QML SpinBox: Binding loop detected for property "implicitWidth"
okt 10 10:11:43 openSUSE systemsettings5[10188]:
file:///usr/share/kpackage/kcms/kcm_kwin_virtualdesktops/contents/ui/main.qml:262:17:
QML SpinBox: Binding loop detected for property "implicitHeight"
okt 10 10:11:43 openSUSE systemsettings5[10188]:
file:///usr/share/kpackage/kcms/kcm_kwin_virtualdesktops/contents/ui/main.qml:155:13:
QML SpinBox: Binding loop detected for property "implicitWidth"
okt 10 10:11:43 openSUSE systemsettings5[10188]:
file:///usr/share/kpackage/kcms/kcm_kwin_virtualdesktops/contents/ui/main.qml:155:13:
QML SpinBox: Binding loop detected for property "implicitWidth"
okt 10 10:11:43 openSUSE systemsettings5[10188]:
file:///usr/share/kpackage/kcms/kcm_kwin_virtualdesktops/contents/ui/main.qml:155:13:
QML SpinBox: Binding loop detected for property "implicitHeight"
okt 10 10:11:43 openSUSE systemsettings5[10188]:
file

[frameworks-kactivities] [Bug 443537] Activity settings window has no labels in it

[Szőts Ákos]

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

--- Comment #1 from Szőts Ákos  ---
When I open the dialogue, I'm presented with the following QML errors:

okt 10 10:11:54 openSUSE systemsettings5[10188]: kf.kirigami:
Units.devicePixelRatio is deprecated (since 5.86 ): This returns 1 when using
Qt HiDPI scaling.
okt 10 10:11:54 openSUSE systemsettings5[10188]: kf.kirigami: Previous message
repeats 176 times.
okt 10 10:11:54 openSUSE systemsettings5[10188]:
QQmlEngine::setContextForObject(): Object already has a QQmlContext
okt 10 10:11:54 openSUSE systemsettings5[10188]:
file:///usr/share/kf5/kactivitymanagerd/workspace/settings/qml/activityDialog/GeneralTab.qml:54:
ReferenceError: i18nd is not defined
okt 10 10:11:54 openSUSE systemsettings5[10188]:
file:///usr/share/kf5/kactivitymanagerd/workspace/settings/qml/activityDialog/GeneralTab.qml:68:
ReferenceError: i18nd is not defined
okt 10 10:11:54 openSUSE systemsettings5[10188]:
file:///usr/share/kf5/kactivitymanagerd/workspace/settings/qml/activityDialog/GeneralTab.qml:73:
ReferenceError: i18nd is not defined
okt 10 10:11:54 openSUSE systemsettings5[10188]:
file:///usr/share/kf5/kactivitymanagerd/workspace/settings/qml/activityDialog/GeneralTab.qml:83:
ReferenceError: i18nd is not defined
okt 10 10:11:54 openSUSE systemsettings5[10188]:
file:///usr/share/kf5/kactivitymanagerd/workspace/settings/qml/activityDialog/GeneralTab.qml:82:
ReferenceError: i18nd is not defined
okt 10 10:11:54 openSUSE systemsettings5[10188]:
file:///usr/share/kf5/kactivitymanagerd/workspace/settings/qml/activityDialog/GeneralTab.qml:88:
ReferenceError: i18nd is not defined

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

[frameworks-kactivities] [Bug 443537] New: Activity settings window has no labels in it

[Szőts Ákos]

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

Bug ID: 443537
   Summary: Activity settings window has no labels in it
   Product: frameworks-kactivities
   Version: 5.86.0
  Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: ivan.cu...@kde.org
  Reporter: szots...@gmail.com
CC: plasma-b...@kde.org
  Target Milestone: ---

Created attachment 142293
  --> https://bugs.kde.org/attachment.cgi?id=142293=edit
Activity settings window without labels

SUMMARY

When you create an activity and press its settings button, the presented window
contains no labels at all.

(Alapértelmezés means "Default" in Hungarian)

Operating System: openSUSE Tumbleweed 20211005
KDE Plasma Version: 5.22.5
KDE Frameworks Version: 5.86.0
Qt Version: 5.15.2
Kernel Version: 5.14.6-1-default (64-bit)
Graphics Platform: X11

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

[drkonqi] [Bug 443517] Cannot submit a bug report with Dr. Konqi

[Szőts Ákos]

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

--- Comment #1 from Szőts Ákos  ---
The bug I wanted to report is Bug 443518.

Interestingly, version 5.22.5 doesn't exist here, in the drop-down for either
component.

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

[systemsettings] [Bug 443518] New: System settings crashes after removing virtual desktops

[Szőts Ákos]

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

Bug ID: 443518
   Summary: System settings crashes after removing virtual
desktops
   Product: systemsettings
   Version: 5.22.4
  Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: kcm_kwin_virtualdesktops
  Assignee: kwin-bugs-n...@kde.org
  Reporter: szots...@gmail.com
CC: plasma-b...@kde.org
  Target Milestone: ---

Application: systemsettings5 (5.22.5)

Qt Version: 5.15.2
Frameworks Version: 5.86.0
Operating System: Linux 5.14.6-1-default x86_64
Windowing System: X11
Drkonqi Version: 5.22.5
Distribution: "openSUSE Tumbleweed"

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

1. Open System settings and go to virtual desktops page
2. My setup is currently:
   1st row: one desktop
   2nd row: one desktop (interestingly, now both are named "2nd desktop")
3. Decrease row count below from two to one
4. Remove the bottom desktop with the trash icon
5. Click Apply -> crash

The reporter is unsure if this crash is reproducible.

-- Backtrace:
Application: Rendszerbeállítások (systemsettings5), signal: Segmentation fault
Content of s_kcrashErrorMessage: [Current thread is 1 (Thread 0x7fe543741980
(LWP 13489))]
[KCrash Handler]
#6  std::__atomic_base::load (__m=std::memory_order_relaxed,
this=) at /usr/include/c++/11/bits/atomic_base.h:479
#7  QAtomicOps::loadRelaxed (_q_value=...) at
/usr/include/qt5/QtCore/qatomic_cxx11.h:239
#8  QBasicAtomicInteger::loadRelaxed (this=) at
/usr/include/qt5/QtCore/qbasicatomic.h:107
#9  QtPrivate::RefCount::ref (this=) at
/usr/include/qt5/QtCore/qrefcount.h:55
#10 QString::QString (other=..., this=0x7ffd9eb91af0) at
/usr/include/qt5/QtCore/qstring.h:1094
#11 KWin::DesktopsModel::syncWithServer (this=0x55ee249e0290) at
/usr/src/debug/kwin5-5.22.5-1.2.x86_64/src/kcmkwin/kwindesktop/desktopsmodel.cpp:305
#12 0x7fe52d29f2bb in KWin::VirtualDesktops::save (this=0x55ee249df760) at
/usr/src/debug/kwin5-5.22.5-1.2.x86_64/src/kcmkwin/kwindesktop/virtualdesktops.cpp:80
#13 0x7fe548249862 in KCModuleQml::save (this=0x55ee24ad4990) at
/usr/src/debug/kcmutils-5.86.0-1.3.x86_64/src/kcmoduleqml.cpp:290
#14 0x7fe54825baa7 in KCModuleProxy::save (this=) at
/usr/src/debug/kcmutils-5.86.0-1.3.x86_64/src/kcmoduleproxy.cpp:259
#15 0x7fe54828da21 in ModuleView::moduleSave (this=0x55ee22f361b0,
module=) at
/usr/src/debug/systemsettings5-5.22.5-1.2.x86_64/core/ModuleView.cpp:383
#16 0x7fe54828dd5e in ModuleView::moduleSave (this=) at
/usr/src/debug/systemsettings5-5.22.5-1.2.x86_64/core/ModuleView.cpp:374
#17 0x7fe54828fe66 in ModuleView::qt_static_metacall (_o=,
_c=, _id=, _a=0x7ffd9eb91d70) at
/usr/src/debug/systemsettings5-5.22.5-1.2.x86_64/build/core/systemsettingsview_autogen/EWIEGA46WW/moc_ModuleView.cpp:133
#18 0x7fe546b9f048 in doActivate (sender=0x55ee22f6a8a0,
signal_index=9, argv=0x7ffd9eb91d70) at kernel/qobject.cpp:3898
#19 0x7fe546b984df in QMetaObject::activate
(sender=sender@entry=0x55ee22f6a8a0, m=m@entry=0x7fe547d354e0
,
local_signal_index=local_signal_index@entry=2, argv=argv@entry=0x7ffd9eb91d70)
at kernel/qobject.cpp:3946
#20 0x7fe54790a9f2 in QAbstractButton::clicked
(this=this@entry=0x55ee22f6a8a0, _t1=) at
.moc/moc_qabstractbutton.cpp:308
#21 0x7fe54790ac6a in QAbstractButtonPrivate::emitClicked
(this=0x55ee22d33800) at widgets/qabstractbutton.cpp:415
#22 0x7fe54790c830 in QAbstractButtonPrivate::click (this=0x55ee22d33800)
at widgets/qabstractbutton.cpp:408
#23 0x7fe54790ca53 in QAbstractButton::mouseReleaseEvent
(this=0x55ee22f6a8a0, e=0x7ffd9eb92310) at widgets/qabstractbutton.cpp:1044
#24 0x7fe54785976e in QWidget::event (this=0x55ee22f6a8a0,
event=0x7ffd9eb92310) at kernel/qwidget.cpp:9020
#25 0x7fe547817a7f in QApplicationPrivate::notify_helper
(this=this@entry=0x55ee22c53cf0, receiver=receiver@entry=0x55ee22f6a8a0,
e=e@entry=0x7ffd9eb92310) at kernel/qapplication.cpp:3632
#26 0x7fe54781f584 in QApplication::notify (this=0x7ffd9eb92030,
receiver=0x55ee22f6a8a0, e=0x7ffd9eb92310) at kernel/qapplication.cpp:3076
#27 0x7fe546b689ca in QCoreApplication::notifyInternal2
(receiver=0x55ee22f6a8a0, event=0x7ffd9eb92310) at
kernel/qcoreapplication.cpp:1064
#28 0x7fe54781e093 in QApplicationPrivate::sendMouseEvent
(receiver=receiver@entry=0x55ee22f6a8a0, event=event@entry=0x7ffd9eb92310,
alienWidget=alienWidget@entry=0x55ee22f6a8a0, nativeWidget=0x55ee22d783a0,
buttonDown=, lastMouseReceiver=..., spontaneous=true,
onlyDispatchEnterLeave=false) at kernel/qapplication.cpp:2614
#29 0x7fe54787283c in QWidgetWindow::handleMouseEvent (this=0x55ee231ad990,
event=0x7ffd9eb925e0) at kernel/qwidgetwindow.cpp:683
#30 0x7fe547875c55 in QWidgetWindow::event (this=0x55ee231ad990,
event=0x7ffd9eb925e0) at kernel/qwidgetwindow.cpp:300
#31 

[drkonqi] [Bug 443517] New: Cannot submit a bug report with Dr. Konqi

[Szőts Ákos]

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

Bug ID: 443517
   Summary: Cannot submit a bug report with Dr. Konqi
   Product: drkonqi
   Version: 5.22.4
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: szots...@gmail.com
  Target Milestone: ---

SUMMARY

Drkonqi Version: 5.22.5

STEPS TO REPRODUCE
1. Make an application crash and DrKonqi appear
2. Fill out the form
3. Send the form

OBSERVED RESULT

(rough translation:)
"There was an error during submitting the bug report:
/https://bugs.kde.org/rest/bug?token=215733-7OqnIldkI./;

On "Retry...":
/Did not receive a token./

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

[korganizer] [Bug 440147] KOrganizer doesn't show imported .ical calendar (but uploads it to the server successfully)

[Szőts Ákos]

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

--- Comment #3 from Szőts Ákos  ---
I think I found out the part which causes the problem (and possibly this will
qualify this bug report as a duplicate of the aforementioned one).

ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=;X-NUM-GUESTS=0:mailto:

If "" is exactly the same as my e-mail address then the event
is not shown. "" has no significance in this matter.

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

[korganizer] [Bug 440147] KOrganizer doesn't show imported .ical calendar (but uploads it to the server successfully)

[Szőts Ákos]

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

--- Comment #2 from Szőts Ákos  ---
Sorry, I was indeed vague on my setup. So I received the .ical file from
someone who created that on their Google Calendar. I have a CalDAV server on my
own machine to which KOrganizer is connected. I opened the received .ical file
in KMail for processing by KOrganizer. The local CalDAV server successfully
stored the event by KOrganizer (which I can verify in an other calendar
application).

Yes, the calendar is enabled. I tried to turn it on/off multiple times now and
it correctly shows/hides all the events for that calendar with the exception of
this one.

Akonadiconsole completely correctly shows the event (I could find it by the
local UUID). Its payload tab is perfectly showing the details.

The event doesn't have a VTODO section, only a VEVENT.

I'm now anonymising the .ics file and I'll try to reproduce the bug with it. If
it's successful, I'll send the file to your e-mail address.

Ps.: I tried to import the same file multiple times (because it said it was
successful - see Bug 440145) and even in case of multiple imports the entry
wasn't shown (though the conflicting UUID must have had some influence on it).

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

[korganizer] [Bug 440147] New: KOrganizer doesn't show imported .ical calendar (but uploads it to the server successfully)

[Szőts Ákos]

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

Bug ID: 440147
   Summary: KOrganizer doesn't show imported .ical calendar (but
uploads it to the server successfully)
   Product: korganizer
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: import/export
  Assignee: kdepim-b...@kde.org
  Reporter: szots...@gmail.com
  Target Milestone: ---

SUMMARY

I have an .ical file which is sent from Google calendar. I tried to open the
file itself in KMail, open with KOrganizer, choose "Merge with existing
calendar", and choose the calendar.

What I saw in the logs, the event was successfully imported.

In Akonadi logs I saw:

org.kde.pim.davresource: Received notification for added item. Local id = 
420333 . Remote id =  "" . Collection remote id = 
"https://127.0.0.1:5232/XXX/XXX/;
org.kde.pim.akonadicore: asked to convert a
"application/x-vnd.akonadi.calendar.event" item to format KContacts::Addressee
org.kde.pim.davresource: Item  420333  will be put to 
"https://127.0.0.1:5232/XXX/XXX/1626949401.R950.ics

org.kde.pim.akonadi_indexer_agent: Processing collection:  36
org.kde.pim.akonadi_indexer_agent: 
org.kde.pim.akonadi_indexer_agent: collectionIndexingJob::indexItems(const
QList ) count  1
org.kde.pim.akonadi_indexer_agent: 
CollectionIndexingJob::slotPendingItemsReceived  1
org.kde.pim.akonadi_indexer_agent:  void
CollectionIndexingJob::slotPendingItemsReceived(const Akonadi::Item::List
) 420333
org.kde.pim.akonadi_indexer_agent:  CollectionIndexingJob::slotPendingIndexed 
org.kde.pim.akonadi_indexer_agent: Indexed  1  items in (ms):  3
org.kde.pim.akonadi_indexer_agent: Indexing complete. Total time:  4
org.kde.pim.akonadi_indexer_agent: Processing done
org.kde.pim.akonadi_indexer_agent: Xapian Committed
org.kde.pim.akonadi_indexer_agent: Xapian Committed


In the server logs I saw:

[2021-07-22 12:23:21 +0200] [30108/Thread-4] [INFO] GET response status for
'/XXX/XXX/1626949401.R950.ics' in 0.003 seconds: 200 OK


A different calendar application which connects to the same server successfully
shows the event. KOrganizer does not, even after I restarted both itself and
akonadi.

Let me know if you need any additional debug logs.


SOFTWARE/OS VERSIONS

korganizer: 21.04.3

Operating System: openSUSE Tumbleweed 20210716
KDE Plasma Version: 5.22.3
KDE Frameworks Version: 5.84.0
Qt Version: 5.15.2
Kernel Version: 5.12.3-1-default (64-bit)
Graphics Platform: X11

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

[Akonadi] [Bug 440145] New: KOrganizer reports successful .ical entry import in case of a failed import because of 409 Conflict

[Szőts Ákos]

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

Bug ID: 440145
   Summary: KOrganizer reports successful .ical entry import in
case of a failed import because of 409 Conflict
   Product: Akonadi
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: DAV Resource
  Assignee: kdepim-b...@kde.org
  Reporter: szots...@gmail.com
  Target Milestone: ---

SUMMARY

I have an .ical file which I wanted to import into one of my calendars. The
import failed (each time I tried) but KOrganizer shown in the status bar that
the import was in fact successful. Of course, the imported entry is not visible
in the calendar.

Akonadi logs after clicking the OK button for importing the .ical file for the
2nd+ time:

org.kde.pim.akonadiserver: Subscriber "CollectionDialogMonitor -
94412509232048" disconnected
org.kde.pim.akonadicore:  PLUGIN : identifier
"application/octet-stream@QByteArray"
org.kde.pim.akonadicore: registering Desktop file
"/usr/share/akonadi/plugins/serializer//akonadi_serializer_addressee.desktop"
for ("text/vcard", "text/directory") @ ("legacy", "default",
"KContacts::Addressee")
org.kde.pim.akonadicore: registering Desktop file
"/usr/share/akonadi/plugins/serializer//akonadi_serializer_contactgroup.desktop"
for ("application/x-vnd.kde.contactgroup") @ ("legacy", "default",
"KContacts::ContactGroup")
org.kde.pim.akonadicore: registering Desktop file
"/usr/share/akonadi/plugins/serializer//akonadi_serializer_kalarm.desktop" for
("application/x-vnd.kde.alarm", "application/x-vnd.kde.alarm.active",
"application/x-vnd.kde.alarm.archived", "application/x-vnd.kde.alarm.template")
@ ("default", "KAlarmCal::KAEvent")
org.kde.pim.akonadicore: registering Desktop file
"/usr/share/akonadi/plugins/serializer//akonadi_serializer_kcalcore.desktop"
for ("text/calendar", "application/x-vnd.akonadi.note",
"application/x-vnd.kde.notes") @ ("default", "KCalendarCore::Incidence*")
org.kde.pim.akonadicore: registering Desktop file
"/usr/share/akonadi/plugins/serializer//akonadi_serializer_mail.desktop" for
("message/rfc822", "message/news", "text/x-vnd.akonadi.note") @ ("legacy",
"default", "KMime::Message*")
org.kde.pim.akonadicore: ItemSerializerPluginLoader:  found 32 plugins.
org.kde.pim.akonadicore:  PLUGIN : identifier
"application/x-vnd.kde.notes@KCalendarCore::Incidence*"
org.kde.pim.akonadicore:  PLUGIN : identifier
"application/x-vnd.akonadi.note@default"
org.kde.pim.akonadicore:  PLUGIN : identifier "message/rfc822@default"
org.kde.pim.akonadicore:  PLUGIN : identifier "text/directory@legacy"
org.kde.pim.akonadicore:  PLUGIN : identifier
"application/x-vnd.kde.contactgroup@default"
org.kde.pim.akonadicore:  PLUGIN : identifier
"application/x-vnd.kde.notes@default"
org.kde.pim.akonadicore:  PLUGIN : identifier "message/rfc822@KMime::Message*"
org.kde.pim.akonadicore:  PLUGIN : identifier
"application/x-vnd.kde.alarm.template@default"
org.kde.pim.akonadicore:  PLUGIN : identifier
"text/x-vnd.akonadi.note@KMime::Message*"
org.kde.pim.akonadicore:  PLUGIN : identifier "text/vcard@legacy"
org.kde.pim.akonadicore:  PLUGIN : identifier
"application/x-vnd.kde.alarm.archived@default"
org.kde.pim.akonadicore:  PLUGIN : identifier
"application/x-vnd.akonadi.note@KCalendarCore::Incidence*"
org.kde.pim.akonadicore:  PLUGIN : identifier "text/calendar@default"
org.kde.pim.akonadicore:  PLUGIN : identifier
"application/x-vnd.kde.alarm@default"
org.kde.pim.akonadicore:  PLUGIN : identifier "message/news@default"
org.kde.pim.akonadicore:  PLUGIN : identifier
"text/calendar@KCalendarCore::Incidence*"
org.kde.pim.akonadicore:  PLUGIN : identifier
"text/directory@KContacts::Addressee"
org.kde.pim.akonadicore:  PLUGIN : identifier
"application/x-vnd.kde.alarm.active@KAlarmCal::KAEvent"
org.kde.pim.akonadicore:  PLUGIN : identifier "text/vcard@KContacts::Addressee"
org.kde.pim.akonadicore:  PLUGIN : identifier "message/rfc822@legacy"
org.kde.pim.akonadicore:  PLUGIN : identifier "text/x-vnd.akonadi.note@default"
org.kde.pim.akonadicore:  PLUGIN : identifier
"application/x-vnd.kde.alarm.template@KAlarmCal::KAEvent"
org.kde.pim.akonadicore:  PLUGIN : identifier "text/vcard@default"
org.kde.pim.akonadicore:  PLUGIN : identifier "message/news@legacy"
org.kde.pim.akonadicore:  PLUGIN : identifier "message/news@KMime::Message*"
org.kde.pim.akonadicore:  PLUGIN : identifier
"application/x-vnd.kde.alarm@KAlarmCal::KAEvent"
org.kde.pim.akonadicore:  PLUGIN : identifier
"application/x-vnd.kde.alarm.archived@KAlarmCal::KAEvent"
org.kde.pim.akonadicore:  PLUGIN : identifier
"application/x-vnd.kde.contactgroup@legacy"
org.kde.pim.akonadicore:  PLUGIN : identifier "text/directory@default"
org.kde.pim.akonadicore:  PLUGIN : identifier
"application/x-vnd.kde.contactgroup@KContacts::ContactGroup"
org.kde.pim.akonadicore:  PLUGIN : identifier

[kdeconnect] [Bug 435016] Crash when media controls is in landscape mode

[Szőts Ákos]

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

Szőts Ákos  changed:

   What|Removed |Added

 CC||szots...@gmail.com

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

[Powerdevil] [Bug 433408] [systemd] System powers off when sleep button is pressed instead of going to sleep

[Szőts Ákos]

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

--- Comment #6 from Szőts Ákos  ---
If you could tell me commands to execute, log locations, or any other clues how
to help debugging this, I'd be glad to.

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

[kwin] [Bug 414805] Crash in QScreen::handle() after QXcbIntegration::createPlatformOpenGLContext()

[Szőts Ákos]

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

--- Comment #23 from Szőts Ákos  ---
I usually get this kind of crash when I regularly switch between the two inputs
(DisplayPort and HDMI) of my monitor. I'll continue testing with this pattern
in a few days, therefore anyone who has a better reproducible or can jump in
sooner, feel free to do :).

On a related note, may I ask what will be the fate of the other kwin Valgrind
errors from Comment 20? Should I open separate bug tickets for them? As kwin
crashes under Valgrind quite often it'd also ease further debugging if we
didn't need to filter out duplicate reportings.

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

[kwin] [Bug 414805] Crash in QScreen::handle() after QXcbIntegration::createPlatformOpenGLContext()

[Szőts Ákos]

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

--- Comment #21 from Szőts Ákos  ---
Here are the reported definite leaks:

==23403== 128 (24 direct, 104 indirect) bytes in 1 blocks are definitely lost
in loss record 715 of 1,029
==23403==at 0x483EDEF: operator new(unsigned long) (in
/usr/lib64/valgrind/vgpreload_memcheck-amd64-linux.so)
==23403==by 0x49BDDD4:
KWin::Workspace::registerEventFilter(KWin::X11EventFilter*) (events.cpp:171)
==23403==by 0x1349E201:
KWin::X11StandalonePlatform::createScreenEdge(KWin::ScreenEdges*)
(screenedges_filter.cpp:20)
==23403==by 0x4A332F4: KWin::ScreenEdges::createEdge(KWin::ElectricBorder,
int, int, int, int, bool) (screenedge.cpp:1106)
==23403==by 0x4A342A2:
KWin::ScreenEdges::createVerticalEdge(KWin::ElectricBorder, QRect const&, QRect
const&) (screenedge.cpp:1061)
==23403==by 0x4A34792: KWin::ScreenEdges::recreateEdges()
(screenedge.cpp:1001)
==23403==by 0x4A8DE54: KWin::Workspace::init() (workspace.cpp:218)
==23403==by 0x4A8CE82: KWin::Workspace::Workspace() (workspace.cpp:204)
==23403==by 0x49FE22F: KWin::Application::createWorkspace() (main.cpp:272)
==23403==by 0x111D08: KWin::ApplicationX11::continueStartupWithScreens()
(main_x11.cpp:272)
==23403==by 0x5F26945: call (qobjectdefs_impl.h:398)
==23403==by 0x5F26945: void doActivate(QObject*, int, void**)
(qobject.cpp:3886)
==23403==by 0x134AE5D8: void
KWin::X11StandalonePlatform::doUpdateOutputs()
(x11_platform.cpp:603)


==23403== 128 (24 direct, 104 indirect) bytes in 1 blocks are definitely lost
in loss record 720 of 1,029
==23403==at 0x483EDEF: operator new(unsigned long) (in
/usr/lib64/valgrind/vgpreload_memcheck-amd64-linux.so)
==23403==by 0x49BDDD4:
KWin::Workspace::registerEventFilter(KWin::X11EventFilter*) (events.cpp:171)
==23403==by 0x4AC1C71: KWin::X11EventFilter::X11EventFilter(int, int, int)
(x11eventfilter.cpp:25)
==23403==by 0x134A41FF: KWin::X11StandalonePlatform::init()
(x11_platform.cpp:66)
==23403==by 0x1127E6:
QtPrivate::QFunctorSlotObject, void>::impl(int, QtPrivate::QSlotObjectBase*, QObject*,
void**, bool*) (main_x11.cpp:259)
==23403==by 0x5F26945: call (qobjectdefs_impl.h:398)
==23403==by 0x5F26945: void doActivate(QObject*, int, void**)
(qobject.cpp:3886)
==23403==by 0x4BFF4C2: KSelectionOwner::Private::claimSucceeded()
(kselectionowner.cpp:188)
==23403==by 0x4C047A0: UnknownInlinedFun (kselectionowner.cpp:222)
==23403==by 0x4C047A0: KSelectionOwner::filterEvent(void*)
(kselectionowner.cpp:406)
==23403==by 0x5EED876:
QAbstractEventDispatcher::filterNativeEvent(QByteArray const&, void*, long*)
(qabstracteventdispatcher.cpp:495)
==23403==by 0xC3540E0: QXcbConnection::handleXcbEvent(xcb_generic_event_t*)
(qxcbconnection.cpp:536)
==23403==by 0xC3555F5:
QXcbConnection::processXcbEvents(QFlags)
(qxcbconnection.cpp:1014)
==23403==by 0xC37835B:
QXcbUnixEventDispatcher::processEvents(QFlags)
(qxcbeventdispatcher.cpp:61)


==24377== 8 bytes in 1 blocks are definitely lost in loss record 758 of 21,144
==24377==at 0x483E77F: malloc (in
/usr/lib64/valgrind/vgpreload_memcheck-amd64-linux.so)
==24377==by 0xEEF3798: glXChooseFBConfig (in
/usr/lib64/libGLX_nvidia.so.460.67)
==24377==by 0x92A3FE6: glXChooseFBConfig (libglx.c:1491)
==24377==by 0xE5FD8B4: QGLXContext::init(QXcbScreen*,
QPlatformOpenGLContext*, QVariant const&) (qglxintegration.cpp:484)
==24377==by 0xE5FC1D6:
QXcbGlxIntegration::createPlatformOpenGLContext(QOpenGLContext*) const
(qxcbglxintegration.cpp:191)
==24377==by 0x560889C: QOpenGLContext::create() (qopenglcontext.cpp:612)
==24377==by 0x128AFA9D: UnknownInlinedFun (glxbackend.cpp:380)
==24377==by 0x128AFA9D: KWin::GlxBackend::init() [clone .part.0]
(glxbackend.cpp:189)
==24377==by 0x1268AD88: KWin::SceneOpenGL::createScene(QObject*)
(scene_opengl.cpp:449)
==24377==by 0x12699828: KWin::OpenGLFactory::create(QObject*) const
(scene_opengl.cpp:2725)
==24377==by 0x4985E2E: KWin::Compositor::setupStart() [clone .part.0]
(composite.cpp:238)
==24377==by 0x4988B59: KWin::X11Compositor::start() (composite.cpp:815)
==24377==by 0x5F1C350: QObject::event(QEvent*) (qobject.cpp:1314)


==24377== 16 bytes in 2 blocks are definitely lost in loss record 1,669 of
21,144
==24377==at 0x483F50F: operator new[](unsigned long) (in
/usr/lib64/valgrind/vgpreload_memcheck-amd64-linux.so)
==24377==by 0x77489FE: QLinkedStringHash
>::linkAndReserve(QLinkedStringHash > const&,
int) (qlinkedstringhash_p.h:82)
==24377==by 0x77440B1: copy (qqmlpropertycache.cpp:262)
==24377==by 0x77440B1: QQmlPropertyCache::copyAndReserve(int, int, int,
int) (qqmlpropertycache.cpp:278)
==24377==by 0x76F05E0:
QQmlPropertyCacheCreator::createMetaObject(int,
QV4::CompiledData::Object const*, QQmlRefPointer const&)
(qqmlpropertycachecreator_p.h:351)
==24377==by 0x76F2156:
QQmlPropertyCacheCreator::buildMetaObjectRecursively(int

[kwin] [Bug 414805] Crash in QScreen::handle() after QXcbIntegration::createPlatformOpenGLContext()

[Szőts Ákos]

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

--- Comment #20 from Szőts Ákos  ---
During the day kwin was running in Valgrind and it crashed seven times and
produced 19 different Valgrind .log files. I tried my best to de-duplicate the
error and leak messages there (there were many repeating).

Here come the errors from Valgrind:

==18204== Thread 7 vsync event moni:
==18204== Conditional jump or move depends on uninitialised value(s)
==18204==at 0xEEF521D: glXWaitVideoSyncSGI (in
/usr/lib64/libGLX_nvidia.so.460.67)
==18204==by 0x128B07A2: KWin::SGIVideoSyncVsyncMonitorHelper::poll()
(sgivideosyncvsyncmonitor.cpp:122)
==18204==by 0x5F1C350: QObject::event(QEvent*) (qobject.cpp:1314)
==18204==by 0x4F194FE: QApplicationPrivate::notify_helper(QObject*,
QEvent*) (qapplication.cpp:3632)
==18204==by 0x5EF0329: QCoreApplication::notifyInternal2(QObject*, QEvent*)
(qcoreapplication.cpp:1063)
==18204==by 0x5EF2D60: QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) (qcoreapplication.cpp:1817)
==18204==by 0x5F44D89:
QEventDispatcherUNIX::processEvents(QFlags)
(qeventdispatcher_unix.cpp:468)
==18204==by 0x5EEECEA:
QEventLoop::exec(QFlags) (qeventloop.cpp:232)
==18204==by 0x5D0DDAD: QThread::exec() (qthread.cpp:547)
==18204==by 0x5D0EEF0: QThreadPrivate::start(void*) (qthread_unix.cpp:329)
==18204==by 0x6E67298: start_thread (pthread_create.c:473)
==18204==by 0x64FB3B2: clone (clone.S:95)
==18204==  Uninitialised value was created by a stack allocation
==18204==at 0x5F17F50: QMetaCallEvent::placeMetaCall(QObject*)
(qobject.cpp:613)


==23403== Invalid read of size 16
==23403==at 0x122B1B01: ??? (in /memfd:sljit (deleted))
==23403==by 0xD0C4EB7: ???
==23403==  Address 0xd0c4ede is 62 bytes inside a block of size 76 alloc'd
==23403==at 0x483E77F: malloc (in
/usr/lib64/valgrind/vgpreload_memcheck-amd64-linux.so)
==23403==by 0x5D1A490: QArrayData::allocate(unsigned long, unsigned long,
unsigned long, QFlags) (qarraydata.cpp:218)
==23403==by 0x5D933F9: allocate (qarraydata.h:224)
==23403==by 0x5D933F9: QString::fromLatin1_helper(char const*, int)
(qstring.cpp:5459)
==23403==by 0x671CE5D:
KWin::GLPlatform::detect(KWin::OpenGLPlatformInterface) (qstring.h:701)
==23403==by 0x134B5AE1: KWin::GlxBackend::init() [clone .part.0]
(glxbackend.cpp:196)
==23403==by 0x1228AD88: KWin::SceneOpenGL::createScene(QObject*)
(scene_opengl.cpp:449)
==23403==by 0x12299828: KWin::OpenGLFactory::create(QObject*) const
(scene_opengl.cpp:2725)
==23403==by 0x4985E2E: KWin::Compositor::setupStart() [clone .part.0]
(composite.cpp:238)
==23403==by 0x4988B59: KWin::X11Compositor::start() (composite.cpp:815)
==23403==by 0x5F1C350: QObject::event(QEvent*) (qobject.cpp:1314)
==23403==by 0x4F194FE: QApplicationPrivate::notify_helper(QObject*,
QEvent*) (qapplication.cpp:3632)
==23403==by 0x5EF0329: QCoreApplication::notifyInternal2(QObject*, QEvent*)
(qcoreapplication.cpp:1063)


==23403== Syscall param writev(vector[...]) points to uninitialised byte(s)
==23403==at 0x64F21CD: __writev (writev.c:26)
==23403==by 0x64F21CD: writev (writev.c:24)
==23403==by 0x5B70AD2: UnknownInlinedFun (xcb_conn.c:277)
==23403==by 0x5B70AD2: _xcb_conn_wait.part.0 (xcb_conn.c:523)
==23403==by 0x5B70B8F: UnknownInlinedFun (xcb_out.c:463)
==23403==by 0x5B70B8F: _xcb_out_send (xcb_out.c:464)
==23403==by 0x5B70DE6: UnknownInlinedFun (xcb_out.c:488)
==23403==by 0x5B70DE6: _xcb_out_flush_to (xcb_out.c:477)
==23403==by 0x5B7242A: xcb_request_check (xcb_in.c:743)
==23403==by 0x112601:
QtPrivate::QFunctorSlotObject, void>::impl(int, QtPrivate::QSlotObjectBase*, QObject*,
void**, bool*) (main_x11.cpp:243)
==23403==by 0x5F26945: call (qobjectdefs_impl.h:398)
==23403==by 0x5F26945: void doActivate(QObject*, int, void**)
(qobject.cpp:3886)
==23403==by 0x4BFF4C2: KSelectionOwner::Private::claimSucceeded()
(kselectionowner.cpp:188)
==23403==by 0x4C047A0: UnknownInlinedFun (kselectionowner.cpp:222)
==23403==by 0x4C047A0: KSelectionOwner::filterEvent(void*)
(kselectionowner.cpp:406)
==23403==by 0x5EED876:
QAbstractEventDispatcher::filterNativeEvent(QByteArray const&, void*, long*)
(qabstracteventdispatcher.cpp:495)
==23403==by 0xC3540E0: QXcbConnection::handleXcbEvent(xcb_generic_event_t*)
(qxcbconnection.cpp:536)
==23403==by 0xC3555F5:
QXcbConnection::processXcbEvents(QFlags)
(qxcbconnection.cpp:1014)
==23403==  Address 0xa1bfd7a is 4,538 bytes inside a block of size 21,168
alloc'd
==23403==at 0x4840B65: calloc (in
/usr/lib64/valgrind/vgpreload_memcheck-amd64-linux.so)
==23403==by 0x5B73050: xcb_connect_to_fd (xcb_conn.c:346)
==23403==by 0x5B73C46: xcb_connect_to_display_with_auth_info
(xcb_util.c:534)
==23403==by 0x7BA40E1: _XConnectXCB (xcb_disp.c:78)
==23403==by 0x7B94124: XOpenDisplay (OpenDis.c:129)
==23403==by 0xC379926: QXcbBasicConnection::QXcbBasicCon

[kwin] [Bug 414805] Crash in QScreen::handle() after QXcbIntegration::createPlatformOpenGLContext()

[Szőts Ákos]

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

--- Comment #19 from Szőts Ákos  ---
I attached Valgrind to running kwin_x11. It seems kwin crashes many more times
than without it. It crashes on Alt+Tabs, closing windows, and minimising
windows after returning from sleep (hopefully this is the reproducible case of
the current ticket).

I observed the following errors:

==18204== Syscall param writev(vector[...]) points to uninitialised byte(s)
==18204==at 0x64F21CD: __writev (writev.c:26)
==18204==by 0x64F21CD: writev (writev.c:24)
==18204==by 0x5B70AD2: UnknownInlinedFun (xcb_conn.c:277)
==18204==by 0x5B70AD2: _xcb_conn_wait.part.0 (xcb_conn.c:523)
==18204==by 0x5B70B8F: UnknownInlinedFun (xcb_out.c:463)
==18204==by 0x5B70B8F: _xcb_out_send (xcb_out.c:464)
==18204==by 0x5B70DE6: UnknownInlinedFun (xcb_out.c:488)
==18204==by 0x5B70DE6: _xcb_out_flush_to (xcb_out.c:477)
==18204==by 0x5B7242A: xcb_request_check (xcb_in.c:743)
==18204==by 0x112601:
QtPrivate::QFunctorSlotObject, void>::impl(int, QtPrivate::QSlotObjectBase*, QObject*,
void**, bool*) (main_x11.cpp:243)
==18204==by 0x5F26945: call (qobjectdefs_impl.h:398)
==18204==by 0x5F26945: void doActivate(QObject*, int, void**)
(qobject.cpp:3886)
==18204==by 0x4BFF4C2: KSelectionOwner::Private::claimSucceeded()
(kselectionowner.cpp:188)
==18204==by 0x4C047A0: UnknownInlinedFun (kselectionowner.cpp:222)
==18204==by 0x4C047A0: KSelectionOwner::filterEvent(void*)
(kselectionowner.cpp:406)
==18204==by 0x5EED876:
QAbstractEventDispatcher::filterNativeEvent(QByteArray const&, void*, long*)
(qabstracteventdispatcher.cpp:495)
==18204==by 0xC3540E0: QXcbConnection::handleXcbEvent(xcb_generic_event_t*)
(qxcbconnection.cpp:536)
==18204==by 0xC3555F5:
QXcbConnection::processXcbEvents(QFlags)
(qxcbconnection.cpp:1014)
==18204==  Address 0xa1bfd7a is 4,538 bytes inside a block of size 21,168
alloc'd
==18204==at 0x4840B65: calloc (in
/usr/lib64/valgrind/vgpreload_memcheck-amd64-linux.so)
==18204==by 0x5B73050: xcb_connect_to_fd (xcb_conn.c:346)
==18204==by 0x5B73C46: xcb_connect_to_display_with_auth_info
(xcb_util.c:534)
==18204==by 0x7BA40E1: _XConnectXCB (xcb_disp.c:78)
==18204==by 0x7B94124: XOpenDisplay (OpenDis.c:129)
==18204==by 0xC379926: QXcbBasicConnection::QXcbBasicConnection(char
const*) (qxcbconnection_basic.cpp:114)
==18204==by 0xC355B21: QXcbConnection::QXcbConnection(QXcbNativeInterface*,
bool, unsigned int, char const*) (qxcbconnection.cpp:91)
==18204==by 0xC358992: QXcbIntegration::QXcbIntegration(QStringList const&,
int&, char**) (qxcbintegration.cpp:197)
==18204==by 0x485E45E: create (qxcbmain.cpp:56)
==18204==by 0x485E45E: QXcbIntegrationPlugin::create(QString const&,
QStringList const&, int&, char**) (qxcbmain.cpp:53)
==18204==by 0x55B908B: init_platform (qguiapplication.cpp:1223)
==18204==by 0x55B908B: QGuiApplicationPrivate::createPlatformIntegration()
(qguiapplication.cpp:1481)
==18204==by 0x55BA48F: QGuiApplicationPrivate::createEventDispatcher()
(qguiapplication.cpp:1498)
==18204==by 0x5EF6DB5: QCoreApplicationPrivate::init()
(qcoreapplication.cpp:834)
==18204==  Uninitialised value was created by a stack allocation
==18204==at 0x4BFF450: KSelectionOwner::Private::claimSucceeded()
(kselectionowner.cpp:170)


==18204== Invalid read of size 16
==18204==at 0x12A6CB01: ??? (in /memfd:sljit (deleted))
==18204==by 0xD0A5537: ???
==18204==  Address 0xd0a555e is 62 bytes inside a block of size 76 alloc'd
==18204==at 0x483E77F: malloc (in
/usr/lib64/valgrind/vgpreload_memcheck-amd64-linux.so)
==18204==by 0x5D1A490: QArrayData::allocate(unsigned long, unsigned long,
unsigned long, QFlags) (qarraydata.cpp:218)
==18204==by 0x5D933F9: allocate (qarraydata.h:224)
==18204==by 0x5D933F9: QString::fromLatin1_helper(char const*, int)
(qstring.cpp:5459)
==18204==by 0x671CE5D:
KWin::GLPlatform::detect(KWin::OpenGLPlatformInterface) (qstring.h:701)
==18204==by 0x128B5AE1: KWin::GlxBackend::init() [clone .part.0]
(glxbackend.cpp:196)
==18204==by 0x13181D88: KWin::SceneOpenGL::createScene(QObject*)
(scene_opengl.cpp:449)
==18204==by 0x13190828: KWin::OpenGLFactory::create(QObject*) const
(scene_opengl.cpp:2725)
==18204==by 0x4985E2E: KWin::Compositor::setupStart() [clone .part.0]
(composite.cpp:238)
==18204==by 0x4988B59: KWin::X11Compositor::start() (composite.cpp:815)
==18204==by 0x5F1C350: QObject::event(QEvent*) (qobject.cpp:1314)
==18204==by 0x4F194FE: QApplicationPrivate::notify_helper(QObject*,
QEvent*) (qapplication.cpp:3632)
==18204==by 0x5EF0329: QCoreApplication::notifyInternal2(QObject*, QEvent*)
(qcoreapplication.cpp:1063)


==18204== Invalid read of size 16
==18204==at 0x12A6C6D8: ??? (in /memfd:sljit (deleted))
==18204==by 0xD0A5537: ???
==18204==  Address 0xd0a555e is 62 bytes inside a block of size 76 alloc'd
==18204==at 0x483

[krunner] [Bug 416145] Krunner doesn't immediately intercept keystrokes, leading the user to accidentally type text into whatever app is open

[Szőts Ákos]

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

Szőts Ákos  changed:

   What|Removed |Added

 CC||szots...@gmail.com

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

[systemsettings] [Bug 433299] [systemd] Applications meant to autostart do not start after switching to systemd

[Szőts Ákos]

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

Szőts Ákos  changed:

   What|Removed |Added

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

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

[systemsettings] [Bug 433304] Adding a new automatically starting application generates deprecated/invalid .desktop file

[Szőts Ákos]

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

--- Comment #3 from Szőts Ákos  ---
Currently, it's only cosmetic (apart from the scary-looking red and yellow
lines in the journal).

In the future, though, I don't know how these programs will behave and what
will be their reactions.

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

[Powerdevil] [Bug 433408] [systemd] System powers off when sleep button is pressed instead of going to sleep

[Szőts Ákos]

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

Szőts Ákos  changed:

   What|Removed |Added

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

--- Comment #3 from Szőts Ákos  ---
It seems it is running:

$ systemctl --user  status plasma-powerdevil.service
● plasma-powerdevil.service - Powerdevil
 Loaded: loaded (/usr/lib/systemd/user/plasma-powerdevil.service; static)
 Active: active (running) since Sun 2021-02-21 22:30:45 CET; 8h ago
   Main PID: 1702 (org_kde_powerde)
 CGroup:
/user.slice/user-1000.slice/user@1000.service/background.slice/plasma-powerdevil.service
 └─1702 /usr/lib64/libexec/org_kde_powerdevil

febr 21 22:30:45 openSUSE systemd[1491]: Starting Powerdevil...
febr 21 22:30:45 openSUSE systemd[1491]: Started Powerdevil.


$ ps aux| grep power
root88  0.0  0.0  0 0 ?Ifebr21   0:00
[kworker/12:0-events_freezable_power_]
root   127  0.0  0.0  0 0 ?Ifebr21   0:00
[kworker/12:1-events_freezable_power_]
root  1095  0.0  0.0  0 0 ?Ifebr21   0:00
[kworker/0:2-events_power_efficient]
aki   1702  0.0  0.2 400584 43340 ?Ssl  febr21   0:00
/usr/lib64/libexec/org_kde_powerdevil
root  1714  0.0  0.0 246976 10100 ?Ssl  febr21   0:00
/usr/libexec/upower/upowerd
root 10472  0.0  0.0  0 0 ?I07:00   0:00
[kworker/0:0-events_power_efficient]


In the logs I cannot find anything related:
journalctl -u plasma-powerdevil.service
-- Logs begin at Fri 2020-06-12 14:50:46 CEST, end at Mon 2021-02-22 07:16:52
CET. --
-- No entries --


It seems that powerdevil logs (journalctl | grep powerdevil) are the same with
and without systemd.

Without systemd:
febr 21 22:27:36 openSUSE dbus-daemon[710]: [system] Activating service
name='org.kde.powerdevil.discretegpuhelper' requested by ':1.28' (uid=1000
pid=1757 comm="/usr/lib64/libexec/org_kde_powerdevil ") (using servicehelper)
febr 21 22:27:36 openSUSE dbus-daemon[710]: [system] Successfully activated
service 'org.kde.powerdevil.discretegpuhelper'
febr 21 22:27:36 openSUSE dbus-daemon[710]: [system] Activating service
name='org.kde.powerdevil.chargethresholdhelper' requested by ':1.28' (uid=1000
pid=1757 comm="/usr/lib64/libexec/org_kde_powerdevil ") (using servicehelper)
febr 21 22:27:36 openSUSE dbus-daemon[710]: [system] Successfully activated
service 'org.kde.powerdevil.chargethresholdhelper'
febr 21 22:27:36 openSUSE dbus-daemon[710]: [system] Activating service
name='org.kde.powerdevil.backlighthelper' requested by ':1.28' (uid=1000
pid=1757 comm="/usr/lib64/libexec/org_kde_powerdevil ") (using servicehelper)
febr 21 22:27:36 openSUSE backlighthelper[1853]: org.kde.powerdevil: no kernel
backlight interface found
febr 21 22:27:36 openSUSE dbus-daemon[710]: [system] Successfully activated
service 'org.kde.powerdevil.backlighthelper'
febr 21 22:27:36 openSUSE dbus-daemon[1533]: [session uid=1000 pid=1533]
Activating service name='org.kde.KScreen' requested by ':1.21' (uid=1000
pid=1757 comm="/usr/lib64/libexec/org_kde_powerdevil ")

With systemd:
febr 21 22:29:29 openSUSE dbus-daemon[684]: [system] Activating service
name='org.kde.powerdevil.discretegpuhelper' requested by ':1.25' (uid=1000
pid=1684 comm="/usr/lib64/libexec/org_kde_powerdevil ") (using servicehelper)
febr 21 22:29:29 openSUSE dbus-daemon[684]: [system] Successfully activated
service 'org.kde.powerdevil.discretegpuhelper'
febr 21 22:29:29 openSUSE dbus-daemon[684]: [system] Activating service
name='org.kde.powerdevil.chargethresholdhelper' requested by ':1.25' (uid=1000
pid=1684 comm="/usr/lib64/libexec/org_kde_powerdevil ") (using servicehelper)
febr 21 22:29:29 openSUSE dbus-daemon[684]: [system] Successfully activated
service 'org.kde.powerdevil.chargethresholdhelper'
febr 21 22:29:29 openSUSE dbus-daemon[684]: [system] Activating service
name='org.kde.powerdevil.backlighthelper' requested by ':1.25' (uid=1000
pid=1684 comm="/usr/lib64/libexec/org_kde_powerdevil ") (using servicehelper)
febr 21 22:29:29 openSUSE backlighthelper[1773]: org.kde.powerdevil: no kernel
backlight interface found
febr 21 22:29:29 openSUSE dbus-daemon[684]: [system] Successfully activated
service 'org.kde.powerdevil.backlighthelper'
febr 21 22:29:29 openSUSE dbus-daemon[1494]: [session uid=1000 pid=1494]
Activating service name='org.kde.KScreen' requested by ':1.23' (uid=1000
pid=1684 comm="/usr/lib64/libexec/org_kde_powerdevil ")
febr 21 22:30:07 openSUSE systemd[1477]: plasma-powerdevil.service: Succeeded.

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

[Powerdevil] [Bug 433408] New: [systemd] System powers off when sleep button is pressed instead of going to sleep

[Szőts Ákos]

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

Bug ID: 433408
   Summary: [systemd] System powers off when sleep button is
pressed instead of going to sleep
   Product: Powerdevil
   Version: 5.21.0
  Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: szots...@gmail.com
  Target Milestone: ---

SUMMARY

When systemd startup is enabled in Plasma, pressing the sleep (power) button on
the computer turns the PC off. The button is configured to make the PC go to
sleep and it works fine when systemd is not enabled. 

STEPS TO REPRODUCE
1. Enable systemd startup with "kwriteconfig5 --file startkderc --group General
--key systemdBoot true"
2. Make sure that you have "Sleep when the power button is pressed" as a
desired action set up in Power settings module
3. Press the power button

OBSERVED RESULT

When systemd is enabled, it shuts down the computer instead of making it sleep.

Without systemd enabled after the power button pressed:
febr 21 22:28:16 openSUSE systemd-logind[780]: Power key pressed.
febr 21 22:28:16 openSUSE kded5[1658]: bluedevil: About to suspend
febr 21 22:28:16 openSUSE NetworkManager[1057]:   [1613942896.6691]
manager: sleep: sleep requested (sleeping: no  enabled: yes)
[...]
febr 21 22:28:16 openSUSE systemd[1]: Reached target Sleep.
febr 21 22:28:16 openSUSE systemd[1]: Starting Suspend...

With systemd enabled:
febr 21 22:30:07 openSUSE systemd-logind[746]: Power key pressed.
febr 21 22:30:07 openSUSE systemd-logind[746]: Powering Off...
febr 21 22:30:07 openSUSE systemd-logind[746]: System is powering down.
febr 21 22:30:07 openSUSE systemd[1]: Stopping Session 1 of user aki.
febr 21 22:30:07 openSUSE systemd[1]: Stopping Session c3 of user aki.
febr 21 22:30:07 openSUSE systemd[1]: Removed slice system-modprobe.slice.
febr 21 22:30:07 openSUSE sddm[1292]: Authentication error: "Process crashed"
febr 21 22:30:07 openSUSE sddm[1292]: Auth: sddm-helper crashed (exit code 15)
febr 21 22:30:07 openSUSE sddm[1292]: Authentication error: "Process crashed"
febr 21 22:30:07 openSUSE sddm[1292]: Auth: sddm-helper exited with 15
febr 21 22:30:07 openSUSE sddm[1292]: Display server stopping...

Logs of systemd-logind without systemd enabled:
-- Logs begin at Fri 2020-06-12 14:50:46 CEST, end at Sun 2021-02-21 22:35:13
CET. --
febr 21 22:27:32 openSUSE systemd[1]: Starting User Login Management...
febr 21 22:27:32 openSUSE systemd-logind[780]: Watching system buttons on
/dev/input/event1 (Power Button)
febr 21 22:27:32 openSUSE systemd-logind[780]: Watching system buttons on
/dev/input/event0 (Power Button)
febr 21 22:27:32 openSUSE systemd-logind[780]: New seat seat0.
febr 21 22:27:32 openSUSE systemd[1]: Started User Login Management.
febr 21 22:27:32 openSUSE systemd-logind[780]: Watching system buttons on
/dev/input/event17 (Dell Dell USB Keyboard)
febr 21 22:27:34 openSUSE systemd-logind[780]: Watching system buttons on
/dev/input/event18 (Logitech MX Master 2S)
febr 21 22:27:35 openSUSE systemd-logind[780]: New session 1 of user aki.
febr 21 22:28:16 openSUSE systemd-logind[780]: Power key pressed.
febr 21 22:28:26 openSUSE systemd-logind[780]: Operation 'sleep' finished.
febr 21 22:28:56 openSUSE systemd-logind[780]: System is rebooting.
febr 21 22:28:56 openSUSE systemd-logind[780]: Session 1 logged out. Waiting
for processes to exit.
febr 21 22:28:56 openSUSE systemd-logind[780]: Removed session 1.
febr 21 22:29:01 openSUSE systemd[1]: Stopping User Login Management...
febr 21 22:29:01 openSUSE systemd[1]: systemd-logind.service: Succeeded.
febr 21 22:29:01 openSUSE systemd[1]: Stopped User Login Management.

Logs of systemd-logind with systemd enabled:
-- Logs begin at Fri 2020-06-12 14:50:46 CEST, end at Sun 2021-02-21 22:35:13
CET. --
febr 21 22:29:25 openSUSE systemd[1]: Starting User Login Management...
febr 21 22:29:25 openSUSE systemd-logind[746]: Watching system buttons on
/dev/input/event1 (Power Button)
febr 21 22:29:25 openSUSE systemd-logind[746]: Watching system buttons on
/dev/input/event0 (Power Button)
febr 21 22:29:25 openSUSE systemd-logind[746]: New seat seat0.
febr 21 22:29:25 openSUSE systemd[1]: Started User Login Management.
febr 21 22:29:25 openSUSE systemd-logind[746]: Watching system buttons on
/dev/input/event17 (Dell Dell USB Keyboard)
febr 21 22:29:28 openSUSE systemd-logind[746]: Watching system buttons on
/dev/input/event18 (Logitech MX Master 2S)
febr 21 22:29:28 openSUSE systemd-logind[746]: New session 1 of user aki.
febr 21 22:30:07 openSUSE systemd-logind[746]: Power key pressed.
febr 21 22:30:07 openSUSE systemd-logind[746]: Powering Off...
febr 21 22:30:07 openSUSE systemd-logind[746]: System is powering down.
febr 21 22:30:07 openSUSE systemd-logind[746]: Session 1 logged out. Waiting
for processes to exit.
febr 21 22:30:08 

[systemsettings] [Bug 433299] [systemd] Applications meant to autostart do not start after switching to systemd

[Szőts Ákos]

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

--- Comment #2 from Szőts Ákos  ---
That's strange; if I start xbindkeys, it keeps running for me. Do you have a
config file to read from?

You can paste the following into "~/.xbindkeysrc" for a quick test (feel free
to reconfigure the buttons):

# Volume down
"pamixer --decrease 6"
 b:6

# Volume up
"pamixer --increase 4"
 b:7

If you start xbindkeys --verbose, does it tell you something? For me it writes
the following and keeps running in the foreground:

displayName = :0
rc file = /home/aki/.xbindkeysrc
2 keys in /home/aki/.xbindkeysrc

"pamixer --decrease 6"
m:0x0 + b:6   (mouse)
"pamixer --increase 4"
m:0x0 + b:7   (mouse)
starting loop...

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

[systemsettings] [Bug 433304] New: Adding a new automatically starting application generates deprecated/invalid .desktop file

[Szőts Ákos]

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

Bug ID: 433304
   Summary: Adding a new automatically starting application
generates deprecated/invalid .desktop file
   Product: systemsettings
   Version: 5.21.0
  Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: kcm_autostart
  Assignee: nicolas.fe...@gmx.de
  Reporter: szots...@gmail.com
CC: plasma-b...@kde.org
  Target Milestone: ---

SUMMARY

I created a new autostart .desktop file through the KCM and the validation
service complains.

STEPS TO REPRODUCE
1. Open Automatic start KCM module
2. Add a new "Application"
3. Use an executable (I used /usr/bin/xbindkeys)
4. Run the validator

OBSERVED RESULT

The resulting .desktop file looks like this:

$> cat .config/autostart/xbindkeys.desktop 
[Desktop Entry]
Comment[hu_HU]=
Comment=
Exec=/usr/bin/xbindkeys
GenericName[hu_HU]=
GenericName=
Icon=system-run
MimeType=
Name[hu_HU]=xbindkeys
Name=xbindkeys
Path=
StartupNotify=true
Terminal=false
TerminalOptions=
TryExec=/usr/bin/xbindkeys
Type=Application
X-DBUS-ServiceName=
X-DBUS-StartupType=
X-KDE-SubstituteUID=false
X-KDE-Username=

The validator tells for this file:

$> desktop-file-validate .config/autostart/xbindkeys.desktop 
.config/autostart/xbindkeys.desktop: warning: value "" for key "Comment[hu_HU]"
in group "Desktop Entry" looks the same as that of key "GenericName[hu_HU]"
.config/autostart/xbindkeys.desktop: warning: value "" for key "Comment" in
group "Desktop Entry" looks the same as that of key "GenericName"
.config/autostart/xbindkeys.desktop: warning: value "" for key "Path" in group
"Desktop Entry" does not look like an absolute path
.config/autostart/xbindkeys.desktop: warning: key "TerminalOptions" in group
"Desktop Entry" is deprecated


Possibly this is the reason why systemd-xdg-autostart-generator cannot generate
a .service file which runs without error messages showing up in the log:

febr 20 09:04:12 openSUSE systemd-xdg-autostart-generator[1507]:
/home/aki/.config/autostart/xbindkeys.desktop:14: Unknown key name
'TerminalOptions' in section 'Desktop Entry', ignoring.

febr 20 09:04:12 openSUSE systemd[1499]:
/run/user/1000/systemd/generator.late/app-xbindkeys-autostart.service:17:
WorkingDirectory= path is not absolute, ignoring:


EXPECTED RESULT

No warning messages.


Operating System: openSUSE Tumbleweed 20210217
KDE Plasma Version: 5.21.0
KDE Frameworks Version: 5.79.0
Qt Version: 5.15.2
Kernel Version: 5.10.16-1-default
OS Type: 64-bit
Graphics Platform: X11

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

[systemsettings] [Bug 433299] New: [systemd] Applications meant to autostart do not start after switching to systemd

[Szőts Ákos]

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

Bug ID: 433299
   Summary: [systemd] Applications meant to autostart do not start
after switching to systemd
   Product: systemsettings
   Version: 5.21.0
  Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: kcm_autostart
  Assignee: nicolas.fe...@gmx.de
  Reporter: szots...@gmail.com
CC: plasma-b...@kde.org
  Target Milestone: ---

Created attachment 135944
  --> https://bugs.kde.org/attachment.cgi?id=135944=edit
Automatic startup screenshot

SUMMARY

I have some applications which I configured to automatically start during
login. The configuration has been done by the KCM, no manual work was involved
here.

Now, after switching to systemd many of these applications don't start anymore.

Interestingly, only applications which are manual types don't keep running. In
the screenshot they are "redshift", "xbindkeys", and "xhost-add-root".

In the logs I see that they started successfully but in the task manager they
don't appear anymore. Logs for "xbindkeys":

febr 20 09:09:35 openSUSE systemd[1499]: Starting xbindkeys...
febr 20 09:09:35 openSUSE systemd[1499]: app-xbindkeys-autostart.service:
Succeeded.
febr 20 09:09:35 openSUSE systemd[1499]: Started xbindkeys.

KeePass keeps running but xbindkeys don't for some reason. Their generated unit
files are very similar:

$> cat /run/user/1000/systemd/generator.late/app-keepass-autostart.service 
# Automatically generated by systemd-xdg-autostart-generator

[Unit]
Documentation=man:systemd-xdg-autostart-generator(8)
SourcePath=/home/aki/.config/autostart/keepass.desktop
PartOf=graphical-session.target

Description=KeePass
After=graphical-session.target

[Service]
Type=exec
ExecStart=:/usr/bin/keepass
Restart=no
TimeoutSec=5s
Slice=app.slice
WorkingDirectory=-

$> cat /run/user/1000/systemd/generator.late/app-xbindkeys-autostart.service 
# Automatically generated by systemd-xdg-autostart-generator

[Unit]
Documentation=man:systemd-xdg-autostart-generator(8)
SourcePath=/home/aki/.config/autostart/xbindkeys.desktop
PartOf=graphical-session.target

Description=xbindkeys
After=graphical-session.target

[Service]
Type=exec
ExecStart=:/usr/bin/xbindkeys
Restart=no
TimeoutSec=5s
Slice=app.slice
WorkingDirectory=-


SOFTWARE/OS VERSIONS
Operating System: openSUSE Tumbleweed 20210217
KDE Plasma Version: 5.21.0
KDE Frameworks Version: 5.79.0
Qt Version: 5.15.2
Kernel Version: 5.10.16-1-default
OS Type: 64-bit
Graphics Platform: X11

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

[systemsettings] [Bug 433295] [systemd] Applications meant to autostart do not start after switching to systemd

[Szőts Ákos]

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

Szőts Ákos  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
 Resolution|--- |WORKSFORME

--- Comment #2 from Szőts Ákos  ---
After further debugging it seems that the error messages are not related to the
startup functionality (and most probably are errors in
systemd-xdg-autostart-generator and not in KDE).

To have a more clear picture, I'll clarify this bug report in a new one with
further findings.

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

[systemsettings] [Bug 433295] [systemd] Applications meant to autostart do not start after switching to systemd

[Szőts Ákos]

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

--- Comment #1 from Szőts Ákos  ---
Generated service file:

$> cat /run/user/1000/systemd/generator.late/app-keepass-autostart.service 
# Automatically generated by systemd-xdg-autostart-generator

[Unit]
Documentation=man:systemd-xdg-autostart-generator(8)
SourcePath=/home/aki/.config/autostart/keepass.desktop
PartOf=graphical-session.target

Description=KeePass
After=graphical-session.target

[Service]
Type=exec
ExecStart=:/usr/bin/keepass
Restart=no
TimeoutSec=5s
Slice=app.slice
WorkingDirectory=-

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

[systemsettings] [Bug 433295] New: [systemd] Applications meant to autostart do not start after switching to systemd

[Szőts Ákos]

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

Bug ID: 433295
   Summary: [systemd] Applications meant to autostart do not start
after switching to systemd
   Product: systemsettings
   Version: 5.21.0
  Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: kcm_autostart
  Assignee: nicolas.fe...@gmx.de
  Reporter: szots...@gmail.com
CC: plasma-b...@kde.org
  Target Milestone: ---

SUMMARY

I have some applications which I configured to automatically start during
login. The configuration has been done by the KCM, no manual work was involved
here.

Now, after switching to systemd many of these applications don't start anymore.

In the logs I can see (messages from one startup):

febr 20 08:42:09 openSUSE systemd[1516]:
/run/user/1000/systemd/generator.late/app-xhost-autostart.service:17:
WorkingDirectory= path is not absolute, ignoring: 
febr 20 08:42:09 openSUSE systemd[1516]:
/run/user/1000/systemd/generator.late/app-xbindkeys-autostart.service:17:
WorkingDirectory= path is not absolute, ignoring: 
febr 20 08:42:09 openSUSE systemd[1516]:
/run/user/1000/systemd/generator.late/app-redshift-autostart.service:17:
WorkingDirectory= path is not absolute, ignoring: 
febr 20 08:42:09 openSUSE systemd[1516]:
/run/user/1000/systemd/generator.late/app-org.kde.yakuake-autostart.service:17:
WorkingDirectory= path is not absolute, ignoring: 
febr 20 08:42:09 openSUSE systemd[1516]:
/run/user/1000/systemd/generator.late/app-org.kde.kontact-autostart.service:17:
WorkingDirectory= path is not absolute, ignoring: 
febr 20 08:42:09 openSUSE systemd[1516]:
/run/user/1000/systemd/generator.late/app-keepass-autostart.service:17:
WorkingDirectory= path is not absolute, ignoring: 
febr 20 08:42:09 openSUSE systemd[1516]:
/run/user/1000/systemd/generator.late/app-xhost-autostart.service:17:
WorkingDirectory= path is not absolute, ignoring: 
febr 20 08:42:09 openSUSE systemd[1516]:
/run/user/1000/systemd/generator.late/app-xbindkeys-autostart.service:17:
WorkingDirectory= path is not absolute, ignoring: 
febr 20 08:42:09 openSUSE systemd[1516]:
/run/user/1000/systemd/generator.late/app-redshift-autostart.service:17:
WorkingDirectory= path is not absolute, ignoring: 
febr 20 08:42:09 openSUSE systemd[1516]:
/run/user/1000/systemd/generator.late/app-org.kde.yakuake-autostart.service:17:
WorkingDirectory= path is not absolute, ignoring: 
febr 20 08:42:09 openSUSE systemd[1516]:
/run/user/1000/systemd/generator.late/app-org.kde.kontact-autostart.service:17:
WorkingDirectory= path is not absolute, ignoring: 
febr 20 08:42:09 openSUSE systemd[1516]:
/run/user/1000/systemd/generator.late/app-keepass-autostart.service:17:
WorkingDirectory= path is not absolute, ignoring: 
febr 20 08:42:09 openSUSE systemd[1516]:
/run/user/1000/systemd/generator.late/app-xhost-autostart.service:17:
WorkingDirectory= path is not absolute, ignoring: 
febr 20 08:42:09 openSUSE systemd[1516]:
/run/user/1000/systemd/generator.late/app-xbindkeys-autostart.service:17:
WorkingDirectory= path is not absolute, ignoring: 
febr 20 08:42:09 openSUSE systemd[1516]:
/run/user/1000/systemd/generator.late/app-redshift-autostart.service:17:
WorkingDirectory= path is not absolute, ignoring: 
febr 20 08:42:09 openSUSE systemd[1516]:
/run/user/1000/systemd/generator.late/app-org.kde.yakuake-autostart.service:17:
WorkingDirectory= path is not absolute, ignoring: 
febr 20 08:42:09 openSUSE systemd[1516]:
/run/user/1000/systemd/generator.late/app-org.kde.kontact-autostart.service:17:
WorkingDirectory= path is not absolute, ignoring: 
febr 20 08:42:09 openSUSE systemd[1516]:
/run/user/1000/systemd/generator.late/app-keepass-autostart.service:17:
WorkingDirectory= path is not absolute, ignoring: 

I additionally see the following warnings (which probably not affect whether
the application can be launched but may have other negative consequences down
the road):

febr 20 08:42:08 openSUSE systemd-xdg-autostart-generator[1522]:
/home/aki/.config/autostart/keepass.desktop:15: Unknown key name
'TerminalOptions' in section 'Desktop Entry', ignoring.
febr 20 08:42:08 openSUSE systemd-xdg-autostart-generator[1522]:
/home/aki/.config/autostart/xhost.desktop:14: Unknown key name
'TerminalOptions' in section 'Desktop Entry', ignoring.
febr 20 08:42:08 openSUSE systemd-xdg-autostart-generator[1522]:
/home/aki/.config/autostart/org.kde.kontact.desktop:15: Unknown key name
'TerminalOptions' in section 'Desktop Entry', ignoring.
febr 20 08:42:08 openSUSE systemd-xdg-autostart-generator[1522]: Configuration
file /home/aki/.config/autostart/org.kde.yakuake.desktop is marked executable.
Please remove executable permission bits. Proceeding an>
febr 20 08:42:08 openSUSE systemd-xdg-autostart-generator[1522]:
/home/aki/.config/autostart/org.kde.yakuake.desktop:119: Unknown key name
'TerminalOptions' in section 

[Akonadi] [Bug 431584] New: Akonadi Resources for Google Services asks for Google permissions four times a day

[Szőts Ákos]

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

Bug ID: 431584
   Summary: Akonadi Resources for Google Services asks for Google
permissions four times a day
   Product: Akonadi
   Version: 5.16.0
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: IMAP resource
  Assignee: kdepim-b...@kde.org
  Reporter: szots...@gmail.com
  Target Milestone: ---

SUMMARY

Seemingly at random times, but every time after my computer comes back from
sleep and after the cronjob'd Akonadi restart, my browser pops up a
notification from Google to enable Akonadi Resources for Google Services. I
enable that all time and it seems that it doesn't get remembered.

KWallet seems to work as expected.

Operating System: openSUSE Tumbleweed 20210106
KDE Plasma Version: 5.20.4
KDE Frameworks Version: 5.77.0
Qt Version: 5.15.2
Kernel Version: 5.10.4-1-default
OS Type: 64-bit

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

[Akonadi] [Bug 416036] Error in changing server-side subscriptions if GSSAPI authentication is enabled

[Szőts Ákos]

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

Szőts Ákos  changed:

   What|Removed |Added

 CC||szots...@gmail.com

--- Comment #2 from Szőts Ákos  ---
I can confirm it with Akonadi and KMail 20.08.3.

The difference is that the IMAP account settings page indeed appears but it is
empty.

A similar report is Bug 389772, however, that's much older and that error
doesn't seem to be the case now (possibly it can be closed?).

Logging akonadi and KMail with QT_LOGGING_RULES="*=true;qt.*=false" the logs
are:

Akonadi:
- Account settings window:
org.kde.pim.imapresource: manage subscripts
org.kde.pim.imapresource: current auth mode:  "Gmail"
org.kde.pim.kimap: KIMAP::LoginJob(0x5565d13b3d20)
org.kde.pim.kimap: Connecting to IMAP server with no proxy
org.kde.pim.kimap: connectToHost "imap.gmail.com" 993
org.kde.pim.kimap: KIMAP::LoginJob(0x5565d13b3d20)
org.kde.pim.kimap: TLS negotiation done, the negotiated protocol is "TLSv1.3"
org.kde.pim.kimap: "Capability" "*"
org.kde.pim.kimap: Capabilities updated:  ("IMAP4rev1", "UNSELECT", "IDLE",
"NAMESPACE", "QUOTA", "ID", "XLIST", "CHILDREN", "X-GM-EXT-1", "XYZZY",
"SASL-IR", "AUTH=XOAUTH2", "AUTH=PLAIN", "AUTH=PLAIN-CLIENTTOKEN",
"AUTH=OAUTHBEARER", "AUTH=XOAUTH")
org.kde.pim.kimap: "Capability" "A01"
org.kde.pim.kimap: Trying authmod "XOAUTH2"
[SASL-XOAUTH2] - Requesting authID![SASL-XOAUTH2] - Requesting token
![SASL-XOAUTH2] - filling prompts
!org.kde.pim.kimap: sasl_interact
org.kde.pim.kimap: SASL_INTERACT id: 16386
org.kde.pim.kimap: SASL_CB_[USER|AUTHNAME]: ' "my-email-addr...@gmail.com" '
org.kde.pim.kimap: SASL_INTERACT id: 16388
org.kde.pim.kimap: SASL_CB_PASS: [hidden]
org.kde.pim.kimap: Trying authmod "XOAUTH2"
[SASL-XOAUTH2] - Requesting authID![SASL-XOAUTH2] - Requesting token
!org.kde.pim.kimap: "Login" "+"
org.kde.pim.kimap: sasl_client_step failed with: -1 "SASL(0): successful
result: "
org.kde.pim.kimap: KIMAP::LoginJob(0x5565d13b3d20)

- Context menu:
org.kde.pim.akonadicontrol: Service "org.freedesktop.ReserveDevice1.Audio2"
owner changed from "" to ":1.2066"

KMail:
- Account settings window:


- Context menu:
kf.notifications: Calling notify on "Sound"
kf.notifications: Calling notify on "Taskbar"

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