date:20231205

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

Bug Janitor Service  changed:

   What|Removed |Added

   Severity|normal  |crash

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

[digikam] [Bug 478038] Unable to load the picture

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

Maik Qualmann  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
 CC||metzping...@gmail.com
 Resolution|--- |DUPLICATE

--- Comment #2 from Maik Qualmann  ---


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

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

[digikam] [Bug 439581] Problems under Ubuntu with digiKam as snap package

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

Maik Qualmann  changed:

   What|Removed |Added

 CC||bruno.sap...@laposte.net

--- Comment #37 from Maik Qualmann  ---
*** Bug 478038 has been marked as a duplicate of this bug. ***

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

[Falkon] [Bug 477234] Extension "Aktion ausführen" (this German text can be translated into English like "Execute Action") cannot get loaded

2023-12-05 Thread Juraj

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

--- Comment #3 from Juraj  ---
Hello,

> Does that mean it makes no sense to report new bugs in Falkon
> for all current and maybe future Falkon versions which are still based on QT5

It means that Falkon is being ported to Qt6.

 > Should I wait with reporting new bug issues until the Falkon source
> code will be based on QT6 and can locally get cloned using git?

The "master" branch in git is already Qt6 only and most of the stuff works just
fine.

> Or does it depend on specific software elements, like (specific) browser 
> extensions,
> if it makes sense to currently or still test them or not? 

Well, the extensions in the store[1] will probably not work, unless they are
ported as well.
Most of the other stuff should work, there are mostly only the things which are
harder to find.

It is very helpful to get a beta version a run and report bugs, even if they
will be reported 10 times.
Honestly I overlooked the extensions while porting, it compiles so we can ship
it.

> Are there specific browser extensions embedded into the Falkon QT5 based
> source code which will not be available anymore in the future QT6 based 
> Falkon source code?

All extensions shipped with Falkon should be ported to Qt6.
There is a regression with StatusBarIcons in the Network availability icon, it
does not work yet since this needs to be rewritten and some features added to
Falkon itself. But since Falkon is part of KDE Gear we hit the feature freeze
for 24.02 version and will strive to fix this and more for 24.04 release.

Thank you,
Juraj

PS: Hope it makes sense.
PS:2 All bugreports are welcome, even if there is no reply I read all of them.

[1]: https://store.falkon.org/

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

[digikam] [Bug 477853] digiKam 8.3.0 slow startup on Windows 10 operating system

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

--- Comment #31 from Maik Qualmann  ---
As a note to everyone for whom our current digiKam version, created with Qt6
and  Microsoft Komplier, is too slow, here is a version that was created as
before:

https://download.kde.org/stable/digikam/8.2.0/digiKam-8.2.0-Qt5-Win64.exe

I have now tested both versions here with all database backends on a Windows 10
machine. At the moment "only" with a collection of 50,000 images but with a lot
of albums. But I have no difference when starting, performing database
operations or opening the configuration settings.

I therefore suspect that it may be related to runtime libraries that users have
previously installed. I therefore ask you to install/update the "Visual C++
Redistributable for Visual Studio 2015".

Maik

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

[digikam] [Bug 477853] digiKam 8.3.0 slow startup on Windows 10 operating system

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

Maik Qualmann  changed:

   What|Removed |Added

 CC||erik.herle+digi...@gmail.co
   ||m

--- Comment #30 from Maik Qualmann  ---
*** Bug 478131 has been marked as a duplicate of this bug. ***

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

[digikam] [Bug 478131] dK 8.2.0 very slow and crashes in Windows 10

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

Maik Qualmann  changed:

   What|Removed |Added

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

--- Comment #2 from Maik Qualmann  ---


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

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

[digikam] [Bug 477853] digiKam 8.3.0 slow startup on Windows 10 operating system

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

--- Comment #29 from Maik Qualmann  ---
*** Bug 478075 has been marked as a duplicate of this bug. ***

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

[digikam] [Bug 478075] All database operations are far slower than with previous version

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

Maik Qualmann  changed:

   What|Removed |Added

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

--- Comment #4 from Maik Qualmann  ---


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

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

[digikam] [Bug 478131] dK 8.2.0 very slow and crashes in Windows 10

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

Maik Qualmann  changed:

   What|Removed |Added

 CC||metzping...@gmail.com

--- Comment #1 from Maik Qualmann  ---
Crash is fixed with this Bug 477871

Maik

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

[digikam] [Bug 478136] Digikam crashes when manually adding or correcting people tag in Preview mode

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

Maik Qualmann  changed:

   What|Removed |Added

   Version Fixed In||8.3.0
 Resolution|--- |FIXED
 Status|REPORTED|RESOLVED

--- Comment #1 from Maik Qualmann  ---
Crash is fixed with this Bug 477871

Maik

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

[digikam] [Bug 478136] Digikam crashes when manually adding or correcting people tag in Preview mode

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

Maik Qualmann  changed:

   What|Removed |Added

 CC||metzping...@gmail.com

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

[Falkon] [Bug 477234] Extension "Aktion ausführen" (this German text can be translated into English like "Execute Action") cannot get loaded

2023-12-05 Thread Jens Radloff

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

--- Comment #2 from Jens Radloff  ---
(In reply to Juraj from comment #1)
> This extension is still Qt5 only.
> Thank you for reporting.

You are welcome.

Does that mean it makes no sense to report new bugs in Falkon for all current
and maybe future Falkon versions which are still based on QT5? 

Should I wait with reporting new bug issues until the Falkon source code will
be based on QT6 and can locally get cloned using git?

Or does it depend on specific software elements, like (specific) browser
extensions, if it makes sense to currently or still test them or not? 

Are there specific browser extensions embedded into the Falkon QT5 based source
code which will not be available anymore in the future QT6 based Falkon source
code?

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

[neon] [Bug 478147] New: fwupd shows segmentation fault

2023-12-05 Thread Dennis

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

Bug ID: 478147
   Summary: fwupd shows segmentation fault
Classification: KDE Neon
   Product: neon
   Version: unspecified
  Platform: Neon
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Packages Unstable Edition
  Assignee: neon-b...@kde.org
  Reporter: dennis@thegood.cloud
CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org
  Target Milestone: ---

SUMMARY
fwupd-service does not run (core-dump) and fwupdmgr/fwupdtool shows
segmentation fault.


STEPS TO REPRODUCE
1. pkcon update to latest
2. `sudo systemctl status fwupd.service`
3. `sudo fwupdtool refresh` && `sudo fwupdmgr get-updates`

OBSERVED RESULT
1. `sudo systemctl status fwupd.service
2. `fwupd.service - Firmware update daemon`
```
 Loaded: loaded (/lib/systemd/system/fwupd.service; static)
 Active: failed (Result: core-dump) since Wed 2023-12-06 07:32:01 CET;
10min ago
   Docs: https://fwupd.org/
Process: 32744 ExecStart=/usr/libexec/fwupd/fwupd (code=dumped,
signal=SEGV)
   Main PID: 32744 (code=dumped, signal=SEGV)
CPU: 1.345s

dec 06 07:31:57 xps13-edge systemd[1]: Starting Firmware update daemon...
dec 06 07:31:58 xps13-edge fwupd[32744]: 06:31:58.395 FuEngine
failed to add device usb:06:00:01:02: No de>
dec 06 07:31:59 xps13-edge fwupd[32744]: 06:31:59.466 FuPluginIntelMe 
failed to get public key using /fpf/OemCred>
dec 06 07:32:01 xps13-edge fwupd[32744]: 06:32:01.051 FuCommon
fu_path_get_files: assertion 'path != NULL'>
dec 06 07:32:01 xps13-edge systemd[1]: fwupd.service: Main process exited,
code=dumped, status=11/SEGV
dec 06 07:32:01 xps13-edge systemd[1]: fwupd.service: Failed with result
'core-dump'.
dec 06 07:32:01 xps13-edge systemd[1]: Failed to start Firmware update daemon.
dec 06 07:32:01 xps13-edge systemd[1]: fwupd.service: Consumed 1.345s CPU time.
```
2. `sudo fwupdtool refresh`
```
Loading… [***]06:42:49.363
FuEngine failed to add device usb:06:00:01:02: No device GType set
Loading… [***]06:42:50.458
FuPluginIntelMe  failed to get public key using /fpf/OemCred: generic
failure [0xb]
Loading… [** ]06:42:51.949
FuCommon fu_path_get_files: assertion 'path != NULL' failed
Segmentation fault
```
3. `sudo fwupdmgr get-updates`
```
Failed to connect to daemon: Error calling StartServiceByName for
org.freedesktop.fwupd: Failed to activate service 'org.freedesktop.fwupd':
timed out (service_start_timeout=25000ms)
```
EXPECTED RESULT
1. the system service fwupd.service should be running, yes?

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

`sudo fwupdtool --version`:
```
Loading… [** ]06:42:40.741
FuEngine failed to update history database: device ID
a45df35ac0e948ee180fe216a5f703f32dda163f was not found

compile   org.freedesktop.fwupd 1.9.7
compile   com.hughsie.libxmlb   0.3.14
compile   com.hughsie.libjcat   0.1.9
runtime   org.freedesktop.fwupd-efi 1.4
compile   org.freedesktop.gusb  0.3.10
runtime   org.freedesktop.gusb  0.3.10
runtime   org.freedesktop.fwupd 1.9.7
runtime   org.kernel6.2.0-37-generic
```

ADDITIONAL INFORMATION
- apt packages:
```
fwupd-signed/jammy-updates,now 1.51.1~22.04.1+1.4-0ubuntu0.1 amd64
[installed,automatic]
fwupd/jammy,now 1.9.7-1+22.04+jammy+unstable+build1 amd64 [installed,automatic]
libfwupd2/jammy,now 1.9.7-1+22.04+jammy+unstable+build1 amd64
[installed,automatic]
```

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

[dolphin] [Bug 478103] Choose application dialogue is overflowing

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

fanzhuyi...@gmail.com changed:

   What|Removed |Added

Version|unspecified |24.01.80

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

[dolphin] [Bug 478103] Choose application dialogue is overflowing

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

--- Comment #2 from fanzhuyi...@gmail.com ---
(In reply to fanzhuyifan from comment #1)
> Can reproduce.

Steps to reproduce:

1. create file with unknown extension
2. Right click, open with -> other application
3. scroll

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

[dolphin] [Bug 478103] Choose application dialogue is overflowing

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

fanzhuyi...@gmail.com changed:

   What|Removed |Added

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

--- Comment #1 from fanzhuyi...@gmail.com ---
Can reproduce.

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

[kwin] [Bug 478144] KWin effects do not display properly on the PinePhone

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

Bug Janitor Service  changed:

   What|Removed |Added

   Keywords||qt6

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

[kscreenlocker] [Bug 478111] entering password while screens wake up changes focus on password input

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

fanzhuyi...@gmail.com changed:

   What|Removed |Added

 CC||fanzhuyi...@gmail.com

--- Comment #1 from fanzhuyi...@gmail.com ---
Humm can't reproduce on plasma 6. For me the password focus only changes when I
move the mouse, even though the two screen wake up at different times. Maybe
this has been fixed?

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

[plasmashell] [Bug 478146] New: Desktop widgets that accept scroll input are not inverted when "natural scrolling" is enabled

2023-12-05 Thread Adam Fontenot

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

Bug ID: 478146
   Summary: Desktop widgets that accept scroll input are not
inverted when "natural scrolling" is enabled
Classification: Plasma
   Product: plasmashell
   Version: 5.90.0
  Platform: Arch Linux
OS: Linux
Status: REPORTED
  Keywords: qt6
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: adam.m.fontenot+...@gmail.com
CC: k...@davidedmundson.co.uk
  Target Milestone: 1.0

SUMMARY

This appears to be a regression between Plasma 5.27.9 (X11) and 5.90.0
(Wayland), which I am currently testing.

I use the natural scrolling option on my touchpad. It works in all applications
I've tested (e.g. Dolphin, Okular, Firefox). It does not work on 5.90.0 under
Wayland for any scrollable widget I've tested (volume, brightness).

With natural scrolling enabled, I naively expect that pulling down on the
widget increases the volume, but with this regression Plasma breaks the
expectation.

STEPS TO REPRODUCE
1. Enable natural scrolling
2. Try to scroll "down" (moving your fingers from top to bottom on the
touchpad).

OBSERVED RESULT
The volume / brightness / etc decreases.

EXPECTED RESULT
The volume / brightness / etc increases.


SOFTWARE/OS VERSIONS
Operating System: Arch Linux 
KDE Plasma Version: 5.90.0
KDE Frameworks Version: 5.246.0
Qt Version: 6.6.1
Kernel Version: 6.6.4-arch1-1 (64-bit)
Graphics Platform: Wayland

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

[kwin] [Bug 477959] Plasma 6 feels slow and not very responsive on a laptop with 6th gen i5

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

--- Comment #2 from techxga...@outlook.com ---
Hi Nate, I believe the problem is on the hardware itself.  This laptop is
recently acquired from a friend and the fan, I just realized, wasn't spinning. 
I'll keep you posted for when I get a replacement for it

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

[frameworks-kapidox] [Bug 478145] New: API docs styling for (at least) deprecated list is broken in dark mode

2023-12-05 Thread FeRD

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

Bug ID: 478145
   Summary: API docs styling for (at least) deprecated list is
broken in dark mode
Classification: Frameworks and Libraries
   Product: frameworks-kapidox
   Version: unspecified
  Platform: Other
OS: All
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdelibs-b...@kde.org
  Reporter: ferd...@gmail.com
  Target Milestone: ---

SUMMARY
See, for example,
https://api.kde.org/frameworks/kio/html/deprecated.html#_deprecated53

In dark mode, the list is unreadable, with the  contents being rendered in
white-on-white.

I **believe** this is due to a typo(?) in the CSS files for the documentation.

The doxygen.css file contains the following CSS, which governs that content and
is not palette-aware:

.memdoc, dl.reflist dd {
border-bottom: 1px solid #A8B8D9;  
border-left: 1px solid #A8B8D9;  
border-right: 1px solid #A8B8D9; 
padding: 6px 10px 2px 10px;
background-color: #FBFCFD;
border-top-width: 0;
background-image:url('nav_g.png');
background-repeat:repeat-x;
background-color: #FF;
/* opera specific markup */
border-bottom-left-radius: 4px;
border-bottom-right-radius: 4px;
box-shadow: 5px 5px 5px rgba(0, 0, 0, 0.15);
/* firefox specific markup */
-moz-border-radius-bottomleft: 4px;
-moz-border-radius-bottomright: 4px;
-moz-box-shadow: rgba(0, 0, 0, 0.15) 5px 5px 5px;
/* webkit specific markup */
-webkit-border-bottom-left-radius: 4px;
-webkit-border-bottom-right-radius: 4px;
-webkit-box-shadow: 5px 5px 5px rgba(0, 0, 0, 0.15);
}

customdoxygen.css, the palette-aware enhancement which SHOULD override those
colors, fails to in this case. The reason is because it contains no style rules
for ".memdoc, dl.reflist dd". Instead it contains this similar css, but note
the extra 'l' in "refllist":

.memdoc,
dl.refllist dd {
 background:var(--card);
 color:var(--on-card)
}

I don't know if "dl.refllist" — again, note the extra 'l' — is actually a valid
CSS selector anywhere ELSE in the code (but I doubt it). Or, perhaps it's
simply a typo of "dl.reflist" (probably). But, adding "dl.reflist" to that
style rule, like so:

.memdoc,
dl.reflist dd,
dl.refllist dd {
 background:var(--card);
 color:var(--on-card)
}

...conservatively fixes the styling for the deprecation-list page(s) (and
possibly elsewhere in the API docs), without any risk of breaking styling
elsewhere.

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

[kwin] [Bug 478144] New: KWin effects do not display properly on the PinePhone

2023-12-05 Thread Devin Lin

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

Bug ID: 478144
   Summary: KWin effects do not display properly on the PinePhone
Classification: Plasma
   Product: kwin
   Version: git master
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: major
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: espi...@gmail.com
  Target Milestone: ---

Created attachment 163933
  --> https://bugs.kde.org/attachment.cgi?id=163933=edit
Logs from KWin

SUMMARY
Opening a KWin effect causes the screen to go white. There seems to be some
shader error in the logs.

STEPS TO REPRODUCE
1. Open the task switcher in Plasma Mobile (implemented as a KWin effect)

OBSERVED RESULT
The screen goes white

EXPECTED RESULT
The effect being visible

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: git master
KDE Plasma Version: git master
KDE Frameworks Version: git master
Qt Version: 6.6

ADDITIONAL INFORMATION
See logs attached.

As a sidenote, there are different issues on the OnePlus 6 (the screen goes
black instead)

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

[plasma-nm] [Bug 478143] New: plasma-nm stops working after updates

2023-12-05 Thread Barış Salman

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

Bug ID: 478143
   Summary: plasma-nm stops working after updates
Classification: Plasma
   Product: plasma-nm
   Version: 5.27.9
  Platform: Debian unstable
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: applet
  Assignee: plasma-b...@kde.org
  Reporter: bars...@gmail.com
  Target Milestone: ---

SUMMARY
I run below command to upgrade. After the upgrade plasma-nm stops showing the
active connections. Connection stays active but not showned on plasma-nm.
sudo apt autoremove -y ; sudo apt autoclean -y; sudo apt update -y; sudo apt
upgrade -y 


STEPS TO REPRODUCE
1.  Be connected to a wifi
2. run the upgrade command
3.  watch plasma-nm

OBSERVED RESULT
plasma-nm not showing anything

EXPECTED RESULT
plasma-nm functioning normally

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux: 6.5.0 
(available in About System)
KDE Plasma Version: 5.27.9
KDE Frameworks Version: 5.107.0
Qt Version: 5.15.10

ADDITIONAL INFORMATION

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

[plasma-nm] [Bug 478142] New: plasma-nm widget talks demonic

2023-12-05 Thread Barış Salman

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

Bug ID: 478142
   Summary: plasma-nm widget talks demonic
Classification: Plasma
   Product: plasma-nm
   Version: 5.27.9
  Platform: Debian unstable
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: applet
  Assignee: plasma-b...@kde.org
  Reporter: bars...@gmail.com
  Target Milestone: ---

Created attachment 163932
  --> https://bugs.kde.org/attachment.cgi?id=163932=edit
screenshot of widget and the settings panel, above one suppose to say "redmi9c
bar"

SUMMARY
SSIDs are displayed as weird characters.


STEPS TO REPRODUCE
1.  No idea :/
2. 
3. 

OBSERVED RESULT
Weird characters in SSIDs

EXPECTED RESULT
I expected to see normal characters

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux: 6.5.0 
(available in About System)
KDE Plasma Version: 5.27.9
KDE Frameworks Version: 5.107.0
Qt Version: 5.15.10

ADDITIONAL INFORMATION

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

[okular] [Bug 478141] New: Height of the window decrease after changing tabs

2023-12-05 Thread Wankupi

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

Bug ID: 478141
   Summary: Height of the window decrease after changing tabs
Classification: Applications
   Product: okular
   Version: 23.08.3
  Platform: Arch Linux
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: okular-de...@kde.org
  Reporter: 2893353...@qq.com
  Target Milestone: ---

SUMMARY
After opening multiple tabs, switching tabs will reduce the window height.
The left top and right top will keep it's position, while the bottom will go up
some pixels (less than 10).

STEPS TO REPRODUCE
1.  open (>=2) files in one window
2. switch tabs ( press Ctrl+Tab will be more obviously )
3. focus on the bottom of the window

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 6.6.4-arch1-1
KDE Plasma Version: 5.27.10-1
KDE Frameworks Version: frameworkintegration5 5.112.0-2
Qt Version: qt5-base 5.15.11+kde+r147-1 (qt5) qt6-base 6.6.1-1 (qt6)

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

[kwin] [Bug 478140] Triggering "Overview" generates errors in system journal

2023-12-05 Thread Jin Liu

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

--- Comment #1 from Jin Liu  ---
This would cause a delay up to several seconds when triggering the effect.

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

[kwin] [Bug 478140] Triggering "Overview" generates errors in system journal

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

Bug Janitor Service  changed:

   What|Removed |Added

   Keywords||qt6

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

[plasma-systemmonitor] [Bug 478124] White background in the system monitor

2023-12-05 Thread Prajna Sariputra

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

Prajna Sariputra  changed:

   What|Removed |Added

 CC||putr...@gmail.com

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

[kwin] [Bug 478140] New: Triggering "Overview" generates errors in system journal

2023-12-05 Thread Jin Liu

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

Bug ID: 478140
   Summary: Triggering "Overview" generates errors in system
journal
Classification: Plasma
   Product: kwin
   Version: 5.90.0
  Platform: Arch Linux
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: effects-overview
  Assignee: kwin-bugs-n...@kde.org
  Reporter: ad.liu@gmail.com
  Target Milestone: ---

12月 06 12:21:20 laptop-jin-mi kwin_wayland[797]: QSqlDatabasePrivate::database:
requested database does not belong to the calling thread.
12月 06 12:21:20 laptop-jin-mi kwin_wayland[797]: kde.plasma.activitiesstats:
PlasmaActivities: Database is not open:  "" "" QSqlError("", "Driver not
loaded", "Driver not loaded")
12月 06 12:21:20 laptop-jin-mi kwin_wayland[797]: kde.plasma.activitiesstats:
Plasma Activities ERROR: There is no database. This probably means that you do
not have the Activity Manager running, or that something else is broken on your
system. Recent documents and alike will not work!
12月 06 12:21:20 laptop-jin-mi kwin_wayland[797]: QObject::startTimer: Timers
cannot be started from another thread
12月 06 12:21:21 laptop-jin-mi kwin_wayland[797]: QObject::killTimer: Timers
cannot be stopped from another thread

SOFTWARE/OS VERSIONS
Operating System: Arch Linux 
KDE Plasma Version: 5.90.0
KDE Frameworks Version: 5.246.0
Qt Version: 6.6.1
Kernel Version: 6.6.4-arch1-1 (64-bit)
Graphics Platform: offscreen
Processors: 12 × AMD Ryzen 5 5600H with Radeon Graphics
Memory: 13.5 GiB of RAM
Graphics Processor: AMD Radeon Graphics

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

[kwin] [Bug 478139] New: The status of color management under Plasma 6 + Wayland

2023-12-05 Thread Adam Fontenot

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

Bug ID: 478139
   Summary: The status of color management under Plasma 6 +
Wayland
Classification: Plasma
   Product: kwin
   Version: 5.90.0
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: compositing
  Assignee: kwin-bugs-n...@kde.org
  Reporter: adam.m.fontenot+...@gmail.com
  Target Milestone: ---

Created attachment 163931
  --> https://bugs.kde.org/attachment.cgi?id=163931=edit
Plasma 6 Color Management Status Board 2023-12-05

INTRODUCTION

This is going to be a very broad bug report, which is necessary given the
incomplete state of color management work for Plasma 6. I'm going to be
highlighting a number of issues I've encountered in testing the Plasma 6 beta.
Individual issues can be spun out from this as needed or upon request.

I'm hoping this report will help coordinate efforts around color management
under KDE + Wayland. I can test changes on calibrated WCG and HDR screens, and
update the status board I've included here.

OVERVIEW

If you're familiar with color management on Linux, skip this section.

Linux color management, in the traditional SDR + X11 world, comes in two
pieces. There is a gamut mapping piece, and a gamma / white balance / grey
balance adjustment piece. A calibrated device profile (*.icc, *.icm) contains
information about both - a display characterization that applications can use
to map managed colors into the display gamut along with a LUT that allows the
display to hit a particular gamma and color target.

Traditionally, colord was at the heart of this process. Colord loaded the LUT
into the video card gamma tables (VCGT), making this part of the color
correction process the responsibility of the graphics driver (hopefully
offloaded to hardware). Colord is also a daemon that applications talk to in
order to receive the display profile for their current screen. Applications
that did so managed their own colors. Applications that did not had unmanaged
colors (though they still benefited from the corrections applied via the VCGT).

Under Wayland, most compositors (including KWin) want to have control over the
process. As I understand it, the current plan for KWin is to have the
compositor apply both halves of color management itself. Rather than offloading
the gamma ramsp in the display profile to the VCGT, these are applied in the
compositor for each screen. Likewise, Wayland supporting applications are
supposed to communicate with the compositor (via a brand new protocol) to tell
it what intermediate profile they are targeting, which is then mapped by the
compositor into the display space.

This has several advantages: applications not supporting color management can
be assumed to be sRGB, so they will finally look right. And applications should
now be properly color-managed on multi-monitor setups, without any finicky
hacks by the application to switch profiles dynamically.

PLASMA 6 BETA STATUS

Please refer to the attached status board I've put together showing everything
I've been able to test, as well as stuff that I currently haven't been able to
test. The overall situation looks like this for the core features:

✅ KWin appears to handle the loading of ICC profiles on a per-display basis,
and applies the gamma curves within those profiles. I have not verified that it
does so correctly.

✅ KWin appears to apply color corrections to unmanaged applications, and
assumes sRGB -> display is the correct mapping for this. As a result of this,
previously unmanaged applications and the Plasma desktop itself look correct.
(At present, this might be implemented as a hack by mapping the entire screen
at once. If so this means that any form of color management for applications is
unsupported.)

❌ Legacy applications are broken at present. Even with the colord daemon
running, `colormgr get-devices` returns no devices when running under Plasma 6.
(The Color Management KCM is also missing, that's Bug 477083).

❌ KWin incorrectly maps legacy color managed applications from sRGB into the
display space. This is almost certainly the biggest color management issue with
respect to the upcoming release, because it represents a major regression of
the situation under X11. Graphics artists, photographers, and others working
with materials outside the sRGB space will need to avoid the Wayland release
unless this is fixed.

❓The Wayland color management protocol is still a work in process (and
unmerged). I believe KWin is implementing a draft  version of it. Because it's
so new, I was not able to find programs that advertise support for it.
Therefore I was unable to test a major aspect of recent color management work:
the ability of Wayland apps to tag windows with an appropriate intermediate
color space and have the compositor manage the colors on those windows for
them.

[Powerdevil] [Bug 452829] Configurable keyboard shortcut for turning the screen off, for laptops without a special key that does this

2023-12-05 Thread Jakob Petsovits

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

Jakob Petsovits  changed:

   What|Removed |Added

 CC||jpe...@petsovits.com

--- Comment #1 from Jakob Petsovits  ---
Not a direct fix for this bug, but in Plasma 6.0 you'll be able configure the
screen to automatically turn off after a certain time when the screen is
locked. You can set this to a value in the low seconds and use the "Lock
session" keyboard shortcut, which defaults to "Meta+L", until Plasma adds a
"Turn off screen" shortcut.

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

[digikam] [Bug 478131] dK 8.2.0 very slow and crashes in Windows 10

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

caulier.gil...@gmail.com changed:

   What|Removed |Added

  Component|general |Faces-Workflow
   Platform|Other   |Microsoft Windows
 CC||caulier.gil...@gmail.com

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

[plasmashell] [Bug 467074] When returning from screen energy saving, Plasma forgets that an external screen is connected and doesn't assign it a containment

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

Bug Janitor Service  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|WAITINGFORINFO  |WORKSFORME

--- Comment #32 from Bug Janitor Service  ---
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!

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

[kdenlive] [Bug 439212] Render to XviD fails due to bad parsing syntax

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

Bug Janitor Service  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |WORKSFORME
 Status|NEEDSINFO   |RESOLVED

--- Comment #7 from Bug Janitor Service  ---
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!

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

[krita] [Bug 463135] Keyboard keys lose focus/stop working.

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

Bug Janitor Service  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|WAITINGFORINFO  |WORKSFORME

--- Comment #11 from Bug Janitor Service  ---
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!

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

[Elisa] [Bug 436780] Elisa crashes after opening a directory from Files menu.

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

Bug Janitor Service  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |WORKSFORME
 Status|NEEDSINFO   |RESOLVED

--- Comment #6 from Bug Janitor Service  ---
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!

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

[kdenlive] [Bug 421718] Uninstallation Problem

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

Bug Janitor Service  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |WORKSFORME
 Status|NEEDSINFO   |RESOLVED

--- Comment #10 from Bug Janitor Service  ---
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!

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

[kpat] [Bug 477307] KPATIENCE APPLICATION SUBMENUDEMONSTRATION MENU FOR GAMES (Beleaguered Castle, etc.) disappears and does not re-appear. Is this a software bug?

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

--- Comment #2 from Bug Janitor Service  ---
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

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

[systemsettings] [Bug 477848] Energy Saving KCM should support non-default settings detection

2023-12-05 Thread Jakob Petsovits

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

Jakob Petsovits  changed:

   What|Removed |Added

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

--- Comment #3 from Jakob Petsovits  ---
Git commit 1fa7212e69480b8c86408c0ff0bafb268ffe40e7 by Jakob Petsovits.
Committed on 06/12/2023 at 04:02.
Pushed by jpetso into branch 'master'.

Make highlights work for non-default settings in the profiles KCM

The recent QML port didn't implement the code that was required
for this to work. Here's the fix.

Using SettingStateBinding from kcmutils adds highlights to the
components within the QML page.

In order to also make the (non-)defaultIndicator in the sidebar
list view show up, System Settings needs to be able to construct
a single KCModuleData object through the KCM's plugin factory.
We need to register both the KQuickManagedConfigModule and the
KCModuleData when declaring the plugin, so instead of
K_PLUGIN_CLASS_WITH_JSON we now use K_PLUGIN_FACTORY_WITH_JSON.

ProfilesConfigKCM.{h,cpp} requires some refactoring to use a single
KCModuleData object instead of a collection of three different ones.
Instead of the ProfilesConfigKCM class owning three data objects,
it now only constructs a single one which in turn will create and
expose the KConfigXT-generated settings classes for all profiles.

M  +74   -63   kcmodule/profiles/ProfilesConfigKCM.cpp
M  +34   -29   kcmodule/profiles/ProfilesConfigKCM.h
M  +175  -83   kcmodule/profiles/ui/ProfileConfig.qml

https://invent.kde.org/plasma/powerdevil/-/commit/1fa7212e69480b8c86408c0ff0bafb268ffe40e7

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

[drkonqi] [Bug 287458] Add support for "catch throw" in backtrace generation

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

Nate Graham  changed:

   What|Removed |Added

 CC||n...@kde.org

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

[Welcome Center] [Bug 478138] Installer shortcut in the welcome center for live environments is broken

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

Bug Janitor Service  changed:

   What|Removed |Added

   Keywords||qt6

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

[kwin] [Bug 477900] On Dolphin and Discover window resize various visual elements (such as menus) tremble. (only on Wayland)

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

--- Comment #2 from funkybom...@gmail.com ---
(In reply to Nate Graham from comment #1)
> Probably quite relevant:
> > Graphics Processor: llvmpipe
> 
> Are there any windows that are *not* affected?

Interestingly yes!

Programs tested that are not NOT affected:
Kate
Okular
Ark
Gwenview
Info Center
Synaptic
VLC


Other programs which are affected:
Konsole
System Monitor


This list is not exhaustive. Please advise if you would like me to test more
programs.

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

[amarok] [Bug 393080] Crash in PodcastSettingsDialog::init

2023-12-05 Thread Odin Vex

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

--- Comment #13 from Odin Vex  ---
(In reply to Odin Vex from comment #12)
> The crash is caused by core-impl/podcasts/sql/PodcastSettingsDialog.cpp,
> specifically "buttonBox()->button(QDialogButtonBox::Apply)->setEnabled".
> Comment-out every call (3 total) to that and it'll work fine.

I didn't have time to peek at the Qt documentation to look into Button Box(es)
to determine how best to move forward (aside from commenting them out
temporarily). The dialog width and height were also really goofed on my end
(AUR clone, edit, cmake ..., make, ran the bin without installation, working).

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

[amarok] [Bug 393080] Crash in PodcastSettingsDialog::init

2023-12-05 Thread Odin Vex

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

Odin Vex  changed:

   What|Removed |Added

 CC||odin.vex@ethicalexploiting.
   ||com

--- Comment #12 from Odin Vex  ---
The crash is caused by core-impl/podcasts/sql/PodcastSettingsDialog.cpp,
specifically "buttonBox()->button(QDialogButtonBox::Apply)->setEnabled".
Comment-out every call (3 total) to that and it'll work fine.

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

[Welcome Center] [Bug 478138] Installer shortcut in the welcome center for live environments is broken

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

--- Comment #3 from Neal Gompa  ---
So basically this part of the functionality doesn't seem to work. :(

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

[Welcome Center] [Bug 478138] Installer shortcut in the welcome center for live environments is broken

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

Neal Gompa  changed:

   What|Removed |Added

Summary|Welcome Center fails to |Installer shortcut in the
   |render the installer icon   |welcome center for live
   |for the embedded shortcut   |environments is broken

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

[Welcome Center] [Bug 478138] Welcome Center fails to render the installer icon for the embedded shortcut

2023-12-05 Thread Steve Cossette

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

Steve Cossette  changed:

   What|Removed |Added

 CC||farch...@gmail.com

--- Comment #2 from Steve Cossette  ---
Created attachment 163930
  --> https://bugs.kde.org/attachment.cgi?id=163930=edit
Error on clicking the image

Also seems to pop that error when you click on the image.

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

[Welcome Center] [Bug 478138] Welcome Center fails to render the installer icon for the embedded shortcut

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

--- Comment #1 from Neal Gompa  ---
This is the result of us enabling the live environment welcome mode with Plasma
6: https://pagure.io/livesys-scripts/c/c885b85d77470a7bd771c3dfb4120886728382d4

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

[Welcome Center] [Bug 478138] Welcome Center fails to render the installer icon for the embedded shortcut

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

Neal Gompa  changed:

   What|Removed |Added

 CC||awill...@redhat.com

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

[Welcome Center] [Bug 478138] New: Welcome Center fails to render the installer icon for the embedded shortcut

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

Bug ID: 478138
   Summary: Welcome Center fails to render the installer icon for
the embedded shortcut
Classification: Applications
   Product: Welcome Center
   Version: unspecified
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: major
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: ngomp...@gmail.com
CC: n...@kde.org
  Target Milestone: ---

SUMMARY
In today's Rawhide compose including KDE Plasma Beta 1, our OpenQA tests
detected that the welcome center doesn't render the installer shortcut icon
properly.

This can be observed here:
https://openqa.fedoraproject.org/tests/2298316#step/desktop_notifications/16

The nightly ISO this is testing:
https://kojipkgs.fedoraproject.org/compose/rawhide/Fedora-Rawhide-20231205.n.1/compose/Spins/x86_64/iso/Fedora-KDE-Live-x86_64-Rawhide-20231205.n.1.iso

STEPS TO REPRODUCE
1. Download the mentioned nightly ISO
2. Boot the ISO in a VM or physical machine

OBSERVED RESULT
The welcome center introduces to the live environment, but the installer
shortcut is not rendered properly.

EXPECTED RESULT
The welcome center introduces to the live environment and the installer
shortcut is rendered properly.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Fedora Linux 40 (KDE Plasma)
(available in About System)
KDE Plasma Version: 5.90.0
KDE Frameworks Version: 5.246.0
Qt Version: 6.6.1

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

[kwin] [Bug 478137] Desktop grid is not available as an option for screen edges/corners

2023-12-05 Thread Prajna Sariputra

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

Prajna Sariputra  changed:

   What|Removed |Added

   Keywords||qt6

--- Comment #1 from Prajna Sariputra  ---
*being effectively equivalent to present windows

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

[kwin] [Bug 478137] New: Desktop grid is not available as an option for screen edges/corners

2023-12-05 Thread Prajna Sariputra

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

Bug ID: 478137
   Summary: Desktop grid is not available as an option for screen
edges/corners
Classification: Plasma
   Product: kwin
   Version: master
  Platform: Compiled Sources
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: effects-desktop-grid
  Assignee: kwin-bugs-n...@kde.org
  Reporter: putr...@gmail.com
  Target Milestone: ---

SUMMARY
Currently, the desktop grid is not available as a possible action/effect to
trigger when touching a screen edge or corner. In Plasma 5.27 this wasn't a big
deal since the overview effect is in the list and allows moving windows between
desktops as well as switching to desktops, but with Plasma 6 the overview
effect is far less useful for people with more than one row and column of
desktops (being effectively equivalent to present desktops in that case). As
per bug 477942 the desktop grid effect is explicitly recommended too for those
with such virtual desktop setups.

A mitigating factor is that it's still possible to access the grid by
triggering the edge/corner twice if the overview is enabled for those, but
having to flick the cursor twice seems like a problem when it comes to avoiding
carpal tunnel syndrome and the like.


STEPS TO REPRODUCE
1. Open the screen edges KCM
2. Try to assign the desktop grid to one of the screen edges or corners

OBSERVED RESULT
The desktop grid is not present as one of the options.

EXPECTED RESULT
The desktop grid can be selected for the edge/corner.

SOFTWARE/OS VERSIONS
Operating System: Arch Linux 
KDE Plasma Version: 5.90.0
KDE Frameworks Version: 5.246.0
Qt Version: 6.6.1
Kernel Version: 6.6.3-arch1-1 (64-bit)
Graphics Platform: Wayland

ADDITIONAL INFORMATION
The list of options for each screen edge/corner is getting rather unwieldy, so
maybe adding yet another option to it isn't a good idea without redesigning it
somehow.

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

[drkonqi] [Bug 287458] Add support for "catch throw" in backtrace generation

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

Bug Janitor Service  changed:

   What|Removed |Added

 Status|CONFIRMED   |ASSIGNED

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

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

[drkonqi] [Bug 287458] Add support for "catch throw" in backtrace generation

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

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

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

[systemsettings] [Bug 478089] Previews in the size dropdown have wrong sizes when using a scale factor

2023-12-05 Thread Fushan Wen

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

Fushan Wen  changed:

   What|Removed |Added

   Keywords|qt6 |wayland

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

[digikam] [Bug 478136] Digikam crashes when manually adding or correcting people tag in Preview mode

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

Bug Janitor Service  changed:

   What|Removed |Added

   Severity|grave   |crash

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

[Skanlite] [Bug 478135] ADF-Duplex-unnormal behaviour

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

--- Comment #1 from r...@ffpx.de ---
In the "Configuration" Menu it is possible to save scan as PDF but there is NO
possibility to save all scans to ONE FILE!!!
That's not really a service for a business man! That's impossible!!!
PLEASE add an option to save ALL SCANS to ONE FILE just at least for PDF in ALL
SCAN-Sources! Since I would sometimes scan a book to have it in digital form...

Thanks a lot in advance!!

Ralf Stuttgart

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

[digikam] [Bug 478136] New: Digikam crashes when manually adding or correcting people tag in Preview mode

2023-12-05 Thread Beto Kella

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

Bug ID: 478136
   Summary: Digikam crashes when manually adding or correcting
people tag in Preview mode
Classification: Applications
   Product: digikam
   Version: 8.2.0
  Platform: Microsoft Windows
OS: Microsoft Windows
Status: REPORTED
  Severity: grave
  Priority: NOR
 Component: Faces-Workflow
  Assignee: digikam-bugs-n...@kde.org
  Reporter: betoke...@gmail.com
  Target Milestone: ---

SUMMARY
Manually trying to add or correct a people tag in a picture in Preview mode,
crashes digikam when you try to write or select the person name from the
dropdown dialog. After restarting, the intended face box was actually created,
or the existing is still there (with the wrong name).


STEPS TO REPRODUCE
1. Open picture in Preview mode
2a. Click the "Add a face tag button" and drag the face box. The dialog for
identifying the person will pop-up
2b. Or try to fix the name of a wrongly identified person from the dropdown
menu in the identify the person dialog
3. After a few seconds, digikam crashes
4. Restart digikam and reopen the picture. The new facebox was actually
created, or the existing one is still there (with the wrong name)

OBSERVED RESULT
For a face not automatically detected (happens to me often when the face is
inclined about 45 degrees), you can go to the People view and identify the
person there after restarting (no crashes in People view).
For correcting wrongly recognized people, you can remove all people tags from
the picture, rescan and identify them in the People view.

EXPECTED RESULT
Like in all other versions I have used before, be able to manually add a people
tag in Preview mode, or change a wrongly identified person from the dropdown
menu in the face box

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

ADDITIONAL INFORMATION
Sorry was not able to send the detailed crash report

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

[Elisa] [Bug 478121] Elisa mobile UI: playlist drawer cannot be closed anymore

2023-12-05 Thread Kevin Kofler

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

--- Comment #2 from Kevin Kofler  ---
This should probably say:
interactive: Kirigami.Settings.isMobile
instead of:
interactive: false

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

[Skanlite] [Bug 478135] New: ADF-Duplex-unnormal behaviour

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

Bug ID: 478135
   Summary: ADF-Duplex-unnormal behaviour
Classification: Applications
   Product: Skanlite
   Version: 22.04.3
  Platform: Kubuntu
OS: Linux
Status: REPORTED
  Severity: major
  Priority: NOR
 Component: general
  Assignee: kare.s...@iki.fi
  Reporter: r...@ffpx.de
  Target Milestone: ---

SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug
symbols.
See
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***
Scanning with the Option "Scan source" = ADF Duplex gives TWO sides with the
second one turned ahead.

STEPS TO REPRODUCE
1. Configure ADF Duplex 
2. Configure Scansize A4 (German DIN-Size)
3. Klick "SCAN"

OBSERVED RESULT
The first side is scanned and saved (automatically
The 2. side is scanned and turned ahead in another file
Result 2 FILES instead of ONE
EXPECTED RESULT
ONE FILE as PDF to leaf through!

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 5.1
KDE Frameworks Version: 5.89.0
Qt Version: 5.15.3

ADDITIONAL INFORMATION

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

[kmymoney] [Bug 423783] Sorting only by "entry order" is overridden by entry date

2023-12-05 Thread Jack

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

Jack  changed:

   What|Removed |Added

 CC||ostroffjh@users.sourceforge
   ||.net

--- Comment #1 from Jack  ---
First, the description needs to be clarified, as 'only select "entry order" and
ascending sort order' doesn't make sense.  However, if the intent were "entry
order ascending, then post date ascending" then there is probably a different
issue now than when this was posted.  Currently "entry order" uses the entry
date, not the transaction ID, so the sorting is correct.  Perhaps the available
sort fields need to be modified to (re?)include transaction id.

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

[Elisa] [Bug 478121] Elisa mobile UI: playlist drawer cannot be closed anymore

2023-12-05 Thread Kevin Kofler

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

Kevin Kofler  changed:

   What|Removed |Added

 CC||n...@kde.org

--- Comment #1 from Kevin Kofler  ---
I suspect that the regression is caused by this commit:
https://invent.kde.org/multimedia/elisa/-/commit/6df31bbb78145633a187c56aa25389fee7e45a10

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

[plasmashell] [Bug 478133] Under Plasma 6 beta, ending the plasma session is broken

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

Bug Janitor Service  changed:

   What|Removed |Added

   Keywords||qt6

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

[krita] [Bug 478134] New: Anim Audio: Timeline scrubbing pushing too much audio.

2023-12-05 Thread Emmet O'Neill

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

Bug ID: 478134
   Summary: Anim Audio: Timeline scrubbing pushing too much audio.
Classification: Applications
   Product: krita
   Version: 5.2.1
  Platform: Appimage
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Animation
  Assignee: krita-bugs-n...@kde.org
  Reporter: emmetoneill@gmail.com
  Target Milestone: ---

SUMMARY

When animation with audio, scrubbing (changing frames quickly via the timeline
time ruler header) pushes multiple frames of audio which can block the program
until the audio is processed. 

This is usually a minor issue, but becomes worse with (a) lower playback
framerate and (b) lower playback speed.
Setting the animation to a low speed and framerate before scrubbing (with audio
attached) will push tens of seconds of audio, causing Krita to slow down until
it's all been played.

STEPS TO REPRODUCE
1. Open an animation
2. Attach some audio
3. Set low animation playback framerate.
4. Set low animation playback speed.
5. Scrub between frames on the timeline.

OBSERVED RESULT

Listen to a half minute of cow noises.

EXPECTED RESULT

We probably need to limit the rate of pushing audio based on the amount of time
a single frame of audio takes to play (considering both anim framerate and
speed).

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

[systemsettings] [Bug 478089] Previews in the size dropdown have wrong sizes when using a scale factor

2023-12-05 Thread Jin Liu

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

--- Comment #3 from Jin Liu  ---
(In reply to Nate Graham from comment #2)
> Looks like they are unscaled?

Yes. Unscaled, and some are of wrong sizes.

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

[valgrind] [Bug 476548] valgrind 3.22.0 fails on assertion when loading debuginfo file produced by mold

2023-12-05 Thread Mark Wielaard

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

--- Comment #9 from Mark Wielaard  ---
Also pushed to VALGRIND_3_22_BRANCH as:

commit 1d00e5ce0fb069911c4b525ec38289fb5d9021b0
Author: Paul Floyd 
Date:   Sat Nov 18 08:49:34 2023 +0100

Bug 476548 - valgrind 3.22.0 fails on assertion when loading debuginfo file
produced by mold

(cherry picked from commit 9ea4ae66707a4dcc6f4328e11911652e4418c585)

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

[plasmashell] [Bug 478133] New: Under Plasma 6 beta, ending the plasma session is broken

2023-12-05 Thread Adam Fontenot

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

Bug ID: 478133
   Summary: Under Plasma 6 beta, ending the plasma session is
broken
Classification: Plasma
   Product: plasmashell
   Version: 5.90.0
  Platform: Arch Linux
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Session Management
  Assignee: plasma-b...@kde.org
  Reporter: adam.m.fontenot+...@gmail.com
  Target Milestone: 1.0

Important note: I'm testing Plasma 6 through official packages provided by Arch
Linux in the kde-unstable repository. It's possible that this is a transient
issue caused by Arch Linux packaging. I'll keep an eye on this and close the
issue if it disappears on its own.

SUMMARY
When using Plasma 6, I can't exit the session by any GUI means. Buttons that
log out or shutdown the computer (like the logout widget) have no effect, and
krunner actions like "log out" likewise do nothing.

This happens under both X11 and Wayland sessions.

Possible factors: I don't use SDDM or another login manager, I start Plasma
sessions from a text mode tty.

STEPS TO REPRODUCE
1. Open krunner.
2. Search "log out" and choose the session option to log out.

OBSERVED RESULT
Nothing happens.


SOFTWARE/OS VERSIONS
Operating System: Arch Linux 
KDE Plasma Version: 5.90.0
KDE Frameworks Version: 5.246.0
Qt Version: 6.6.1
Kernel Version: 6.6.4-arch1-1 (64-bit)
Graphics Platform: Wayland

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

[kwin] [Bug 478132] Dragging desktop in desktop grid with multiple monitors have unintended results

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

--- Comment #1 from fanzhuyi...@gmail.com ---
(In reply to fanzhuyifan from comment #0)
> 1. Create 1 virtual desktops

Sorry I mean 2 virtual desktops

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

[kwin] [Bug 478132] Dragging desktop in desktop grid with multiple monitors have unintended results

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

fanzhuyi...@gmail.com changed:

   What|Removed |Added

   Keywords||qt6, usability

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

[kwin] [Bug 478132] New: Dragging desktop in desktop grid with multiple monitors have unintended results

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

Bug ID: 478132
Summary: Dragging desktop in desktop grid with multiple
monitors have unintended results
Classification: Plasma
Product: kwin
Version: git master
Platform: Other
OS: Linux
Status: REPORTED
Severity: minor
Priority: NOR
Component: effects-desktop-grid
Assignee: kwin-bugs-n...@kde.org
Reporter: fanzhuyi...@gmail.com
Target Milestone: ---

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

STEPS TO REPRODUCE
1. Create 1 virtual desktops
2. Set up 2 monitors. Call them A and B
3. Open 1 window on desktop 1 of monitor A
4. Open desktop grid effect
5. drag the empty desktop 1 on monitor B to desktop 2

OBSERVED RESULT
There is no visual feedback on monitor A, but the window is moved to desktop 2.

EXPECTED RESULT
The visual feedback should be consistent with the actual results. In
particular, one of the two things should happen:

1. There is no visual feedback on monitor A, and the windows on monitor A are
not effected

2. There is visual feedback of moving the windows on monitor A, and the windows
on monitor A are also moved.

SOFTWARE/OS VERSIONS
Windows:
macOS:
Linux/KDE Plasma:
(available in About System)
KDE Plasma Version: plasma 6 beta
KDE Frameworks Version:
Qt Version:

ADDITIONAL INFORMATION

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

[Elisa] [Bug 477792] The playlist in party mode in Elisa is broken.

2023-12-05 Thread Jack Hill

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

Jack Hill  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |---
  Component|upnp|general
 Status|NEEDSINFO   |CONFIRMED
 Ever confirmed|0   |1

--- Comment #5 from Jack Hill  ---
Ah, I didn't realise those two attachments were different. I can confirm this
now. The UPnP component is for universal plug and play, which I believe is
broken in Elisa. I've moved it to general now.

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

[dolphin] [Bug 451050] Dolphin crashing when connecting SMB share

2023-12-05 Thread Matthias Gruß

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

--- Comment #38 from Matthias Gruß  ---
Application: Dolphin (dolphin), signal: Segmentation fault

[KCrash Handler]
#4  0x7f493e91f5c8 in KCoreDirListerCache::slotUpdateResult(KJob*) () at
/lib64/libKF5KIOCore.so.5
#5  0x7f493cce8871 in void doActivate(QObject*, int, void**) () at
/lib64/libQt5Core.so.5
#6  0x7f493e0e6706 in KJob::result(KJob*, KJob::QPrivateSignal) () at
/lib64/libKF5CoreAddons.so.5
#7  0x7f493e0ec5bb in KJob::finishJob(bool) () at
/lib64/libKF5CoreAddons.so.5
#8  0x7f493cce8871 in void doActivate(QObject*, int, void**) () at
/lib64/libQt5Core.so.5
#9  0x7f493e8c5bc8 in KIO::SlaveInterface::dispatch(int, QByteArray const&)
() at /lib64/libKF5KIOCore.so.5
#10 0x7f493e8c07fb in KIO::SlaveInterface::dispatch() () at
/lib64/libKF5KIOCore.so.5
#11 0x7f493e8c3251 in KIO::Slave::gotInput() () at
/lib64/libKF5KIOCore.so.5
#12 0x7f493cce8871 in void doActivate(QObject*, int, void**) () at
/lib64/libQt5Core.so.5
#13 0x7f493ccdf11b in QObject::event(QEvent*) () at /lib64/libQt5Core.so.5
#14 0x7f493d9aeb75 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /lib64/libQt5Widgets.so.5
#15 0x7f493ccb4598 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at /lib64/libQt5Core.so.5
#16 0x7f493ccb7a45 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () at /lib64/libQt5Core.so.5
#17 0x7f493cd06fef in postEventSourceDispatch(_GSource*, int (*)(void*),
void*) () at /lib64/libQt5Core.so.5
#18 0x7f493a912e5c in g_main_context_dispatch_unlocked.lto_priv () at
/lib64/libglib-2.0.so.0
#19 0x7f493a96ddd8 in g_main_context_iterate_unlocked.isra () at
/lib64/libglib-2.0.so.0
#20 0x7f493a910ad3 in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#21 0x7f493cd06ad9 in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQt5Core.so.5
#22 0x7f493ccb2f5b in
QEventLoop::exec(QFlags) () at
/lib64/libQt5Core.so.5
#23 0x7f493ccbb1eb in QCoreApplication::exec() () at /lib64/libQt5Core.so.5
#24 0x559e85ff9055 in main ()
[Inferior 1 (process 5596) detached]

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

[plasmashell] [Bug 478086] plasmashell crashed sometimes in QtWaylandClient::QWaylandWindow::createDecoration when hovering over task manager icons

2023-12-05 Thread Matt Fagnani

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

Matt Fagnani  changed:

   What|Removed |Added

Summary|plasmashell crashed |plasmashell crashed
   |sometimes in|sometimes in
   |QWaitCondition::wait when   |QtWaylandClient::QWaylandWi
   |hovering over task manager  |ndow::createDecoration when
   |icons   |hovering over task manager
   ||icons
 Resolution|WAITINGFORINFO  |---
 Status|NEEDSINFO   |REPORTED

--- Comment #3 from Matt Fagnani  ---
(In reply to Nate Graham from comment #2)
> Does the issue reproduce if you uncheck "Show small preview windows when
> hovering over Tasks" in the Task Manager widget's settings window and then
> do the same thing to cause the crash to happen?

I unchecked "Show small preview windows when hovering over Tasks" in the Task
Manager widget's settings window. I tried to reproduce the crash as in comment
1 for several minutes, but plasmashell didn't crash. The 5 crashes like this in
Plasma 5.90.0 took from 1 second to 2 minutes to happen, so the problem might
not happen with the preview windows disabled. I checked "Show small preview
windows when hovering over Tasks" in the Task Manager widget's settings window.
I reproduced the crash after about 1 minute of moving the cursor as before. I
think that the problem is actually in thread 73 instead of thread 1 as in the
trace I put in comment. drkonqi focused on thread 1, but it was just
waiting/polling. Both thread 73 and thread 1 had [KCrash Handler] at the top in
drkonqi. Using coredumpctl gdb, the trace of thread 73 was the following.

(gdb) thread 73
[Switching to thread 73 (Thread 0x7f369df6f6c0 (LWP 3082))]
#0  0x7f375d51841d in __GI___poll (fds=fds@entry=0x7f369df6d768,
nfds=nfds@entry=1, timeout=timeout@entry=1000) at
../sysdeps/unix/sysv/linux/poll.c:29
Downloading source file
/usr/src/debug/glibc-2.38.9000-26.fc40.x86_64/io/../sysdeps/unix/sysv/linux/poll.c
29return SYSCALL_CANCEL (poll, fds, nfds, timeout);
(gdb) bt
#0  0x7f375d51841d in __GI___poll (fds=fds@entry=0x7f369df6d768,
nfds=nfds@entry=1, timeout=timeout@entry=1000) at
../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7f37607feb98 in poll (__timeout=1000, __nfds=1, __fds=0x7f369df6d768)
at /usr/include/bits/poll2.h:39
#2  pollDrKonqiSocket (sockfd=3, pid=) at
/usr/src/debug/kf6-kcrash-5.246.0-1.fc40.x86_64/src/kcrash.cpp:844
#3  KCrash::startProcess (argv=argv@entry=0x7f369df6d8a8,
waitAndExit=waitAndExit@entry=true, argc=)
at /usr/src/debug/kf6-kcrash-5.246.0-1.fc40.x86_64/src/kcrash.cpp:706
#4  0x7f37607ff659 in KCrash::defaultCrashHandler (sig=11) at
/usr/src/debug/kf6-kcrash-5.246.0-1.fc40.x86_64/src/kcrash.cpp:602
#5  
#6  0x7f375dec0a40 in typeinfo name for QObjectCleanupHandler () from
/lib64/libQt6Core.so.6
#7  0x7f37604f3f5a in QtWaylandClient::QWaylandWindow::createDecoration
(this=0x564f65c87540)
at
/usr/src/debug/qt6-qtwayland-6.6.1-1.fc40.x86_64/src/client/qwaylandwindow.cpp:1034
#8  0x7f37588e199c in QtWaylandClient::QWaylandGLContext::makeCurrent
(this=this@entry=0x7f3710002490, surface=)
at
/usr/src/debug/qt6-qtwayland-6.6.1-1.fc40.x86_64/src/hardwareintegration/client/wayland-egl/qwaylandglcontext.cpp:315
#9  0x7f375e79c188 in QOpenGLContext::makeCurrent (this=0x7f37100021e0,
surface=surface@entry=0x564f65d371f0)
at
/usr/src/debug/qt6-qtbase-6.6.1-1.fc40.x86_64/src/gui/kernel/qopenglcontext.cpp:661
#10 0x7f375e7b48e9 in QRhiGles2::ensureContext (this=0x7f3710001b70,
surface=0x564f65d371f0)
at
/usr/src/debug/qt6-qtbase-6.6.1-1.fc40.x86_64/src/gui/rhi/qrhigles2.cpp:619
#11 0x7f375e7c071e in QRhiGles2::beginFrame (this=0x7f3710001b70,
swapChain=0x7f37101c8ea0)
at
/usr/src/debug/qt6-qtbase-6.6.1-1.fc40.x86_64/src/gui/rhi/qrhigles2.cpp:2028
#12 0x7f375e644bea in QRhi::beginFrame (this=0x7f3710001b50,
swapChain=0x7f37101c8ea0, flags=..., flags@entry=...)
at /usr/src/debug/qt6-qtbase-6.6.1-1.fc40.x86_64/src/gui/rhi/qrhi.cpp:10146
#13 0x7f375f8c29f4 in QSGRenderThread::syncAndRender
(this=this@entry=0x564f66f2b500) at /usr/include/qt6/QtCore/qflags.h:73
#14 0x7f375f8c5e93 in QSGRenderThread::run (this=0x564f66f2b500)
at
/usr/src/debug/qt6-qtdeclarative-6.6.1-1.fc40.x86_64/src/quick/scenegraph/qsgthreadedrenderloop.cpp:946
#15 0x7f375dd50ace in operator() (__closure=) at
/usr/src/debug/qt6-qtbase-6.6.1-1.fc40.x86_64/src/corelib/thread/qthread_unix.cpp:324
#16 (anonymous
namespace)::terminate_on_exception >
(t=...)
at
/usr/src/debug/qt6-qtbase-6.6.1-1.fc40.x86_64/src/corelib/thread/qthread_unix.cpp:260
#17 QThreadPrivate::start (arg=0x564f66f2b500) at
/usr/src/debug/qt6-qtbase-6.6.1-1.fc40.x86_64/src/corelib/thread/qthread_unix.cpp:283
#18

[krunner] [Bug 478042] very slow loading time on first launch

2023-12-05 Thread Henning

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

--- Comment #6 from Henning  ---
CLI gives no output.

I just created a desktop entry and set it to autostart. Now I dont have this
anymore, because I am certain it can just be fixed by autostarting krunner,
preloading the needed resources etc.

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

[plasma-systemmonitor] [Bug 478128] Adding and removing headers in the system monitor breaks the save

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

Bug Janitor Service  changed:

   What|Removed |Added

   Keywords||qt6

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

[dolphin] [Bug 451050] Dolphin crashing when connecting SMB share

2023-12-05 Thread Matthias Gruß

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

--- Comment #37 from Matthias Gruß  ---
In my case, it is about the share on a Synology NAS. 
After calling smb://192.168.2.150/ the login and password are requested.

Output in the terminal when calling without slash (192.168.2.150):

matthias@fedora-notebook:~$ dolphin
kf.kio.core: Internal error: itemsInUse did not contain
QUrl("smb://matsch@192.168.2.150/")
KCrash: Application 'dolphin' crashing...
KCrash: Attempting to start /usr/libexec/drkonqi
kf5idletime_wayland: This plugin does not support polling idle time
[1]+  Angehalten  dolphin

Output of coredumpctl info dolphin:


   PID: 3861 (dolphin)
   UID: 1000 (matthias)
   GID: 1000 (matthias)
Signal: 11 (SEGV)
 Timestamp: Thu 2023-11-30 08:57:15 CET (5 days ago)
  Command Line: /usr/bin/dolphin
Executable: /usr/bin/dolphin
 Control Group:
/user.slice/user-1000.slice/user@1000.service/app.slice/app-\x2fusr\x2fbin\x2fdolphin-2a68a52399074d6baf01951b89126bdd.scope
  Unit: user@1000.service
 User Unit:
app-\x2fusr\x2fbin\x2fdolphin-2a68a52399074d6baf01951b89126bdd.scope
 Slice: user-1000.slice
 Owner UID: 1000 (matthias)
   Boot ID: 04f8632289b54a5fa2947f45f8271790
Machine ID: 5db137b5cf784732be137c6dcb9329d1
  Hostname: fedora-notebook
   Storage:
/var/lib/systemd/coredump/core.dolphin.1000.04f8632289b54a5fa2947f45f8271790.3861.170133103500.zst
(missing)
   Package: dolphin/23.08.3-1.fc39
  build-id: 196e791b2c06aeee903690cac5e4b3b9a7aaeb66
   Message: Process 3861 (dolphin) of user 1000 dumped core.

Module kio_file.so from rpm kf5-kio-5.111.0-1.fc39.x86_64
Module libxdg-shell.so from rpm
qt5-qtwayland-5.15.11-1.fc39.x86_64
Module libwebpdemux.so.2 from rpm libwebp-1.3.2-2.fc39.x86_64
Module libwebpmux.so.3 from rpm libwebp-1.3.2-2.fc39.x86_64
Module libqwebp.so from rpm
qt5-qtimageformats-5.15.11-1.fc39.x86_64
Module libqwbmp.so from rpm
qt5-qtimageformats-5.15.11-1.fc39.x86_64
Module libjbig.so.2.1 from rpm jbigkit-2.1-26.fc39.x86_64
Module libLerc.so.4 from rpm liblerc-4.0.0-4.fc39.x86_64
Module libwebp.so.7 from rpm libwebp-1.3.2-2.fc39.x86_64
Module libtiff.so.5 from rpm libtiff-4.4.0-8.fc39.x86_64
Module libqtiff.so from rpm
qt5-qtimageformats-5.15.11-1.fc39.x86_64
Module libqsvg.so from rpm qt5-qtsvg-5.15.11-1.fc39.x86_64
Module libmng.so.2 from rpm libmng-2.0.3-19.fc39.x86_64
Module libqmng.so from rpm
qt5-qtimageformats-5.15.11-1.fc39.x86_64
Module libqjpeg.so from rpm qt5-qtbase-5.15.11-7.fc39.x86_64
Module libqjp2.so from rpm
qt5-qtimageformats-5.15.11-1.fc39.x86_64
Module libqico.so from rpm qt5-qtbase-5.15.11-7.fc39.x86_64
Module libqicns.so from rpm
qt5-qtimageformats-5.15.11-1.fc39.x86_64
Module libqgif.so from rpm qt5-qtbase-5.15.11-7.fc39.x86_64
Module kimg_xcf.so from rpm
kf5-kimageformats-5.111.0-1.fc39.x86_64
Module kimg_tga.so from rpm
kf5-kimageformats-5.111.0-1.fc39.x86_64
Module kimg_rgb.so from rpm
kf5-kimageformats-5.111.0-1.fc39.x86_64
Module liblcms2.so.2 from rpm lcms2-2.15-2.fc39.x86_64
Module libjasper.so.6 from rpm jasper-3.0.6-4.fc39.x86_64
Module libjpeg.so.62 from rpm libjpeg-turbo-2.1.4-3.fc39.x86_64
Module libraw.so.23 from rpm LibRaw-0.21.1-5.fc39.x86_64
Module kimg_raw.so from rpm
kf5-kimageformats-5.111.0-1.fc39.x86_64
Module kimg_ras.so from rpm
kf5-kimageformats-5.111.0-1.fc39.x86_64
Module kimg_qoi.so from rpm
kf5-kimageformats-5.111.0-1.fc39.x86_64
Module kimg_psd.so from rpm
kf5-kimageformats-5.111.0-1.fc39.x86_64
Module kimg_pic.so from rpm
kf5-kimageformats-5.111.0-1.fc39.x86_64
Module kimg_pcx.so from rpm
kf5-kimageformats-5.111.0-1.fc39.x86_64
Module kimg_ora.so from rpm
kf5-kimageformats-5.111.0-1.fc39.x86_64
Module kimg_kra.so from rpm
kf5-kimageformats-5.111.0-1.fc39.x86_64
Module libjxl_threads.so.0.8 from rpm
jpegxl-0.8.2-3.fc39.x86_64
Module kimg_jxl.so from rpm
kf5-kimageformats-5.111.0-1.fc39.x86_64
Module libsharpyuv.so.0 from rpm libwebp-1.3.2-2.fc39.x86_64
Module libheif.so.1 from rpm libheif-1.16.2-2.fc39.x86_64
Module kimg_heif.so from rpm
kf5-kimageformats-5.111.0-1.fc39.x86_64
Module kimg_hdr.so from rpm
kf5-kimageformats-5.111.0-1.fc39.x86_64
Module libIlmThread-3_1.so.30 from rpm
openexr-3.1.10-2.fc39.x86_64
Module libIex-3_1.so.30 from rpm openexr-3.1.10-2.fc39.x86_64

[kdenlive] [Bug 476634] Error moving project folder

2023-12-05 Thread Kirby

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

Kirby  changed:

   What|Removed |Added

 CC||kirbyiw...@gmail.com

--- Comment #4 from Kirby  ---
I also have this problem (on windows 10) and I wanted to add that the
workaround doesn't work for me, I'll explain:

I want to create a new project in a specific folder (i.e. Parent folder of the
project file) because that's the only way I have found that I can have the
capture folder to be the same as the project folder (I do a lot of overdubbing,
and I don't want to have all the audio captures mixed up in the same folder).
What I've tried:

-Moving the folder after using the "default" folder (doesn't work because I
can't move from C: to D:)
-Creating the project with "custom project folder" on D:, then moving it to a
specific folder in D: (capture folder stays in the original custom folder on
D:, not in the moved one).
-Creating the project with "custom project folder", then on the create menu
change that folder to D:/correctfolder (capture folder stays in the original
custom folder I have on environment settings).
-Choosing "parent folder of project file", which makes the environment option
show "always use active project folder" (but then when I save the file on D: it
tries to move it from C:, which fails).

If there's a workaround for this, I would love to know, else, I hope this can
be fixed soon.

Thank you!

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

[audiotube] [Bug 477390] Doesn't build

2023-12-05 Thread Antonio Rojas

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

Antonio Rojas  changed:

   What|Removed |Added

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

--- Comment #1 from Antonio Rojas  ---
Fixed with qcoro 0.10

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

[kwin] [Bug 475423] kwin_wayland crashes in KWin::WaylandWindow::belongsToSameApplication() when clicking on notification

2023-12-05 Thread Vlad Zahorodnii

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

Vlad Zahorodnii  changed:

   What|Removed |Added

 CC||bednarczyk.pa...@outlook.co
   ||m

--- Comment #6 from Vlad Zahorodnii  ---
*** Bug 477868 has been marked as a duplicate of this bug. ***

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

[kwin] [Bug 477868] kwin crash in KWin::SurfaceInterface::client() when accessing the right click context menu of the steam application

2023-12-05 Thread Vlad Zahorodnii

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

Vlad Zahorodnii  changed:

   What|Removed |Added

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

--- Comment #2 from Vlad Zahorodnii  ---


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

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

[digikam] [Bug 478131] New: dK 8.2.0 very slow and crashes in Windows 10

2023-12-05 Thread Erik Herlé

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

Bug ID: 478131
   Summary: dK 8.2.0 very slow and crashes in Windows 10
Classification: Applications
   Product: digikam
   Version: 8.2.0
  Platform: Other
OS: Microsoft Windows
Status: REPORTED
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: digikam-bugs-n...@kde.org
  Reporter: erik.herle+digi...@gmail.com
  Target Milestone: ---

SUMMARY
New version 8.2.0 of digikam is very slow and crashes multiple times.

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


STEPS TO REPRODUCE
1.  Install new version with Chocolatey
2. Start digiKam
3. query some photos, edit face tags

OBSERVED RESULT
1. dK starts very slowly.
2. different crashes during simple actions

EXPECTED RESULT
1. Same startup time as previous versions.
2. No crashes

SOFTWARE/OS VERSIONS
Windows: 10
Qt Version: 6

ADDITIONAL INFORMATION
After reading bug 478075 (https://bugs.kde.org/show_bug.cgi?id=478075), I
downloaded the Qt5 version of digiKam 8.2.0 and that runs OK. Same startup
times as before and no crashes.

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

[plasma-systemmonitor] [Bug 478128] Adding and removing headers in the system monitor breaks the save

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

Zhora Zmeikin  changed:

   What|Removed |Added

Summary|Editing applets in the  |Adding and removing headers
   |system monitor makes other  |in the system monitor
   |applets disappear   |breaks the save

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

[krunner] [Bug 477794] Commands have too low priority

2023-12-05 Thread Natalie Clarius

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

--- Comment #10 from Natalie Clarius  ---
I agree that if two results have the same category relevance, it should fall
back to the highest match relevance rather than to the internal (alphabetical?)
ordering, like how we did previously with the match type.

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

[plasma-systemmonitor] [Bug 478128] Editing applets in the system monitor makes other applets disappear

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

--- Comment #2 from Zhora Zmeikin  ---
Created attachment 163929
  --> https://bugs.kde.org/attachment.cgi?id=163929=edit
Video with a clearer demonstration

I have tested and the problem is with the headers. It seems any addition and
deletion of them can cause some errors in saving.

For example, adding a header at the very beginning will break all other
headers. We can restore them without any problems, but if we remove the very
last header after that, the last widget is gone.

More clearly recorded on the video.

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

[kwin] [Bug 476653] Plastik and other 3rd-party window decoration themes do not work on X11

2023-12-05 Thread Vlad Zahorodnii

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

Vlad Zahorodnii  changed:

   What|Removed |Added

 Resolution|--- |FIXED
  Latest Commit||https://invent.kde.org/plas
   ||ma/kwin/-/commit/b01b626ca8
   ||1d23583a8c33307a94874a8ff0a
   ||d37
 Status|ASSIGNED|RESOLVED

--- Comment #10 from Vlad Zahorodnii  ---
Git commit b01b626ca81d23583a8c33307a94874a8ff0ad37 by Vlad Zahorodnii.
Committed on 05/12/2023 at 23:04.
Pushed by vladz into branch 'master'.

x11: Fix MouseButtonPress events sent to decoration

ButtonPressEvent::state includes keys and buttons prior to the button
press has been generated.

On the other hand, it appears that QMouseEvent::buttons() should include
currently pressed buttons, i.e. the button that has been just pressed
should be in that bitfield.

This is important for QQuickDeliveryAgent, which checks
QMouseEvent::button() and QMouseEvent::buttons() to decide whether to
send the button event only to tap handlers or both tap handlers and
mouse areas.

M  +12   -4src/events.cpp

https://invent.kde.org/plasma/kwin/-/commit/b01b626ca81d23583a8c33307a94874a8ff0ad37

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

[Elisa] [Bug 478130] New: Integrate radio stations catalog(s)

2023-12-05 Thread Antonios Hazim

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

Bug ID: 478130
   Summary: Integrate radio stations catalog(s)
Classification: Applications
   Product: Elisa
   Version: 23.08.3
  Platform: Arch Linux
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: matthieu_gall...@yahoo.fr
  Reporter: antonios.ha...@tutanota.com
  Target Milestone: ---

SUMMARY
Elisa lacks an easy way to discover and add radio channels. Cantata (RIP) on
the other hand has integration of IceCast, ShoutCast & TuneIn.

STEPS TO REPRODUCE
1. Open Elisa
2. Tap Radio Stations tab
3. Create radio station

OBSERVED RESULT
Manual addition of radio station's data

EXPECTED RESULT
Search in integrated catalogs (optional)

SOFTWARE/OS VERSIONS
Linux: 6.4.16
(available in About System)
KDE Plasma Version: 5.27.9 (xwayland)
KDE Frameworks Version: 5.112.0
Qt Version: 5.15.11

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

[plasma-systemmonitor] [Bug 478126] kstatsviewer and systemmonitor write incorrect data

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

--- Comment #1 from qweriop.tr...@gmail.com ---
After rebooting the issue disappeared, but after a while it started again, but
now only the Write speed is affected and instead of 3696742298972245
something, it's around 270 MiB/s.
I've tried multiple times but I cannot consistently replicate the issue.

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

[Elisa] [Bug 478129] New: Files tab always opens root directory

2023-12-05 Thread Antonios Hazim

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

Bug ID: 478129
   Summary: Files tab always opens root directory
Classification: Applications
   Product: Elisa
   Version: 23.08.3
  Platform: Arch Linux
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: matthieu_gall...@yahoo.fr
  Reporter: antonios.ha...@tutanota.com
  Target Milestone: ---

SUMMARY
Opening the files tab opens the root folder always, neither remebering the last
opened directory nor an option for default directory is available. 

STEPS TO REPRODUCE
1. Open Elisa
2. Tap "Files" tab 

OBSERVED RESULT
Landing in root directory

EXPECTED RESULT
Last opened directory or a preset default

SOFTWARE/OS VERSIONS
Linux: 6.4.16
(available in About System)
KDE Plasma Version: 5.27.9 (xwayland)
KDE Frameworks Version: 5.112.0
Qt Version: 5.15.11

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

[plasma-systemmonitor] [Bug 478128] Editing applets in the system monitor makes other applets disappear

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

--- Comment #1 from Zhora Zmeikin  ---
Created attachment 163928
  --> https://bugs.kde.org/attachment.cgi?id=163928=edit
After saving the changes and restarting the program

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

[systemsettings] [Bug 477380] debian12 says bluetooth is disabled. can't enable bluetooth in settings page

2023-12-05 Thread Steven

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

--- Comment #3 from Steven  ---
The problem was missing firmware.  I installed package firmware-realtek 
and now bluetooth works.

On 11/29/23 5:51 PM, Nate Graham wrote:
> https://bugs.kde.org/show_bug.cgi?id=477380
>
> Nate Graham  changed:
>
> What|Removed |Added
> 
>   Resolution|--- |NOT A BUG
>   CC||n...@kde.org
>   Status|REPORTED|RESOLVED
>
> --- Comment #1 from Nate Graham  ---
> Thanks for the bug report! Unfortunately I'm having a hard time figuring out
> what bug is being reported here. I'd recommend posting a question at
> https://discuss.kde.org/c/help/6, and hopefully the people there can help you
> determine what the problem is and whether it's caused by a bug in any KDE
> software. If that's determined to be the cause, please don't hesitate to come
> back here, re-open this bug report, and describe what the problem was
> determined to be.
>
> Thanks again!
>

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

[plasma-systemmonitor] [Bug 478128] New: Editing applets in the system monitor makes other applets disappear

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

Bug ID: 478128
   Summary: Editing applets in the system monitor makes other
applets disappear
Classification: Applications
   Product: plasma-systemmonitor
   Version: 5.90.0
  Platform: Neon
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: ksysguard-b...@kde.org
  Reporter: rs5334...@gmail.com
CC: ahiems...@heimr.nl, plasma-b...@kde.org
  Target Milestone: ---

Created attachment 163927
  --> https://bugs.kde.org/attachment.cgi?id=163927=edit
Before saving changes

I decided to customize the system monitor, I edited the home page. Saved the
changes, after logging in again I noticed that my widget was just gone.

I did the customization again, saved, re-entered and now another widget is
gone. It looks like the saving of changes is not happening correctly.

I took two screenshots, in the first one I customized the first group of
widgets. The second screenshot shows the result after restarting the program. A
group of other widgets disappeared.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: KDE Neon (Unstable), Wayland
KDE Plasma Version: 5.90.0
KDE Frameworks Version: 5.246.0
Qt Version: 6.6.0

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

[plasmashell] [Bug 478096] Panel sometimes does not cast a shadow on windows anymore

2023-12-05 Thread Jakob Petsovits

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

--- Comment #5 from Jakob Petsovits  ---
(In reply to Nate Graham from comment #3)
> Anyway, let's make this bug report about the real issue, which is the panel
> not casting a shadow like it should.

So how are things supposed to work exactly then, how do I tell the difference?
Windows with extra content underneath the panel get shadowed, and windows
snapped to the panel have no shadow? Uniformly dropping shadows on all windows
wouldn't resolve the issue I raised in the original comment.

> Can you see if it's Bug 477884?

I can confirm that floating the panel will add a little shadow, and de-floating
it without Plasma restart retains the same shadow. It seems likely that my
screenshot was affected by Bug 477884, given the complete absence of shadows.

I can not confirm that we're talking about the same issue, because I'm still
looking for a distinction between snapped vs. partially covered. And while
you're right that removing excessive frames in Qt 6 based apps exacerbates the
issue, I'd also like to point out that my reproduction steps & screenshot
feature Firefox, which is independent from all of those happenings. What I'm
after here is really to be able to tell if I can see the bottom of any window.

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

[frameworks-kglobalaccel] [Bug 141968] Holding down key to launch app spawns insane number of windows which can bog down the system

2023-12-05 Thread Noah Davis

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

Noah Davis  changed:

   What|Removed |Added

 CC||noaha...@gmail.com

--- Comment #6 from Noah Davis  ---
The quickest solution would be to tell app devs to limit the shortcuts within
the apps that define the shortcuts, but then every app that naively implements
a global shortcut would still have this problem and apps might have slightly
different solutions for achieving the same end.

Something to consider is how the excessive global shortcut activation are being
triggered. In the case of the original report, auto repeat is what causes the
issue. Since KGlobalAccel's API uses QActions to register events, maybe we
could make something like `action->setAutoRepeat(false)` work? It could make it
so you have to release the shortcut sequence keys before it can be triggered
again. Auto repeat couldn't be disabled by default since there's no way to
determine whether an app dev explicitly set auto repeat on or left it at the
default value. At least it wouldn't require every app to implement their own
solution. It might not completely solve the problem, but it might solve most
issues caused by user input.

We could probably rate limit the processing of global shortcuts via timers.
However, how long or short the timer should be would probably be highly
dependent on the app and what the global shortcut does. There could be a global
shortcut that benefits from being able to be activated rapidly (e.g., volume
and brightness shortcuts). That once again means apps have to share some
responsibility for their behavior. Even 0ms timers might at least help with
compressing events created in rapid succession, but probably wouldn't solve the
issue. If we went this route, perhaps the behavior could be configurable by app
devs with the default being a behavior we generally consider safe?

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

[plasmashell] [Bug 477866] Media Player applet reloads the cover art on opening

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

Nate Graham  changed:

   What|Removed |Added

   Severity|normal  |minor
 Status|REPORTED|CONFIRMED
 Ever confirmed|0   |1
 CC||n...@kde.org,
   ||qydwhotm...@gmail.com

--- Comment #1 from Nate Graham  ---
Can reproduce.

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

[Falkon] [Bug 477234] Extension "Aktion ausführen" (this German text can be translated into English like "Execute Action") cannot get loaded

2023-12-05 Thread Juraj

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

Juraj  changed:

   What|Removed |Added

 Status|REPORTED|CONFIRMED
 CC||jurajora...@mailo.com
 Ever confirmed|0   |1

--- Comment #1 from Juraj  ---
This extension is still Qt5 only.
Thank you for reporting.

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

[kwin] [Bug 477868] kwin crash in KWin::SurfaceInterface::client() when accessing the right click context menu of the steam application

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

Nate Graham  changed:

   What|Removed |Added

 CC||n...@kde.org,
   ||vlad.zahorod...@kde.org,
   ||xaver.h...@gmail.com

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

[kwin] [Bug 477854] KWin compositing crashes on Nvidia 340