[plasmashell] [Bug 454946] New: plasmashell crashes when switching between layouts

[Erich Eickmeyer]

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

Bug ID: 454946
   Summary: plasmashell crashes when switching between layouts
   Product: plasmashell
   Version: 5.24.5
  Platform: Ubuntu Packages
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: eeickme...@ubuntu.com
CC: k...@davidedmundson.co.uk
  Target Milestone: 1.0

Application: plasmashell (5.24.5)

Qt Version: 5.15.3
Frameworks Version: 5.94.0
Operating System: Linux 5.17.0-1004-oem x86_64
Windowing System: X11
Distribution: Ubuntu 22.04 LTS
DrKonqi: 5.24.5 [KCrashBackend]

-- Information about the crash:
- What I was doing when the application crashed:
When switching between layouts, plasmashell inevitably crashes, and sometimes
fails to recover. This can be reproduced in both virtual machines and on actual
hardware.

- Unusual behavior I noticed:
Black screen, sometimes full kwin crash as well would happen.

- Custom settings of the application:
Stock Kubuntu installation, Kubuntu Focus hardware

The crash can be reproduced every time.

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

[KCrash Handler]
#4  0x7f4c702014c4 in QQuickWindow::maybeUpdate() () from
/lib/x86_64-linux-gnu/libQt5Quick.so.5
#5  0x7f4c701e9e1a in QQuickItemPrivate::setEffectiveVisibleRecur(bool) ()
from /lib/x86_64-linux-gnu/libQt5Quick.so.5
#6  0x7f4c701e9e8b in QQuickItemPrivate::setEffectiveVisibleRecur(bool) ()
from /lib/x86_64-linux-gnu/libQt5Quick.so.5
#7  0x7f4c701e9fb7 in QQuickItemPrivate::setVisible(bool) () from
/lib/x86_64-linux-gnu/libQt5Quick.so.5
#8  0x7f4c6e7cf783 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x7f4c7077cde6 in Plasma::Applet::destroyedChanged(bool) () from
/lib/x86_64-linux-gnu/libKF5Plasma.so.5
#10 0x7f4c70790af8 in ?? () from /lib/x86_64-linux-gnu/libKF5Plasma.so.5
#11 0x7f4c7077e08a in Plasma::Applet::destroy() () from
/lib/x86_64-linux-gnu/libKF5Plasma.so.5
#12 0x55f492d75254 in ?? ()
#13 0x55f492d78dd8 in ?? ()
#14 0x55f492da9d83 in ?? ()
#15 0x7f4c6f14959b in ?? () from /lib/x86_64-linux-gnu/libQt5DBus.so.5
#16 0x7f4c6f14cfec in ?? () from /lib/x86_64-linux-gnu/libQt5DBus.so.5
#17 0x7f4c6f14d9f9 in ?? () from /lib/x86_64-linux-gnu/libQt5DBus.so.5
#18 0x7f4c6f14fdac in ?? () from /lib/x86_64-linux-gnu/libQt5DBus.so.5
#19 0x7f4c6e7c540e in QObject::event(QEvent*) () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#20 0x7f4c6f48e713 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#21 0x7f4c6e797e2a in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /lib/x86_64-linux-gnu/libQt5Core.so.5
#22 0x7f4c6e79af17 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#23 0x7f4c6e7f1a57 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#24 0x7f4c6cb67d1b in g_main_context_dispatch () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#25 0x7f4c6cbbc6f8 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#26 0x7f4c6cb653c3 in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#27 0x7f4c6e7f10a8 in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib/x86_64-linux-gnu/libQt5Core.so.5
#28 0x7f4c6e79674b in
QEventLoop::exec(QFlags) () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#29 0x7f4c6e79ece4 in QCoreApplication::exec() () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#30 0x55f492d50dce in ?? ()
#31 0x7f4c6e0b3d90 in __libc_start_call_main
(main=main@entry=0x55f492d4ff70, argc=argc@entry=2,
argv=argv@entry=0x7ffd15d4a068) at ../sysdeps/nptl/libc_start_call_main.h:58
#32 0x7f4c6e0b3e40 in __libc_start_main_impl (main=0x55f492d4ff70, argc=2,
argv=0x7ffd15d4a068, init=, fini=,
rtld_fini=, stack_end=0x7ffd15d4a058) at ../csu/libc-start.c:392
#33 0x55f492d50ef5 in ?? ()
[Inferior 1 (process 2036) detached]

Possible duplicates by query: bug 453681, bug 450723, bug 450594, bug 450163,
bug 450124.

Reported using DrKonqi

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

[plasmashell] [Bug 454946] plasmashell crashes when switching between layouts

[Erich Eickmeyer]

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

Erich Eickmeyer  changed:

   What|Removed |Added

 Status|NEEDSINFO   |REPORTED
 Resolution|WAITINGFORINFO  |---
 CC||rikmi...@kde.org

--- Comment #2 from Erich Eickmeyer  ---
Hi Nate,

I'm afraid the debug symbols were unavailable even though the correct packages
were installed. And sorry, I should've clarified: this crash happens when
switching between look & feel t (global) themes when "Use desktop layout from
theme" is checked.

Thanks!

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

[plasmashell] [Bug 454946] plasmashell crashes when switching between Global Theme desktop layouts

[Erich Eickmeyer]

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

--- Comment #4 from Erich Eickmeyer  ---
Right, that's why I added Rik Mills on the CC here, maybe he can chime-in to
help.

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

[plasmashell] [Bug 454946] plasmashell crashes when switching between Global Theme desktop layouts

[Erich Eickmeyer]

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

Erich Eickmeyer  changed:

   What|Removed |Added

 Resolution|BACKTRACE   |---
 Status|NEEDSINFO   |REPORTED

--- Comment #6 from Erich Eickmeyer  ---
Thanks for the hint, Rik!

Here's the full backtrace:

Application: Plasma (plasmashell), signal: Segmentation fault

[KCrash Handler]
#4  0x7f2c8df6b4c4 in QQuickWindow::maybeUpdate() () from
/lib/x86_64-linux-gnu/libQt5Quick.so.5
#5  0x7f2c8df53e1a in QQuickItemPrivate::setEffectiveVisibleRecur(bool) ()
from /lib/x86_64-linux-gnu/libQt5Quick.so.5
#6  0x7f2c8df53e8b in QQuickItemPrivate::setEffectiveVisibleRecur(bool) ()
from /lib/x86_64-linux-gnu/libQt5Quick.so.5
#7  0x7f2c8df53fb7 in QQuickItemPrivate::setVisible(bool) () from
/lib/x86_64-linux-gnu/libQt5Quick.so.5
#8  0x7f2c8c539783 in QtPrivate::QSlotObjectBase::call (a=0x7ffdf1acad50,
r=0x556422a0cf20, this=0x556422b61840) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#9  doActivate (sender=0x556422a17b90, signal_index=5,
argv=0x7ffdf1acad50) at kernel/qobject.cpp:3886
#10 0x7f2c8c532a97 in QMetaObject::activate (sender=,
m=m@entry=0x7f2c8e570980 ,
local_signal_index=local_signal_index@entry=2, argv=argv@entry=0x7ffdf1acad50)
at kernel/qobject.cpp:3946
#11 0x7f2c8e4e6de6 in Plasma::Applet::destroyedChanged (this=, _t1=, _t1@entry=true) at
./obj-x86_64-linux-gnu/src/plasma/KF5Plasma_autogen/include/moc_applet.cpp:546
#12 0x7f2c8e4faaf8 in Plasma::AppletPrivate::setDestroyed
(this=0x556422896c40, destroyed=destroyed@entry=true) at
./src/plasma/private/applet_p.cpp:232
#13 0x7f2c8e4e808a in Plasma::Applet::destroy (this=0x556422a17b90) at
./src/plasma/applet.cpp:309
#14 0x556420a68254 in ShellCorona::unload (this=this@entry=0x5564227b7b20)
at ./shell/shellcorona.cpp:834
#15 0x556420a6bdd8 in ShellCorona::unload (this=0x5564227b7b20) at
./shell/shellcorona.cpp:606
#16 ShellCorona::loadLookAndFeelDefaultLayout (this=0x5564227b7b20,
packageName=...) at ./shell/shellcorona.cpp:602
#17 0x556420a9cd83 in PlasmaShellAdaptor::qt_metacall (this=0x556422948ad0,
_c=QMetaObject::InvokeMetaMethod, _id=3, _a=0x7ffdf1acafa0) at
./obj-x86_64-linux-gnu/shell/plasmashelladaptor.moc:197
#18 0x7f2c8ceb359b in QDBusConnectionPrivate::deliverCall (this=, object=, msg=..., metaTypes=..., slotIdx=)
at ../../include/QtCore/../../src/corelib/tools/qvarlengtharray.h:190
#19 0x7f2c8ceb6fec in QDBusConnectionPrivate::activateCall
(this=this@entry=0x7f2c78008a00, object=0x556422948ad0, flags=flags@entry=273,
msg=...) at ./src/dbus/qdbusintegrator.cpp:904
#20 0x7f2c8ceb79f9 in QDBusConnectionPrivate::activateCall (msg=...,
flags=273, object=, this=0x7f2c78008a00) at
./src/dbus/qdbusintegrator.cpp:853
#21 QDBusConnectionPrivate::activateObject (this=0x7f2c78008a00, node=...,
msg=..., pathStartPos=) at ./src/dbus/qdbusintegrator.cpp:1497
#22 0x7f2c8ceb9dac in QDBusActivateObjectEvent::placeMetaCall
(this=0x7f2c7804acf0) at ./src/dbus/qdbusintegrator.cpp:1617
#23 0x7f2c8c52f40e in QObject::event (this=0x5564227b7b20,
e=0x7f2c7804acf0) at kernel/qobject.cpp:1314
#24 0x7f2c8d1f8713 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#25 0x7f2c8c501e2a in QCoreApplication::notifyInternal2
(receiver=0x5564227b7b20, event=0x7f2c7804acf0) at
kernel/qcoreapplication.cpp:1064
#26 0x7f2c8c504f17 in QCoreApplicationPrivate::sendPostedEvents
(receiver=0x0, event_type=0, data=0x556422697ec0) at
kernel/qcoreapplication.cpp:1821
#27 0x7f2c8c55ba57 in postEventSourceDispatch (s=0x556422787ec0) at
kernel/qeventdispatcher_glib.cpp:277
#28 0x7f2c8a8d1d1b in g_main_dispatch (context=0x7f2c80005010) at
../../../glib/gmain.c:3417
#29 g_main_context_dispatch (context=0x7f2c80005010) at
../../../glib/gmain.c:4135
#30 0x7f2c8a9266f8 in g_main_context_iterate.constprop.0
(context=context@entry=0x7f2c80005010, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at ../../../glib/gmain.c:4211
#31 0x7f2c8a8cf3c3 in g_main_context_iteration (context=0x7f2c80005010,
may_block=1) at ../../../glib/gmain.c:4276
#32 0x7f2c8c55b0a8 in QEventDispatcherGlib::processEvents
(this=0x5564227884e0, flags=...) at kernel/qeventdispatcher_glib.cpp:423
#33 0x7f2c8c50074b in QEventLoop::exec (this=this@entry=0x7ffdf1acb580,
flags=..., flags@entry=...) at
../../include/QtCore/../../src/corelib/global/qflags.h:69
#34 0x7f2c8c508ce4 in QCoreApplication::exec () at
../../include/QtCore/../../src/corelib/global/qflags.h:121
#35 0x556420a43dce in main (argc=, argv=) at
./shell/main.cpp:238
[Inferior 1 (process 1472) detached]

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

[digikam] [Bug 465548] New: digikam crashes with illegal instruction on AMD Athlon II

[Erich Eickmeyer]

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

Bug ID: 465548
   Summary: digikam crashes with illegal instruction on AMD Athlon
II
Classification: Applications
   Product: digikam
   Version: 8.0.0
  Platform: Ubuntu
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: digikam-bugs-n...@kde.org
  Reporter: eeickme...@ubuntu.com
  Target Milestone: ---

SUMMARY

The following is a downstream bug reported on Launchpad at
https://launchpad.net/bugs/2000718, more logs available there. Filer's name is
Graeme Hewson
***
The crash happens early in the initialisation, since it occurs just trying to
display the version:

$ digikam --version
Illegal instruction (core dumped)
$

Gdb shows the failing instruction:

$ gdb digikam
GNU gdb (Ubuntu 12.1-3ubuntu2) 12.1
Copyright (C) 2022 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from digikam...

This GDB supports auto-downloading debuginfo from the following URLs:
https://debuginfod.ubuntu.com
Enable debuginfod for this session? (y or [n]) y
Debuginfod has been enabled.
To make this setting permanent, add 'set debuginfod enabled on' to .gdbinit.
Reading symbols from
/home/ghewson/.cache/debuginfod_client/c793f63692bc8f2f3ec63f47803ccc5398e78dcb/debuginfo...
(gdb) r
Starting program: /usr/bin/digikam
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffd13966c0 (LWP 319127)]

Thread 1 "digikam" received signal SIGILL, Illegal instruction.
0x76c748b4 in operator* (m1=..., m2=...) at
/usr/include/x86_64-linux-gnu/qt5/QtGui/qmatrix4x4.h:642
642 /usr/include/x86_64-linux-gnu/qt5/QtGui/qmatrix4x4.h: Directory not empty.
(gdb) disas /s $pc-10,+20
Dump of assembler code from 0x76c748aa to 0x76c748be:
/usr/include/x86_64-linux-gnu/qt5/QtGui/qmatrix4x4.h:
642 in /usr/include/x86_64-linux-gnu/qt5/QtGui/qmatrix4x4.h
643 in /usr/include/x86_64-linux-gnu/qt5/QtGui/qmatrix4x4.h
644 in /usr/include/x86_64-linux-gnu/qt5/QtGui/qmatrix4x4.h
645 in /usr/include/x86_64-linux-gnu/qt5/QtGui/qmatrix4x4.h
646 in /usr/include/x86_64-linux-gnu/qt5/QtGui/qmatrix4x4.h
647 in /usr/include/x86_64-linux-gnu/qt5/QtGui/qmatrix4x4.h
648 in /usr/include/x86_64-linux-gnu/qt5/QtGui/qmatrix4x4.h
649 in /usr/include/x86_64-linux-gnu/qt5/QtGui/qmatrix4x4.h
   0x76c748aa <_ZmlRK10QMatrix4x4S1_+154>: sub %dh,%bl
   0x76c748ac <_ZmlRK10QMatrix4x4S1_+156>: movlhps %xmm0,%xmm7

642 in /usr/include/x86_64-linux-gnu/qt5/QtGui/qmatrix4x4.h
   0x76c748af <_ZmlRK10QMatrix4x4S1_+159>: movups 0x30(%r9),%xmm0
=> 0x76c748b4 <_ZmlRK10QMatrix4x4S1_+164>: extractps $0x2,%xmm12,%r11d
   0x76c748bb <_ZmlRK10QMatrix4x4S1_+171>: extractps $0x1,%xmm12,%edi
End of assembler dump.
(gdb)

EXTRACTPS is part of the SSE4.1 instruction set, which is not supported by AMD
Athlon II Regor processors (or any other in the family, I believe): they
support only the SSE4a instruction group.

References:

https://en.wikipedia.org/wiki/SSE4#SSE4.1

https://en.wikipedia.org/wiki/List_of_AMD_Athlon_II_processors#%22Regor%22_(C2/C3,_45_nm,_Dual-core)

ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: digikam 4:8.0.0~git20221002-0ubuntu1
ProcVersionSignature: Ubuntu 5.19.0-26.27-generic 5.19.7
Uname: Linux 5.19.0-26-generic x86_64
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: KDE
Date: Thu Dec 29 10:41:20 2022
EcryptfsInUse: Yes
InstallationDate: Installed on 2015-09-08 (2668 days ago)
InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
SourcePackage: digikam
UpgradeStatus: Upgraded to kinetic on 2022-10-25 (64 days ago)
***


STEPS TO REPRODUCE
Per the above report, it fails upon execution with illegal instruction.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Ubuntu 22.10
KDE Plasma Version: 5.25 or 5.26
Qt Version:  5.15

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

[digikam] [Bug 465548] digikam crashes with illegal instruction on AMD Athlon II

[Erich Eickmeyer]

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

Erich Eickmeyer  changed:

   What|Removed |Added

 CC||mity...@gmail.com

--- Comment #3 from Erich Eickmeyer  ---
(In reply to Maik Qualmann from comment #2)
> Ok, this is not a digiKam problem. There is a problem with compiling the Qt
> library. If it doesn't crahes with other programs, it's because they don't
> use QMatrix4x4. Someone enabled an optimization when compiling the Qt
> packages that is not supported on all processors. Report it to the creators
> of the Qt packages on your system.
> 
> Maik

Well, if that's the case then every single Qt application would be dying on his
system, which is not the case. Adding Dmitry Shachnev to this conversation as
we're officially outside my realm of expertise.

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

[digikam] [Bug 465548] digikam crashes with illegal instruction on AMD Athlon II

[Erich Eickmeyer]

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

--- Comment #4 from Erich Eickmeyer  ---
Inspecting the code with another, it seems as though you've got an issue here:

https://invent.kde.org/graphics/digikam/-/blob/master/core/cmake/macros/MacroSSE.cmake#L40

You're getting the SSE info from the host as opposed to building generically or
using -march=native.

I'd consider this rather odd and setting it so that it fails on processors
other than the one it's building on. In other words, this is bad practice.

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

[kscreenlocker] [Bug 457284] X11: Lock screen wallpaper is all black after sleep

[Erich Eickmeyer]

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

Erich Eickmeyer  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |---
 Status|NEEDSINFO   |CONFIRMED

--- Comment #10 from Erich Eickmeyer  ---
(In reply to Fushan Wen from comment #8)
> Can't reproduce. Can you still reproduce it after removing
> ~/.cache/kscreenlocker_greet/ ? If you can test 5.26 Beta it would be better.

No effect. Cannot test on 5.26 Beta, I do not have access to binary builds at
this time. Latest test on 5.25.5 resulted in same issue. Bear in mind, this is
on an Nvidia discrete GPU in Performance mode, issue does not occur if in
Powersave (integrated graphics) mode.

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

[kscreenlocker] [Bug 457284] Lock screen wallpaper is all black after waking from sleep

[Erich Eickmeyer]

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

--- Comment #23 from Erich Eickmeyer  ---
(In reply to Nate Graham from comment #21)
> We've made a change that we're pretty sure will fix this in Plasma 5.26!
> Please re-open if you find that you can still reproduce the issue in 5.26
> after upgrade (and a reboot, of course!).

Sadly, I can't 100% confirm this. I just upgraded to Plasma 5.26 beta from the
Kubuntu beta PPA which might not have the latest commits and, sadly, the issue
still exists there. That said, I won't reopen as I don't believe this fits the
test case.

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

[digikam] [Bug 465548] digiKam crashes with illegal instruction on AMD Athlon II due to SSE detection with CMake

[Erich Eickmeyer]

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

--- Comment #12 from Erich Eickmeyer  ---
(In reply to caulier.gilles from comment #11)
> To Erich Eickmeyer comment 4:
> 
> This is how original QtAV deal with SSE instructions. I only port all QtAV
> rules to a modern CMake implementation. C++ codes still the same.
> 
> Gilles Caulier

If you have ported the QtAV rules into your code, then by that logic it is a
bug in your code.

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

[digikam] [Bug 463439] Build system requires external git source

[Erich Eickmeyer]

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

--- Comment #4 from Erich Eickmeyer  ---
(In reply to caulier.gilles from comment #3)
> The deviation is due to the large collection of files to test digiKam
> implementations, including photos and videos. We use a dedicated git-fs
> repository for that. As i know no other KDE application do the same for the
> moment.

Hi Gilles,

This makes sense, but only when building locally. When using a distribution
build system, such as the ones in use by Debian and Ubuntu where no external
sources can be accessed, this is an impossible situation. These build systems
are designed to run the unit tests as designed by the upstream developers for
robustness. As far as I know, all KDE applications are meant to be distributed
by distributions, and DigiKam is no different, is it not? If it's no different,
then the unit tests should not rely on external sources, as is the case
currently.

In order to get it to build with the unit tests properly, we had to add the
unit tests to the packaging side, which is a poor workaround. Disabling the
unit tests is simply bad practice from a distribution standpoint, as you can
imagine.

I hope you understand where we're coming from.

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

[digikam] [Bug 463439] Build system requires external git source

[Erich Eickmeyer]

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

--- Comment #7 from Erich Eickmeyer  ---
(In reply to caulier.gilles from comment #5)
> >This makes sense, but only when building locally. 
> 
> And here you are wrong: the digiKam unit-test build is managed in the gitlab
> CI while developers commit in the source repository. The data are not used
> only by developers locally, but also online in gitlab. 

Sorry, that was my mistake, I didn't account for CI systems.

> This solution to separate the huge unit test data from the source code is to
> reduce the tarball size at release time. This solution was proposed by the
> KDE system admins and i'm sure that others huge KDE applications as Krita
> and Kdenlive will also take this way in the future.

Then this issue will be reported accordingly to those projects as well at those
times. Also adding Aleix Pol to CC as this is a distribution blocker for the
reasons I will outline below. This is basically a huge mistake not to include
*everything* needed to build and test the applications in the release tarballs
as it only hurts the distributions. Were the distributions not consulted prior
to this change?

> >When using a distribution build system, such as the ones in use by Debian 
> >and Ubuntu where no external sources can be accessed, this is an >impossible 
> >situation. These build systems are designed to run the unit tests as 
> >designed by the upstream developers for robustness. As far as I >know, all 
> >KDE applications are meant to be distributed by distributions, and DigiKam 
> >is no different, is it not? 
> 
> Of course. But the unit -tests are already processed previously in your CI
> automatically while the evolution of the application, this is the main goal.
> 
> >If it's no different, then the unit tests should not rely on external 
> >sources, as is the case currently.
> 
> 2 solutions for you: disabling unit tests while building package as we
> process unit tests in digiKam CI,

We cannot rely on your tests as we cannot trust that your CI system is
identical to our build environment.

> or found a solution to open access to
> external resources as the git-fs data repository in your build CI. 

That's a non-starter per policy. That simply will not happen under any
circumstances as that breaks our trusted sources policy. I am far from the
person in charge of this policy, that lies with the Ubuntu Technical Board.

The only solution to this problem is to reverse this change as proposed by the
KDE system admins (you said proposed, you never said it was mandated, so I'm
not sure why it took effect). I'm sure it was well-intentioned to keep the size
of the tarballs down, but it seems as though the proposal did not count on the
fact that many distributions, Debian and Ubuntu included, need to do the unit
tests against their own build environments.

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

[digikam] [Bug 463439] Build system requires external git source

[Erich Eickmeyer]

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

Erich Eickmeyer  changed:

   What|Removed |Added

 CC||aleix...@kde.org

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

[kwin] [Bug 438312] Restarting kwin_x11 forgets activities assigned to windows

[Erich Eickmeyer]

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

Erich Eickmeyer  changed:

   What|Removed |Added

 CC||eeickme...@ubuntu.com
 Status|RESOLVED|REOPENED
 Resolution|FIXED   |---

--- Comment #21 from Erich Eickmeyer  ---
I see the fix has not yet been cherry-picked to be in 5.24 for release in
5.24.7 (the current LTS release of Plasma). I highly suggest and urge this be
done to keep with the 2-year LTS promise.

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

[plasmashell] [Bug 413645] Can't remember desktop widget positions after reboot

[Erich Eickmeyer]

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

Erich Eickmeyer  changed:

   What|Removed |Added

 CC||eeickme...@ubuntu.com
 Resolution|FIXED   |---
 Status|RESOLVED|REOPENED

--- Comment #62 from Erich Eickmeyer  ---
I see the fix has not been worked on for 5.24 for release in 5.24.7 (the
current LTS release of Plasma). I highly suggest and urge this be done to keep
with the 2-year LTS promise.

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

[kscreenlocker] [Bug 457284] Lock screen wallpaper is all black after waking from sleep

[Erich Eickmeyer]

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

Erich Eickmeyer  changed:

   What|Removed |Added

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

--- Comment #28 from Erich Eickmeyer  ---
(In reply to Ali from comment #27)
> I downgraded the nvidia-driver to 510 and apply this line 
> > sudo chmod +x /usr/share/screen-resolution-extra/nvidia-polkit
> open nvidia-settings and save the x server display configuration by pressing
> "save to x configuration file"

That's merely a workaround and can actually break some laptop displays. Please
do not give such advice as a "bugfix".

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

[gwenview] [Bug 441121] gwenview crashes when opening .jpg in X11 Session (wayland not possible on graphics card)

[Erich Eickmeyer]

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

Erich Eickmeyer  changed:

   What|Removed |Added

 CC||eeickme...@ubuntu.com

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

[gwenview] [Bug 441121] gwenview crashes when opening .jpg in X11 Session (wayland not possible on graphics card)

[Erich Eickmeyer]

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

--- Comment #19 from Erich Eickmeyer  ---
Created attachment 144108
  --> https://bugs.kde.org/attachment.cgi?id=144108&action=edit
New crash information added by DrKonqi

gwenview (21.11.90) using Qt 5.15.2

- What I was doing when the application crashed:
Attempting to open a family photo I had just exported from Darktable

-- Backtrace (Reduced):
#4  __pthread_kill_implementation (no_tid=0, signo=6, threadid=139723732405312)
at pthread_kill.c:44
#5  __pthread_kill_internal (signo=6, threadid=139723732405312) at
pthread_kill.c:80
#6  __GI___pthread_kill (threadid=139723732405312, signo=signo@entry=6) at
pthread_kill.c:91
#7  0x7f13fcc35476 in __GI_raise (sig=sig@entry=6) at
../sysdeps/posix/raise.c:26
#8  0x7f13fcc1b7b7 in __GI_abort () at abort.c:79

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

[frameworks-kdesu] [Bug 452532] kdesu not working after upgrade from Ubuntu 20.04 to 22.04

[Erich Eickmeyer]

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

--- Comment #4 from Erich Eickmeyer  ---
(In reply to Ahmad Samir from comment #3)
> The daemon is kdesud, which is typically installed in /usr/libexec.

That's true on Arch systems, but not Debian/Ubuntu. It's just one way, not the
only way.

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

[frameworks-kdesu] [Bug 452532] kdesu not working after upgrade from Ubuntu 20.04 to 22.04

[Erich Eickmeyer]

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

--- Comment #13 from Erich Eickmeyer  ---
My 2c is this is something that KDE *should* fix in kdesu because it means that
kdesu has been taking advantage of an exploit in sudo for years, perhaps
decades. Basically, it's the same mechanism that the CVE exploits, and that's
not a good thing. To use a security hole for functionality sake, even if
unknown at the time, is generally bad practice.

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

[frameworks-kdesu] [Bug 452532] kdesu not working after upgrade from Ubuntu 20.04 to 22.04

[Erich Eickmeyer]

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

Erich Eickmeyer  changed:

   What|Removed |Added

 CC||eeickme...@ubuntu.com

--- Comment #2 from Erich Eickmeyer  ---
We have been noticing this behavior on Ubuntu for a few months, but the blame
was being passed to pkexec, not realizing that when, for instance, discover
launches software-properties-qt that it uses kdesu to do so. 

We have an open downstream bug report at https://launchpad.net/bugs/1965439

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

[frameworks-plasma] [Bug 454946] plasmashell crashes in Plasma::Applet::destroyedChanged() when switching between Global Theme desktop layouts

[Erich Eickmeyer]

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

--- Comment #8 from Erich Eickmeyer  ---
Still having this issue with 5.25.1, but I'm unable to provide a further
backtrace as drkonqi is also malfunctioning. However, the symptoms are exactly
the same.

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

[plasmashell] [Bug 456049] New: On multiple displays, when relogging or rebooting, widgets will move or resize

[Erich Eickmeyer]

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

Bug ID: 456049
   Summary: On multiple displays, when relogging or rebooting,
widgets will move or resize
   Product: plasmashell
   Version: 5.25.1
  Platform: Kubuntu Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Desktop Containment
  Assignee: plasma-b...@kde.org
  Reporter: eeickme...@ubuntu.com
CC: notm...@gmail.com
  Target Milestone: 1.0

SUMMARY

Signing out and back in with multiple monitors connected and/or setting a
different monitor to primary screen will move  widgets seemingly randomly based
on the system.

STEPS TO REPRODUCE
1. Connect to external monitor
2. Add widgets to desktop
3. Relog or reboot

OBSERVED RESULT

Widgets move to different location than originally placed

EXPECTED RESULT

Widgets remain in same place after relog or reboot

SOFTWARE/OS VERSIONS
Linux: Kubuntu 22.04
KDE Plasma Version: Plasma 5.25.1
KDE Frameworks Version: 5.95.0
Qt Version: 5.15.3

ADDITIONAL INFORMATION

Reported by Kubuntu Focus testers

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

[plasmashell] [Bug 456049] On multiple displays, when relogging or rebooting, widgets will move or resize

[Erich Eickmeyer]

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

--- Comment #1 from Erich Eickmeyer  ---
Created attachment 150202
  --> https://bugs.kde.org/attachment.cgi?id=150202&action=edit
Before relog or reboot 2 monitors

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

[plasmashell] [Bug 456049] On multiple displays, when relogging or rebooting, widgets will move or resize

[Erich Eickmeyer]

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

--- Comment #2 from Erich Eickmeyer  ---
Created attachment 150203
  --> https://bugs.kde.org/attachment.cgi?id=150203&action=edit
After relog or reboot 2 monitors

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

[plasmashell] [Bug 456049] On multiple displays, when relogging or rebooting, widgets will move or resize

[Erich Eickmeyer]

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

--- Comment #3 from Erich Eickmeyer  ---
Created attachment 150204
  --> https://bugs.kde.org/attachment.cgi?id=150204&action=edit
Before relog or reboot 4 monitors

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

[plasmashell] [Bug 456049] On multiple displays, when relogging or rebooting, widgets will move or resize

[Erich Eickmeyer]

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

--- Comment #4 from Erich Eickmeyer  ---
Created attachment 150205
  --> https://bugs.kde.org/attachment.cgi?id=150205&action=edit
After relog or reboot 4 monitors

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

[kontact] [Bug 457897] New: Kontact (or Kmail) hangs when selecting email, and crashes when closing

[Erich Eickmeyer]

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

Bug ID: 457897
   Summary: Kontact (or Kmail) hangs when selecting email, and
crashes when closing
   Product: kontact
   Version: unspecified
  Platform: Ubuntu Packages
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: eeickme...@ubuntu.com
  Target Milestone: ---

Application: kontact (5.20.3 (22.04.3))

Qt Version: 5.15.4
Frameworks Version: 5.96.0
Operating System: Linux 5.15.0-24-lowlatency x86_64
Windowing System: X11
Distribution: Ubuntu Kinetic Kudu (development branch)
DrKonqi: 5.25.4 [KCrashBackend]

-- Information about the crash:
Sometimes an email that has been filtered-out to another folder or otherwise
deleted from the inbox, it remains in the inbox. When this happens, selecting
it will cause the application to allow other emails to be selected, but the
application will hang and not display the email or open the email in a window.
Closing the application results in a crash.

The crash can be reproduced every time.

-- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault

[KCrash Handler]
#4  0x7fd388b7ceb8 in QScopedPointer >::operator-> (this=0x8) at
../../include/QtCore/../../src/corelib/tools/qscopedpointer.h:118
#5  qGetPtrHelper > > (ptr=...) at
../../include/QtCore/../../src/corelib/global/qglobal.h:1143
#6  QAction::d_func (this=0x0) at
../../include/QtWidgets/../../src/widgets/kernel/qaction.h:63
#7  QAction::setText (this=this@entry=0x0, text=...) at kernel/qaction.cpp:714
#8  0x7fd31fef44b2 in KMMainWidget::updateFolderMenu (this=0x55ec79c1c690)
at ./src/kmmainwidget.cpp:4037
#9  0x7fd31fefecc7 in KMMainWidget::setupActions (this=) at
./src/kmmainwidget.cpp:3399
#10 0x7fd31ff049e2 in KMMainWidget::KMMainWidget
(this=this@entry=0x55ec79c1c690, parent=parent@entry=0x55ec75400960,
aGUIClient=aGUIClient@entry=0x55ec7e31e5a0, actionCollection=,
config=...) at ./src/kmmainwidget.cpp:242
#11 0x7fd33425b2c7 in KMailPart::KMailPart (this=0x55ec7e31e570,
parentWidget=, parent=, __in_chrg=, __vtt_parm=) at ./src/kmail_part.cpp:69
#12 0x7fd33425b8b5 in KPluginFactory::createPartInstance
(parentWidget=0x7fd36c03c190, parent=0x7fd36c03c190, args=...) at
/usr/include/KF5/KCoreAddons/kpluginfactory.h:897
#13 0x7fd38921d172 in KPluginFactory::create(char const*, QWidget*,
QObject*, QList const&, QString const&) () from
/lib/x86_64-linux-gnu/libKF5CoreAddons.so.5
#14 0x7fd3893abaa7 in KPluginFactory::create (args=...,
parent=0x7fd36c03c190, this=0x55ec71a2af50) at
/usr/include/KF5/KCoreAddons/kpluginfactory.h:939
#15 KPluginFactory::instantiatePlugin (args=...,
parent=0x7fd36c03c190, data=...) at
/usr/include/KF5/KCoreAddons/kpluginfactory.h:509
#16 KontactInterface::Core::createPart (this=0x7fd36c03c190,
libname=0x55ec735e5588 "kmailpart") at ./src/core.cpp:70
#17 0x7fd3893ad0d2 in KontactInterface::Plugin::loadPart
(this=this@entry=0x55ec71889eb0) at ./src/plugin.cpp:129
#18 0x7fd3345dfc6a in KMailPlugin::createPart (this=0x55ec71889eb0) at
./src/kontactplugin/kmail/kmail_plugin.cpp:149
#19 0x7fd3893af0ac in KontactInterface::Plugin::part
(this=this@entry=0x55ec71889eb0) at ./src/plugin.cpp:140
#20 0x7fd3893dc2bb in Kontact::MainWindow::selectPlugin
(this=0x7fd36c03c190, plugin=0x55ec71889eb0) at ./src/mainwindow.cpp:552
#21 0x7fd3893dd8c4 in Kontact::MainWindow::loadSettings
(this=this@entry=0x7fd36c03c190) at ./src/mainwindow.cpp:681
#22 0x7fd3893e1cc8 in Kontact::MainWindow::initObject (this=0x7fd36c03c190)
at ./src/mainwindow.cpp:147
#23 0x7fd3893e2720 in Kontact::MainWindow::MainWindow (this=, this=) at ./src/mainwindow.cpp:84
#24 0x55ec7061e705 in KontactApp::activate (this=0x7ffd0f8977e0, args=...,
workingDir=...) at ./src/main.cpp:115
#25 0x7fd3893ab1be in KontactInterface::PimUniqueApplication::newInstance
(this=0x7ffd0f8977e0, startupId=..., arguments=..., workingDirectory=...) at
./src/pimuniqueapplication.cpp:174
#26 0x7fd3893ae2b7 in
KontactInterface::PimUniqueApplication::qt_static_metacall (_c=,
_id=, _a=0x7ffd0f897100, _o=0x7ffd0f8977e0) at
./obj-x86_64-linux-gnu/src/KF5KontactInterface_autogen/EWIEGA46WW/moc_pimuniqueapplication.cpp:87
#27 KontactInterface::PimUniqueApplication::qt_static_metacall
(_o=_o@entry=0x7ffd0f8977e0, _c=_c@entry=QMetaObject::InvokeMetaMethod,
_id=_id@entry=1, _a=_a@entry=0x7ffd0f897100) at
./obj-x86_64-linux-gnu/src/KF5KontactInterface_autogen/EWIEGA46WW/moc_pimuniqueapplication.cpp:79
#28 0x7fd3893ae3b3 in KontactInterface::PimUniqueApplication::qt_metacall
(this=0x7ffd0f8977e0, _c=QMetaObject::InvokeMetaMethod, _id=1,
_a=0x7ffd0f897100) at
./obj-x86_64-linux-gnu/src/KF5KontactInterface_autogen/EWIEGA46WW/moc_pimuniqueapplication.cpp:124
#29 0x7fd38914523b in QDBusConnectionPrivate::

[digikam] [Bug 457121] digikam 7.7.0 FTBFS against libavcodec59

[Erich Eickmeyer]

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

Erich Eickmeyer  changed:

   What|Removed |Added

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

--- Comment #7 from Erich Eickmeyer  ---
We decided a way forward is that we're going to have to package git snapshots
while we wait for official beta or final releases. Let me know if you would
like some testing done in the meantime, I'd be more than happy to help with
that. :)

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

[digikam] [Bug 457121] digikam 7.7.0 FTBFS against libavcodec59

[Erich Eickmeyer]

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

--- Comment #10 from Erich Eickmeyer  ---
Our problem in both Debian Unstable (sid) and Ubuntu Kinetic Kudu (Future
22.10, due in October) is that ffmpeg 4 simply no longer exists, therefore
7.8.0 is a no-go for us. Therefore, we must use the master code for 8.0.0, even
if incomplete.

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

[digikam] [Bug 457121] digikam 7.7.0 FTBFS against libavcodec59

[Erich Eickmeyer]

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

--- Comment #12 from Erich Eickmeyer  ---
(In reply to caulier.gilles from comment #11)
> Again, the decision to drop ffmpeg 4.x always maintained in favor to not
> mature yet ffmpeg 5 is typically dangerous. Not all clients code using
> ffmpeg API will not immediately switch to new API and perform regression
> cases.
> 
> Gilles Caulier

Of course, but I'm on the receiving end of this as much as you are. I'm a mere
packager and had no input in the decision to drop ffmpeg 4 in favor of ffmpeg
5. However, what's done is done, and this is what I have to work with.

Erich

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

[systemsettings] [Bug 453752] Effects Settings from XDG_CONFIG_DIRS are discarded when user clicks on [Defaults]

[Erich Eickmeyer]

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

Erich Eickmeyer  changed:

   What|Removed |Added

 CC||eeickme...@ubuntu.com

--- Comment #2 from Erich Eickmeyer  ---
On the contrary, Nate, this is something that should be inherited by
$XDG_CONFIG_DIRS in which case /usr/share/kubuntu-default-settings/kf5-settings
is added to the path by the distribution. Therefore, by adding a file with a
config to the aforementioned directory is inherently doing the same as adding
it to /etc/xdg since it is in the same $XDG_CONFIG_DIRS path, at least
according to the XDG spec.

This is, of course, unless KDE is deviating from the Open Desktop Guidelines
and not using the $XDG_CONFIG_DIRS system variable when searching for config
files.

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

[systemsettings] [Bug 453752] Effects Settings from XDG_CONFIG_DIRS are discarded when user clicks on [Defaults]

[Erich Eickmeyer]

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

Erich Eickmeyer  changed:

   What|Removed |Added

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

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

[systemsettings] [Bug 456956] New: Power script settings, perhaps other settings, from $XDG_CONFIG_DIRS are discarded when user clicks on Defaults

[Erich Eickmeyer]

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

Bug ID: 456956
   Summary: Power script settings, perhaps other settings, from
$XDG_CONFIG_DIRS are discarded when user clicks on
Defaults
   Product: systemsettings
   Version: 5.24.6
  Platform: Kubuntu Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: kcm_powerdevil
  Assignee: plasma-b...@kde.org
  Reporter: eeickme...@ubuntu.com
CC: k...@privat.broulik.de
  Target Milestone: ---

SUMMARY

If a distribution or OEM places a powermanaagementprofilesrc file in the path
defined in $XDG_CONFIG_DIRS, whether that's in /etc/xdg or otherwise, the
settings fail to propogate but get superseded by some kind of built-in
hardcoded mechanism as opposed to those that were defined by the distribution
or OEM. These settings should simply get written based on whatever the
hardcoded defaults are *unless* a default has been defined somewhere in the
$XDG_CONFIG_DIRS path (in this case,
~/.config/kdedefaults:/etc/xdg/xdg-plasma:/etc/xdg:/usr/share/kubuntu-default-settings/kf5-settings).

Additionally, a few GUI glitches occur, such as the checkbox getting rechecked
without anything in the script box, as well as a few other items that don't
make logical sense. You'll probably have to see for yourself as you work in the
steps to reproduce below.

STEPS TO REPRODUCE
1. Create a script in /usr/local/bin. I made one called
/usr/local/bin/HelloPopup with the following contents:

#! /bin/bash

kdialog --msgbox 'Hello World'

2. Add the following to /etc/xdg/powermanagement

[AC][RunScript]
idleTime=60
scriptCommand=/usr/local/bin/HelloPopup
scriptPhase=0

[Battery][RunScript]
idleTime=60
scriptCommand=/usr/local/bin/HelloPopup
scriptPhase=0

[LowBattery][RunScript]
idleTime=60
scriptCommand=/usr/local/bin/HelloPopup
scriptPhase=0

3. Create a new user.

4. Open System Settings > Power Management > Energy Saving

Notice all fields are correct, including script field.

5. Uncheck script field, click apply.

6. Switch to a different System Settings module and come back to Energy Saving.

7. Click "Defaults", click "Yes".

OBSERVED RESULT

Script field does not result in original default being applied.

EXPECTED RESULT

Script field goes back to original default.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Kubuntu 22.04
(available in About System)
KDE Plasma Version: 5.24.6
KDE Frameworks Version: 5.95.0
Qt Version: 5.13.3

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

[systemsettings] [Bug 456956] Power script settings, perhaps other settings, from $XDG_CONFIG_DIRS are discarded when user clicks on Defaults

[Erich Eickmeyer]

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

--- Comment #1 from Erich Eickmeyer  ---
In the steps to reproduce, step #2:

s/powermanagement/powermanagementrc

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

[systemsettings] [Bug 456956] Power script settings, perhaps other settings, from $XDG_CONFIG_DIRS are discarded when user clicks on Defaults

[Erich Eickmeyer]

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

--- Comment #2 from Erich Eickmeyer  ---
(In reply to Erich Eickmeyer from comment #1)
> In the steps to reproduce, step #2:
> 
> s/powermanagement/powermanagementrc

By that I meant powermanagementprofilesrc

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

[systemsettings] [Bug 456956] Power script settings, perhaps other settings, from $XDG_CONFIG_DIRS are discarded when user clicks on Defaults

[Erich Eickmeyer]

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

--- Comment #3 from Erich Eickmeyer  ---
(In reply to Erich Eickmeyer from comment #0)
> SUMMARY
> 
> If a distribution or OEM places a powermanaagementprofilesrc file in the
> path defined in $XDG_CONFIG_DIRS, whether that's in /etc/xdg or otherwise,
> the settings fail to propogate but get superseded by some kind of built-in
> hardcoded mechanism as opposed to those that were defined by the
> distribution or OEM. These settings should simply get written based on
> whatever the hardcoded defaults are *unless* a default has been defined
> somewhere in the $XDG_CONFIG_DIRS path (in this case,
> ~/.config/kdedefaults:/etc/xdg/xdg-plasma:/etc/xdg:/usr/share/kubuntu-
> default-settings/kf5-settings).
> 

This isn't entirely accurate. As in Step 3 of the Steps to Reproduce, the
initial propagation is there, it's just not there after the steps are taken in
the Steps to Reproduce.

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

[systemsettings] [Bug 456956] Power script settings, perhaps other settings, from $XDG_CONFIG_DIRS are discarded when user clicks on Defaults

[Erich Eickmeyer]

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

--- Comment #4 from Erich Eickmeyer  ---
Issue is also present in Plasma 5.25.3

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

[frameworks-kglobalaccel] [Bug 456958] New: kglobalshortcutsrc does not propagate via $XDG_CONFIG_DIRS

[Erich Eickmeyer]

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

Bug ID: 456958
   Summary: kglobalshortcutsrc does not propagate via
$XDG_CONFIG_DIRS
   Product: frameworks-kglobalaccel
   Version: 5.95.0
  Platform: Kubuntu Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdelibs-b...@kde.org
  Reporter: eeickme...@ubuntu.com
  Target Milestone: ---

SUMMARY

If a distribution or OEM places a kglobalshortcuts file in the path defined in
$XDG_CONFIG_DIRS, whether that's in /etc/xdg or otherwise, the settings fail to
propogate but get superseded by some kind of built-in hardcoded mechanism as
opposed to those that were defined by the distribution or OEM. These settings
should simply get written based on whatever the hardcoded defaults are *unless*
a default has been defined somewhere in the $XDG_CONFIG_DIRS path (in this
case,
~/.config/kdedefaults:/etc/xdg/xdg-plasma:/etc/xdg:/usr/share/kubuntu-default-settings/kf5-settings).


STEPS TO REPRODUCE
1. Create a /etc/xdg/kglobalshortcutsrc file containing the following:

[kwin]
Decrease Opacity=Meta+_,,Decrease Opacity of Active Window by 5 %
Increase Opacity=Meta++,,Increase Opacity of Active Window by 5 %


2. Create a new user. 
3. Login as new user.
4. Open Dolphin.
5. Attempt to decrease and increase opacity with Meta-Shift-+ or Meta-Shift-=.

OBSERVED RESULT
Shortcut keys have no effect. Corresponding setting in System Settings >
Shortcuts > Shortcuts > KWin shows "No active shortcuts.

EXPECTED RESULT
Shortcut keys should change opacity of the active window and be set to do so by
default. This should be able to be verified via System Settings > Shortcuts >
Shortcuts > KWin.

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

ADDITIONAL INFORMATION
Without a way for distributions and OEMs to set hardware or distribution-unique
shortcuts, this limits the customization capabilities of KDE Plasma to be
custom pre-configured.

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

[systemsettings] [Bug 453752] Effects Settings from XDG_CONFIG_DIRS are discarded when user clicks on [Defaults]

[Erich Eickmeyer]

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

Erich Eickmeyer  changed:

   What|Removed |Added

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

--- Comment #4 from Erich Eickmeyer  ---
That's exactly what Michael was referring to is that even when a file named
"kwinrc" is in that path with those contents, it has no effect when "Defaults"
is selected. The initial configuration is honored, but when "Defaults" is
selected, it no longer gathers the defaults from the $XDG_CONFIG_DIRS path.

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

[systemsettings] [Bug 453752] Effects Settings from XDG_CONFIG_DIRS are discarded when user clicks on [Defaults]

[Erich Eickmeyer]

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

--- Comment #6 from Erich Eickmeyer  ---
No, my testing involved using /etc/xdg directly. It's simply not inheriting
$XDG_CONFIG_DIRS paths.

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

[systemsettings] [Bug 453752] Effects Settings from XDG_CONFIG_DIRS are discarded when user clicks on [Defaults]

[Erich Eickmeyer]

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

--- Comment #7 from Erich Eickmeyer  ---
(In reply to Erich Eickmeyer from comment #6)
> No, my testing involved using /etc/xdg directly. It's simply not inheriting
> $XDG_CONFIG_DIRS paths.

Rather, my testing involved both directories.

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

[frameworks-kglobalaccel] [Bug 456958] kglobalshortcutsrc does not propagate via $XDG_CONFIG_DIRS

[Erich Eickmeyer]

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

--- Comment #4 from Erich Eickmeyer  ---
(In reply to Nate Graham from comment #3)
> There may be a second issue here; my ~/.config/kglobalaccelrc file has
> entries for all shortcuts written to it, even those with empty shortcuts. So
> for example my file has:
> 
> Decrease Opacity=none,,Decrease Opacity of Active Window by 5 %
> Increase Opacity=none,,Increase Opacity of Active Window by 5 %
> 
> This will override any default settings at a lower level because user
> settings take precedence over systemwide settings.

If ${setting}=none, shouldn't it look for a setting up the path until it finds
one to fill the gap? Seems like if it's writing that, it would prevent any
default from being configured ever.

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

[digikam] [Bug 457121] New: digikam 7.7.0 FTBFS against libavcodec59

[Erich Eickmeyer]

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

Bug ID: 457121
   Summary: digikam 7.7.0 FTBFS against libavcodec59
   Product: digikam
   Version: 7.7.0
  Platform: Ubuntu Packages
OS: Linux
Status: REPORTED
  Severity: grave
  Priority: NOR
 Component: Portability-Compilation
  Assignee: digikam-bugs-n...@kde.org
  Reporter: eeickme...@ubuntu.com
  Target Milestone: ---

SUMMARY

Digikam 7.7.0 has completely failed to build from source against all
architectures supported by Ubuntu when built against libavcodec59. Apparently
the compiler in both Ubuntu and Debian has been spitting-out compiler
deprication warnings with previous ffmpeg releases for some time now.

>From the logs:

/<>/core/libs/threadimageio/video/videodecoder_p.cpp: In member
function ‘bool Digikam::VideoDecoder::Private::initializeVideo()’:
/<>/core/libs/threadimageio/video/videodecoder_p.cpp:93:49: error:
invalid conversion from ‘const AVCodec*’ to ‘AVCodec*’ [-fpermissive]
   93 | pVideoCodec   =
avcodec_find_decoder(pVideoCodecParameters->codec_id);
  |
^
  | |
  | const AVCodec*
make[3]: ***
[core/libs/threadimageio/CMakeFiles/core_threadimageio_obj.dir/build.make:443:
core/libs/threadimageio/CMakeFiles/core_threadimageio_obj.dir/video/videodecoder_p.cpp.o]
Error 1
make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu'


STEPS TO REPRODUCE
1. Attempt to build binary package using source package in Ubuntu's launchpad
infrastructure

OBSERVED RESULT
All binary packages in all architectures fail to build.

EXPECTED RESULT
All binary packages in all architectures build.

SOFTWARE/OS VERSIONS
Linux: Ubuntu 22.10

ADDITIONAL INFORMATION
amd64 log:
https://launchpad.net/ubuntu/+source/digikam/4:7.7.0-2ubuntu2/+build/24183396
Other build logs available at
https://launchpad.net/ubuntu/+source/digikam/4:7.7.0-2ubuntu2

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

[digikam] [Bug 457121] digikam 7.7.0 FTBFS against libavcodec59

[Erich Eickmeyer]

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

--- Comment #2 from Erich Eickmeyer  ---
(In reply to caulier.gilles from comment #1)
> From a developer viewpoint, FFMpeg 4.x LTS is robust and work very well. I
> recommend to not switch to ffmpeg 5 in production for the moment.

Well, we don't really have much choice. Debian, and therefore Ubuntu, is moving
to ffmpeg 5. So, this is a distribution-level decision and not one that can be
overridden.

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

[digikam] [Bug 457121] digikam 7.7.0 FTBFS against libavcodec59

[Erich Eickmeyer]

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

--- Comment #3 from Erich Eickmeyer  ---
(In reply to caulier.gilles from comment #1)
> digiKam 8.x ==> ffmpeg 4.x or 5.x (code compile with ffmpeg 5.x but it not
> yet suitable for production).

If you have at any point a pre-release for digiKam 8.x, please advise. As it
stands currently, 7.7.0 cannot be released in Ubuntu 22.10 in October. Feature
Freeze comes end of August, at which point it's likely we'll have to eject
digiKam from the repository for the FTBFS issue unless we can get that resolved
via a patch.

I'm the leader of the Ubuntu Studio flavor, and digiKam is our premiere photo
management application. I really don't want to lose it, so I'm trying to find
solutions to this issue sooner rather than later.

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

[digikam] [Bug 457121] digikam 7.7.0 FTBFS against libavcodec59

[Erich Eickmeyer]

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

--- Comment #5 from Erich Eickmeyer  ---
(In reply to caulier.gilles from comment #4)
> Hi Erich,
> 
> The solution for you is to use 7.x as well. If ffmpeg 5.x is present, the
> Media Player support will be disabled at configuration time. Of course you
> will not able to play with video files (aka thumbnails and preview will be
> unavailable).

In our packaging we simply had forced it with "DENABLE_MEDIAPLAYER=ON" in our
debian/rules file, and removing that enabled it to build in my PPA. I'm working
with one of our more senior Ubuntu developers to see if we should proceed with
that route, or if he wants to do a manual patch to port it over to ffmpeg5 as
he has more experience with that than I do.

> For 8.x, the plan is to release before end of this year and if projects
> advance well, to include the both GoSC 2022 tasks in this release. We will
> see.
> 
> https://community.kde.org/GSoC/2022/Ideas#digiKam
> 

That will likely not make it in time for 22.10, but will likely make it for
23.04 in April 2023.

> 8.x will be also compatible with Qt 6, but i do not recommend to use Qt6 for
> the moment. 8.x will be compatible with Qt5 LTS, so this version rock well.

I don't foresee the transition to Qt6 for some time.

> About the 8.x pending list bugs, we have the famous Media Player code to
> finalize with ffmpeg 5.x, and other regression checks to verify. For ex, we
> will progressively switch metadata write operations to ExifTool instead
> Exiv2, as this last library break regression tests more and more. ExifTool
> write feature have been introduced in 8.x only. We need to check
> performances and suitability.
> 
> Don't forget the bundles that we provide, as AppImage which still compiled
> with ffmpeg 4.x. There are 2 versions: one build by the team, other one
> build with KDE infrastructure.

Appimages cannot be packaged in Ubuntu under any circumstances.. However, there
is a snap which, if a couple of things were tweaked, could be seeded. However,
I think we might have a solution with the .deb package whether it's the port or
the mediaplayer disable.

> The first one is provided since a very long time and is very powerful and
> complete. It's based on 7.x code.
> 
> https://files.kde.org/digikam/
> 
> The second one need to be finalized as it do not support Mysql/mariadb
> database. It based on 8.x code. Some links:
> 
> https://binary-factory.kde.org/view/AppImage/job/Digikam_Nightly_appimage-
> centos7/

Remember, I'm coming at this from a packaging/distribution perspective, so I'm
looking for pre-release code as opposed to pre-release compiled/executable
code. If we can get it in to the repository prior to our Feature Freeze, then
that negates the need for a Feature Freeze Exception when a digiKam final
release would come later as it would be considered a bugfix.

Thanks for your time, Gilles. I really appreciate it. If you have any other
info, that would be helpful.

Erich

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

[kscreenlocker] [Bug 457284] New: Lock screen shows black on Nvidia hardware

[Erich Eickmeyer]

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

Bug ID: 457284
   Summary: Lock screen shows black on Nvidia hardware
   Product: kscreenlocker
   Version: 5.25.3
  Platform: Kubuntu Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: eeickme...@ubuntu.com
CC: bhus...@gmail.com
  Target Milestone: ---

SUMMARY
Lock screen shows black on Nvidia hardware. We did not see the same result on
intel hardware with the same setup.


STEPS TO REPRODUCE
1. Instal KDE 5.25.2 and 22.04 Jammy Jellyfish on a kubuntu focus system and
reboot
2. Close the lid of the laptop and wait ~5 seconds for it to go to sleep
3. Open the lid and the lock screen should show up with a black background

OBSERVED RESULT

Lock screen has a black background because no background is selected

EXPECTED RESULT

Lock screen should should have a background selected

SOFTWARE/OS VERSIONSLinux/KDE Plasma: Kubuntu 22.04 / 5.25.2
KDE Plasma Version: 5.25.2
KDE Frameworks Version: 5.95.0
Qt Version: 5.15.3

ADDITIONAL INFORMATION

Occured on nvidia hardware, did not occur on intel hardware.

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

[kscreenlocker] [Bug 457284] Lock screen shows black on Nvidia hardware

[Erich Eickmeyer]

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

--- Comment #2 from Erich Eickmeyer  ---
(In reply to Nate Graham from comment #1)
> Do you see the interactive UI elements for the lock screen, or is the entire
> screen black?

The UI elements are there and it is interactive.

> Can you move the cursor?

Cursor is active.

The only issue is the background is black.

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

[kwin] [Bug 457284] Lock screen wallpaper is all black on Nvidia hardware

[Erich Eickmeyer]

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

--- Comment #4 from Erich Eickmeyer  ---
(In reply to Nate Graham from comment #3)
> Thanks. Moving to KWin since it seems like this is probably a graphics
> issue. Possibly even an issue with the NVIDIA drivers.
> 
> Does it reproduce with both Wayland and X11?

We are unable to even launch Wayland under 5.25.x as it immediately crashes on
our Nvidia hardware. That might be a separate bug.

> Does this happen on the desktop too, or just the lock screen?

It's just the lock screen.

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

[Discover] [Bug 432513] New: Discover/Packagekit appears to be marking packages as manually installed

[Erich Eickmeyer]

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

Bug ID: 432513
   Summary: Discover/Packagekit appears to be marking packages as
manually installed
   Product: Discover
   Version: 5.18.5
  Platform: Ubuntu Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: PackageKit
  Assignee: lei...@leinir.dk
  Reporter: er...@ericheickmeyer.com
CC: aleix...@kde.org
  Target Milestone: ---

SUMMARY
With the machines I help administer, we have been finding situations where the
/boot directory is filling-up beyond 3 kernels on LUKS encrypted systems. apt
autoremove is not removing old kernels as expected, nor is unattended-upgrades
on the Ubuntu machines picking-up on the removable kernels.

We have had a system with as many as 15 kernel packages installed as a result
of this not working as expected.

The majority of these machines are using Discover to do their package
upgrading, which uses PackageKit as its backend.

This has led us to believe that Discover and Packagekit are possibly marking
apt packages that should be marked as "auto" as "manual". We were able to get
unattended-upgrades to to the trick and "apt autoremove" to do its job by using
"apt-mark auto linux-image-${version}-generic). However, this manual
intervention should not be required.

Per this downstream bug, we have confirmed that the problem does not lie in apt
nor unattended-upgrades.

STEPS TO REPRODUCE
1. Run Kubuntu normally on a LUKS encrypted system
2. Wait a few upgrades on the kernels over time
3. Kernels do not get automatically removed and /boot partition fills-up.

OBSERVED RESULT
Boot partition gets full blocking further upgrades of any packages. Unused/old
kernel images do not get automatically removed. Investigation shows new kernel
versions are marked as manually installed.

EXPECTED RESULT
Unused kernel images should be automatically removed upon reboot and/or using
"apt autoremove". Applications installed from a metapackage (case in point,
linux-image-generic) should be marked as auto-installed, allowing the
autoremove process to work as expected.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Ubuntu 20.04 LTS
(available in About System)
KDE Plasma Version: 5.18.5
KDE Frameworks Version: 5.68.0
Qt Version: 5.12.8

ADDITIONAL INFORMATION

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

[Discover] [Bug 432513] Discover/Packagekit appears to be marking packages as manually installed

[Erich Eickmeyer]

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

--- Comment #1 from Erich Eickmeyer  ---
Downstream bug: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1914278

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

[Discover] [Bug 432513] Discover/Packagekit appears to be marking packages as manually installed

[Erich Eickmeyer]

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

Erich Eickmeyer  changed:

   What|Removed |Added

 CC||eeickme...@ubuntu.com

--- Comment #2 from Erich Eickmeyer  ---
Apparently this is an upstream bug in Packagekit:
https://github.com/PackageKit/PackageKit/issues/450

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

[digikam] [Bug 463439] New: Build system requires external git source

[Erich Eickmeyer]

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

Bug ID: 463439
   Summary: Build system requires external git source
Classification: Applications
   Product: digikam
   Version: 8.0.0
  Platform: Ubuntu
OS: Linux
Status: REPORTED
  Severity: major
  Priority: NOR
 Component: general
  Assignee: digikam-bugs-n...@kde.org
  Reporter: eeickme...@ubuntu.com
  Target Milestone: ---

SUMMARY

This was an attempt to include the 8.0.0-beta1 for Ubuntu Lunar Lobster, future
release 23.04. Regardless of environment, this issue would happen even in a
stable release.

During an atempt to build from the tarball for 8.0.0-beta1, the Launchpad build
system failed to build from source as it is (intentionally) unable to download
from external sources. Note that this would be the same for Debian as well.
Please include the unit tests in the source tarball as well so that
distributions can properly test the beta.

Note that we would like these unit tests if they are automated since debhelper
typically will run test suites at the end of the build process, typically by
invoking "make test".

STEPS TO REPRODUCE

Attempt to package from official tarball using offiical Debian packaging
guidelines invoking Debhelper

OBSERVED RESULT

Failed to build from source:

git clone https://invent.kde.org/graphics/digikam-test-data.git
/<>/test-data
/bin/sh: 1: git: not found

(note: installing git as a build dependency would not resolve this as git would
be unable to download in this environment)

Complete build log at
https://launchpadlibrarian.net/642172379/buildlog_ubuntu-lunar-amd64.digikam_4%3A8.0.0~beta1-0ubuntu1~ppa1_BUILDING.txt.gz

EXPECTED RESULT

Complete build without invoking git to download unit tests from an external
source.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma:  Ubuntu Lunar Lobster Development Environment (Future 23.04)

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

[digikam] [Bug 463439] Build system requires external git source

[Erich Eickmeyer]

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

--- Comment #2 from Erich Eickmeyer  ---
(In reply to caulier.gilles from comment #1)
> The external git repository is delegate to host unit tests data.
> 
> To drop this extra dependency, just disable unit test build with cmake
> option -DBUILD_TESTING=OFF
> 
> Gilles Caulier

Thanks, that just leaves the concern that our auto package tests (and Debian's)
will have no test suite to run against. These tests are written and included by
the upstream developers and our test systems make sure that the packages are
correctly tested. This leaves a void in that system. Nearly every other KDE
package includes this, so I'm puzzled as to why the deviation.

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

[kwin] [Bug 457284] Lock screen wallpaper is all black after waking from sleep

[Erich Eickmeyer]

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

--- Comment #31 from Erich Eickmeyer  ---
Finally on Plasma 5.26.1. So far, I have not seen this bug appear, so I'm very
close to marking this as fixed, but I want to do a little more testing before
closing.

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

[kwin] [Bug 457284] Lock screen wallpaper is all black after waking from sleep

[Erich Eickmeyer]

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

Erich Eickmeyer  changed:

   What|Removed |Added

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

--- Comment #32 from Erich Eickmeyer  ---
Confirmed bug is gone as of 5.26.1. Thanks!

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

[kscreenlocker] [Bug 455738] KScreenLocker with black screen after some minutes in sleep

[Erich Eickmeyer]

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

Erich Eickmeyer  changed:

   What|Removed |Added

 CC||eeickme...@ubuntu.com
 Resolution|--- |DUPLICATE
 Status|REPORTED|RESOLVED

--- Comment #3 from Erich Eickmeyer  ---


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

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

[kwin] [Bug 457284] Lock screen wallpaper is all black after waking from sleep

[Erich Eickmeyer]

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

Erich Eickmeyer  changed:

   What|Removed |Added

 CC||higor...@gmail.com

--- Comment #33 from Erich Eickmeyer  ---
*** Bug 455738 has been marked as a duplicate of this bug. ***

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

[Breeze] [Bug 431712] New: Breeze-Dark GTK: Incorrect colors in Evolution

[Erich Eickmeyer]

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

Bug ID: 431712
   Summary: Breeze-Dark GTK: Incorrect colors in Evolution
   Product: Breeze
   Version: 5.18.5
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: gtk theme
  Assignee: uhh...@gmail.com
  Reporter: er...@ericheickmeyer.com
CC: plasma-b...@kde.org
  Target Milestone: ---

Created attachment 134947
  --> https://bugs.kde.org/attachment.cgi?id=134947&action=edit
Breeze-Dark GTK on Evolution

SUMMARY

The Breeze-Dark GTK theme is rendering incorrectly in the Account Setup Wizard
of Evolution. Attached are two examples: one using Breeze-Dark, the other using
Adwaita-Dark.

STEPS TO REPRODUCE
1. Set GTK 3 theme to Breeze Dark, make sure Breeze Dark colors are selected.
2. Run evoluton. Observe account setup window.
3. If Evolution has been run before, Go to File > New > Mail Account

OBSERVED RESULT

White text on white background can be observed in the left pane of the wizard.
EXPECTED RESULT

White text on a dark background should be observed.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Kubuntu 20.04 LTS
(available in About System)
KDE Plasma Version: 5.18.5
KDE Frameworks Version: 5.68
Qt Version: 5.12.8

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

[Breeze] [Bug 431712] Breeze-Dark GTK: Incorrect colors in Evolution

[Erich Eickmeyer]

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

--- Comment #1 from Erich Eickmeyer  ---
Created attachment 134948
  --> https://bugs.kde.org/attachment.cgi?id=134948&action=edit
Adwaita-Dark on Evolution

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

[Breeze] [Bug 431712] Breeze-Dark GTK: Incorrect colors in Evolution

[Erich Eickmeyer]

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

--- Comment #3 from Erich Eickmeyer  ---
That cannot be done. The newest version of the theme simply won't install. And
since this is on the LTS version of Plasma (5.18), it really needs to be fixed
in that branch.

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

[Breeze] [Bug 431712] Breeze-Dark GTK: Incorrect colors in Evolution

[Erich Eickmeyer]

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

--- Comment #4 from Erich Eickmeyer  ---
Created attachment 134969
  --> https://bugs.kde.org/attachment.cgi?id=134969&action=edit
Breeze GTK on Evolution

Also discovered it's occurring on the standard (light) version of the theme,
just inverted.

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

[Breeze] [Bug 431712] Breeze-Dark GTK: Incorrect colors in Evolution

[Erich Eickmeyer]

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

Erich Eickmeyer  changed:

   What|Removed |Added

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

--- Comment #5 from Erich Eickmeyer  ---
(In reply to Jan Blackquill (Carson Black) from comment #2)
> Doesn't seem to be reproducible on latest Breeze GTK for me. Can you try
> using the latest release version and see if this is still reproducible on it
> for you?

The latest version of the Breeze GTK theme requires a newer version of GTK than
is available in the Ubuntu 20.04 LTS repos. Since Plasma 5.18 is an LTS,
whatever fix was done to the Breeze GTK theme in the latest version needs to be
cherry-picked back to the LTS version. As you can see per the attachments, this
isn't a bug in GTK since using Adwaita-Dark makes things show-up as expected.
Additionally, I have tried with the Materia theme and this issue is also not
present, which means the issue is in the Breeze theme.

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

[kontact] [Bug 405695] New: Crash while opening Contact Settings

[Erich Eickmeyer]

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

Bug ID: 405695
   Summary: Crash while opening Contact Settings
   Product: kontact
   Version: 5.10.3
  Platform: Ubuntu Packages
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: eeickme...@ubuntu.com
  Target Milestone: ---

Application: kontact (5.10.3)

Qt Version: 5.11.3
Frameworks Version: 5.56.0
Operating System: Linux 5.0.0-7-generic x86_64
Distribution: Ubuntu Disco Dingo (development branch)

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

Attempting to open Kontact settings (Settings > Configure Kontact)

Reproducible every time.

Ubuntu 19.04 Disco Dingo (pre-release)

The crash can be reproduced every time.

-- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fbdf24f8f40 (LWP 8505))]

Thread 52 (Thread 0x7fbd8e7fc700 (LWP 23596)):
#0  0x7fbdf229a916 in futex_reltimed_wait_cancelable (private=, reltime=0x7fbd8e7fb3c0, expected=0, futex_word=0x7fbd8e7fb5a8) at
../sysdeps/unix/sysv/linux/futex-internal.h:142
#1  0x7fbdf229a916 in __pthread_cond_wait_common (abstime=0x7fbd8e7fb460,
mutex=0x7fbd8e7fb558, cond=0x7fbd8e7fb580) at pthread_cond_wait.c:533
#2  0x7fbdf229a916 in __pthread_cond_timedwait (cond=0x7fbd8e7fb580,
mutex=0x7fbd8e7fb558, abstime=0x7fbd8e7fb460) at pthread_cond_wait.c:667
#3  0x7fbdebf8fa47 in  () at /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#4  0x7fbdebf9231a in  () at /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#5  0x7fbdebf92402 in  () at /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#6  0x7fbdebf96991 in  () at /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#7  0x7fbdebf97c8f in  () at /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#8  0x7fbdebfa0c91 in  () at /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#9  0x7fbdf2294182 in start_thread (arg=) at
pthread_create.c:486
#10 0x7fbdf34a8faf in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 51 (Thread 0x7fbca7dd2700 (LWP 23595)):
#0  0x7fbdf229a916 in futex_reltimed_wait_cancelable (private=, reltime=0x7fbca7dd13c0, expected=0, futex_word=0x7fbca7dd15a8) at
../sysdeps/unix/sysv/linux/futex-internal.h:142
#1  0x7fbdf229a916 in __pthread_cond_wait_common (abstime=0x7fbca7dd1460,
mutex=0x7fbca7dd1558, cond=0x7fbca7dd1580) at pthread_cond_wait.c:533
#2  0x7fbdf229a916 in __pthread_cond_timedwait (cond=0x7fbca7dd1580,
mutex=0x7fbca7dd1558, abstime=0x7fbca7dd1460) at pthread_cond_wait.c:667
#3  0x7fbdebf8fa47 in  () at /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#4  0x7fbdebf9231a in  () at /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#5  0x7fbdebf92402 in  () at /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#6  0x7fbdebf96991 in  () at /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#7  0x7fbdebf97e71 in  () at /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#8  0x7fbdebfa0c91 in  () at /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#9  0x7fbdf2294182 in start_thread (arg=) at
pthread_create.c:486
#10 0x7fbdf34a8faf in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 50 (Thread 0x7fbc9e10f700 (LWP 18686)):
#0  0x7fbdf229a916 in futex_reltimed_wait_cancelable (private=, reltime=0x7fbc9e10e3c0, expected=0, futex_word=0x7fbc9e10e5a8) at
../sysdeps/unix/sysv/linux/futex-internal.h:142
#1  0x7fbdf229a916 in __pthread_cond_wait_common (abstime=0x7fbc9e10e460,
mutex=0x7fbc9e10e558, cond=0x7fbc9e10e580) at pthread_cond_wait.c:533
#2  0x7fbdf229a916 in __pthread_cond_timedwait (cond=0x7fbc9e10e580,
mutex=0x7fbc9e10e558, abstime=0x7fbc9e10e460) at pthread_cond_wait.c:667
#3  0x7fbdebf8fa47 in  () at /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#4  0x7fbdebf9231a in  () at /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#5  0x7fbdebf92402 in  () at /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#6  0x7fbdebf96991 in  () at /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#7  0x7fbdebf97e71 in  () at /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#8  0x7fbdebfa0c91 in  () at /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#9  0x7fbdf2294182 in start_thread (arg=) at
pthread_create.c:486
#10 0x7fbdf34a8faf in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 49 (Thread 0x7fbc9e910700 (LWP 9509)):
#0  0x7fbdf229a916 in futex_reltimed_wait_cancelable (private=, reltime=0x7fbc9e90f3c0, expected=0, futex_word=0x7fbc9e90f5a8) at
../sysdeps/unix/sysv/linux/futex-internal.h:142
#1  0x7fbdf229a916 in __pthread_cond_wait_common (abstime=0x7fbc9e90f460,
mutex=0x7fbc9e90f558, cond=0x7fbc9e90f580) at pthread_cond_wait.c:533
#2  0x7fbdf229a916

[kontact] [Bug 405695] Crash while opening Kontact Settings

[Erich Eickmeyer]

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

Erich Eickmeyer  changed:

   What|Removed |Added

 CC|eeickme...@ubuntu.com   |

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

[kontact] [Bug 405695] Crash while opening Kontact Settings

[Erich Eickmeyer]

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

Erich Eickmeyer  changed:

   What|Removed |Added

 CC||eeickme...@ubuntu.com

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

[kontact] [Bug 405695] Crash while opening Kontact Settings

[Erich Eickmeyer]

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

Erich Eickmeyer  changed:

   What|Removed |Added

Summary|Crash while opening Contact |Crash while opening Kontact
   |Settings|Settings

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

[systemsettings] [Bug 421240] New: Create a way to set a variable for downstreams to customize default GTK theme

[Erich Eickmeyer]

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

Bug ID: 421240
   Summary: Create a way to set a variable for downstreams to
customize default GTK theme
   Product: systemsettings
   Version: 5.18.4
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: kcm_style
  Assignee: plasma-b...@kde.org
  Reporter: er...@ericheickmeyer.com
CC: zom...@protonmail.com
  Target Milestone: ---

SUMMARY
Currently, barring using /etc/skel, there is no way to set the default GTK
theme for downstream Linux distributions. In my case, Ubuntu Studio, we use the
Materia theme by default. We wish to make it the default for GTK and Qt
applications, which I can do for Qt, but not for GTK.

STEPS TO REPRODUCE
Attempt to set default GTK theme via $XDG_CONFIG_DIRS/gtk-3.0/settings.ini
and/or $XDG_CONFIG_DIR/.gtkrc-2.0


OBSERVED RESULT
Settings are completely ignored, defaults to Breeze theme.

EXPECTED RESULT
Settings default to theme set in $XDG_CONFIG_DIRS/gtk-3.0/settings.ini and/or
$XDG_CONFIG_DIRS/.gtkrc-2.0

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Ubuntu 20.04 LTS
(available in About System)
KDE Plasma Version: 5.18.4
KDE Frameworks Version: 5.68.0
Qt Version: 5.12.8

ADDITIONAL INFORMATION
I'm the Ubuntu Studio lead, and, while not completely barring our transition to
KDE Plasma, this does create an issue for users that hit the "default" button
and it defaults to Breeze. Currently, I'm having to use /etc/skel to set the
default for new user accounts, which is far from ideal.

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

[Powerdevil] [Bug 389991] Sleep key no longer initiates sleep

[Erich Eickmeyer]

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

Erich Eickmeyer  changed:

   What|Removed |Added

 CC||er...@ericheickmeyer.com

--- Comment #7 from Erich Eickmeyer  ---
Upgraded Kubuntu to Plasma 5.12, had the same problem with the brightness keys
(both screen and keyboard) on my 2011 MacBook Pro. Workaround fix was to fix
the global keyboard shortcuts in power management by custom-assigning the
respective functions to the correct keys. It pops up dialogs saying there's a
conflict. Do it twice and it will realize that the button you're using is the
default and assign it accordingly.

Seems as though the global shortcut mapping is getting confused between
releases specifically as it comes to power management control.

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

[Welcome Center] [Bug 499555] New: Feature Request: Ability to customize or remove default pages

[Erich Eickmeyer]

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

Bug ID: 499555
   Summary: Feature Request: Ability to customize or remove
default pages
Classification: Applications
   Product: Welcome Center
   Version: unspecified
  Platform: Ubuntu
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: eeickme...@ubuntu.com
CC: n...@kde.org, olib...@outlook.com
  Target Milestone: ---

Created attachment 177996
  --> https://bugs.kde.org/attachment.cgi?id=177996&action=edit
Ubuntu Studio Desktop Thumbnail

SUMMARY

As discussed in
https://discuss.kde.org/t/customizing-the-welcome-center-for-distros/29286,
Ubuntu Studio has a different layout for its desktop (see screenshot thumbnail
attached) and would need to change SimpleByDefault.qml to match. 

Additionally, as this is launched by Plasma itself and not via a systemd unit,
command line options to skip pages (show certain pages by default) will not
work.

Unfortunately to do what is needed would require forking the package with a
patch which is not ideal.

Therefore, this feature request is for customizations or overrides of all
pages, perhaps via /usr/share/plasma/plasma-welcome/{matching page name}.qml.
Granted the contents of the introduction page can be overridden via a .desktop
file, but that's still very restricting compared to a wholesale override via
QML. However, if the .desktop file override is the only way, then more than one
so that other pages can be overridden would be wonderful.

STEPS TO REPRODUCE

N/A

OBSERVED RESULT

N/A

EXPECTED RESULT

N/A

SOFTWARE/OS VERSIONS
Operating System: Ubuntu Studio 25.04
KDE Plasma Version: 6.2.91
KDE Frameworks Version: 6.10.0
Qt Version: 6.8.1

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

[Welcome Center] [Bug 499555] Feature Request: Ability to customize or remove default pages

[Erich Eickmeyer]

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

--- Comment #4 from Erich Eickmeyer  ---
(In reply to Oliver Beard from comment #3)
> Could you make a list of changes/deviations that would need to be supported
> for Ubuntu Studio's Welcome Center to fit in perfectly?

Really, the only thing we need at this time is the ability to replace or modify
SimpleWhenNeeded.qml as it's the only real showstopper. That said, if that can
be handled, then there's probably no reason why they cannot all be handled from
my perspective, which is somewhat limited in that regard as it might be a much
larger project than what my limited knowledge on it might anticipate.

The other thing is, by default, the original introduction page defaults to
getting the distribution name from the distro, which is not necessarily the
flavor name (Kubuntu and Ubuntu Studio both show as Ubuntu). I saw where it is
getting that information, and that's not something we can (or should) change
for the sake of this. This, however, is easily mitigated by the .desktop file
mentioned in the README.md.

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

[Welcome Center] [Bug 499555] Feature Request: Ability to customize or remove default pages

[Erich Eickmeyer]

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

--- Comment #2 from Erich Eickmeyer  ---
(In reply to Oliver Beard from comment #1)
> We definitely plan to support customising the pages shown with more
> precision than the current distro pages system offers.
> 
> For this, though, we definitely need customisation of the existing pages,
> including declaratively changing the background, panel position, panel
> floating, and widget order (and presence). I can certainly add this.
> 
> What you can do, for now, is to patch the QML. It *should* be relatively
> simple to change the anchors for the mock panel to place it at the top, and
> the background is only in a few places if you'd like to change that as well.

Right, we can patch the QML, but Kubuntu doesn't desire that (we share all of
the same packages, no additional repos). It would require patching-out *all* or
some of the QML and replacing it with custom pages defined in a separate
settings package (the 01-*.qml extended pages). The unfortunate part is that
will make it out-of-order.

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

[Discover] [Bug 481993] Discover fails to launch after upgrade to Neon 6.0

[Erich Eickmeyer]

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

Erich Eickmeyer  changed:

   What|Removed |Added

 CC||eeickme...@ubuntu.com

--- Comment #33 from Erich Eickmeyer  ---
This same thing is happening again in Discover 6.2.91

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