[dolphin] [Bug 434130] New: Copy doesn't work from USB-Drive to Harddrive

[Attila]

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

Bug ID: 434130
   Summary: Copy doesn't work from USB-Drive to Harddrive
   Product: dolphin
   Version: 20.12.2
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: grave
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: bugs.kde.att...@online.de
CC: kfm-de...@kde.org
  Target Milestone: ---

SUMMARY
WHen I copy one file from USB-Drive to Harddrive, it won't be completed. The
progress dialog doesn't finish. However the file is copied. Then I click on
"Cancel" to close the progress dialog.

Copying more than one file doesn't work, because the progress dialog from the
first file blocks the whole copy procedure.

STEPS TO REPRODUCE
1. Plugin an USB-Drive and mount it
2. Copy one or more files of your choice from the USB-Drive to Harddrive

SOFTWARE/OS VERSIONS

Linux/KDE Plasma: 
Operating System: Fedora 33
KDE Plasma Version: 5.20.5
KDE Frameworks Version: 5.79.0
Qt Version: 5.15.2
Kernel Version: 5.10.16-200.fc33.x86_64
OS Type: 64-bit
Processors: 8 × Intel® Core™ i7-4770T CPU @ 2.50GHz
Memory: 7.2 GiB of RAM
Graphics Processor: Mesa DRI Intel® HD Graphics 4600

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

[kate] [Bug 433924] regular expressions unicode support

[Christoph Cullmann]

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

--- Comment #6 from Christoph Cullmann  ---
The next frameworks release 5.81 will have the fixes to the part, that means
binary factory will have that in a bit over a month.

The application fixes should be directly visible in the nightly builds there.

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

[krita] [Bug 434131] New: Lots of layers = UI lag

[Manga Tengu]

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

Bug ID: 434131
   Summary: Lots of layers = UI lag
   Product: krita
   Version: 4.4.3-beta1
  Platform: macOS (DMG)
OS: macOS
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Usability
  Assignee: krita-bugs-n...@kde.org
  Reporter: mangate...@gmail.com
  Target Milestone: ---

Having lots of layers make the document tab and the layer docker sluggish.

The use case is the following: On a single file, I storyboard a chapter of my
webtoon series. A chapter is 40 to 80 panels long. I draw each panel on a
separate layer. Then, I have a script Wolthera helped me to develop, that
exports each layer to a separate file so I get the real skeleton of my chapter
ready.

So I end up with lots and lots of layers. Since the script is recursive, I can
have folders containing subfolders of layers, etc. and everything works fine.
But layer navigation becomes extremely laggy...

To reproduce:
make an A3 at 300 dpi document 
add something like 50 layers to it.
Try to navigate smoothly. The only thing that will kinda work smoothly is
dragging a layer.

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

[plasma-systemmonitor] [Bug 434074] System Monitor segmentation faulted in QWidget::internalWinId() when terminating processes running as root

[Matt Fagnani]

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

--- Comment #1 from Matt Fagnani  ---
I ran gdb plasma-systemmonitor and terminated abrt-dump-journal-xorg as I
described. The segmentation fault was shown in QWidget::effectiveWinId which
was frame 1 in the original trace. The polkit and kauth functions in
kf5-kauth-5.79.0-2.fc34 in frames 1 and 2 might indicate that the KDE PolicyKit
agent was in the process of starting when the crash happened.

(gdb) bt
#0  QWidget::effectiveWinId() const (this=0x57385,
this@entry=0x7fffa3f0)
at kernel/qwidget.cpp:2462
#1  0x7fff92695931 in KAuth::Polkit1Backend::preAuthAction(QString const&,
QWidget*)
(this=, action=..., parent=0x7fffa3f0)
at
/usr/src/debug/kf5-kauth-5.79.0-2.fc34.x86_64/src/backends/polkit-1/Polkit1Backend.cpp:63
#2  0x74fe11cb in KAuth::ExecuteJob::Private::doExecuteAction()
(this=0x583fc330)
at
/usr/src/debug/kf5-kauth-5.79.0-2.fc34.x86_64/src/kauthexecutejob.cpp:142
#3  0x768fc257 in QObject::event(QEvent*) (this=0x583fc260,
e=0x583fc380)
at kernel/qobject.cpp:1314
#4  0x773f0e73 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
(this=, receiver=0x583fc260, e=0x583fc380) at
kernel/qapplication.cpp:3632
#5  0x768d4f48 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
(receiver=0x583fc260, event=0x583fc380) at
kernel/qcoreapplication.cpp:1063
#6  0x768d7c76 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*)
(receiver=0x0, event_type=0, data=0x55586d80) at
kernel/qcoreapplication.cpp:1817
#7  0x76921c57 in postEventSourceDispatch(GSource*, GSourceFunc,
gpointer) (s=0x555b5350)
at kernel/qeventdispatcher_glib.cpp:277
#8  0x7542c3d7 in g_main_dispatch (context=0x555c6ae0) at
../glib/gmain.c:3337
#9  g_main_context_dispatch (context=0x555c6ae0) at ../glib/gmain.c:4055
#10 0x75480518 in g_main_context_iterate.constprop.0
(context=context@entry=0x555c6ae0, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at ../glib/gmain.c:4131
#11 0x75429b13 in g_main_context_iteration (context=0x555c6ae0,
may_block=1)
at ../glib/gmain.c:4196
#12 0x769216f8 in
QEventDispatcherGlib::processEvents(QFlags)
--Type  for more, q to quit, c to continue without paging--c
(this=0x555b58c0, flags=...) at kernel/qeventdispatcher_glib.cpp:423
#13 0x768d39b2 in
QEventLoop::exec(QFlags) (this=0x7fffa940,
flags=..., flags@entry=...) at
../../include/QtCore/../../src/corelib/global/qflags.h:69
#14 0x77975f7e in KJob::exec() (this=this@entry=0x583fc260) at
/usr/include/qt5/QtCore/qflags.h:121
#15 0x7fff91f92e82 in
KSysGuard::ProcessController::Private::runKAuthAction(QString const&,
QVector const&, QMap const&)
(this=this@entry=0x57385580, actionId=..., pids=..., options=...) at
/usr/src/debug/libksysguard-5.21.2-1.fc34.x86_64/processcore/process_controller.cpp:269
#16 0x7fff91f932ad in KSysGuard::ProcessController::sendSignal(QVector
const&, int) (this=0x7fffaac8, this@entry=0x57385b90, pids=...,
signal=-21880, signal@entry=15) at
/usr/src/debug/libksysguard-5.21.2-1.fc34.x86_64/processcore/process_controller.cpp:86
#17 0x7fff91f938d6 in
KSysGuard::ProcessController::sendSignal(QList const&, int)
(this=0x57385b90, pids=, signal=15) at
/usr/src/debug/libksysguard-5.21.2-1.fc34.x86_64/processcore/process_controller.cpp:100
#18 0x7fff91f7e147 in
KSysGuard::ProcessController::qt_static_metacall(QObject*, QMetaObject::Call,
int, void**) (_o=_o@entry=0x57385b90,
_c=_c@entry=QMetaObject::InvokeMetaMethod, _id=_id@entry=2,
_a=_a@entry=0x7fffad20) at
/usr/src/debug/libksysguard-5.21.2-1.fc34.x86_64/x86_64-redhat-linux-gnu/processcore/processcore_autogen/EWIEGA46WW/moc_process_controller.cpp:165
#19 0x7fff91f7e383 in
KSysGuard::ProcessController::qt_metacall(QMetaObject::Call, int, void**)
(this=0x57385b90, _c=QMetaObject::InvokeMetaMethod, _id=2,
_a=0x7fffad20) at
/usr/src/debug/libksysguard-5.21.2-1.fc34.x86_64/x86_64-redhat-linux-gnu/processcore/processcore_autogen/EWIEGA46WW/moc_process_controller.cpp:282
#20 0x77e01b25 in QQmlObjectOrGadget::metacall(QMetaObject::Call, int,
void**) const (this=0x7fffafc0, type=QMetaObject::InvokeMetaMethod,
index=, argv=) at qml/qqmlobjectorgadget.cpp:51
#21 0x77d081cb in CallMethod (callType=,
callArgs=0x7fffadd0, engine=, argTypes=,
argCount=, returnType=, index=,
object=) at /usr/include/qt5/QtCore/qvarlengtharray.h:201
#22 CallPrecise(QQmlObjectOrGadget const&, QQmlPropertyData const&,
QV4::ExecutionEngine*, QV4::CallData*, QMetaObject::Call) (object=...,
data=..., engine=engine@entry=0x55670090,
callArgs=callArgs@entry=0x7fffe210e598,
callType=callType@entry=QMetaObject::InvokeMetaMethod) at
jsruntime/qv4qobjectwrapper.cpp:1569
#23 0x77d0927b in CallOverloaded
(callType=QMetaObject::InvokeMetaMethod, propertyCach

[kmail2] [Bug 434132] New: Text on HTML-"buttons" invisible

[Attila]

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

Bug ID: 434132
   Summary: Text on HTML-"buttons" invisible
   Product: kmail2
   Version: 5.15.3
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: bugs.kde.att...@online.de
  Target Milestone: ---

Created attachment 136478
  --> https://bugs.kde.org/attachment.cgi?id=136478&action=edit
Text on button invisible

SUMMARY
The text on "modern" buttons is invisible in almost every HTML-formatted
e-mail. I have to higlight the text by mouse to be able to read the text on
those buttons (see attachments).

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 
Operating System: Fedora 33
KDE Plasma Version: 5.20.5
KDE Frameworks Version: 5.79.0
Qt Version: 5.15.2
Kernel Version: 5.10.16-200.fc33.x86_64
OS Type: 64-bit
Processors: 8 × Intel® Core™ i7-4770T CPU @ 2.50GHz
Memory: 7.2 GiB of RAM
Graphics Processor: Mesa DRI Intel® HD Graphics 4600

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

[kmail2] [Bug 434132] Text on HTML-"buttons" invisible

[Attila]

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

--- Comment #1 from Attila  ---
Created attachment 136479
  --> https://bugs.kde.org/attachment.cgi?id=136479&action=edit
Text on button highlighted

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

[Breeze] [Bug 434133] New: The header doesn't disappear when using a per app color scheme without header support

[Reid]

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

Bug ID: 434133
   Summary: The header doesn't disappear when using a per app
color scheme without header support
   Product: Breeze
   Version: 5.21.2
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: QStyle
  Assignee: plasma-b...@kde.org
  Reporter: this.is.r...@tutanota.com
CC: noaha...@gmail.com
  Target Milestone: ---

Created attachment 136480
  --> https://bugs.kde.org/attachment.cgi?id=136480&action=edit
Header stays when using Breeze Dark globally and BreezeDracula for Kate alone

SUMMARY
The header doesn't disappear when using a per app color scheme without header
support if the global color scheme does support headers

STEPS TO REPRODUCE
1. Set a global colorscheme with header support (Breeze Light/Dark)
2. Set a per app color scheme without header support (tested with Kate and
Breeze Dracula)
3. 

OBSERVED RESULT
The header stays using the color from the global color scheme (check
attachment)

EXPECTED RESULT
The header should disappear the same way it does with global color schemes
without header support

SOFTWARE/OS VERSIONS
Operating System: Arch Linux
KDE Plasma Version: 5.21.2
KDE Frameworks Version: 5.79.0
Qt Version: 5.15.2

ADDITIONAL INFORMATION

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

[plasmashell] [Bug 427700] Bluetooth mouse lags after couple of seconds inactivity

[bugzilla_noreply]

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

el...@seznam.cz changed:

   What|Removed |Added

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

--- Comment #1 from el...@seznam.cz ---
I found out that this is not a Plasma bug because it also manifests on Mint
with Cinnamon. It can be fixed by setting kernel parameter
btusb.enable_autosuspend=0 . See
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801642 for more info.

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

[gcompris] [Bug 433800] Share:dataset "norest", task with rest (task 5 step 4)

[Rolas]

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

--- Comment #4 from Rolas  ---
does this code indicate that we will see a candy jar for residue?
with option "no rest" must not be visible candy jar:  "forceShowBasket": true,

 {
"instruction": qsTr("Charles wants to share his 6 pieces of
candy with 2 of his girl friends. Can he split the pieces of candy equally?"),
"randomisedInputData": false,
"totalBoys": 0,
"totalGirls": 2,
"totalCandies": 6,
"forceShowBasket": true,
"placedInGirls": 0,
"placedInBoys": 0
},
{
"instruction": qsTr("For her birthday, Elizabeth has 8 pieces
of candy to share with 3 of her friends: 2 girls and 1 boy. How should she
split the pieces of candy?"),
"randomisedInputData": false,
"totalBoys": 1,
"totalGirls": 2,
"totalCandies": 12,
"forceShowBasket": true,
"placedInGirls": 2,
"placedInBoys": 0
},
{
"instruction": qsTr("Jason's father gave him 16 pieces of candy
to share with his friends: 2 boys and 2 girls. Help him give the pieces of
candy to his friends."),
"randomisedInputData": false,
"totalBoys": 2,
"totalGirls": 2,
"totalCandies": 16,
"forceShowBasket": true,
"placedInGirls": 0,
"placedInBoys": 0
},

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

[frameworks-baloo] [Bug 434000] baloo works but Dolphin doesn't return any result

[Guido]

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

--- Comment #4 from Guido  ---
Reindexing did solve the problem.

Thank you.

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

[frameworks-baloo] [Bug 434000] baloo works but Dolphin doesn't return any result

[Guido]

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

Guido  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED

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

[Discover] [Bug 432971] Discover constantly lists "KDE Application Platform" as having an update when there is no update

[Lyubomir]

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

--- Comment #2 from Lyubomir  ---
(In reply to Aleix Pol from comment #1)
> Can you try running "flatpak repair"?

I haven't run flatpak repair as the issue seems to be gone now by itself.

I have no idea neither why it has gotten into the loop of constantly listing it
as update nor why it has gone away.

Feel free to close this bug and i'll feel free to reopen it if the issue
returns.

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

[krita] [Bug 434131] Lots of layers = UI lag

[Halla Rempt]

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

Halla Rempt  changed:

   What|Removed |Added

 Resolution|--- |WAITINGFORINFO
 CC||ha...@valdyas.org
 Status|REPORTED|NEEDSINFO

--- Comment #1 from Halla Rempt  ---
I made a document like that, with about sixty layers some of them in some
groups, and pgup/pgdn was instant, ctrl-pgup/ctrl-pgdn was instant, d&d was
instant -- which navigation tasks were slow for you? And could you perhaps
share privately a file where you observe the slowdown?

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

[krita] [Bug 434131] Lots of layers = UI lag

[Manga Tengu]

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

--- Comment #2 from Manga Tengu  ---
Yes I have 2 concrete files that, if opened together, moving layers up and down
or just changing selection is sluggish. How shall I share these ? (around 20
MB)

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

[krita] [Bug 434131] Lots of layers = UI lag

[Halla Rempt]

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

--- Comment #3 from Halla Rempt  ---
A google drive link or dropbox link shared with vur...@gmail.com would work for
me.

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

[krita] [Bug 434131] Lots of layers = UI lag

[Manga Tengu]

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

--- Comment #4 from Manga Tengu  ---
Done ! Thank you.

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

[krita] [Bug 434134] New: dialogue windows vanish on small monitor

[bugzilla_noreply]

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

Bug ID: 434134
   Summary: dialogue windows vanish on small monitor
   Product: krita
   Version: 4.4.2
  Platform: unspecified
OS: Microsoft Windows
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: General
  Assignee: krita-bugs-n...@kde.org
  Reporter: dancamer...@gmail.com
  Target Milestone: ---

SUMMARY
This program is all but unusable on a small (13inch) monitor.  Even with the
window maximized, it regularly spontaneously shifts between showing everything
and cutting off the bottom (including the horizontal scrollbar and the bottom
of the docked tools panel).  If it's not maximized, it always cuts off, and if
I try to make it small enough to fit, it either does nothing or disappears (it
doesn't close, it teleports off the edge of screen where I can't access it). 
The dialogue boxes do the same thing--half the time they're too big to see
everything, and if I try to shrink them, they do nothing or teleport off the
screen.  When they teleport, that basically freezes the entire program.  I just
had to restart my computer (and lose unsaved work) because there was no other
way to close Krita, because it had an open dialogue box that couldn't be
closed.

Also - this is a lot of hoops to make someone jump through to submit a bug
report.

STEPS TO REPRODUCE
1. Open Krita on a small monitor, 13inch or less.
2. Try to make it fit.  Try to make the main window or a dialogue box
comfortably smaller than the whole monitor size.

OBSERVED RESULT
Windows teleport off the screen.

EXPECTED RESULT
Windows should be resizable.

SOFTWARE/OS VERSIONS
Windows 10
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION
Krita

 Version: 4.4.2
 Languages: en_US, en
 Hidpi: true

Qt

  Version (compiled): 5.12.9
  Version (loaded): 5.12.9

OS Information

  Build ABI: x86_64-little_endian-llp64
  Build CPU: x86_64
  CPU: x86_64
  Kernel Type: winnt
  Kernel Version: 10.0.18363
  Pretty Productname: Windows 10 (10.0)
  Product Type: windows
  Product Version: 10

OpenGL Info

  Vendor:  "Google Inc." 
  Renderer:  "ANGLE (Intel(R) HD Graphics 5500 Direct3D11 vs_5_0 ps_5_0)" 
  Version:  "OpenGL ES 3.0 (ANGLE 2.1.0.57ea533f79a7)" 
  Shading language:  "OpenGL ES GLSL ES 3.00 (ANGLE 2.1.0.57ea533f79a7)" 
  Requested format:  QSurfaceFormat(version 3.0, options
QFlags(DeprecatedFunctions), depthBufferSize 24,
redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8,
stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::DoubleBuffer,
swapInterval 0, colorSpace QSurfaceFormat::DefaultColorSpace, profile 
QSurfaceFormat::CompatibilityProfile) 
  Current format:QSurfaceFormat(version 3.0, options
QFlags(), depthBufferSize 24, redBufferSize 8,
greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, stencilBufferSize 8,
samples 0, swapBehavior QSurfaceFormat::DefaultSwapBehavior, swapInterval 0,
colorSpace QSurfaceFormat::DefaultColorSpace, profile 
QSurfaceFormat::NoProfile) 
 Version: 3.0
 Supports deprecated functions false 
 is OpenGL ES: true 

QPA OpenGL Detection Info 
  supportsDesktopGL: true 
  supportsAngleD3D11: true 
  isQtPreferAngle: true 

Hardware Information

  GPU Acceleration: auto
  Memory: 8073 Mb
  Number of Cores: 4
  Swap Location: C:/Users/Dan Cameron/AppData/Local/Temp

Current Settings

  Current Swap Location: C:/Users/Dan Cameron/AppData/Local/Temp
  Current Swap Location writable: true
  Undo Enabled: true
  Undo Stack Limit: 30
  Use OpenGL: true
  Use OpenGL Texture Buffer: true
  Use AMD Vectorization Workaround: false
  Canvas State: OPENGL_SUCCESS
  Autosave Interval: 900
  Use Backup Files: true
  Number of Backups Kept: 1
  Backup File Suffix: ~
  Backup Location: Same Folder as the File
  Backup Location writable: false
  Use Win8 Pointer Input: false
  Use RightMiddleTabletButton Workaround: false
  Levels of Detail Enabled: false
  Use Zip64: false


Display Information
Number of screens: 2
Screen: 0
Name: \\.\DISPLAY1
Depth: 32
Scale: 2
Resolution in pixels: 960x540
Manufacturer: 
Model: 
Refresh Rate: 60
Screen: 1
Name: \\.\DISPLAY2
Depth: 32
Scale: 1
Resolution in pixels: 1600x900
Manufacturer: 
Model: 
Refresh Rate: 59

Current Settings

  Current Swap Location: C:/Users/Dan Cameron/AppData/Local/Temp
  Current Swap Location writable: true
  Undo Enabled: true
  Undo Stack Limit: 30
  Use OpenGL: true
  Use OpenGL Texture Buffer: true
  Use AMD Vectorization Workaround: false
  Canvas State: OPENGL_SUCCESS
  Autosave Interval: 900
  Use Backup Files: true
  Number of Backups Kept: 1
  Backup File

[systemsettings] [Bug 434135] New: Systemsettings crashes if bb10bright application style selected

[Tony Green]

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

Bug ID: 434135
   Summary: Systemsettings crashes if bb10bright application style
selected
   Product: systemsettings
   Version: 5.21.1
  Platform: Manjaro
OS: Linux
Status: REPORTED
  Severity: crash
  Priority: NOR
 Component: generic-crash
  Assignee: plasma-b...@kde.org
  Reporter: k...@web-brewer.co.uk
  Target Milestone: ---

Created attachment 136481
  --> https://bugs.kde.org/attachment.cgi?id=136481&action=edit
Output when running systemsettings in a konsole

SUMMARY
I was experimenting with application style in systemsettings. I selected
"bb10bright", clicked "apply" and systemsettings crashed. Every subsequent
attempt at running systemsettings just crashed immediately until I restored my
~/.config directory from backup.

STEPS TO REPRODUCE
1. Open systemsettings
2. Select appearance => application style
3. Select bb10bright and click "apply"

OBSERVED RESULT
systemsettings crashes

EXPECTED RESULT
systemsettings shouldn't crash

SOFTWARE/OS VERSIONS

Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 5.21.1
KDE Frameworks Version: 5.79.0
Qt Version: 5.15.1

ADDITIONAL INFORMATION

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

[systemsettings] [Bug 434135] Systemsettings crashes if bb10bright application style selected

[David Redondo]

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

David Redondo  changed:

   What|Removed |Added

 Status|REPORTED|NEEDSINFO
 CC||k...@david-redondo.de
 Resolution|--- |BACKTRACE

--- Comment #1 from David Redondo  ---
Without a backtrace it is impossible to tell why it crashed, but I suspect it's
an issue in the bb10bright style

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

[Breeze] [Bug 434133] The header doesn't disappear when using a per app color scheme without header support

[David Redondo]

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

David Redondo  changed:

   What|Removed |Added

 Status|REPORTED|CONFIRMED
 Ever confirmed|0   |1
 CC||k...@david-redondo.de

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

[digikam] [Bug 434112] digikam-7.2* crashes at first start after install while starting main view

[Jever]

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

--- Comment #17 from Jever <201...@gmx.de> ---
(In reply to Maik Qualmann from comment #16)
> A new digiKam-7.2.0 Windows version with the latest changes is available.
> Please test it and post the DebugView log from the start. There is no need
> to download the "-debug" version.
> 
> https://files.kde.org/digikam/
> 
> Maik

Moin Maik,

I used digiKam-7.2.0-20210307T200519-Win64.exe for testing.
It installs ok.
while first start there is no download of facesengine and so no creating of the
folder "C:/Users/jever.LOKAL/AppData/Roaming/digikam/facesengine".
It starts up and runs well as far as I can see.

Jever

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

[digikam] [Bug 434112] digikam-7.2* crashes at first start after install while starting main view

[Maik Qualmann]

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

--- Comment #18 from Maik Qualmann  ---
The download must take place in any case if the files are not yet available.
Please post the log to see if everything is really ok.

Maik

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

[systemsettings] [Bug 434135] Systemsettings crashes if bb10bright application style selected

[Tony Green]

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

--- Comment #2 from Tony Green  ---
(In reply to David Redondo from comment #1)
> Without a backtrace it is impossible to tell why it crashed, but I suspect
> it's an issue in the bb10bright style

Backtrace from another attempt:

GNU gdb (GDB) 10.1
Copyright (C) 2020 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-pc-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 systemsettings5...
(No debugging symbols found in systemsettings5)
[?2004h(gdb) run
[?2004l
Starting program: /usr/bin/systemsettings5 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[New Thread 0x71795640 (LWP 1183563)]
[New Thread 0x7fffebfff640 (LWP 1183564)]
[New Thread 0x7fffe9405640 (LWP 1183565)]
[New Thread 0x7fffe8ac3640 (LWP 1183566)]
[New Thread 0x7fffde5a0640 (LWP 1183567)]
[New Thread 0x7fffddd9f640 (LWP 1183568)]
[New Thread 0x7fffdd59e640 (LWP 1183569)]
[New Thread 0x7fffdcd9d640 (LWP 1183570)]
[New Thread 0x7fffc7fff640 (LWP 1183571)]
[New Thread 0x7fffc77fe640 (LWP 1183572)]
[New Thread 0x7fffc6ffd640 (LWP 1183573)]
[New Thread 0x7fffc67fc640 (LWP 1183574)]
[New Thread 0x7fffc5ffb640 (LWP 1183575)]
[Thread 0x7fffc5ffb640 (LWP 1183575) exited]
[New Thread 0x7fffc5ffb640 (LWP 1183576)]
[New Thread 0x7fffabfff640 (LWP 1183577)]
[New Thread 0x7fffab7fe640 (LWP 1183578)]
[New Thread 0x7fffaaffd640 (LWP 1183579)]
[New Thread 0x7fffaa7fc640 (LWP 1183580)]
file:///usr/share/kpackage/genericqml/org.kde.systemsettings.sidebar/contents/ui/SubCategoryPage.qml:157:9:
QML Connections: Implicitly defined onFoo properties in Connections are
deprecated. Use this syntax instead: function onFoo() { ... }
file:///usr/share/kpackage/genericqml/org.kde.systemsettings.sidebar/contents/ui/SubCategoryPage.qml:147:9:
QML Connections: Implicitly defined onFoo properties in Connections are
deprecated. Use this syntax instead: function onFoo() { ... }
[New Thread 0x7fffa8b73640 (LWP 1183581)]
[New Thread 0x7fff93681640 (LWP 1183583)]
[New Thread 0x7fff92e80640 (LWP 1183584)]
file:///usr/share/kpackage/genericqml/org.kde.systemsettings.sidebar/contents/ui/introPage.qml:109:27:
QML IntroIcon (parent or ancestor of QQuickLayoutAttached): Binding loop
detected for property "minimumHeight"
file:///usr/share/kpackage/genericqml/org.kde.systemsettings.sidebar/contents/ui/introPage.qml:109:27:
QML IntroIcon (parent or ancestor of QQuickLayoutAttached): Binding loop
detected for property "minimumHeight"
file:///usr/share/kpackage/genericqml/org.kde.systemsettings.sidebar/contents/ui/introPage.qml:109:27:
QML IntroIcon (parent or ancestor of QQuickLayoutAttached): Binding loop
detected for property "minimumHeight"
[New Thread 0x7fff9207f640 (LWP 1183585)]
file:///usr/share/kpackage/genericqml/org.kde.systemsettings.sidebar/contents/ui/introPage.qml:109:27:
QML IntroIcon (parent or ancestor of QQuickLayoutAttached): Binding loop
detected for property "minimumHeight"
file:///usr/share/kpackage/genericqml/org.kde.systemsettings.sidebar/contents/ui/introPage.qml:109:27:
QML IntroIcon (parent or ancestor of QQuickLayoutAttached): Binding loop
detected for property "minimumHeight"
file:///usr/share/kpackage/genericqml/org.kde.systemsettings.sidebar/contents/ui/introPage.qml:109:27:
QML IntroIcon (parent or ancestor of QQuickLayoutAttached): Binding loop
detected for property "minimumHeight"
[New Thread 0x7fff90fc4640 (LWP 1183586)]
[New Thread 0x7fff83d3b640 (LWP 1183591)]
[New Thread 0x7fff82901640 (LWP 1183592)]
[Thread 0x7fff82901640 (LWP 1183592) exited]
QQmlEngine::setContextForObject(): Object already has a QQmlContext
QCoreApplication::postEvent: Unexpected null receiver
[New Thread 0x7fff82901640 (LWP 1183593)]
[Thread 0x7fff82901640 (LWP 1183593) exited]
file:///usr/lib/qt/qml/org/kde/newstuff/qml/private/ErrorDisplayer.qml:14:35:
QML Connections: Implicitly defined onFoo properties in Connections are
deprecated. Use this syntax instead: function onFoo() { ... }
file:///usr/lib/qt/qml/org/kde/newstuff/qml/QuestionAsker.qml:91:5: QML
Connections: Implicitly defined onFoo properties in Connections are deprecated.
Use this syntax instead: function onFoo() { ... }
file:///usr/lib/qt/qml/org/kde/newstuff/qml/QuestionAsker.qml:91:5: QML
Connections: Cannot assign to non-existent property "onClosing"
file:///usr/lib/qt/qml/org/kde/newstuff/qml/QuestionAsker.qml:50:5: QML
Co

[systemsettings] [Bug 434135] Systemsettings crashes if bb10bright application style selected

[David Redondo]

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

David Redondo  changed:

   What|Removed |Added

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

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

[digikam] [Bug 434112] digikam-7.2* crashes at first start after install while starting main view

[Jever]

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

--- Comment #19 from Jever <201...@gmx.de> ---
Created attachment 136482
  --> https://bugs.kde.org/attachment.cgi?id=136482&action=edit
New Log of first run after install of 7.2.0

digiKam-7.2.0-20210307T200519-Win64.exe

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

[digikam] [Bug 434112] digikam-7.2* crashes at first start after install while starting main view

[Jever]

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

--- Comment #20 from Jever <201...@gmx.de> ---
(In reply to Maik Qualmann from comment #18)
> The download must take place in any case if the files are not yet available.
> Please post the log to see if everything is really ok.
> 
> Maik

... I searched for the folder and recogniced that is already there.

I looked at the wrong folder (Local user / domain user)!
Sorry for the noise.

Jever

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

[digikam] [Bug 434112] digikam-7.2* crashes at first start after install while starting main view

[Maik Qualmann]

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

--- Comment #21 from Maik Qualmann  ---
The face recognition will not work, however, an exception occurs in OpenCV. It
just doesn't crash anymore.

--
[7152] digikam.facedb:
"C:/Users/jever.LOKAL/AppData/Roaming/digikam/facesengine/openface_nn4.small2.v1.t7"
 
[7152] digikam.facedb: cv::Exception: OpenCV(4.5.1)
/mnt/data/7.x/project/bundles/mxe/temp.build/ext_opencv/ext_opencv-prefix/src/ext_opencv/modules/dnn/src/torch/THDiskFile.cpp:496:
error: (-2:Unspecified error) cannot open

in mode r  in function 'THDiskFile_new'   
--

This is not a file not found error, it cannot be opened. I suspect an
anti-virus program is preventing access to the file.

Maik

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

[plasma-systemmonitor] [Bug 434040] Default CPU usage graph scales badly to 16+ cores

[David Redondo]

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

David Redondo  changed:

   What|Removed |Added

 CC||k...@david-redondo.de

--- Comment #1 from David Redondo  ---
FYI you can adjust the opacity of the fill color of the lines, for example the
plasma widgets use more transparency by default

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

[krita] [Bug 434131] Lots of layers = UI lag

[Halla Rempt]

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

--- Comment #5 from Halla Rempt  ---
Got it. On Linux, I don't see performance problems, so I'm trying on my mac
now.

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

[krita] [Bug 434131] Lots of layers = UI lag

[Halla Rempt]

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

--- Comment #6 from Halla Rempt  ---
Hm... On my powerbook m1, I also don't see any lag, not when switching between
files, not changing the current layer or moving the current layer in the layer
stack. The files really aren't excessively big, too.

I've tried both with canvas acceleration on and off.

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

[krita] [Bug 434131] Lots of layers = UI lag

[Manga Tengu]

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

--- Comment #7 from Manga Tengu  ---
changing layer and moving layers should be laggy

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

[krita] [Bug 434134] dialogue windows vanish on small monitor

[Halla Rempt]

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

Halla Rempt  changed:

   What|Removed |Added

 Resolution|--- |NOT A BUG
 CC||ha...@valdyas.org
 Status|REPORTED|RESOLVED

--- Comment #1 from Halla Rempt  ---
I'm sorry, but this isn't something we can fix. A resolution of 960x540 just is
too small and 1600x1200 might work, but you'll have to be careful when enabling
or disabling dockers, and the animation workspace won't work at all.

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

[valgrind] [Bug 432870] gdbserver_tests:nlcontrolc hangs with newest glibc2.33 x86-64

[Mark Wielaard]

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

Mark Wielaard  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|REPORTED|CONFIRMED

--- Comment #8 from Mark Wielaard  ---
(In reply to Philippe Waroquiers from comment #7)
> Created attachment 136473 [details]
> fix nlcontrolc.vgtest blocking on arm64 or newer glibc
> 
> Attach patch should fix the blockage. Tested on debian 10/amd64 and on an
> arm64 platform.

Tested on x86_64 against glibc 2.17, 2.32, and 2.33.9000, on arm64 against
glibc 2.33. Passed on all.

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

[kruler] [Bug 432521] Cannot move on wayland

[Mads]

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

Mads  changed:

   What|Removed |Added

 CC||m...@ab3.no

--- Comment #2 from Mads  ---
Any news on this? I experience the same thing with e.g. Audacious, I can't move
the window without holding the Super key.

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

[gcompris] [Bug 434136] New: leave a tank or turn around?

[Rolas]

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

Bug ID: 434136
   Summary: leave a tank or turn around?
   Product: gcompris
   Version: unspecified
  Platform: Other
OS: Other
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: jaz...@gmail.com
  Reporter: rolasor...@gmail.com
  Target Milestone: ---

clickgame

here is a game instruction:
Catch all the swimming fish before they leave the fish tank.

but they do not leave the tank,
they turn around and fly on!

what is the game algorithm?
fish leave bank or turn around?

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

[kruler] [Bug 432521] Cannot move on wayland

[Bernhard]

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

--- Comment #3 from Bernhard  ---
(In reply to Mads from comment #2)
> Any news on this? I experience the same thing with e.g. Audacious, I can't
> move the window without holding the Super key.

I am pretty sure this has to be fixed on a per-application-basis. You should
probably report this on their bug tracker as well.

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

[ksmserver] [Bug 433293] Some KDE processes (like kdeconnectd) are not killed after session logout, hog CPU

[Marco Ambu]

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

Marco Ambu  changed:

   What|Removed |Added

 CC||marco.a...@gmail.com

--- Comment #10 from Marco Ambu  ---
Since you mentioned drkonqi, can this be related to bug #433293?
I have the same issue described in that ticket as well where on logoff, some
processes are not stopped and start hogging the CPU when I re-login.

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

[neon] [Bug 434038] Please provide an updated version of Maliit that is usable

[Jonathan Riddell]

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

--- Comment #2 from Jonathan Riddell  ---
We don't typically package stuff that isn't KDE since we're a KDE package.  But
this is an infrastructure package and we can't easily point to
snaps/flatpaks/appimages that might replace it and we already package it for
unstable so maybe we should.  What think you Harald?

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

[krita] [Bug 434131] Lots of layers = UI lag

[Halla Rempt]

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

--- Comment #8 from Halla Rempt  ---
Yes, those are the actions I tried: it's all instant on test hardware -- the M1
macbook pro and my t470p.

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

[neon] [Bug 434038] Please provide an updated version of Maliit that is usable

[Harald Sitter]

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

--- Comment #3 from Harald Sitter  ---
We kinda need it for plasma mobile anyway, which I guess is why we have it
unstable? May as well put it into release.

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

[kdenetwork-filesharing] [Bug 432757] kdenetwork-filesharing: AuthHelper does not sanitize command-line arguments

[Harald Sitter]

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

Harald Sitter  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|ASSIGNED|RESOLVED
  Latest Commit||https://invent.kde.org/netw
   ||ork/kdenetwork-filesharing/
   ||commit/19f000d8f9348f53e33a
   ||40a8723e9bbe09474be6
   Version Fixed In||20.12.3

--- Comment #3 from Harald Sitter  ---
Git commit 19f000d8f9348f53e33a40a8723e9bbe09474be6 by Harald Sitter.
Committed on 08/03/2021 at 10:36.
Pushed by sitter into branch 'release/20.12'.

run input user/group names through input validation

to harden against abuse we'll match them against a regex that should
only match what could possibly be a valid user or group name.

thanks to Wolfgang Frisch and SUSE for the suggestion
FIXED-IN: 20.12.3

M  +12   -4samba/filepropertiesplugin/authhelper.cpp

https://invent.kde.org/network/kdenetwork-filesharing/commit/19f000d8f9348f53e33a40a8723e9bbe09474be6

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

[plasmashell] [Bug 397210] Touchpad applet is missing from the system tray under Wayland

[Patrick Silva]

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

Patrick Silva  changed:

   What|Removed |Added

Summary|Touchpad indicator is   |Touchpad applet is missing
   |missing from the system |from the system tray under
   |tray under Wayland  |Wayland
Version|5.20.2  |5.21.2

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

[frameworks-plasma] [Bug 422072] Plasma hangs when quickly moving the mouse cursor back and forth

[Alexander Schlarb]

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

Alexander Schlarb  changed:

   What|Removed |Added

 Attachment #136360|0   |1
is obsolete||

--- Comment #8 from Alexander Schlarb  ---
Created attachment 136483
  --> https://bugs.kde.org/attachment.cgi?id=136483&action=edit
plasmashell 5.21.2 hang backtrace

No change with plasmashell 5.21.2 from Debian experimental.

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

[krita] [Bug 434015] Crash due to colorspace conversion after paste

[Halla Rempt]

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

Halla Rempt  changed:

   What|Removed |Added

 CC||ha...@valdyas.org

--- Comment #1 from Halla Rempt  ---
Ah, isn't this just the copy an empty layer issue that I fixed already?

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

[krita] [Bug 434131] Lots of layers = UI lag

[Manga Tengu]

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

--- Comment #9 from Manga Tengu  ---
I'm at a loss. It's super slugish here and I have no clue what causes it...

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

[gcompris] [Bug 434137] New: the water does not run on the flame

[Rolas]

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

Bug ID: 434137
   Summary: the water does not run on the flame
   Product: gcompris
   Version: unspecified
  Platform: Other
OS: Other
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: jaz...@gmail.com
  Reporter: rolasor...@gmail.com
  Target Milestone: ---

Created attachment 136484
  --> https://bugs.kde.org/attachment.cgi?id=136484&action=edit
the water does not run on the flame - step 2 on my screen

my little son says:
how can I put out a fire when the water is running all the way to the side, not
on the fire?

sometimes the hose appears very far from the fire

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

[systemsettings] [Bug 434138] New: kinfocenter crashes at startup on neon unstable

[Patrick Silva]

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

Bug ID: 434138
   Summary: kinfocenter crashes at startup on neon unstable
   Product: systemsettings
   Version: unspecified
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: bugsefor...@gmx.com
  Target Milestone: ---

Application: systemsettings5 (5.21.80)

Qt Version: 5.15.2
Frameworks Version: 5.80.0
Operating System: Linux 5.8.0-44-generic x86_64
Windowing System: Wayland
Drkonqi Version: 5.21.80
Distribution: KDE neon Unstable Edition

-- Information about the crash:
- What I was doing when the application crashed:
kinfocenter does not open on neon unstable and Plasma shows a crash
notification.

The crash can be reproduced every time.

-- Backtrace:
Application: Info Center (systemsettings5), signal: Segmentation fault
Content of s_kcrashErrorMessage: [Current thread is 1 (Thread 0x7f44ede908c0
(LWP 9430))]
[New LWP 9432]
[New LWP 9433]
[New LWP 9434]
[New LWP 9435]
[New LWP 9436]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
0x7f44f20cbaff in __GI___poll (fds=fds@entry=0x7ffeae904268,
nfds=nfds@entry=1, timeout=timeout@entry=1000) at
../sysdeps/unix/sysv/linux/poll.c:29

Thread 6 (Thread 0x7f44e54d0700 (LWP 9436)):
#0  futex_wait_cancelable (private=, expected=0,
futex_word=0x562933f4ac48) at ../sysdeps/nptl/futex-internal.h:183
#1  __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x562933f4abf8,
cond=0x562933f4ac20) at pthread_cond_wait.c:508
#2  __pthread_cond_wait (cond=0x562933f4ac20, mutex=0x562933f4abf8) at
pthread_cond_wait.c:638
#3  0x7f44e73f3e6b in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
#4  0x7f44e73f3a6b in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
#5  0x7f44f0c65609 in start_thread (arg=) at
pthread_create.c:477
#6  0x7f44f20d8293 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 5 (Thread 0x7f44e5cd1700 (LWP 9435)):
#0  futex_wait_cancelable (private=, expected=0,
futex_word=0x562933f4ac48) at ../sysdeps/nptl/futex-internal.h:183
#1  __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x562933f4abf8,
cond=0x562933f4ac20) at pthread_cond_wait.c:508
#2  __pthread_cond_wait (cond=0x562933f4ac20, mutex=0x562933f4abf8) at
pthread_cond_wait.c:638
#3  0x7f44e73f3e6b in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
#4  0x7f44e73f3a6b in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
#5  0x7f44f0c65609 in start_thread (arg=) at
pthread_create.c:477
#6  0x7f44f20d8293 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 4 (Thread 0x7f44e64d2700 (LWP 9434)):
#0  futex_wait_cancelable (private=, expected=0,
futex_word=0x562933f4ac48) at ../sysdeps/nptl/futex-internal.h:183
#1  __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x562933f4abf8,
cond=0x562933f4ac20) at pthread_cond_wait.c:508
#2  __pthread_cond_wait (cond=0x562933f4ac20, mutex=0x562933f4abf8) at
pthread_cond_wait.c:638
#3  0x7f44e73f3e6b in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
#4  0x7f44e73f3a6b in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
#5  0x7f44f0c65609 in start_thread (arg=) at
pthread_create.c:477
#6  0x7f44f20d8293 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 3 (Thread 0x7f44e6cd3700 (LWP 9433)):
#0  futex_wait_cancelable (private=, expected=0,
futex_word=0x562933f4ac48) at ../sysdeps/nptl/futex-internal.h:183
#1  __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x562933f4abf8,
cond=0x562933f4ac20) at pthread_cond_wait.c:508
#2  __pthread_cond_wait (cond=0x562933f4ac20, mutex=0x562933f4abf8) at
pthread_cond_wait.c:638
#3  0x7f44e73f3e6b in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
#4  0x7f44e73f3a6b in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
#5  0x7f44f0c65609 in start_thread (arg=) at
pthread_create.c:477
#6  0x7f44f20d8293 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 2 (Thread 0x7f44ed224700 (LWP 9432)):
#0  g_main_context_iterate (context=context@entry=0x7f44e8000c20,
block=block@entry=1, dispatch=dispatch@entry=1, self=) at
../../../glib/gmain.c:4029
#1  0x7f44f03552c3 in g_main_context_iteration (context=0x7f44e8000c20,
may_block=may_block@entry=1) at ../../../glib/gmain.c:4108
#2  0x7f44f27e5fbb in QEventDispatcherGlib::processEvents
(this=0x7f44e8000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#3  0x7f44f278a1ab in QEventLoop::exec (this=this@entry=0x7f44ed223cb0,
flags=..., flags@entry=...) at
../../include/QtCore/../../src/corelib/global/qflags.h:141
#4  0x7f44f25a4a12 in QThread::exec (this=this@entry=0x7f44f1539d80
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()

[Discover] [Bug 425680] Discover crashes when I cancel Snap installation

[Patrick Silva]

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

--- Comment #2 from Patrick Silva  ---
This crash is still reproducible.

Operating System: KDE neon Unstable Edition
KDE Plasma Version: 5.21.80
KDE Frameworks Version: 5.80.0
Qt Version: 5.15.2
Graphics Platform: Wayland

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

[Powerdevil] [Bug 434012] while playing an audio stream monitor is switched off after a delay

[Nicolas Fella]

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

Nicolas Fella  changed:

   What|Removed |Added

 CC||nicolas.fe...@gmx.de

--- Comment #3 from Nicolas Fella  ---
It's up to the application to request that the screen will not be turned off.

Firefox does exactly that when I use Spotify Web

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

[krita] [Bug 434131] Lots of layers = UI lag

[Halla Rempt]

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

--- Comment #10 from Halla Rempt  ---
Me too... Even on my 2015 macbook pro, it's not really sluggish. It's slower
than the t470 and the M1, of course, since it's pretty old hardware by now, but
it's perfectly usable :-(

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

[gcompris] [Bug 434136] leave a tank or turn around?

[bugzilla_noreply]

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

anim...@gmail.com changed:

   What|Removed |Added

 CC||anim...@gmail.com

--- Comment #1 from anim...@gmail.com ---
Indeed, the fish never leave the aquarium.

I've wondered about that when I was reviewing the strings and noticed the same.
But I've decided the keep the existing text for now to not break existing
translations and audio voices, as this extra part is not really impacting the
main description of the activity, that users have to click the fish.

Also, as this activity is really just to learn to click on something, I think
we don't want to add a time restriction to make it more accessible to everyone.

Though we can discuss more about if we really should update the description, in
which case we can change it for next feature release.

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

[krita] [Bug 434131] Lots of layers = UI lag

[Manga Tengu]

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

--- Comment #11 from Manga Tengu  ---
is there anything else I can provide ? Except recording a useless video ?

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

[neon] [Bug 400386] Sometimes Drkonqi does not install debug packages of KDE software on neon unstable edition

[Patrick Silva]

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

--- Comment #9 from Patrick Silva  ---
Created attachment 136485
  --> https://bugs.kde.org/attachment.cgi?id=136485&action=edit
degug symbols of Discover

drkonqi failed to install debug symbols of Discover again.


Operating System: KDE neon Unstable Edition
KDE Plasma Version: 5.21.80
KDE Frameworks Version: 5.80.0
Qt Version: 5.15.2
Graphics Platform: Wayland

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

[krita] [Bug 434015] Crash due to colorspace conversion after paste

[Paolo Amadini]

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

--- Comment #2 from Paolo Amadini  ---
(In reply to Halla Rempt from comment #1)
> Ah, isn't this just the copy an empty layer issue that I fixed already?

This happens regardless of whether the layer is empty, and it was reproducible
on a recent git master branch, so I believe it's not related.

In my tests, this bug seems limited to the case where the image being pasted
has the "Alpha Mask" colorspace. I just tried to paste the image as a new
document before step 5, convert it to the "Grayscale/Aplha" colorspace, then
copy and paste it in the original document, and it doesn't crash.

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

[kwin] [Bug 434118] Graphical artifacts since updating to 5.21.1

[postix]

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

--- Comment #4 from postix  ---
Created attachment 136486
  --> https://bugs.kde.org/attachment.cgi?id=136486&action=edit
Screenshot from a screenrecording from a person on reddit

I've noticed that someone published a screen recording of a Plasma 5.21 session
in which the same artifacts can be seen [1] at second 13-14. 

I made a screenshot and attached it here. This at least proofs that it's not
only me who is affected.

[1]
https://www.reddit.com/r/kde/comments/m07uoy/any_kind_of_window_tiling_is_not_working_on_kde/

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

[neon] [Bug 400386] Sometimes Drkonqi does not install debug packages of KDE software on neon unstable edition

[Patrick Silva]

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

--- Comment #10 from Patrick Silva  ---
Humm, drkonqi asks for more debug packages but apparently the generated
backtrace is good.

Application: Discover (plasma-discover), signal: Segmentation fault
Content of s_kcrashErrorMessage: [Current thread is 1 (Thread 0x7f425443fe40
(LWP 9483))]
[New LWP 9484]
[New LWP 9485]
[New LWP 9486]
[New LWP 9487]
[New LWP 9488]
[New LWP 9489]
[New LWP 9494]
[New LWP 9495]
[New LWP 9496]
[New LWP 9497]
[New LWP 9502]
[New LWP 9503]
[New LWP 9527]
[New LWP 10083]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
0x7f4258a09aff in __GI___poll (fds=fds@entry=0x7ffdc2565968,
nfds=nfds@entry=1, timeout=timeout@entry=1000) at
../sysdeps/unix/sysv/linux/poll.c:29

Thread 15 (Thread 0x7f4218977700 (LWP 10083)):
#0  0x7f4258a09aff in __GI___poll (fds=0x7f422403a2b0, nfds=1, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7f425737d18e in g_main_context_poll (priority=,
n_fds=1, fds=0x7f422403a2b0, timeout=, context=0x7f422402a000)
at ../../../glib/gmain.c:4346
#2  g_main_context_iterate (context=context@entry=0x7f422402a000,
block=block@entry=1, dispatch=dispatch@entry=1, self=) at
../../../glib/gmain.c:4042
#3  0x7f425737d2c3 in g_main_context_iteration (context=0x7f422402a000,
may_block=may_block@entry=1) at ../../../glib/gmain.c:4108
#4  0x7f4258fd4fbb in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7f4224030a90, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#5  0x7f4258f791ab in
QEventLoop::exec(QFlags)
(this=this@entry=0x7f4218976be0, flags=..., flags@entry=...) at
../../include/QtCore/../../src/corelib/global/qflags.h:141
#6  0x7f4258d93a12 in QThread::exec() (this=this@entry=0x56421be9c530) at
../../include/QtCore/../../src/corelib/global/qflags.h:121
#7  0x7f425aaf038a in QQuickPixmapReader::run() (this=0x56421be9c530) at
util/qquickpixmapcache.cpp:1024
#8  0x7f4258d94bac in QThreadPrivate::start(void*) (arg=0x56421be9c530) at
thread/qthread_unix.cpp:329
#9  0x7f4257d2a609 in start_thread (arg=) at
pthread_create.c:477
#10 0x7f4258a16293 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 14 (Thread 0x7f4217971700 (LWP 9527)):
#0  0x7f425737b11c in g_source_iter_next (iter=iter@entry=0x7f4217970bb0,
source=source@entry=0x7f4217970ba8) at ../../../glib/gmain.c:1023
#1  0x7f425737cadf in g_main_context_check
(context=context@entry=0x7f41ce25fe70, max_priority=2147483647,
fds=fds@entry=0x7f41cca156a0, n_fds=n_fds@entry=1) at
../../../glib/gmain.c:3860
#2  0x7f425737d132 in g_main_context_iterate
(context=context@entry=0x7f41ce25fe70, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at ../../../glib/gmain.c:4044
#3  0x7f425737d2c3 in g_main_context_iteration
(context=context@entry=0x7f41ce25fe70, may_block=may_block@entry=1) at
../../../glib/gmain.c:4108
#4  0x7f421711199d in dconf_gdbus_worker_thread (user_data=0x7f41ce25fe70)
at ../gdbus/dconf-gdbus-thread.c:82
#5  0x7f42573a6911 in g_thread_proxy (data=0x7f41b8002360) at
../../../glib/gthread.c:807
#6  0x7f4257d2a609 in start_thread (arg=) at
pthread_create.c:477
#7  0x7f4258a16293 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 13 (Thread 0x7f41d3fff700 (LWP 9503)):
#0  0x7f4258a09aff in __GI___poll (fds=0x7f41c8072600, nfds=1, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7f425737d18e in g_main_context_poll (priority=,
n_fds=1, fds=0x7f41c8072600, timeout=, context=0x7f41c8000c20)
at ../../../glib/gmain.c:4346
#2  g_main_context_iterate (context=context@entry=0x7f41c8000c20,
block=block@entry=1, dispatch=dispatch@entry=1, self=) at
../../../glib/gmain.c:4042
#3  0x7f425737d2c3 in g_main_context_iteration (context=0x7f41c8000c20,
may_block=may_block@entry=1) at ../../../glib/gmain.c:4108
#4  0x7f4258fd4fbb in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7f41c8000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#5  0x7f4258f791ab in
QEventLoop::exec(QFlags)
(this=this@entry=0x7f41d3ffec20, flags=..., flags@entry=...) at
../../include/QtCore/../../src/corelib/global/qflags.h:141
#6  0x7f4258d93a12 in QThread::exec() (this=) at
../../include/QtCore/../../src/corelib/global/qflags.h:121
#7  0x7f4258d94bac in QThreadPrivate::start(void*) (arg=0x564215d62150) at
thread/qthread_unix.cpp:329
#8  0x7f4257d2a609 in start_thread (arg=) at
pthread_create.c:477
#9  0x7f4258a16293 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 12 (Thread 0x7f421636e700 (LWP 9502)):
#0  futex_wait_cancelable (private=, expected=0,
futex_word=0x564215caa730) at ../sysdeps/nptl/futex-internal.h:183
#1  __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x564215caa6e0,
cond=0x564215caa708) at pthread_cond_wait.c:508
#2  __pthread_cond_wait (cond=0x564215caa708, mutex=0x564215caa6e0) at
pthread_cond_wait.c:638
#3  0x

[neon] [Bug 400386] Sometimes Drkonqi does not install debug packages of KDE software on neon unstable edition

[Harald Sitter]

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

--- Comment #11 from Harald Sitter  ---
What's the output of `apt-cache policy plasma-discover plasma-discover-dbgsym`

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

[neon] [Bug 400386] Sometimes Drkonqi does not install debug packages of KDE software on neon unstable edition

[Harald Sitter]

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

--- Comment #12 from Harald Sitter  ---
And please also the output of `dpkg -S
/lib/x86_64-linux-gnu/libsnapd-glib.so.1`

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

[neon] [Bug 400386] Sometimes Drkonqi does not install debug packages of KDE software on neon unstable edition

[Patrick Silva]

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

--- Comment #13 from Patrick Silva  ---
output of your first command:

plasma-discover:
  Installed: 5.21.2+p20.04+git20210308.0223-0
  Candidate: 5.21.2+p20.04+git20210308.0223-0
  Version table:
 *** 5.21.2+p20.04+git20210308.0223-0 500
500 http://archive.neon.kde.org/unstable focal/main amd64 Packages
100 /var/lib/dpkg/status
 5.21.2+p20.04+git20210306.0222-0 500
500 http://archive.neon.kde.org/unstable focal/main amd64 Packages
 5.18.5-0ubuntu0.1 500
500 http://ubuntu.c3sl.ufpr.br/ubuntu focal-updates/universe amd64
Packages
 5.18.4.1-0ubuntu1 500
500 http://ubuntu.c3sl.ufpr.br/ubuntu focal/universe amd64 Packages
plasma-discover-dbgsym:
  Installed: 5.21.2+p20.04+git20210308.0223-0
  Candidate: 5.21.2+p20.04+git20210308.0223-0
  Version table:
 *** 5.21.2+p20.04+git20210308.0223-0 500
500 http://archive.neon.kde.org/unstable focal/main amd64 Packages
100 /var/lib/dpkg/status
 5.21.2+p20.04+git20210306.0222-0 500
500 http://archive.neon.kde.org/unstable focal/main amd64 Packages
 5.18.5-0ubuntu0.1 500
500 http://ddebs.ubuntu.com focal-updates/universe amd64 Packages
 5.18.4.1-0ubuntu1 500
500 http://ddebs.ubuntu.com focal/universe amd64 Packages

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

[neon] [Bug 400386] Sometimes Drkonqi does not install debug packages of KDE software on neon unstable edition

[Patrick Silva]

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

--- Comment #14 from Patrick Silva  ---
output of "dpkg -S /lib/x86_64-linux-gnu/libsnapd-glib.so.1":

dpkg-query: no path found matching pattern
/lib/x86_64-linux-gnu/libsnapd-glib.so.1

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

[gcompris] [Bug 434137] the water does not run on the flame

[bugzilla_noreply]

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

anim...@gmail.com changed:

   What|Removed |Added

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

--- Comment #1 from anim...@gmail.com ---
Right, the algorithm to draw the line should be improved a bit to never go
below the fire. I'll try to look at it.

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

[gcompris] [Bug 434137] the water does not run on the flame

[bugzilla_noreply]

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

anim...@gmail.com changed:

   What|Removed |Added

   Assignee|jaz...@gmail.com|anim...@gmail.com

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

[plasma-systemmonitor] [Bug 434039] Memory details are missing

[Arjen Hiemstra]

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

Arjen Hiemstra  changed:

   What|Removed |Added

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

--- Comment #1 from Arjen Hiemstra  ---
What's your use case? One of the reasons we did not add it is that we did not
know an actual usecase that isn't solved better by some dedicated tool. If you
have a usecase though, we may reconsider that.

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

[plasma-systemmonitor] [Bug 429156] Legend is truncated on first page view

[Arjen Hiemstra]

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

Arjen Hiemstra  changed:

   What|Removed |Added

 CC||nicolas.wer...@ymail.com

--- Comment #1 from Arjen Hiemstra  ---
*** Bug 434041 has been marked as a duplicate of this bug. ***

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

[plasma-systemmonitor] [Bug 434041] Labels in memory overview overlap and curve is wrong at the start

[Arjen Hiemstra]

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

Arjen Hiemstra  changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 Status|REPORTED|RESOLVED

--- Comment #2 from Arjen Hiemstra  ---


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

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

[gcompris] [Bug 434137] the water does not run on the flame

[bugzilla_noreply]

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

anim...@gmail.com changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|CONFIRMED   |RESOLVED

--- Comment #2 from anim...@gmail.com ---
Should be fixed with commit ceaffefc

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

[plasma-systemmonitor] [Bug 434041] Labels in memory overview overlap and curve is wrong at the start

[Arjen Hiemstra]

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

--- Comment #3 from Arjen Hiemstra  ---
> Also the line starts out very weirdly. The memory usage profile was flat for 
> the last 10 hours, but the widgets shows a few weird jumps in the beginning. 
> This is probably related to the smoothing?

This is an unfortunate artifact of the smoothing algorithm that doesn't deal
well with rapid changes in value. Unfortunately it's all a tradeoff since there
are ways to avoid the spikes but those cause other issues. Right now the
algorithm at least matches what other chart libraries out there do.

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

[frameworks-kglobalaccel] [Bug 403636] Media Pause button doesn't work properly

[Bug Janitor Service]

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

Bug Janitor Service  changed:

   What|Removed |Added

 Status|CONFIRMED   |ASSIGNED

--- Comment #16 from Bug Janitor Service  ---
A possibly relevant merge request was started @
https://invent.kde.org/frameworks/kwindowsystem/-/merge_requests/15

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

[neon] [Bug 400386] Sometimes Drkonqi does not install debug packages of KDE software on neon unstable edition

[Harald Sitter]

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

--- Comment #15 from Harald Sitter  ---
Right. So. What's going on there is that you somehow have foreign stuff
installed in the form of /lib/x86_64-linux-gnu/libsnapd-glib.so.1 and
snapd-glib.so.1, but they aren't coming from a deb, much less from a deb that
is neon's or ubuntu's (which are the only ones that would generally have debug
symbols). Consequently the tool can't resolve packages to install to improve
the backtrace. There's nothing we can do there, in fact, I don't think we can
even detect this any better.

This is kind of going off on a tangent but that backtrace isn't of very good
quality actually ;). When scoring a trace, drkonqi looks at the quality of each
line in the crashing thread (the one at the bottom in your paste) and then
additionally weights them how close they are to the origin of the crash. That
is because in the frames closest to the crash is where things usually have gone
wrong

e.g. in your trace frame #6 is of poor quality (it lacks source file reference
and line reference) and has a weight of 13, frame 7-9 are of the worst quality
and contain no useful information whatsoever with a weight of 12-10. To put
that into perspective the weight of these 4 frames is 46, the weight of the
remaining frames is only 45: even though the other frames are of excellent
quality they are less than half as impactful on the overall score. All in all
the trace is probably at 1 star quality and very close to two stars (the fact
that the first frame is somewhat useful pulls the score up quite a bit). 

And to get back to the original problem. The reason the top most frames score
so poorly is because they are from the library that isn't from us or ubuntu so
there are no debug symbols.

I'll leave the bug open in case you find another example where resolution
fails. This one at least wasn't our fault :)

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

[Powerdevil] [Bug 434012] while playing an audio stream monitor is switched off after a delay

[Philippe ROUBACH]

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

--- Comment #4 from Philippe ROUBACH  ---
I don't believe that FF, Chrome, webkit gets a bug. It's too much.

Perhaps FF, Chrome, webkit send the request and the request is not transmitted.

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

[plasma-systemmonitor] [Bug 434074] System Monitor segmentation faulted in QWidget::internalWinId() when terminating processes running as root

[Bug Janitor Service]

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

Bug Janitor Service  changed:

   What|Removed |Added

 Status|REPORTED|ASSIGNED
 Ever confirmed|0   |1

--- Comment #2 from Bug Janitor Service  ---
A possibly relevant merge request was started @
https://invent.kde.org/plasma/libksysguard/-/merge_requests/133

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

[plasmashell] [Bug 434139] New: Minimizing effect occurs in the wrong spot.

[Dashon]

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

Bug ID: 434139
   Summary: Minimizing effect occurs in the wrong spot.
   Product: plasmashell
   Version: 5.21.2
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Task Manager and Icons-Only Task Manager
  Assignee: h...@kde.org
  Reporter: dashonww...@pm.me
CC: plasma-b...@kde.org
  Target Milestone: 1.0

SUMMARY
The minimize effect, particularly I'm using the magic lamp effect, will occur
toward the left side of the task manager when the app in question is not pinned
to the task manager as well as started from the task manager. If a app is both
pinned to the task manager and started from the task manager then minimizing
the app will show the app going toward it's own icon. 

STEPS TO REPRODUCE PART 1
1. Launch an app not pinned to the task manager.
2. Minimize the app


OBSERVED RESULT
The minimize animation does not go towards the direction of its icon.

EXPECTED RESULT
The animation should go towards the direction of its own icon.

SOFTWARE/OS VERSIONS
Operating System: EndeavourOS
KDE Plasma Version: 5.21.2
KDE Frameworks Version: 5.79.0
Qt Version: 5.15.2
Kernel Version: 5.10.11-zen2-1-zen
OS Type: 64-bit
Graphics Platform: X11
Processors: 4 × Intel® Core™ i7-7500U CPU @ 2.70GHz
Memory: 15.4 GiB of RAM
Graphics Processor: Mesa Intel® HD Graphics 620

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

[plasmashell] [Bug 434139] Minimizing effect occurs in the wrong spot.

[Dashon]

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

Dashon  changed:

   What|Removed |Added

 CC||dashonww...@pm.me

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

[plasma-systemmonitor] [Bug 434040] Default CPU usage graph scales badly to 16+ cores

[Arjen Hiemstra]

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

Arjen Hiemstra  changed:

   What|Removed |Added

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

--- Comment #2 from Arjen Hiemstra  ---
Please don't put multiple issues in one report, it makes it hard to deal with
the individual issues.

> But KSysguard solved that more nicely, by first shrinking the legend to just 
> colored percentages. You should still wrap them at some point, because 
> otherwise 48 threads will fit on pretty much no screen, but having a colored 
> line next to it is not very useful at that size.

This may be tweaked later, but KSysGuard's solution also does not scale too
well and additionally has quite some contrast problems.

> Secondly, the default of using a stacked chart leads to a chart going to 
> 1600%, but because only one core is pinned, that one sits at 1/16th of the 
> chart. This does not provide much useful information about why an application 
> hangs, since it looks like it is hanging in IO instead of in a CPU loop.

Seems to me this is better solved by the process table? How would you even
distinguish single process usage from the history chart? In any case, stacked
means you get to see individual core usage as well as overall usage and in my
opinion it is actually easier to distinguish cores, even with lower fill
opacity the screenshot of KSysGuard is pretty useless to me. That said, this is
why the entire thing is configurable so you can choose not to use stacked (and
as David said, you can also choose the fill opacity.)

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

[plasma-disks] [Bug 429804] kinfocenter does not detect problem with hard disk

[Bug Janitor Service]

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

Bug Janitor Service  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|REPORTED|ASSIGNED

--- Comment #9 from Bug Janitor Service  ---
A possibly relevant merge request was started @
https://invent.kde.org/plasma/plasma-disks/-/merge_requests/14

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

[neon] [Bug 434038] Please provide an updated version of Maliit that is usable

[Nathan]

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

--- Comment #4 from Nathan <2gd4...@gmail.com> ---
I temporarily switched to the unstable repo and manged to install
maliit-keyboard with its dependancies without any issues. I could not get it to
work but it has installed.

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

[lattedock] [Bug 434070] Blurred bar at the bottom of the dock when blur is enabled and using "screen" margins.

[phoenix.]

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

phoenix.  changed:

   What|Removed |Added

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

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

[lattedock] [Bug 434070] Blurred bar at the bottom of the dock when blur is enabled and using "screen" margins.

[phoenix.]

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

--- Comment #23 from phoenix.  ---
still happens, using aur git version. also tried kde gitlab version. still the
same

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

[lattedock] [Bug 434070] Blurred bar at the bottom of the dock when blur is enabled and using "screen" margins.

[Michail Vourlakos]

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

--- Comment #24 from Michail Vourlakos  ---
(In reply to phoenix. from comment #23)
> still happens, using aur git version. also tried kde gitlab version. still
> the same

if you use Breeze as plasma theme is this reproducable?

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

[plasma-systemmonitor] [Bug 434037] Application page should be hidden on unsupported systems

[Arjen Hiemstra]

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

Arjen Hiemstra  changed:

   What|Removed |Added

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

--- Comment #1 from Arjen Hiemstra  ---
This has already been fixed in master.

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

[plasma-systemmonitor] [Bug 434037] Application page should be hidden on unsupported systems

[Arjen Hiemstra]

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

Arjen Hiemstra  changed:

   What|Removed |Added

   Version Fixed In||Plasma 5.22

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

[frameworks-kwayland] [Bug 433791] Crash when closing window after being opened more than once

[Harald Sitter]

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

Harald Sitter  changed:

   What|Removed |Added

 CC||kwin-bugs-n...@kde.org
Version|5.21.0  |5.79.0
Product|kinfocenter |frameworks-kwayland
  Component|general |general
   Assignee|plasma-b...@kde.org |mgraess...@kde.org

--- Comment #4 from Harald Sitter  ---
Crash is in kwayland. Moving bug.

The backtrace is unfortunately missing the most important frame.

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

[frameworks-kglobalaccel] [Bug 403636] Media Pause button doesn't work properly

[David Redondo]

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

David Redondo  changed:

   What|Removed |Added

 Status|ASSIGNED|RESOLVED
 Resolution|--- |FIXED
  Latest Commit||https://invent.kde.org/fram
   ||eworks/kwindowsystem/commit
   ||/53daf6bff454bf8c0a2cb18a57
   ||587de5d9e93887

--- Comment #17 from David Redondo  ---
Git commit 53daf6bff454bf8c0a2cb18a57587de5d9e93887 by David Redondo.
Committed on 08/03/2021 at 11:22.
Pushed by davidre into branch 'master'.

Add MediaPause key to mapping

We were missing it.

M  +1-0src/platforms/xcb/kkeyserver.cpp

https://invent.kde.org/frameworks/kwindowsystem/commit/53daf6bff454bf8c0a2cb18a57587de5d9e93887

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

[plasma-nm] [Bug 433254] plasma network-manager fails to connect to PAN GP vpn

[Andrei Slavoiu]

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

Andrei Slavoiu  changed:

   What|Removed |Added

 CC||ansl...@yahoo.com

--- Comment #1 from Andrei Slavoiu  ---
Confirming. I had my PAN GP configured and working fine for several months.
Today, after changing the gateway for an experiment, I couldn't get it to work
with either the new or old gateway. Turns out saving the configuration changed
the protocol from PAN GP to Pulse and it was impossible to change it back to
PAN GP from the UI, it kept being changed to Pulse when saving the config.

Workaround: stop NetworkManager service and manually edit the connection file,
in the section [vpn] replace line "protocol=pulse" with "protocol=gp", start
the NetworkManager service back. As long a plasma-nm is only used to
connect/disconnect from VPN everithing is fine.

Linux: 5.11.2
KDE Plasma Version: 5.21.2
KDE Frameworks Version: 5.79.0
Qt Version: 5.15.2
NetworkNamager version: 1.28.0
openconnect version: 8.10

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

[dolphin] [Bug 428567] Improve RTL interface for Dolphin

[Omeritzics]

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

Omeritzics  changed:

   What|Removed |Added

 Attachment #132987|How the RTL interface   |How the RTL interface
description|should be   |should be (illustration)

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

[neon] [Bug 400386] Sometimes Drkonqi does not install debug packages of KDE software on neon unstable edition

[Patrick Silva]

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

--- Comment #16 from Patrick Silva  ---
Thanks for your detailed explanation Harald.

libsnapd-glib1 package owns /lib/x86_64-linux-gnu/libsnapd-glib.so.1.

$ sudo apt-file search /lib/x86_64-linux-gnu/libsnapd-glib.so.1
libsnapd-glib1: /usr/lib/x86_64-linux-gnu/libsnapd-glib.so.1
libsnapd-glib1: /usr/lib/x86_64-linux-gnu/libsnapd-glib.so.1.0.0

libsnapd-glib1 package is available in ubuntu repos:

$ apt info libsnapd-glib1
Package: libsnapd-glib1
Version: 1.58-0ubuntu0.20.04.0
Priority: optional
Section: libs
Source: snapd-glib
Origin: Ubuntu
Maintainer: Ubuntu Developers 
Original-Maintainer: Ayatana Packagers

Bugs: https://bugs.launchpad.net/ubuntu/+filebug
Installed-Size: 373 kB
Depends: libc6 (>= 2.4), libglib2.0-0 (>= 2.46), libjson-glib-1.0-0 (>= 1.2.0),
libsoup2.4-1 (>= 2.39.2)
Suggests: snapd
Homepage: https://github.com/snapcore/snapd-glib
Task: ubuntu-desktop-minimal, ubuntu-desktop, kubuntu-desktop, xubuntu-core,
xubuntu-desktop, lubuntu-desktop, ubuntustudio-video, ubuntustudio-audio,
ubuntukylin-desktop, ubuntu-mate-core, ubuntu-mate-desktop,
ubuntu-budgie-desktop
Download-Size: 90,1 kB
APT-Manual-Installed: no
APT-Sources: http://ubuntu.c3sl.ufpr.br/ubuntu focal-updates/main amd64
Packages
Description: GLib snapd library

N: There is 1 additional record. Please use the '-a' switch to see it


I have installed libsnapd-glib1-dbgsym package manually and tried to generate a
good backtrace with drkonqi after re-login, but it failed with "debugger quit
unexpectedly" or similar error message. Then I rebooted my laptop and drkonqi
was finally able to generate a good backtrace.

Application: Discover (plasma-discover), signal: Segmentation fault
Content of s_kcrashErrorMessage: [Current thread is 1 (Thread 0x7f4f84075e40
(LWP 1300))]
[New LWP 1302]
[New LWP 1303]
[New LWP 1304]
[New LWP 1305]
[New LWP 1306]
[New LWP 1307]
[New LWP 1308]
[New LWP 1309]
[New LWP 1312]
[New LWP 1313]
[New LWP 1314]
[New LWP 1315]
[New LWP 1321]
[New LWP 1323]
[New LWP 1353]
[New LWP 1419]
[New LWP 1420]
[New LWP 1421]
[New LWP 1422]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
0x7f4f8863faff in __GI___poll (fds=fds@entry=0x7ffc65b7e8a8,
nfds=nfds@entry=1, timeout=timeout@entry=1000) at
../sysdeps/unix/sysv/linux/poll.c:29

Thread 20 (Thread 0x7f4ef77fe700 (LWP 1422)):
#0  0x7f4f86fb1112 in g_source_iter_next (iter=iter@entry=0x7f4ef77fda20,
source=source@entry=0x7f4ef77fda18) at ../../../glib/gmain.c:1053
#1  0x7f4f86fb2adf in g_main_context_check
(context=context@entry=0x7f4ef0325800, max_priority=2147483647,
fds=fds@entry=0x7f4ef0336fe0, n_fds=n_fds@entry=1) at
../../../glib/gmain.c:3860
#2  0x7f4f86fb3132 in g_main_context_iterate
(context=context@entry=0x7f4ef0325800, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at ../../../glib/gmain.c:4044
#3  0x7f4f86fb32c3 in g_main_context_iteration (context=0x7f4ef0325800,
may_block=may_block@entry=1) at ../../../glib/gmain.c:4108
#4  0x7f4f88c0afbb in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7f4ef002d6c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#5  0x7f4f88baf1ab in
QEventLoop::exec(QFlags)
(this=this@entry=0x7f4ef77fdbe0, flags=..., flags@entry=...) at
../../include/QtCore/../../src/corelib/global/qflags.h:141
#6  0x7f4f889c9a12 in QThread::exec() (this=this@entry=0x55904a819480) at
../../include/QtCore/../../src/corelib/global/qflags.h:121
#7  0x7f4f8a72638a in QQuickPixmapReader::run() (this=0x55904a819480) at
util/qquickpixmapcache.cpp:1024
#8  0x7f4f889cabac in QThreadPrivate::start(void*) (arg=0x55904a819480) at
thread/qthread_unix.cpp:329
#9  0x7f4f87960609 in start_thread (arg=) at
pthread_create.c:477
#10 0x7f4f8864c293 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 19 (Thread 0x7f4f117fd700 (LWP 1421)):
#0  futex_abstimed_wait_cancelable (private=,
abstime=0x7f4f117fcb90, clockid=, expected=0,
futex_word=0x55904980fef4) at ../sysdeps/nptl/futex-internal.h:320
#1  __pthread_cond_wait_common (abstime=0x7f4f117fcb90, clockid=, mutex=0x55904980fea0, cond=0x55904980fec8) at pthread_cond_wait.c:520
#2  __pthread_cond_timedwait (cond=0x55904980fec8, mutex=0x55904980fea0,
abstime=0x7f4f117fcb90) at pthread_cond_wait.c:656
#3  0x7f4f889d0ca8 in QWaitConditionPrivate::wait_relative(QDeadlineTimer)
(this=0x55904980fea0, deadline=...) at thread/qwaitcondition_unix.cpp:136
#4  QWaitConditionPrivate::wait(QDeadlineTimer) (deadline=...,
this=0x55904980fea0) at thread/qwaitcondition_unix.cpp:144
#5  QWaitCondition::wait(QMutex*, QDeadlineTimer)
(this=this@entry=0x55904a25b2c0, mutex=mutex@entry=0x559045c7e008,
deadline=...) at thread/qwaitcondition_unix.cpp:225
#6  0x7f4f889ce1b1 in QThreadPoolThread::run() (this=0x55904a25b2b0) at
../../include/QtCore/../../src/corelib/thread/qmutex.h:270
#7  0x7f4f889cabac in QThreadPrivate::start(void*) (arg=0x559

[Discover] [Bug 425680] Discover crashes when I cancel Snap installation

[Patrick Silva]

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

--- Comment #3 from Patrick Silva  ---
new and better backtrace:

Application: Discover (plasma-discover), signal: Segmentation fault
Content of s_kcrashErrorMessage: [Current thread is 1 (Thread 0x7f4f84075e40
(LWP 1300))]
[New LWP 1302]
[New LWP 1303]
[New LWP 1304]
[New LWP 1305]
[New LWP 1306]
[New LWP 1307]
[New LWP 1308]
[New LWP 1309]
[New LWP 1312]
[New LWP 1313]
[New LWP 1314]
[New LWP 1315]
[New LWP 1321]
[New LWP 1323]
[New LWP 1353]
[New LWP 1419]
[New LWP 1420]
[New LWP 1421]
[New LWP 1422]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
0x7f4f8863faff in __GI___poll (fds=fds@entry=0x7ffc65b7e8a8,
nfds=nfds@entry=1, timeout=timeout@entry=1000) at
../sysdeps/unix/sysv/linux/poll.c:29

Thread 20 (Thread 0x7f4ef77fe700 (LWP 1422)):
#0  0x7f4f86fb1112 in g_source_iter_next (iter=iter@entry=0x7f4ef77fda20,
source=source@entry=0x7f4ef77fda18) at ../../../glib/gmain.c:1053
#1  0x7f4f86fb2adf in g_main_context_check
(context=context@entry=0x7f4ef0325800, max_priority=2147483647,
fds=fds@entry=0x7f4ef0336fe0, n_fds=n_fds@entry=1) at
../../../glib/gmain.c:3860
#2  0x7f4f86fb3132 in g_main_context_iterate
(context=context@entry=0x7f4ef0325800, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at ../../../glib/gmain.c:4044
#3  0x7f4f86fb32c3 in g_main_context_iteration (context=0x7f4ef0325800,
may_block=may_block@entry=1) at ../../../glib/gmain.c:4108
#4  0x7f4f88c0afbb in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7f4ef002d6c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#5  0x7f4f88baf1ab in
QEventLoop::exec(QFlags)
(this=this@entry=0x7f4ef77fdbe0, flags=..., flags@entry=...) at
../../include/QtCore/../../src/corelib/global/qflags.h:141
#6  0x7f4f889c9a12 in QThread::exec() (this=this@entry=0x55904a819480) at
../../include/QtCore/../../src/corelib/global/qflags.h:121
#7  0x7f4f8a72638a in QQuickPixmapReader::run() (this=0x55904a819480) at
util/qquickpixmapcache.cpp:1024
#8  0x7f4f889cabac in QThreadPrivate::start(void*) (arg=0x55904a819480) at
thread/qthread_unix.cpp:329
#9  0x7f4f87960609 in start_thread (arg=) at
pthread_create.c:477
#10 0x7f4f8864c293 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 19 (Thread 0x7f4f117fd700 (LWP 1421)):
#0  futex_abstimed_wait_cancelable (private=,
abstime=0x7f4f117fcb90, clockid=, expected=0,
futex_word=0x55904980fef4) at ../sysdeps/nptl/futex-internal.h:320
#1  __pthread_cond_wait_common (abstime=0x7f4f117fcb90, clockid=, mutex=0x55904980fea0, cond=0x55904980fec8) at pthread_cond_wait.c:520
#2  __pthread_cond_timedwait (cond=0x55904980fec8, mutex=0x55904980fea0,
abstime=0x7f4f117fcb90) at pthread_cond_wait.c:656
#3  0x7f4f889d0ca8 in QWaitConditionPrivate::wait_relative(QDeadlineTimer)
(this=0x55904980fea0, deadline=...) at thread/qwaitcondition_unix.cpp:136
#4  QWaitConditionPrivate::wait(QDeadlineTimer) (deadline=...,
this=0x55904980fea0) at thread/qwaitcondition_unix.cpp:144
#5  QWaitCondition::wait(QMutex*, QDeadlineTimer)
(this=this@entry=0x55904a25b2c0, mutex=mutex@entry=0x559045c7e008,
deadline=...) at thread/qwaitcondition_unix.cpp:225
#6  0x7f4f889ce1b1 in QThreadPoolThread::run() (this=0x55904a25b2b0) at
../../include/QtCore/../../src/corelib/thread/qmutex.h:270
#7  0x7f4f889cabac in QThreadPrivate::start(void*) (arg=0x55904a25b2b0) at
thread/qthread_unix.cpp:329
#8  0x7f4f87960609 in start_thread (arg=) at
pthread_create.c:477
#9  0x7f4f8864c293 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 18 (Thread 0x7f4f10ffc700 (LWP 1420)):
#0  futex_abstimed_wait_cancelable (private=,
abstime=0x7f4f10ffbb90, clockid=, expected=0,
futex_word=0x559049fd8190) at ../sysdeps/nptl/futex-internal.h:320
#1  __pthread_cond_wait_common (abstime=0x7f4f10ffbb90, clockid=, mutex=0x559049fd8140, cond=0x559049fd8168) at pthread_cond_wait.c:520
#2  __pthread_cond_timedwait (cond=0x559049fd8168, mutex=0x559049fd8140,
abstime=0x7f4f10ffbb90) at pthread_cond_wait.c:656
#3  0x7f4f889d0ca8 in QWaitConditionPrivate::wait_relative(QDeadlineTimer)
(this=0x559049fd8140, deadline=...) at thread/qwaitcondition_unix.cpp:136
#4  QWaitConditionPrivate::wait(QDeadlineTimer) (deadline=...,
this=0x559049fd8140) at thread/qwaitcondition_unix.cpp:144
#5  QWaitCondition::wait(QMutex*, QDeadlineTimer)
(this=this@entry=0x55904a0c4060, mutex=mutex@entry=0x559045c7e008,
deadline=...) at thread/qwaitcondition_unix.cpp:225
#6  0x7f4f889ce1b1 in QThreadPoolThread::run() (this=0x55904a0c4050) at
../../include/QtCore/../../src/corelib/thread/qmutex.h:270
#7  0x7f4f889cabac in QThreadPrivate::start(void*) (arg=0x55904a0c4050) at
thread/qthread_unix.cpp:329
#8  0x7f4f87960609 in start_thread (arg=) at
pthread_create.c:477
#9  0x7f4f8864c293 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 17 (Thread 0x7f4f46874700 (LWP 1419)):
#

[Discover] [Bug 432971] Discover constantly lists "KDE Application Platform" as having an update when there is no update

[Aleix Pol]

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

Aleix Pol  changed:

   What|Removed |Added

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

--- Comment #3 from Aleix Pol  ---
Thank you!

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

[neon] [Bug 400386] Sometimes Drkonqi does not install debug packages of KDE software on neon unstable edition

[Harald Sitter]

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

--- Comment #17 from Harald Sitter  ---
(In reply to Patrick Silva from comment #16)
> Thanks for your detailed explanation Harald.
> 
> libsnapd-glib1 package owns /lib/x86_64-linux-gnu/libsnapd-glib.so.1.
> 
> $ sudo apt-file search /lib/x86_64-linux-gnu/libsnapd-glib.so.1
> libsnapd-glib1: /usr/lib/x86_64-linux-gnu/libsnapd-glib.so.1
> libsnapd-glib1: /usr/lib/x86_64-linux-gnu/libsnapd-glib.so.1.0.0

It's cool that this worked but there's still something funny about it

/lib/x86_64-linux-gnu/libsnapd-glib.so.1 (the path you have)

is not

/usr/lib/x86_64-linux-gnu/libsnapd-glib.so.1 (the path the package has)

I have the package installed and the file in /lib doesn't exist for me. Yet
they must be the same file otherwise you'd not have managed to generate a trace
(gdb resolves symbols by a build-specific debug id set at build time, meaning
that since gdb found the symbols it must be the same file from the same build).
Perhaps something copied the file to /lib?

It's very strange but doesn't really change the fact that we can't resolve the
debug package for a file path that dpkg doesn't know about ^^

BTW, you need also libsnapd-qt1-dbgsym. The top most frame still is missing
source context.

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

[drkonqi] [Bug 432924] drkonqi crash on wayland

[Harald Sitter]

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

Harald Sitter  changed:

   What|Removed |Added

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

--- Comment #2 from Harald Sitter  ---
Is this reproducible? If so please provide some steps.

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

[Powerdevil] [Bug 434012] while playing an audio stream monitor is switched off after a delay

[Nicolas Fella]

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

--- Comment #5 from Nicolas Fella  ---
When power management is inhibited the applet displays that. Please check if
this is the case for you

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

[Powerdevil] [Bug 434012] while playing an audio stream monitor is switched off after a delay

[Nicolas Fella]

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

--- Comment #6 from Nicolas Fella  ---
Created attachment 136487
  --> https://bugs.kde.org/attachment.cgi?id=136487&action=edit
Screenshot

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

[plasma-systemmonitor] [Bug 434074] System Monitor segmentation faulted in QWidget::internalWinId() when terminating processes running as root

[Arjen Hiemstra]

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

Arjen Hiemstra  changed:

   What|Removed |Added

 Status|ASSIGNED|RESOLVED
  Latest Commit||https://invent.kde.org/plas
   ||ma/libksysguard/commit/2e2f
   ||52d29932ce49ab2ae92aac6dc76
   ||75d66fd12
 Resolution|--- |FIXED

--- Comment #3 from Arjen Hiemstra  ---
Git commit 2e2f52d29932ce49ab2ae92aac6dc7675d66fd12 by Arjen Hiemstra.
Committed on 08/03/2021 at 11:55.
Pushed by ahiemstra into branch 'master'.

Properly initialize the parent widget to nullptr in ProcessController

Otherwise we end up sending some garbage pointer address to KAuth which
will crash trying to dereference it.

M  +1-1processcore/process_controller.cpp

https://invent.kde.org/plasma/libksysguard/commit/2e2f52d29932ce49ab2ae92aac6dc7675d66fd12

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

[plasma-systemmonitor] [Bug 434074] System Monitor segmentation faulted in QWidget::internalWinId() when terminating processes running as root

[Arjen Hiemstra]

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

Arjen Hiemstra  changed:

   What|Removed |Added

  Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas
   |ma/libksysguard/commit/2e2f |ma/libksysguard/commit/77e7
   |52d29932ce49ab2ae92aac6dc76 |b53cd8ad19eac09078c092943f5
   |75d66fd12   |19797c4b6

--- Comment #4 from Arjen Hiemstra  ---
Git commit 77e7b53cd8ad19eac09078c092943f519797c4b6 by Arjen Hiemstra.
Committed on 08/03/2021 at 12:43.
Pushed by ahiemstra into branch 'Plasma/5.21'.

Properly initialize the parent widget to nullptr in ProcessController

Otherwise we end up sending some garbage pointer address to KAuth which
will crash trying to dereference it.


(cherry picked from commit 2e2f52d29932ce49ab2ae92aac6dc7675d66fd12)

M  +1-1processcore/process_controller.cpp

https://invent.kde.org/plasma/libksysguard/commit/77e7b53cd8ad19eac09078c092943f519797c4b6

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

[systemsettings] [Bug 434138] kinfocenter crashes at startup on neon unstable

[Nicolas Fella]

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

Nicolas Fella  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
 CC||nicolas.fe...@gmx.de
 Resolution|--- |DUPLICATE

--- Comment #1 from Nicolas Fella  ---


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

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

[systemsettings] [Bug 434045] Systemsettings crashes "org.kde.systemsettings.app: Error loading plugin"

[Nicolas Fella]

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

Nicolas Fella  changed:

   What|Removed |Added

 CC||bugsefor...@gmx.com

--- Comment #8 from Nicolas Fella  ---
*** Bug 434138 has been marked as a duplicate of this bug. ***

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

[konsole] [Bug 433945] Background transparency not applied to custom background colors

[J]

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

--- Comment #6 from J  ---
Hi

Thanks for the info, I have installed the One Half Light Theme and had another
play around.
I have run the original ANSI escape code you specified ("echo -e
'\u001b[40m123456'" ) using the One Half Light Theme set to 50% transparency
and it shows the same blocked out text background in your first image. 

To confirm it was not the theme itself I tried a variety of colour schemes, and
as you mentioned any black background colour scheme set to 50% transparency
displays the text the correct way(readable), but any colour scheme with a light
or white background displays the text in a black box (Barely readable or
unreadable) same as the example in your first image.


Conclusion:
I was able to reproduce after installing the custom theme (One Half Light) and
testing any default colour scheme with a light or white background.

Software/OS Version:
Operating System: Fedora 33
KDE Plasma Version: 5.20.5
KDE Frameworks Version: 5.79.0
Qt Version: 5.15.2
Kernel Version: 5.10.17-200.fc33.x86_64
OS Type: 64-bit

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

[kdenlive] [Bug 358046] Changelog missing since 15.12

[farid]

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

farid  changed:

   What|Removed |Added

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

--- Comment #11 from farid  ---
What exactly is needed to resolve this task?

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

[kdenlive] [Bug 402550] Rendering of 30-minute video to default Generic MPEG-2 takes more than 12 hours and no sound

[bugzilla_noreply]

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

--- Comment #6 from iticdig...@disroot.org ---
Created attachment 136488
  --> https://bugs.kde.org/attachment.cgi?id=136488&action=edit
screenshot of timeline

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

[neon] [Bug 400386] Sometimes Drkonqi does not install debug packages of KDE software on neon unstable edition

[Patrick Silva]

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

--- Comment #18 from Patrick Silva  ---
(In reply to Harald Sitter from comment #17)
> Perhaps something copied the file to /lib?

I don't know. Is there any way to find this out?

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