[systemsettings] [Bug 439797] System Settings crashes in KCMLookandFeel::knsEntryChanged() when I try to update a global theme via GHNS window of Global Theme KCM

[Antonio Rojas]

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

Antonio Rojas  changed:

   What|Removed |Added

 CC||akhileshdeod...@gmail.com

--- Comment #28 from Antonio Rojas  ---
*** Bug 446058 has been marked as a duplicate of this bug. ***

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

[systemsettings] [Bug 446058] System Settings Crashed

[Antonio Rojas]

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

Antonio Rojas  changed:

   What|Removed |Added

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

--- Comment #1 from Antonio Rojas  ---


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

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

[KScreen] [Bug 446026] Monitor rotation crashes plasma

[webstar]

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

--- Comment #2 from webstar  ---
(In reply to Nate Graham from comment #1)
> Seems like the X server itself is crashing!
> 
> Does this happen in the Plasma Wayland session too?

I tried the Plasma Wayland session but it was running so unstable that I wasn't
able to change any settings in kscreen. After doing a more deeper research, the
issue seems to be caused by the xf86-video-ati driver.

Related information:

 - https://bugs.archlinux.org/task/72759
 - https://gitlab.freedesktop.org/xorg/driver/xf86-video-ati/-/issues/198
 -
https://github.com/archlinux/svntogit-packages/commit/494a0b762f8ef7d16c6d0e396d365f6337a201de#diff-3e341d2d9c67be01819b25b25d5e53ea3cdf3a38d28846cda85a195eb9b7203a

I'm not able to test the fix yet, but will change the status of this report
when I'm able to do so.

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

[kdenlive] [Bug 443324] Spacer Tool hangs the app if used with grouped clips

[bugzilla_noreply]

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

--- Comment #11 from biblio...@gmail.com ---
Maybe, this could help. Short and simple summary of how Spacer should work if
clicked on a group, IMHO:

1. Each element of the clicked group should move with Spacer (no matter if
there are non-adjacent elements—and I cannot imagine any, other reason). The
essential point is, the group (as an entity previously created by the user)
should stay intact after Spacer operation is finished. (Now it doesn't.)

2. All clips (and groups of clips) to the right of the rightmost clip of the
clicked group are to form a temporary group to move along the clicked group.
After Spacer operation ends, the temporary group should be properly ungrouped
(without creating new groups nor breaking existing ones made by the user).

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

[kdenlive] [Bug 445644] timeline mess after re-open

[Dr. Ashutosh Pradhan]

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

--- Comment #15 from Dr. Ashutosh Pradhan  ---
(In reply to Dr. Ashutosh Pradhan from comment #14)
> (In reply to Dr. Ashutosh Pradhan from comment #11)
> > (In reply to emohr from comment #10)
> > > Thanks all for testing.
> > > 
> > > @all. Please upload your Kdenlive project files "before the mess" and 
> > > "after
> > > the mess" here so we can check what happen.
> > 
> > You cannot discriminate the file before the mess and after the mess. It is
> > practically difficult to share file before and after as the moment you close
> > a file all the tracks go haywire and you have to re-align them. However,
> > even if you re-align them on timeline, they look good on timeline yet when
> > you render the video, the video is all mess. The basic function of KDEnLive
> > of having multitrack video editing has got compromised in Ver
> > kdenlive-21.08.3. You need to check it yourself, yet I will try and share
> > the screen shots.
> 
> In source you need to fix it, if you have image files with extended duration
> on same track that of video it messes up the entire track timeline. Please
> replicate issue at your end and fix it in source.

Yes this trick fixed the mess up issue: One need to keep images in other track
and group them first and then group all the clips. This is a short term
solution till the time the coding team fix the issue in source code. 

I love KDEnLive it really delivers wonderful videos.

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

[Discover] [Bug 445652] Plasma keeps asking for reboot since upgrading to Fedora 34

[Ovidiu-Florin BOGDAN]

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

--- Comment #5 from Ovidiu-Florin BOGDAN  ---
Is there anything I can do to resolve this?

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

[kdenlive] [Bug 446063] Size Function on "Transform" and "Position and Zoom" Makes .mts Video Fail to Render

[bugzilla_noreply]

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

paloverde7...@gmail.com changed:

   What|Removed |Added

Summary|Size Function on|Size Function on
   |"Transform" and "Position   |"Transform" and "Position
   |and Zoom" Makes .mts video  |and Zoom" Makes .mts Video
   |Fail to Render  |Fail to Render

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

[libksane] [Bug 445139] Skanpage coredump

[idimitro]

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

idimitro  changed:

   What|Removed |Added

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

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

[kdenlive] [Bug 446063] Size Function on "Transform" and "Position and Zoom" Makes .mts video Fail to Render

[bugzilla_noreply]

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

paloverde7...@gmail.com changed:

   What|Removed |Added

  Alias||jmmj0103

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

[kdenlive] [Bug 446063] New: Size Function on "Transform" and "Position and Zoom" Makes .mts video Fail to Render

[bugzilla_noreply]

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

Bug ID: 446063
   Summary: Size Function on "Transform" and "Position and Zoom"
Makes .mts video Fail to Render
   Product: kdenlive
   Version: 21.11.80
  Platform: Microsoft Windows
OS: Microsoft Windows
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Effects & Transitions
  Assignee: vpi...@kde.org
  Reporter: paloverde7...@gmail.com
  Target Milestone: ---

SUMMARY
In Stable releases 21.08.2, 21.08.3, and Beta build 21.11.80, using the Size
function on an .mts file with the Transform effect or the Position and Zoom
effect will show the effect correctly in the Preview Render, but will not
render the video barring the first frame when the project is fully rendered.
The audio track renders as normal, it is only the video that is affected.

STEPS TO REPRODUCE
1. Apply the "Transform" or the "Position and Zoom" effect to an .mts video
clip.
2. Set the "Size" value to any variable.
3. Render and play back the exported video.

OBSERVED RESULT
The audio and any .mts video without either effect will play as intended, but
the video altered with the steps above will show as blank (except for possibly
1 frame).

EXPECTED RESULT
The rendered video should not display as blank in an exported project, and the
Size effect should be rendered as well.

SOFTWARE/OS VERSIONS
Windows: 10 Pro, Version 19044.1348

ADDITIONAL INFORMATION
I have not noticed any other effects causing this problem, but I will update
this report should I come across any. Video will be provided should repo steps
not reproduce the issue.

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

[Akonadi] [Bug 445249] Akonadi crash after unplugging Thunderbolt dock with attached monitor on Wayland

[Krisztián Szegi]

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

--- Comment #6 from Krisztián Szegi  ---
Application: akonadiserver (5.18.3 (21.08.3))

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

-- Information about the crash:
- What I was doing when the application crashed:
This also happens to me - as far as the backtrace is concerned, the same thing
- but with a totally different user action as its cause.
In my case, the crash happens when I open an krdc (rdp client) connection.

- Unusual behavior I noticed:
There are a bunch of oddness with some recent updates, not necessarily related,
but severly lowering the comfort level:
- Display configuration has no setting anymore to select primary screen.
- I can force it to be the laptop's screen instead of the external, with some
toggling of the external's enabled checkbox
- This is sometimes forgotten after reboot.
- Desktop widgets placed in the corner is being displaced inwards on ALMOST
EVERY login. Somehow this is almost deterministic.
- I had my whole desktop (background, widgets erased, different Task-manager on
Panel  - or different panel?) replaced with an update

-- Backtrace
Same as Philipp Reichmuth's, DrKonqi said this issue is already exist...

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

[krita] [Bug 435293] color history popup shouldn't appear centered

[Emmet O'Neill]

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

Emmet O'Neill  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|REPORTED|CONFIRMED

--- Comment #7 from Emmet O'Neill  ---
SySagar and I were able to confirm that this issue, so I've marked this as
confirmed.

Sy would like to take a crack at improving this, too.

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

[kmail2] [Bug 446052] Drag&Drop Mails in Kmail does not work using git-master snapshots since 2-3 days

[Laurent Montel]

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

Laurent Montel  changed:

   What|Removed |Added

  Latest Commit||https://invent.kde.org/pim/
   ||mailcommon/commit/b7d1febaa
   ||24d0fcf9418ffaff9d27e03b6cb
   ||2470
 Resolution|--- |FIXED
 Status|REPORTED|RESOLVED

--- Comment #1 from Laurent Montel  ---
Git commit b7d1febaa24d0fcf9418ffaff9d27e03b6cb2470 by Laurent Montel.
Committed on 25/11/2021 at 06:17.
Pushed by mlaurent into branch 'master'.

Fix 446052: Drag&Drop Mails in Kmail does not work using git-master snapshots
since 2-3 days

M  +1-1src/folder/foldertreeview.cpp

https://invent.kde.org/pim/mailcommon/commit/b7d1febaa24d0fcf9418ffaff9d27e03b6cb2470

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

[krita] [Bug 435293] color history popup shouldn't appear centered

[Emmet O'Neill]

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

Emmet O'Neill  changed:

   What|Removed |Added

 CC||emmetoneill@gmail.com

--- Comment #6 from Emmet O'Neill  ---
To add more information, the "color history popup" is a GUI element that can be
summoned by a keyboard shortcut action. (The default keybinding is `H`.)

I had no idea that this thing even existed, and you're right Manga Tengu, it's
not the best UX.

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

[kaffeine] [Bug 446062] New: The logs show kaffeine "recognises" my DVB-T card, but then states "Device not found"

[Ian]

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

Bug ID: 446062
   Summary: The logs show kaffeine "recognises" my DVB-T card, but
then states "Device not found"
   Product: kaffeine
   Version: 2.0.14
  Platform: Ubuntu Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: mchehab+hua...@kernel.org
  Reporter: ian.smit...@gmail.com
  Target Milestone: ---

SUMMARY
kaffeine worked with my DVB-T card, but has stopped. I may have updated
software as I do regularly, but cannot recall what was updated.
kaffeine "recognises" my card according to the log, but then states the device
hasn't been found!
me-tv works with the card.



STEPS TO REPRODUCE
1.  Run kaffeine
2. Go to Television "button"

OBSERVED RESULT
Notification that "Device not found"

EXPECTED RESULT
Being able to access DVB-T card

SOFTWARE/OS VERSIONS
Ubuntu 18.04
kernel: 4.15.0-162-generic

apt show kaffeine
Package: kaffeine
Version: 2.0.14-1
Priority: optional
Section: universe/kde
Origin: Ubuntu
Maintainer: Ubuntu Developers 
Original-Maintainer: Debian KDE Extras Team

Bugs: https://bugs.launchpad.net/ubuntu/+filebug
Installed-Size: 10.2 MB
Depends: kio, libc6 (>= 2.14), libdvbv5-0 (>= 1.4.0), libkf5configcore5 (>=
4.97.0), libkf5configwidgets5 (>= 4.96.0), libkf5coreaddons5 (>= 4.100.0),
libkf5dbusaddons5 (>= 4.99.0), libkf5i18n5 (>= 4.97.0), libkf5kiocore5 (>=
4.96.0), libkf5kiofilewidgets5 (>= 4.96.0), libkf5solid5 (>= 4.97.0),
libkf5widgetsaddons5 (>= 4.96.0), libkf5windowsystem5 (>= 4.96.0),
libkf5xmlgui-bin, libkf5xmlgui5 (>= 4.96.0), libqt5core5a (>= 5.9.0~beta),
libqt5dbus5 (>= 5.4.0), libqt5gui5 (>= 5.7.0), libqt5sql5 (>= 5.4.0),
libqt5widgets5 (>= 5.6.0~beta), libqt5x11extras5 (>= 5.6.0), libqt5xml5 (>=
5.4.0), libstdc++6 (>= 4.2.1), libvlc5 (>= 3.0.0), libxss1, kinit, iso-codes,
libqt5sql5-sqlite, vlc-plugin-base, vlc-plugin-video-output
Suggests: libdvdcss2
Homepage: http://kaffeine.kde.org
Supported: 3y
Download-Size: 5,475 kB
APT-Manual-Installed: yes
APT-Sources: http://gb.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages
Description: versatile media player for KDE
 Kaffeine is a media player for KDE based on VLC, which gives it a wide
 variety of supported media types and lets Kaffeine access CDs, DVDs, and
 network streams easily.  Kaffeine also has an excellent support of digital
 TV (DVB).
 .
 Kaffeine can keep track of multiple playlists simultaneously, and supports
 autoloading of subtitle files for use while playing video.

Log in kaffeine reports:-

24-11-21 21:04:46.753 [Warning ] Qt: Session management error: Could not open
network socket
24-11-21 21:04:48.132 [Info] kaffeine.dvb: Using built-in dvb device
manager
24-11-21 21:04:48.603 [Info] kaffeine.dev: Found dvb device
P14f1880200709601: Conexant CX22702 DVB-T
24-11-21 21:04:48.706 [Warning ] QObject::connect: No such slot
DvbTab::hideCursor()
24-11-21 21:04:48.850 [Warning ] Invalid Context= "stock" line for icon theme: 
"/usr/share/icons/ubuntu-mono-dark/stock/16/"
24-11-21 21:04:48.850 [Warning ] Invalid Context= "stock" line for icon theme: 
"/usr/share/icons/ubuntu-mono-dark/stock/22/"
24-11-21 21:04:48.850 [Warning ] Invalid Context= "stock" line for icon theme: 
"/usr/share/icons/ubuntu-mono-dark/stock/24/"
24-11-21 21:04:48.850 [Warning ] Invalid Context= "stock" line for icon theme: 
"/usr/share/icons/ubuntu-mono-dark/stock/32/"
24-11-21 21:04:48.850 [Warning ] Invalid Context= "stock" line for icon theme: 
"/usr/share/icons/ubuntu-mono-dark/stock/48/"
24-11-21 21:04:48.850 [Warning ] Invalid Context= "stock" line for icon theme: 
"/usr/share/icons/ubuntu-mono-dark/stock/64/"
24-11-21 21:04:48.850 [Warning ] Invalid Context= "stock" line for icon theme: 
"/usr/share/icons/ubuntu-mono-dark/stock/128/"
24-11-21 21:04:49.052 [Debug   ] kf5.kio.core: Refilling KProtocolInfoFactory
cache in the hope to find "mtp"
24-11-21 21:04:51.571 [Debug   ] Disc in /dev/sr0 is a Video DVD
24-11-21 21:04:52.436 [Warning ] kf5.kservice.services: The desktop entry file
"/usr/share/applications/unity-lens-photos.desktop" has Type= "Application" but
no Exec line
24-11-21 21:04:52.436 [Warning ] kf5.kservice.sycoca: Invalid Service : 
"/usr/share/applications/unity-lens-photos.desktop"
24-11-21 21:04:52.677 [Warning ] kf5.kservice.services: KServiceTypeTrader:
serviceType "ThumbCreator" not found
24-11-21 21:04:52.679 [Warning ] kf5.kservice.services: KServiceTypeTrader:
serviceType "ThumbCreator" not found
24-11-21 21:04:52.964 [Warning ] kf5.kservice.services: KServiceTypeTrader:
serviceType "ThumbCreator" not found
24-11-21 21:04:52.965 [Warning ] kf5.kservice.services: KServiceTypeTrader:
serviceType "ThumbCreator" not found

lspci
00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models
30h-3fh) Processor Root Complex
00:01.0 VGA compatible controller: Advanced Micro

[kdenlive] [Bug 445644] timeline mess after re-open

[Dr. Ashutosh Pradhan]

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

--- Comment #14 from Dr. Ashutosh Pradhan  ---
(In reply to Dr. Ashutosh Pradhan from comment #11)
> (In reply to emohr from comment #10)
> > Thanks all for testing.
> > 
> > @all. Please upload your Kdenlive project files "before the mess" and "after
> > the mess" here so we can check what happen.
> 
> You cannot discriminate the file before the mess and after the mess. It is
> practically difficult to share file before and after as the moment you close
> a file all the tracks go haywire and you have to re-align them. However,
> even if you re-align them on timeline, they look good on timeline yet when
> you render the video, the video is all mess. The basic function of KDEnLive
> of having multitrack video editing has got compromised in Ver
> kdenlive-21.08.3. You need to check it yourself, yet I will try and share
> the screen shots.

In source you need to fix it, if you have image files with extended duration on
same track that of video it messes up the entire track timeline. Please
replicate issue at your end and fix it in source.

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

[kdenlive] [Bug 445644] timeline mess after re-open

[Dr. Ashutosh Pradhan]

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

--- Comment #13 from Dr. Ashutosh Pradhan  ---
(In reply to Dr. Ashutosh Pradhan from comment #11)
> (In reply to emohr from comment #10)
> > Thanks all for testing.
> > 
> > @all. Please upload your Kdenlive project files "before the mess" and "after
> > the mess" here so we can check what happen.
> 
> You cannot discriminate the file before the mess and after the mess. It is
> practically difficult to share file before and after as the moment you close
> a file all the tracks go haywire and you have to re-align them. However,
> even if you re-align them on timeline, they look good on timeline yet when
> you render the video, the video is all mess. The basic function of KDEnLive
> of having multitrack video editing has got compromised in Ver
> kdenlive-21.08.3. You need to check it yourself, yet I will try and share
> the screen shots.

I have successfully identified and resolved the issue. I noticed that if the
.jpg or .png files are on same track as of video or audio the remaining clips
mess up. Hence I placed all .jpg and .png file on a separate track. I grouped
all the images together. Then I grouped all clips before closing the project.
Then I closed it and re-opened it, the timeline was intact. I am rendering the
video now for final output. Hope since the clips were not messed up the
rendered video too should be fine. Will let community know the result in new
four hours.

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

[plasmashell] [Bug 446061] New: Buffer for spa_pod_builder can be too small for some setup

[bugzilla_noreply]

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

Bug ID: 446061
   Summary: Buffer for spa_pod_builder can be too small for some
setup
   Product: plasmashell
   Version: 5.23.3
  Platform: Debian testing
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Task Manager and Icons-Only Task Manager
  Assignee: h...@kde.org
  Reporter: oii...@yahoo.com
CC: plasma-b...@kde.org
  Target Milestone: 1.0

SUMMARY
Libtaskmanager's buffer for spa_builder (see
https://invent.kde.org/plasma/plasma-workspace/-/blob/master/libtaskmanager/declarative/pipewiresourcestream.cpp#L187)
is too small on certain configurations. Because podBuilder->state.offset is
never reset
(https://gitlab.freedesktop.org/pipewire/pipewire/-/blob/master/spa/include/spa/pod/builder.h),
the buffer space can run out when EGL returns a long list of dma_buf modifiers,
causing PipeWire negotiation to fail.

An example is when EGL returns 20 modifiers. There are 6 formats defined in
pipewiresourcestream.cpp, for each format it will construct 2 frames, one with
21*8=168 bytes long of modifiers. The modifier lists for all frames will be
6*168=1008 bytes (only 16 bytes left of 1024 bytes), let alone other frames.

This seems to be the root cause for Bug 445461, but does not resolve Bug 444107
completely.


SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Debian testing
KDE Plasma Version: 5.23.3
KDE Frameworks Version: 5.86.0
Qt Version: 5.15.2

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

[krita] [Bug 444320] Selected brush resets after opening a first file

[Bug Janitor Service]

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

Bug Janitor Service  changed:

   What|Removed |Added

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

--- Comment #4 from Bug Janitor Service  ---
Thanks for your comment!

Automatically switching the status of this bug to REPORTED so that the KDE team
knows that the bug is ready to get confirmed.

In the future you may also do this yourself when providing needed information.

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

[lattedock] [Bug 444433] Latte crashes while using Zoom application.

[Bug Janitor Service]

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

Bug Janitor Service  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|WAITINGFORINFO  |WORKSFORME

--- Comment #3 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.

[libksane] [Bug 445139] Skanpage coredump

[Bug Janitor Service]

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

--- Comment #9 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.

[kwin] [Bug 444298] Unable to set 240 Hz

[Bug Janitor Service]

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

Bug Janitor Service  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|WAITINGFORINFO  |WORKSFORME

--- Comment #13 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.

[kwin] [Bug 443222] [Wayland] adding a new screen causes lockscreen to crash. Reboot needed

[Bug Janitor Service]

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

--- Comment #8 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.

[plasmashell] [Bug 445210] Plasma hangs all but mouse moves and some beep - no keyboard response

[Bug Janitor Service]

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

--- Comment #6 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.

[krunner] [Bug 446060] New: Calculator shows an erratic speed of light

[bugzilla_noreply]

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

Bug ID: 446060
   Summary: Calculator shows an erratic speed of light
   Product: krunner
   Version: 5.23.3
  Platform: Debian testing
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: calculator
  Assignee: alexander.loh...@gmx.de
  Reporter: oii...@yahoo.com
CC: plasma-b...@kde.org
  Target Milestone: ---

SUMMARY
The calculator plugin in krunner shows the speed of light (c) incorrectly.
Either the value should be corrected or 'c' should be changed to not denote the
speed of light.

STEPS TO REPRODUCE
Type '=c' into krunner.

OBSERVED RESULT
299.792458 m/s

EXPECTED RESULT
299792458 m/s

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Debian testing
KDE Plasma Version: 5.23.3
KDE Frameworks Version: 5.86.0
Qt Version: 5.15.2

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

[kwin] [Bug 446059] New: Mouse cursor unable to interact with windows if the mouse has gone to sleep

[bugzilla_noreply]

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

Bug ID: 446059
   Summary: Mouse cursor unable to interact with windows if the
mouse has gone to sleep
   Product: kwin
   Version: 5.22.5
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: input
  Assignee: kwin-bugs-n...@kde.org
  Reporter: ncdeh...@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
***
If my mouse (Saitek Cyborg Rat9) goes to sleep and I turn it back on, the
cursor becomes unable to click on/select/interact with any windows, through
mousing over or clicking any of the buttons. The cursor still moves. The only
thing I have found which fixes it is to press Ctrl+Alt+F2 to switch to a
different TTY and back.

STEPS TO REPRODUCE
1. Let mouse go to sleep/ step away from computer for a long time
2. Turn mouse back on
3. Try to click on any window

OBSERVED RESULT
Mouse functions after waking up

EXPECTED RESULT
Mouse functions after changing TTYs

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

ADDITIONAL INFORMATION

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

[systemsettings] [Bug 446058] New: System Settings Crashed

[Akhilesh]

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

Bug ID: 446058
   Summary: System Settings Crashed
   Product: systemsettings
   Version: 5.23.3
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: akhileshdeod...@gmail.com
  Target Milestone: ---

Application: systemsettings5 (5.23.3)

Qt Version: 5.15.3
Frameworks Version: 5.88.0
Operating System: Linux 5.11.0-40-generic x86_64
Windowing System: X11
Distribution: KDE neon User - Plasma 25th Anniversary Edition
DrKonqi: 5.23.3 [KCrashBackend]

-- Information about the crash:
- What I was doing when the application crashed:
  I was going to install new global theme but while installing it got crashed
but theme installed successfully.

The crash can be reproduced every time.

-- Backtrace:
Application: System Settings (systemsettings5), signal: Segmentation fault

[New LWP 53462]
[New LWP 53463]
[New LWP 53464]
[New LWP 53465]
[New LWP 53466]
[New LWP 53467]
[New LWP 53472]
[New LWP 53473]
[New LWP 53532]
[New LWP 53751]
[New LWP 53752]
[New LWP 53753]
[New LWP 53759]
[New LWP 53760]
[New LWP 53761]
[New LWP 53762]
[New LWP 53764]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
0x7f3b401eaaff in __GI___poll (fds=0x7ffefc99ddb8, nfds=1, timeout=1000) at
../sysdeps/unix/sysv/linux/poll.c:29
__preamble__
drkonqi_qmltrace_thread:1
Failed to do pygdbmi parsing: No module named 'pygdbmi'
frame={level="0",func="onEntryEvent",file="/usr/share/kpackage/kcms/kcm_lookandfeel/contents/ui/main.qml",fullname="/usr/share/kpackage/kcms/kcm_lookandfeel/contents/ui/main.qml",line="124",lan".
-
(beware that frames may have been optimized out)

[Current thread is 1 (Thread 0x7f3b3ba209c0 (LWP 53460))]

Thread 18 (Thread 0x7f3ac3fff700 (LWP 53764)):
#0  __GI___libc_read (nbytes=16, buf=0x7f3ac3ffe990, fd=67) at
../sysdeps/unix/sysv/linux/read.c:26
#1  __GI___libc_read (fd=67, buf=0x7f3ac3ffe990, nbytes=16) at
../sysdeps/unix/sysv/linux/read.c:24
#2  0x7f3b3e322b2f in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f3b3e2d9ebe in g_main_context_check () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f3b3e2da312 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7f3b3e2da4a3 in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#6  0x7f3b407b861b in QEventDispatcherGlib::processEvents
(this=0x7f3ab8000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#7  0x7f3b4075c8ab in QEventLoop::exec (this=this@entry=0x7f3ac3ffeba0,
flags=..., flags@entry=...) at
../../include/QtCore/../../src/corelib/global/qflags.h:141
#8  0x7f3b405762c2 in QThread::exec (this=) at
../../include/QtCore/../../src/corelib/global/qflags.h:121
#9  0x7f3b3f8ba3fa in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5
#10 0x7f3b4057745c in QThreadPrivate::start (arg=0x563897fca790) at
thread/qthread_unix.cpp:329
#11 0x7f3b3ec99609 in start_thread (arg=) at
pthread_create.c:477
#12 0x7f3b401f7293 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 17 (Thread 0x7f3ad9640700 (LWP 53762)):
#0  0x7f3b3e2d825d in g_source_ref () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7f3b3e2d8328 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f3b3e2d982b in g_main_context_prepare () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f3b3e2da29b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f3b3e2da4a3 in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7f3b407b861b in QEventDispatcherGlib::processEvents
(this=0x7f3ac8000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#6  0x7f3b4075c8ab in QEventLoop::exec (this=this@entry=0x7f3ad963fbe0,
flags=..., flags@entry=...) at
../../include/QtCore/../../src/corelib/global/qflags.h:141
#7  0x7f3b405762c2 in QThread::exec (this=) at
../../include/QtCore/../../src/corelib/global/qflags.h:121
#8  0x7f3b4057745c in QThreadPrivate::start (arg=0x563898477340) at
thread/qthread_unix.cpp:329
#9  0x7f3b3ec99609 in start_thread (arg=) at
pthread_create.c:477
#10 0x7f3b401f7293 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 16 (Thread 0x7f3ad9ffb700 (LWP 53761)):
#0  0x7f3b3e2d68ed in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7f3b3e2d8345 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f3b3e2d9cbf in g_main_context_check () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f3b3e2da312 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f3b3e2da4a3 in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7f3b407b861b in QEventDispatcherGl

[kdenlive] [Bug 445644] timeline mess after re-open

[Dr. Ashutosh Pradhan]

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

--- Comment #12 from Dr. Ashutosh Pradhan  ---
(In reply to emohr from comment #10)
> Thanks all for testing.
> 
> @all. Please upload your Kdenlive project files "before the mess" and "after
> the mess" here so we can check what happen.

I have realized the .jpg files extended over track shrink to one second and
then all the clips around the goes to toss. However, the single .jpg or .png
files placed on whole track remains intact. I have been spending time to render
a 42 minutes Zoom Presentation where I had earlier included .jpg files of the
slides. Which after render made the video irrelevant with complete mess though
the timeline showed everything intact. The moment I closed the project file and
opened it, the mess in rendered video matched with mess on timeline. Then I
replace .jpg files with Zoom presentation video which stay on its time. Yet few
.jpgs again made the video irrelevant.

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

[kdenlive] [Bug 445644] timeline mess after re-open

[Dr. Ashutosh Pradhan]

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

--- Comment #11 from Dr. Ashutosh Pradhan  ---
(In reply to emohr from comment #10)
> Thanks all for testing.
> 
> @all. Please upload your Kdenlive project files "before the mess" and "after
> the mess" here so we can check what happen.

You cannot discriminate the file before the mess and after the mess. It is
practically difficult to share file before and after as the moment you close a
file all the tracks go haywire and you have to re-align them. However, even if
you re-align them on timeline, they look good on timeline yet when you render
the video, the video is all mess. The basic function of KDEnLive of having
multitrack video editing has got compromised in Ver kdenlive-21.08.3. You need
to check it yourself, yet I will try and share the screen shots.

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

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

[Jonathan Neufeld]

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

Jonathan Neufeld  changed:

   What|Removed |Added

 CC||supp...@extollit.com

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

[krunner] [Bug 446057] New: Setting Space as Keyword delimiter has no effect in Krunner

[Fushan Wen]

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

Bug ID: 446057
   Summary: Setting Space as Keyword delimiter has no effect in
Krunner
   Product: krunner
   Version: master
  Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
  Keywords: usability
  Severity: normal
  Priority: NOR
 Component: webshortcuts
  Assignee: alexander.loh...@gmx.de
  Reporter: qydwhotm...@gmail.com
CC: plasma-b...@kde.org
  Target Milestone: ---

SUMMARY
When I set Keyword delimiter to Space, and I try to type "g hello", Krunner
does not show an option to search on the web like "g:hello".


STEPS TO REPRODUCE
1.  Set Keyword delimiter to Space, and enable Google search engine keyword as
g.
2. Open Krunner
3. Type "g hello"

OBSERVED RESULT
No option to search on the web

EXPECTED RESULT
An option to search on the web

SOFTWARE/OS VERSIONS
Information for package libKF5Runner5:
--
Repository : unstable-kde-frameworks
Name   : libKF5Runner5
Version: 5.89.0git.2026T064119~4afed93-ku.2.1
Arch   : x86_64
Vendor : obs://build.opensuse.org/KDE:Unstable
Installed Size : 355.2 KiB
Installed  : Yes
Status : up-to-date
Source package : krunner-5.89.0git.2026T064119~4afed93-ku.2.1.src
Summary: KDE Framework for providing different actions given a string
query
Description: 
KDE Framework for providing different actions given a string query.

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

[plasmashell] [Bug 399864] Folder view crashes when moving file from popup views into parent view

[Fushan Wen]

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

Fushan Wen  changed:

   What|Removed |Added

 CC||qydwhotm...@gmail.com
   Version Fixed In||5.24

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

[plasmashell] [Bug 399864] Folder view crashes when moving file from popup views into parent view

[Fushan Wen]

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

Fushan Wen  changed:

   What|Removed |Added

 Status|ASSIGNED|RESOLVED
  Latest Commit||https://invent.kde.org/plas
   ||ma/plasma-desktop/commit/c1
   ||93fd4c3a6135dfccd5696c3fcd8
   ||4a12b1af8fa
 Resolution|--- |FIXED

--- Comment #30 from Fushan Wen  ---
Git commit c193fd4c3a6135dfccd5696c3fcd84a12b1af8fa by Fushan Wen, on behalf of
Marco Martin.
Committed on 25/11/2021 at 02:02.
Pushed by fusionfuture into branch 'master'.

never delete any dialog if there is a drag in progress anywhere

on Wayland deleting either the source or the target of a qdrag
causes crashes due to the nested event loops.
keep a global track if any item started a drag anywhere, if so
don't delete any dialog but queue it for destruction

M  +1-0containments/desktop/package/contents/ui/FolderView.qml
M  +3-3containments/desktop/package/contents/ui/FolderViewDialog.qml
M  +64   -11   containments/desktop/plugins/folder/foldermodel.cpp
M  +25   -1containments/desktop/plugins/folder/foldermodel.h

https://invent.kde.org/plasma/plasma-desktop/commit/c193fd4c3a6135dfccd5696c3fcd84a12b1af8fa

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

[Discover] [Bug 445923] Discover crash when clicking it from systray

[David]

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

--- Comment #2 from David  ---
This is another crash **with** debug symbols installed. It doesn't look like
they add anything to the log:

Application: Discover (plasma-discover), signal: Segmentation fault

[KCrash Handler]
#4  0x7fb5e4438458 in ?? () from
/usr/lib/x86_64-linux-gnu/qt5/plugins/discover/flatpak-backend.so
#5  0x7fb5e443e1fa in ?? () from
/usr/lib/x86_64-linux-gnu/qt5/plugins/discover/flatpak-backend.so
#6  0x7fb5e4441c4e in ?? () from
/usr/lib/x86_64-linux-gnu/qt5/plugins/discover/flatpak-backend.so
#7  0x7fb62b505d6e in QObject::event(QEvent*) () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7fb62c6276af in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#9  0x7fb62b4d975a in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /lib/x86_64-linux-gnu/libQt5Core.so.5
#10 0x7fb62b4dc7a7 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#11 0x7fb62b531733 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#12 0x7fb629b5fc7b in g_main_context_dispatch () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#13 0x7fb629b5ff28 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#14 0x7fb629b5ffdf in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#15 0x7fb62b530db4 in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib/x86_64-linux-gnu/libQt5Core.so.5
#16 0x7fb62b4d816b in
QEventLoop::exec(QFlags) () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#17 0x7fb62b4e0440 in QCoreApplication::exec() () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#18 0x55955e0a7f51 in ?? ()
#19 0x7fb62ae7ee4a in __libc_start_main (main=0x55955e0a76a0, argc=3,
argv=0x7ffd75c7b368, init=, fini=,
rtld_fini=, stack_end=0x7ffd75c7b358) at ../csu/libc-start.c:314
#20 0x55955e0a844a in ?? ()
[Inferior 1 (process 1720198) detached]

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

[Breeze] [Bug 446056] New: Inkscape indicator for docking is invisible in Breeze-gtk

[bugzilla_noreply]

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

Bug ID: 446056
   Summary: Inkscape indicator for docking is invisible in
Breeze-gtk
   Product: Breeze
   Version: 5.23.3
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: gtk theme
  Assignee: uhh...@gmail.com
  Reporter: doncb...@gmail.com
CC: plasma-b...@kde.org
  Target Milestone: ---

SUMMARY
Normally, there is an outline box in Inkscape to tell if the dialog attached to
the mouse can be docked. It does not appear in the Breeze-gtk themes however.
It should look as shown:
https://media.inkscape.org/media/resources/file/2021-11-21_19-09-22.gif


STEPS TO REPRODUCE
1. Open Inkscape
2. Open some dialogs (e.g. XML Editor and Fill and Stroke w/ Ctrl + Shift + x
and Ctrl + Shift + f)
3. Click and drag a tab to the side of a dialog

OBSERVED RESULT
There is no docking outline

EXPECTED RESULT
There should be a visible outline to tell if the dialog can be docked/snapped.

SOFTWARE/OS VERSIONS
KDE Plasma Version: 5.23.3
KDE Frameworks Version: 5.87.0
Qt Version: 5.15.2

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

[frameworks-syntax-highlighting] [Bug 445918] Markdown headings highlighted completely in purple rending text unreadable

[Jan Paul Batrina]

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

Jan Paul Batrina  changed:

   What|Removed |Added

 CC||jpmbatrin...@gmail.com
 Ever confirmed|0   |1
Product|kate|frameworks-syntax-highlight
   ||ing
Version|21.08.3 |5.88.0
 Status|REPORTED|CONFIRMED
  Component|kwrite  |theme

--- Comment #1 from Jan Paul Batrina  ---
Confirmed with these steps:

1. open/create .md file
2. Insert the following text:

# heading
## heading

# heading 2

3. Place cursor on "# heading 2"

This is (unintentionally) caused by the folding region highlight introduced by
https://invent.kde.org/frameworks/ktexteditor/-/merge_requests/194. The fix
would be to ensure that the Heading color(s) and the Bracket Highlight Color
are not the same, at least for the default color schemes.

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

[plasmashell] [Bug 446055] New: System tray moves itself to the left of the global menu when plasma starts

[Sawyer]

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

Bug ID: 446055
   Summary: System tray moves itself to the left of the global
menu when plasma starts
   Product: plasmashell
   Version: 5.23.3
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: System Tray
  Assignee: plasma-b...@kde.org
  Reporter: sawyer.r.steph...@gmail.com
CC: mate...@gmail.com
  Target Milestone: 1.0

Created attachment 143925
  --> https://bugs.kde.org/attachment.cgi?id=143925&action=edit
the system tray shifting itself to the left

SUMMARY
If I rearrange my desktop so that the system tray displays on the right side in
a global menu instead on the task bar, the system tray would shift itself to
the left of the global menu upon plasma starting up again, causing it to get in
the way of the menu options. This means I would have to reenter into edit mode
each time just to move the system tray to the right again where I want it to
be.


STEPS TO REPRODUCE
1. From the desktop add the application menu bar (global menu)
2. Add or move the system tray to the right of the application menu bar
3. Restart plasma

OBSERVED RESULT
The system tray shifts itself to the left despite never being in edit mode

EXPECTED RESULT
The system tray should of stayed where it was left

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 5.15.4-arch1-1 (64 bit)
KDE Plasma Version: 5.23.3
KDE Frameworks Version: 5.88.0
Qt Version: 5.15.2

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

[konsole] [Bug 445846] "Bi-directional text rendering" should be renamed to something like "Support for complex scripts"

[Duncan]

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

--- Comment #4 from Duncan <1i5t5.dun...@cox.net> ---
(In reply to Ahmad Samir from comment #3)
> To disambiguate, "Support for complex scripts (RTL, Chinese, Urdu ...etc)" ?

Works for me! =:^)

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

[kdenlive] [Bug 443324] Spacer Tool hangs the app if used with grouped clips

[bugzilla_noreply]

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

--- Comment #10 from biblio...@gmail.com ---
P.S. Just formality: right to the group == right to the rightmost element of
the group.

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

[kdenlive] [Bug 443324] Spacer Tool hangs the app if used with grouped clips

[bugzilla_noreply]

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

--- Comment #9 from biblio...@gmail.com ---
(In reply to emohr from comment #8)
> Question to your point 2): we have 3 clips on a track: A, B, C. A and C are
> grouped. You click with spacer on clip C. Should A and B also move in the
> spacer operation?

$One-million question! Strangely, my reply is: A should, and B shouldn't.

Maybe, it is to be discussed with experts (I am not), but in my general and
formal view, as you Spacer click on an element, and if the element is a part of
a group, what should move is the respective group as a whole (treated as a
single element), and all the elements to the right of the group. In our case, A
& C are to move as a group, and B shouldn't because B is not right to the
group! In my understanding, the group, if it is a group, should be treated as
one element consistently.

Following the above: (1) I suppose the Spacer algorithm could reliably work
like it did in case of clicking the leftmost element of a group (no crashes in
that case were detected), the only correction expected is that the first moving
element should be the leftmost element of the clicked group. And, by the way,
the group should not treated as temporary like other moving elements to the
right of it. ))

(2) Maybe, the whole practice of grouping non-adjacent clips in one track
should be considered weird. ))

The practice of grouping not adjacent

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

[kwin] [Bug 446054] New: Zoom effect freezes screen only on Wayland

[Josep Febrer]

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

Bug ID: 446054
   Summary: Zoom effect freezes screen only on Wayland
   Product: kwin
   Version: git master
  Platform: Debian unstable
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: effects-various
  Assignee: kwin-bugs-n...@kde.org
  Reporter: jfeb...@gmail.com
  Target Milestone: ---

SUMMARY
***
After building KWin from the latest git master I found that when I activate the
zoom effect on Wayland the screen freezes and the cursor disappears. I haven't
found a way to restore it.
I have to go to a tty to restart the session. When the freeze happens I
discovered that the keyboard is still responding because I can stop a window
which is playing music with a keyboard shortcut but even if I exit the session
with a keyboard shortcut the screen remains friezed as nothing happened.
Under X11 I can use the zoom effect as usual without any issue.
***


STEPS TO REPRODUCE
1. Turn on the zoom effect on system settings.
2. Use the zoom effect with a keyboard shortcut.

OBSERVED RESULT

The screen freezes completely and I have to go a tty to be able to restart the
desktop session.

EXPECTED RESULT

The screen should be zoomed.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Debian GNU/Linux unstable
(available in About System)
KDE Plasma Version: 5.23.80
KDE Frameworks Version: 5.88.0
Qt Version: 5.15.2

ADDITIONAL INFORMATION

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

[plasmashell] [Bug 446053] New: Several times switch of user session type between wayland and x11 leads to crash of plasmashell

[pveax]

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

Bug ID: 446053
   Summary: Several times switch of user session type between
wayland and x11 leads to crash of plasmashell
   Product: plasmashell
   Version: 5.23.3
  Platform: Manjaro
OS: Linux
Status: REPORTED
  Severity: crash
  Priority: NOR
 Component: generic-crash
  Assignee: plasma-b...@kde.org
  Reporter: pv...@mailforspam.com
  Target Milestone: 1.0

IMPORTANT NOTE

I select `plasmashell`'s closest (newest possible) version in the `*Version`
list to what I have, but I was USING the newer (still absent in the list)
version:
```
~/Desktop ❯ plasmashell -v   
plasmashell 5.23.80
```
`plasmashell` is owned by `plasma-workspace`.
The GIT COMMIT HASH of the `plasma-workspace` is `81bb5ae6a`.

SUMMARY

Sometimes plasmashell crashes while doing (x11 <-> wayland) switch.

STEPS TO REPRODUCE

I did several times switch between user session types of wayland and x11, than
`plasmashell` crashed. I see such bug earlier at least for 3 months in a row.
So it is not the brand new bug.
Please note, that I did about 5 full cycle (x11 <-> wayland) switches. All that
switches I did within a single PC boot up, did not reboot PC between them. I
saw no any visual problems: all switches works fine. But only by logs I saw:
```
~/Desktop ❯ journalctl -b -p3 | grep -iE "dumped|gpu|crash|hang"
Nov 25 01:13:27 pc systemd-coredump[10936]: Process 10927 (plasmashell) of user
1000 dumped core.
Found module libKF5Crash.so.5 with
build-id: 57a05e1c2e20581835cb791cd6852ce27b256c56
Nov 25 01:13:28 pc systemd-coredump[10947]: Process 10943 (xdg-desktop-por) of
user 1000 dumped core.
Found module libKF5Crash.so.5 with
build-id: 57a05e1c2e20581835cb791cd6852ce27b256c56
Nov 25 01:13:29 pc systemd-coredump[10932]: Process 10392 (plasmashell) of user
1000 dumped core.
Found module libdrm_amdgpu.so.1
with build-id: 587ec7f42cd8e6298ef2bf769df3a9417be90103
Found module libKF5Crash.so.5 with
build-id: 57a05e1c2e20581835cb791cd6852ce27b256c56
#1  0x7fa04e7b946c
_ZN6KCrash19defaultCrashHandlerEi (libKF5Crash.so.5 + 0x546c)
~/Desktop ❯ 
```

Here I reported the first one crash of mentioned queue (from `Nov 25
01:13:27`).

LOGGED RESULT

`plasmashell` crash

EXPECTED RESULT

No any crash while switching user session type

SOFTWARE/OS VERSIONS

```
Operating System: Manjaro Linux
KDE Plasma Version: 5.23.80
KDE Frameworks Version: 5.89.0
Qt Version: 5.15.2
Kernel Version: 5.15.4-2-MANJARO (64-bit)
Graphics Platform: Wayland

Processors: 4 × Intel® Core™ i5-8250U CPU @ 1.60GHz
Memory: 31.1 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics 620
```

`sddm` git hash commit is `6a7d25f`.

ADDITIONAL INFORMATION

Severity was chosen above crash, cause the process do not crash itself, but
crash even other process.

Backtrace with no debugging symbols :(

```
~/Desktop ❯ gdb /usr/bin/plasmashell
core.plasmashell.1000.61425207cf014933b79d1b466f03bab9.10927.163779200700
GNU gdb (GDB) 11.1
Copyright (C) 2021 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 /usr/bin/plasmashell...
(No debugging symbols found in /usr/bin/plasmashell)
[New LWP 10927]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
Core was generated by `/usr/bin/plasmashell'.
Program terminated with signal SIGABRT, Aborted.
#0  0x7f7c72447d22 in raise () from /usr/lib/libc.so.6
(gdb) bt
#0  0x7f7c72447d22 in raise () from /usr/lib/libc.so.6
#1  0x7f7c72431862 in abort () from /usr/lib/libc.so.6
#2  0x7f7c7287d910 in QMessageLogger::fatal(char const*, ...) const () from
/usr/lib/libQt5Core.so.5
#3  0x7f7c72e78155 in QGuiApplicationPrivate::createPlatformIntegration()
() from /usr/lib/libQt5Gui.so.5
#4  0x7f7c72e78661 in QGuiApplicationPrivate::createEventDispatcher() ()
from /usr/lib/libQt5Gui.so.5
#5  0x7f7c72aad137 in QCoreApplicationPrivate::init() () from
/usr/lib/libQt5Core.so.5
#6  0x7f7c72e7b673 in QGuiApplicationPrivate::init() () from
/usr/lib/libQt

[frameworks-kio] [Bug 328709] Add a Hard link option when moving/copying files in Dolphin

[Marcus Sundman]

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

Marcus Sundman  changed:

   What|Removed |Added

 CC||sund...@iki.fi

--- Comment #9 from Marcus Sundman  ---
Is there some workaround for the lack of built-in hardlink creation? Maybe
something in the "activities" menu? Or something for "Open with..."?

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

[Breeze] [Bug 445960] Hover and focus colors applied inconsistently throughout different widgets

[Noah Davis]

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

--- Comment #8 from Noah Davis  ---
There are a lot of issues surrounding the customization of color schemes that
aren't likely to be resolved unless we make a new color scheme system.

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

[Breeze] [Bug 445960] Hover and focus colors applied inconsistently throughout different widgets

[Noah Davis]

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

--- Comment #7 from Noah Davis  ---
(In reply to Nate Graham from comment #6)
> Why not just use what we have though? Are there really so many 3rd-party
> color schemes that do this wrong? If Breeze does, surely we can fix that.

I was talking about 3rd party apps. When apps have to do a bit of custom
painting for their delegates (Qt Widget item delegates can be kind of a mess to
implement, unlike Qt Quick) or some other widget, they use QPalette::Highlight.
Even KDE apps do this. It doesn't help that KColorScheme is part of a tier 3
framework, so custom Qt Widget components in lower tiers can't use it. With
that said, you also cannot guarantee that all 3rd party color schemes
(including popular ones) will work well with any decision we make. The simplest
answer that is least likely to result in more problems down the line is to just
use QPalette::Highlight.

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

[kwin] [Bug 441547] Crash in KWin::clamp_row() when switching activities

[bugzilla_noreply]

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

--- Comment #14 from ham...@laposte.net ---
ADDITIONAL INFORMATION
I use the nvidia driver 495.44
I see these logs "plasmashell[1830]: requesting unexisting screen -1" everytime
I switch between activities. It's not related with the kwin crash.

I can provide a complete backtrace if needed.

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

[kmail2] [Bug 446052] New: Drag&Drop Mails in Kmail does not work using git-master snapshots since 2-3 days

[Robby Engelmann]

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

Bug ID: 446052
   Summary: Drag&Drop Mails in Kmail does not work using
git-master snapshots since 2-3 days
   Product: kmail2
   Version: Git (master)
  Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: UI
  Assignee: kdepim-b...@kde.org
  Reporter: robby.engelm...@r-engelmann.de
  Target Milestone: ---

SUMMARY
***
Drag&Drop Mails in Kmail does not work using git-master snapshots since 2-3
days
***
STEPS TO REPRODUCE
1. use OpenSuse Unstable = git master snapshots for frameworks+plasma+gear
2.  open kmail, try to move mail to another folder

OBSERVED RESULT
cannot move to another folder, but move is possible if folder is added to
favorite folders

EXPECTED RESULT
works as normal

SOFTWARE/OS VERSIONS
Operating System: openSUSE Tumbleweed 20211123
KDE Plasma Version: 5.23.80
KDE Frameworks Version: 5.89.0
Qt Version: 5.15.2
Kernel Version: 5.15.3-1-default (64-bit)
Graphics Platform: Wayland
Processors: 8 × Intel® Core™ i7-10510U CPU @ 1.80GHz
Memory: 31.0 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics

ADDITIONAL INFORMATION
downstream bug: http://bugzilla.opensuse.org/show_bug.cgi?id=1193055

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

[kwin] [Bug 441547] Crash in KWin::clamp_row() when switching activities

[bugzilla_noreply]

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

ham...@laposte.net changed:

   What|Removed |Added

 CC||ham...@laposte.net

--- Comment #13 from ham...@laposte.net ---
I have this bug with kwin_x11. It crashes sometimes when hitting meta-tab to
switch between activities.

I see theses logs just before it crashes :
plasmashell[1830]: requesting unexisting screen -1
plasmashell[1830]: requesting unexisting screen -1

(gdb) bt
#0  0x7f8582543d22 in raise () at /usr/lib/libc.so.6
#1  0x7f8583e7e064 in KCrash::defaultCrashHandler(int) () at
/usr/lib/libKF5Crash.so.5
#2  0x7f8582543da0 in  () at /usr/lib/libc.so.6
#3  0x7f85824462f1 in  () at /usr/lib/libkwin4_effect_builtins.so.1
#4  0x7f8582446adb in  () at /usr/lib/libkwin4_effect_builtins.so.1
#5  0x7f8583fe2524 in
KWin::EffectsHandlerImpl::paintWindow(KWin::EffectWindow*, int, QRegion const&,
KWin::WindowPaintData&) ()
at /usr/lib/libkwin.so.5
#6  0x7f8584068809 in KWin::Scene::paintWindow(KWin::Scene::Window*, int,
QRegion const&) () at /usr/lib/libkwin.so.5
#7  0x7f8584066e67 in KWin::Scene::paintSimpleScreen(int, QRegion const&)
() at /usr/lib/libkwin.so.5
#8  0x7f8583fe2324 in KWin::EffectsHandlerImpl::paintScreen(int, QRegion
const&, KWin::ScreenPaintData&) () at /usr/lib/libkwin.so.5
#9  0x7f8583fe2324 in KWin::EffectsHandlerImpl::paintScreen(int, QRegion
const&, KWin::ScreenPaintData&) () at /usr/lib/libkwin.so.5
#10 0x7f8583fe2324 in KWin::EffectsHandlerImpl::paintScreen(int, QRegion
const&, KWin::ScreenPaintData&) () at /usr/lib/libkwin.so.5
#11 0x7f858406817e in KWin::Scene::paintScreen(QRegion const&, QRegion
const&, QRegion*, QRegion*, KWin::RenderLoop*, QMatrix4x4 const&) () at
/usr/lib/libkwin.so.5
#12 0x7f85707041d2 in KWin::SceneOpenGL::paint(KWin::AbstractOutput*,
QRegion const&, QList const&, KWin::RenderLoop*) () at
/usr/lib/qt/plugins/org.kde.kwin.scenes/KWinSceneOpenGL.so
#13 0x7f8583fac01c in KWin::Compositor::composite(KWin::RenderLoop*) () at
/usr/lib/libkwin.so.5
#14 0x7f8583fac47d in KWin::X11Compositor::composite(KWin::RenderLoop*) ()
at /usr/lib/libkwin.so.5
#15 0x7f858342e7ab in  () at /usr/lib/libQt5Core.so.5
#16 0x7f8583f5f333 in KWin::RenderLoop::frameRequested(KWin::RenderLoop*)
() at /usr/lib/libkwin.so.5
#17 0x7f85840563d4 in KWin::RenderLoopPrivate::dispatch() () at
/usr/lib/libkwin.so.5
#18 0x7f858342e7ab in  () at /usr/lib/libQt5Core.so.5
#19 0x7f858343277b in QTimer::timeout(QTimer::QPrivateSignal) () at
/usr/lib/libQt5Core.so.5
#20 0x7f858342446f in QObject::event(QEvent*) () at
/usr/lib/libQt5Core.so.5
#21 0x7f8582a4cd62 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /usr/lib/libQt5Widgets.so.5
#22 0x7f85833f73fa in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at /usr/lib/libQt5Core.so.5
#23 0x7f858344f39d in QTimerInfoList::activateTimers() () at
/usr/lib/libQt5Core.so.5
#24 0x7f858344d879 in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#25 0x7f857c15139f in  () at /usr/lib/libQt5XcbQpa.so.5
#26 0x7f85833f5d6c in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#27 0x7f85833fe2d4 in QCoreApplication::exec() () at
/usr/lib/libQt5Core.so.5
#28 0x55f73cf7a441 in  ()
#29 0x7f858252eb25 in __libc_start_main () at /usr/lib/libc.so.6
#30 0x55f73cf7a97e in  ()

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

[frameworks-kio] [Bug 445801] Doesn't honor the system umask for newly-created files

[Enzo]

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

--- Comment #6 from Enzo  ---
Maybe i am wrong, but when you copy a file you first create an empty one. Then
you fill it in with the original content.

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

[krita] [Bug 446029] Cannot drop web images onto the welcome screen

[amyspark]

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

amyspark  changed:

   What|Removed |Added

 Status|CONFIRMED   |ASSIGNED
   Assignee|krita-bugs-n...@kde.org |a...@amyspark.me

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

[Plasma Vault] [Bug 446051] Vault not recognized after upgrade

[Ivan Čukić]

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

--- Comment #1 from Ivan Čukić  ---
Hi,

The paths are stored as absolute paths in $HOME/.config/plasmavaultrc so that
is the place you need to update them.

Advised approach:
killall kded5
edit the file - replace all /home/OLD_USERNAME with /home/NEW_USERNAME
kded5

This should do the trick.

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

[Plasma Vault] [Bug 446051] New: Vault not recognized after upgrade

[bugzilla_noreply]

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

Bug ID: 446051
   Summary: Vault not recognized after upgrade
   Product: Plasma Vault
   Version: unspecified
  Platform: Ubuntu Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: ivan.cu...@kde.org
  Reporter: mipacig...@nefacility.com
  Target Milestone: ---

SUMMARY

I upgraded from Kubuntu 20.10 to Kubuntu 21.10, but my old vault isn't showing
up in the widget, even though I can see the files in
`~/.local/share/plasma-vault/VAULT-NAME.enc/*` (there's a bunch of 3-character
directories and a `cryfs.config`) and the directory `~/Vaults/VAULT-NAME`
exists (but it's empty, as expected). Any idea what I need to do for the vault
to be recognized?

During the upgrade, I also chose a different username, so my `/home/{username}`
directory is different. Maybe `cryfs.config` is using absolute paths? The file
seems to be binary and I don't know which format it uses, so I can't tell
what's inside.

I can create new vaults without issues.


SOFTWARE/OS VERSIONS
Linux/KDE Plasma:  Kubuntu 21.10
KDE Plasma Version: 5.22.5
KDE Frameworks Version: 5.86.0
Qt Version: 5.15.2

ADDITIONAL INFORMATION

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

[extra-cmake-modules] [Bug 446050] ECMGenerateQmlTypes generates plugins.qmltypes in source directory which is incompatible with CMAKE_DISABLE_SOURCE_CHANGES

[Bug Janitor Service]

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

Bug Janitor Service  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|REPORTED|ASSIGNED

--- Comment #1 from Bug Janitor Service  ---
A possibly relevant merge request was started @
https://invent.kde.org/frameworks/extra-cmake-modules/-/merge_requests/201

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

[frameworks-kio] [Bug 404777] KIO::CopyJob::setDefaultPermissions does not work

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

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

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

[extra-cmake-modules] [Bug 446050] New: ECMGenerateQmlTypes generates plugins.qmltypes in source directory which is incompatible with CMAKE_DISABLE_SOURCE_CHANGES

[Dawid Wróbel]

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

Bug ID: 446050
   Summary: ECMGenerateQmlTypes generates plugins.qmltypes in
source directory which is incompatible with
CMAKE_DISABLE_SOURCE_CHANGES
   Product: extra-cmake-modules
   Version: 5.88.0
  Platform: Other
OS: Other
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: ecm-bugs-n...@kde.org
  Reporter: m...@dawidwrobel.com
  Target Milestone: ---

SUMMARY

The ECMGenerateQmlTypes says in its description:

"The developer will be in charge of making sure that these files are up to
date. The plugin.qmltypes file will sit in the source directory."

Which implies that it should be the developer themselves that need to keep this
file up to date. However, the file is being generated by each CMake passing and
saved in the source code, which makes it immediately incompatible with
CMAKE_DISABLE_SOURCE_CHANGES.

Moreover, this seems to argue with another default behavior, which installs the
auto-generated file to a final location:

"This function will include the code that installs the file in the right place"

At this point, is it even necessary to modify the source code, if the file is
being always regenerated and that copy is installed?

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

[frameworks-kio] [Bug 445801] Doesn't honor the system umask for newly-created files

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |---
Summary|Doesn't honor the umask |Doesn't honor the system
   |while saving screenshots|umask for newly-created
   ||files
 CC||a.samir...@gmail.com
 Status|NEEDSINFO   |CONFIRMED
 Ever confirmed|0   |1
   See Also||https://bugs.kde.org/show_b
   ||ug.cgi?id=404777

--- Comment #5 from Nate Graham  ---
Looks like there's still a use case that needs to be fixed, then. Perhaps only
copying got fixed, and file creation still suffers from the bug.

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

[kdenlive] [Bug 445727] Rendering skips image duration

[bugzilla_noreply]

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

--- Comment #14 from s33_furt...@protonmail.com ---
i have used this song (https://youtu.be/2XQTYv3z4Uo) converted to mp3 by Vividl
(https://github.com/Bluegrams/Vividl), but i have used other musics and even
recorded with my own mic and i got the same result

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

[frameworks-kio] [Bug 445801] Doesn't honor the umask while saving screenshots

[Enzo]

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

--- Comment #4 from Enzo  ---
5.88

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

[frameworks-kio] [Bug 426528] Changing upper/lowercase on renaming a folder on a CIFS mount triggers multiple bugs

[Nate Graham]

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

--- Comment #4 from Nate Graham  ---
That's what kio-fuse is supposed to do.

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

[plasmashell] [Bug 445409] Plasma freezes or crashes when restoring Firefox on Wayland

[Philip McGrath]

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

--- Comment #6 from Philip McGrath  ---
(In reply to Méven Car from comment #5)
> "I have experienced this using the Wayland session on Kubuntu 21.10 with
> 5.23.3 from the Kubuntu backports PPA."
> 
> (K)ubuntu does not use the KDE Qt patch collection, this reduces stability
> especially with Wayland.

Do you know of a thread or issue or something where I could find more
discussion on this? I hadn't been aware of it, and I haven't found much more
with some searching on my own.

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

[kdenlive] [Bug 445727] Rendering skips image duration

[bugzilla_noreply]

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

--- Comment #13 from s33_furt...@protonmail.com ---
Created attachment 143924
  --> https://bugs.kde.org/attachment.cgi?id=143924&action=edit
The video at the end of the project

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

[Breeze] [Bug 445809] Menu styling: right-aligned shortcut text has unnecessary spacing

[Nate Graham]

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

--- Comment #7 from Nate Graham  ---
OMG LOL

Maybe we can do it for all other cases at least, since that is quite a rare use
case.

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

[kdenlive] [Bug 445727] Rendering skips image duration

[bugzilla_noreply]

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

--- Comment #12 from s33_furt...@protonmail.com ---
Created attachment 143923
  --> https://bugs.kde.org/attachment.cgi?id=143923&action=edit
The first image of the project

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

[kdenlive] [Bug 445727] Rendering skips image duration

[bugzilla_noreply]

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

--- Comment #11 from s33_furt...@protonmail.com ---
Created attachment 143922
  --> https://bugs.kde.org/attachment.cgi?id=143922&action=edit
The kdenlive project

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

[Breeze] [Bug 445960] Hover and focus colors applied inconsistently throughout different widgets

[Nate Graham]

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

--- Comment #6 from Nate Graham  ---
Why not just use what we have though? Are there really so many 3rd-party color
schemes that do this wrong? If Breeze does, surely we can fix that.

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

[systemsettings] [Bug 445647] Misleading tooltip text for Force Font DPI

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

Summary|Misleading tooltip text for |Misleading tooltip text for
   |Firce Font DPI  |Force Font DPI

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

[kdenlive] [Bug 445727] Rendering skips image duration

[bugzilla_noreply]

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

--- Comment #10 from s33_furt...@protonmail.com ---
Created attachment 143921
  --> https://bugs.kde.org/attachment.cgi?id=143921&action=edit
Image of the output video skipping time

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

[kdenlive] [Bug 445727] Rendering skips image duration

[bugzilla_noreply]

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

--- Comment #9 from s33_furt...@protonmail.com ---
Created attachment 143920
  --> https://bugs.kde.org/attachment.cgi?id=143920&action=edit
Image of the sources and the Kdenlive project timeline

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

[Spectacle] [Bug 445487] Feature: qrcode support in captured image

[bronko]

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

--- Comment #2 from bronko  ---
(In reply to Nate Graham from comment #1)
> What's the use case? Why would someone want to do this?

My use case was an assembly manuel containing lots of qrcodes, telling me to
scan them and watch the assembly video (there were no hyperlinks as text of
course).
So i fired up spectactle to see if it would recognize the qrcodes, it did not.
Thought it might be a useful addition so i suggested it.

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

[frameworks-kio] [Bug 426528] Changing upper/lowercase on renaming a folder on a CIFS mount triggers multiple bugs

[Alexander Ewering]

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

--- Comment #3 from Alexander Ewering  ---
(In reply to Nate Graham from comment #2)
> Reason #487,498 not to use manual mounts :)

If you know of a robust way to "properly" make a CIFS share available so that
it can be universally accessed, including by stuff like Apache, FreeFileSync
and other non-KIO-aware apps, I'm all ears

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

[plasmashell] [Bug 419225] Task Manager's Show in Activities Menu should be identical to KWin's equivalent menu accessed through the window decoration

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 Status|REPORTED|CONFIRMED
 Ever confirmed|0   |1

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

[plasmashell] [Bug 419225] Task Manager's Show in Activities Menu should be identical to KWin's equivalent menu accessed through the window decoration

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

  Component|Task Manager and Icons-Only |general
   |Task Manager|
Summary|Consistency: Show in|Task Manager's Show in
   |Activities Menu |Activities Menu should be
   ||identical to KWin's
   ||equivalent menu accessed
   ||through the window
   ||decoration
 Ever confirmed|1   |0
 Status|RESOLVED|REPORTED
 Resolution|DUPLICATE   |---
   Assignee|h...@kde.org|k...@davidedmundson.co.uk

--- Comment #9 from Nate Graham  ---
OK, re-opening. Ideally they would share code so that consistency could be
achieved truly automatically. That's hard though because one lives in KWin and
is a QMenu, and the other lives in Plasma and is a QML-based menu.

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

[kdeplasma-addons] [Bug 445643] Store path to current POTD image in in its config file to enable various useful purposes for other software

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

   Severity|normal  |wishlist
Product|plasmashell |kdeplasma-addons
 Ever confirmed|0   |1
   Assignee|notm...@gmail.com   |i...@guoyunhe.me
Summary|Checkbox to disable image   |Store path to current POTD
   |background in "Picture of   |image in in its config file
   |the Day" module |to enable various useful
   ||purposes for other software
 Status|REPORTED|CONFIRMED
   Target Milestone|1.0 |---
  Component|Desktop Containment |Picture of the Day

--- Comment #6 from Nate Graham  ---
Solution 1 seems like the best to me, but also exposing the path to the current
POTD wallpaper somewhere feels reasonable. Let's make this bug report about
that, since https://phabricator.kde.org/T13037 seems to have gotten stuck

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

[plasma-pa] [Bug 446011] Volume up / down animation sound cause audio to be distorted

[André Martins]

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

--- Comment #4 from André Martins  ---
(In reply to Nate Graham from comment #1)
> What do you mean by "Distorted"? Is it because the feedback sound gets
> played on top of the audio of whatever is also playing? Or does the audio of
> whatever's playing sound different on its own?

Please see both attachments. One is was a record of the internal audio
(Expected sound). The other was a record going through the speakers of
headphones (Distorted sound).

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

[plasma-pa] [Bug 446011] Volume up / down animation sound cause audio to be distorted

[André Martins]

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

--- Comment #3 from André Martins  ---
Created attachment 143919
  --> https://bugs.kde.org/attachment.cgi?id=143919&action=edit
speaker output

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

[plasma-pa] [Bug 446011] Volume up / down animation sound cause audio to be distorted

[André Martins]

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

--- Comment #2 from André Martins  ---
Created attachment 143918
  --> https://bugs.kde.org/attachment.cgi?id=143918&action=edit
system input sound

This is the system recorded output. The one I was expecting to hear.

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

[kdeplasma-addons] [Bug 446048] Glitchy font in plasma-widgets popup windows (list of updates, clipboard history) when scroll

[bugzilla_noreply]

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

bom...@gmail.com changed:

   What|Removed |Added

 CC||bom...@gmail.com

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

[ark] [Bug 446049] New: Ark crashed the plasmashell process while archiving (or ending archiving) a folder into 7zip default profile format

[pveax]

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

Bug ID: 446049
   Summary: Ark crashed the plasmashell process while archiving
(or ending archiving) a folder into 7zip default
profile format
   Product: ark
   Version: 21.11.80
  Platform: Manjaro
OS: Linux
Status: REPORTED
  Severity: major
  Priority: NOR
 Component: general
  Assignee: elvis.angelac...@kde.org
  Reporter: pv...@mailforspam.com
CC: aa...@kde.org, rthoms...@gmail.com
  Target Milestone: ---

IMPORTANT NOTES

1. It is the same issue as was reported in the
https://bugs.kde.org/show_bug.cgi?id=446006 ticked, but on newer (even
unreleased) git KDE app's version.

2. I select `ark`'s closest (newest possible) version to what I have in the
`*Version` list, but I was USING the newer (still absent in the list) version:
```
~/Desktop ❯ ark --version
ark 22.03.70
~/Desktop ❯ 
```
The GIT COMMIT HASH is `fe618843`.

SUMMARY

Ark crashed the plasmashell process when archiving (or ending to archive) a
folder into 7zip default profile format (LZMA2, level 5/9 or 6/10)

STEPS TO REPRODUCE

0. Download the
https://mirror.koddos.net/manjaro/unstable/core/x86_64/glibc-2.33-5-x86_64.pkg.tar.zst
file to Desktop.
1. Unpack it. You got another archive.
2. Unpack it into single folder.
3. Click on mouse's secondary btn on that Desktop folder.
4. Select `Compress` -> `Compress to...`
5. In the popped up archiving setting window I have `7z` format already
selected, probably I use default settings for all. Click OK.

Wait 10-15 seconds. Plasma panels disappeared and was restarted, core dump file
appears.

OBSERVED RESULT

`plasmashell` crash

EXPECTED RESULT

No any crash while Ark archiving things.

SOFTWARE/OS VERSIONS

```
Operating System: Manjaro Linux
KDE Plasma Version: 5.23.80
KDE Frameworks Version: 5.89.0
Qt Version: 5.15.2
Kernel Version: 5.15.4-1-MANJARO (64-bit)
Graphics Platform: X11

Processors: 4 × Intel® Core™ i5-8250U CPU @ 1.60GHz
Memory: 31.1 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics 620
```

ADDITIONAL INFORMATION

App versions possibly involved here:
```
~/Desktop ❯ plasmashell --version
plasmashell 5.23.80
```
`plasma-workspace` commit is `81bb5ae6a`
```
~/Desktop ❯ dolphin --version
dolphin 22.03.70
```
`dolphin` commit is `caa639fb4`

Severity chosen above crash, cause the process do not crash itself, but crash
even other process.

Backtrace with no debugging symbols :(

```
gdb /usr/bin/plasmashell
core.plasmashell.1000.d4580c22d52b48a3a96a4d87c5b2f1ae.975.163777288000 
...
[New LWP 1202]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
Core was generated by `/usr/bin/plasmashell'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x7f5c38364d22 in raise () from /usr/lib/libc.so.6
[Current thread is 1 (Thread 0x7f5c33aa0f40 (LWP 975))]
(gdb) bt
#0  0x7f5c38364d22 in raise () at /usr/lib/libc.so.6
#1  0x7f5c3a87346c in KCrash::defaultCrashHandler(int) () at
/usr/lib/libKF5Crash.so.5
#2  0x7f5c38364da0 in  () at /usr/lib/libc.so.6
#3  0x7f5c389ed029 in QObjectPrivate::maybeSignalConnected(unsigned int)
const () at /usr/lib/libQt5Core.so.5
#4  0x7f5c389fa360 in  () at /usr/lib/libQt5Core.so.5
#5  0x7f5c394ae901 in KJob::result(KJob*, KJob::QPrivateSignal) () at
/usr/lib/libKF5CoreAddons.so.5
#6  0x7f5c394b011c in KJob::finishJob(bool) () at
/usr/lib/libKF5CoreAddons.so.5
#7  0x7f5c389fa7cb in  () at /usr/lib/libQt5Core.so.5
#8  0x7f5bed58f027 in Kerfuffle::ReadOnlyArchiveInterface::finished(bool)
() at /usr/lib/libkerfuffle.so.22
#9  0x7f5c389fa7cb in  () at /usr/lib/libQt5Core.so.5
#10 0x7f5c3892c719 in QProcess::finished(int, QProcess::ExitStatus) () at
/usr/lib/libQt5Core.so.5
#11 0x7f5c38932226 in  () at /usr/lib/libQt5Core.so.5
#12 0x7f5c3893235e in  () at /usr/lib/libQt5Core.so.5
#13 0x7f5c389fa800 in  () at /usr/lib/libQt5Core.so.5
#14 0x7f5c389fdc90 in QSocketNotifier::activated(QSocketDescriptor,
QSocketNotifier::Type, QSocketNotifier::QPrivateSignal) () at
/usr/lib/libQt5Core.so.5
#15 0x7f5c389fe49d in QSocketNotifier::event(QEvent*) () at
/usr/lib/libQt5Core.so.5
#16 0x7f5c396c4d62 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /usr/lib/libQt5Widgets.so.5
#17 0x7f5c389c341a in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at /usr/lib/libQt5Core.so.5
#18 0x7f5c38a1cc5e in  () at /usr/lib/libQt5Core.so.5
#19 0x7f5c36c544dc in g_main_context_dispatch () at
/usr/lib/libglib-2.0.so.0
#20 0x7f5c36ca8799 in  () at /usr/lib/libglib-2.0.so.0
#21 0x7f5c36c51bc1 in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#22 0x7f5c38a1c046 in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#23 0x7f5c389c1d8c in
QEventLoop::exec(QFlags) () a

[kdeplasma-addons] [Bug 446048] Glitchy font in plasma-widgets popup windows (list of updates, clipboard history) when scroll

[bugzilla_noreply]

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

--- Comment #2 from bom...@gmail.com ---
Forgot to write. Reproducible on both X11 and wayland

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

[kdeplasma-addons] [Bug 446048] Glitchy font in plasma-widgets popup windows (list of updates, clipboard history) when scroll

[bugzilla_noreply]

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

--- Comment #1 from bom...@gmail.com ---
Created attachment 143917
  --> https://bugs.kde.org/attachment.cgi?id=143917&action=edit
screenshot

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

[kdeplasma-addons] [Bug 446048] New: Glitchy font in plasma-widgets popup windows (list of updates, clipboard history) when scroll

[bugzilla_noreply]

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

Bug ID: 446048
   Summary: Glitchy font in plasma-widgets popup windows (list of
updates, clipboard history) when scroll
   Product: kdeplasma-addons
   Version: 5.23.3
  Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: General
  Assignee: plasma-b...@kde.org
  Reporter: bom...@gmail.com
  Target Milestone: ---

Created attachment 143916
  --> https://bugs.kde.org/attachment.cgi?id=143916&action=edit
video

SUMMARY
Font become glithy if you scroll content. 


STEPS TO REPRODUCE
1. Open popup with list of updates by click on software update applet (or
clipboard history)
2. Scroll content 

OBSERVED RESULT
Font is glitchy on some scroll positions.

EXPECTED RESULT
Font is clear

SOFTWARE/OS VERSIONS
Windows: -
macOS: -
Linux/KDE Plasma: openSUSE Tumbleweed 20211120
(available in About System)
KDE Plasma Version: 5.23.3
KDE Frameworks Version: 5.88.0
Qt Version: 5.15.2

ADDITIONAL INFORMATION

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

[krunner] [Bug 446045] Does not activate when using currency symbols rather than names

[Kai Uwe Broulik]

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

Kai Uwe Broulik  changed:

   What|Removed |Added

 CC||k...@privat.broulik.de

--- Comment #1 from Kai Uwe Broulik  ---
12$ works through the currency runner whereas $12 is only done through the
qalculate runner.

I guess the heuristic of "number + suffix" in the unitsrunner doesn't apply for
all cases.

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

[systemsettings] [Bug 445884] When opening System Settings, the window opening animation is laggy on X11

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

   Severity|normal  |minor

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

[systemsettings] [Bug 445638] Black background when window is resized on X11 with QtQuick hardware rendering

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |---
   Severity|normal  |minor
Summary|Black background when   |Black background when
   |resize  |window is resized on X11
   ||with QtQuick hardware
   ||rendering
 Status|NEEDSINFO   |REPORTED

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

[plasmashell] [Bug 445901] Cannot remove favorites with touchscreen

[Nate Graham]

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

--- Comment #3 from Nate Graham  ---
Neither am I.

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

[kwin] [Bug 445905] Option to disable slide effect for activity switching

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

   Priority|NOR |LO
   Severity|minor   |wishlist
 Status|NEEDSINFO   |CONFIRMED
Product|plasmashell |kwin
  Component|Activity Switcher   |activities
   Assignee|ivan.cu...@kde.org  |kwin-bugs-n...@kde.org
Summary|While changing activities,  |Option to disable slide
   |wallpapers slide and there  |effect for activity
   |is no way to disable this   |switching
 Resolution|WAITINGFORINFO  |---
   Target Milestone|1.0 |---
 Ever confirmed|0   |1

--- Comment #3 from Nate Graham  ---
Thanks.

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

[dolphin] [Bug 445606] Dolphin ignores 'Skip previews for remote files above: no previews' and is extremely slow when browsing through a shared folder mounted with CIFS

[Nate Graham]

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

--- Comment #5 from Nate Graham  ---
We should investigate that separately. Should be fixable. Can you file a new
bug report for it?

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

[kwin] [Bug 445973] Wayland Window Cornered To left up corner

[Nate Graham]

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

--- Comment #3 from Nate Graham  ---
Thanks. Does the problem go away if you change the window placement mode to
something different, like "Centered?

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

[frameworks-plasma] [Bug 411462] Plasma dialogs (applet popups, OSDs, notifications) should not be movable, maximizable, or minimizable, or tilable

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

   Priority|NOR |VHI

--- Comment #14 from Nate Graham  ---
Raising priority due to number of duplicates.

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

[plasmashell] [Bug 445663] Kickoff is maximized if window placement is set to "Maximized"

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 Status|CONFIRMED   |RESOLVED

--- Comment #6 from Nate Graham  ---
Gross. I'll mark it as a duplicate of Bug 411462, then. It seems like there is
a way to work around this issue in the applet's own code, seeing as how it does
not affect all of them. But still. we should fix it in a generic way so such
(undiscovered?) workarounds are not needed.

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

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

[frameworks-plasma] [Bug 411462] Plasma dialogs (applet popups, OSDs, notifications) should not be movable, maximizable, or minimizable, or tilable

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 CC||poperi...@mailbox.org

--- Comment #13 from Nate Graham  ---
*** Bug 445663 has been marked as a duplicate of this bug. ***

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

[kmail2] [Bug 446047] New: DKIM Plugin shows different results for the same email

[bugzilla_noreply]

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

Bug ID: 446047
   Summary: DKIM Plugin shows different results for the same email
   Product: kmail2
   Version: unspecified
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: tho...@zell-mbc.com
  Target Milestone: ---

Created attachment 143915
  --> https://bugs.kde.org/attachment.cgi?id=143915&action=edit
Screenshots of DKIM messages

SUMMARY
***
I have enabled the DKIM plugin which produces some confusing output.
When highlighting a properly signed email KMail will display a message similar
to below in the KMail status bar:
DKIM: valid (signed by gmail.com)

When hovering with the mouse over this text a "Not signed" tool-tip will
appear?

Furthermore, when I select anther email, signed or unsigned, and return to the
previous one, the status bar will only show "signed by," without the actual
signing domain:
DKIM: valid (signed by)

>From there on the signing domain won't show again for this email, it might for
others but only once.


***


STEPS TO REPRODUCE
1. Select an email from a sender which is know to use DKIM signatures (gmail,
ebay, google.com, etc.)  
2. Check DKIM message in KMail status bar, signer domain may show
3. Select any other email
4. Return to previous one, signer domain is missing.

OBSERVED RESULT
Signer domain is showing only when an email is selected for the first time

EXPECTED RESULT
Signer domain is showing every time an email is selected


SOFTWARE/OS VERSIONS
Operating System: Arch Linux
KDE Plasma Version: 5.23.3
KDE Frameworks Version: 5.88.0
Qt Version: 5.15.2
Kernel Version: 5.15.4-arch1-1 (64-bit)
Graphics Platform: X11
KMail Version 5.18.3 (21.08.3)

ADDITIONAL INFORMATION

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

[plasmashell] [Bug 445554] Trying to move the Panel crashes the whole desktop

[bugzilla_noreply]

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

--- Comment #2 from lrdarkne...@yahoo.de ---
(In reply to Nate Graham from comment #1)
> Can you attach a backtrace of the crash? See
> https://community.kde.org/Guidelines_and_HOWTOs/Debugging/
> How_to_create_useful_crash_reports

I would like to provide a backtrace, but i am simply not able to generate one.
Since I am using Manjaro, there seem to be no pre-compiled Plasmashell binaries
available and I am not willing to compile KDE Plasmashell again from scratch
(nor would i know how, sorry).

When i execute "coredumpctl list" there is no recent plasma crash listed. Just
a bunch of older crashes with missing core files:
[laurenzb@laurenz-manjaro ~]$ coredumpctl list
TIME   PID  UID  GID SIG COREFILE EXE  
   SIZE
Sat 2021-04-10 15:25:02 CEST  1663 1000 1000 SIGABRT missing 
/usr/bin/kglobalaccel5n/a
Sat 2021-04-10 15:25:03 CEST  1726 1000 1000 SIGABRT missing 
/usr/lib/xdg-desktop-portal-kde   n/a
Sat 2021-04-10 15:25:34 CEST  1913 1000 1000 SIGABRT missing 
/usr/lib/kf5/klaunchern/a
Sat 2021-04-10 15:25:34 CEST  1898 1000 1000 SIGABRT missing 
/usr/bin/ksplashqml   n/a
Sat 2021-04-10 15:26:18 CEST  2299 1000 1000 SIGABRT missing  /usr/bin/dolphin 
n/a
Sat 2021-04-10 15:26:52 CEST  2397 1000 1000 SIGABRT missing 
/usr/bin/systemsettings5  n/a
Sat 2021-04-10 15:42:31 CEST  1963 1000 1000 SIGSEGV missing 
/usr/bin/plasmashell  n/a
Sat 2021-04-10 15:43:31 CEST  1809 1000 1000 SIGABRT missing 
/usr/bin/kwalletd5n/a
Sat 2021-04-10 15:43:31 CEST  2555 1000 1000 SIGABRT missing 
/usr/lib/baloorunner  n/a
Sat 2021-04-10 15:43:39 CEST  2205 1000 1000 SIGABRT missing 
/usr/bin/msm_kde_notifier n/a
Sat 2021-04-10 15:43:41 CEST  2035 1000 1000 SIGABRT missing 
/usr/lib/kdeconnectd  n/a
Sat 2021-04-10 15:43:42 CEST  1994 1000 1000 SIGABRT missing 
/usr/lib/kactivitymanagerdn/a
Sat 2021-04-10 15:43:43 CEST  1976 1000 1000 SIGABRT missing 
/usr/lib/org_kde_powerdevil   n/a
Sat 2021-04-10 15:43:43 CEST  9277 1000 1000 SIGABRT missing  /usr/bin/konsole 
n/a
Sat 2021-04-10 15:43:46 CEST  1936 1000 1000 SIGABRT missing  /usr/bin/kded5   
n/a
Sat 2021-04-10 15:43:47 CEST 11090 1000 1000 SIGABRT missing 
/usr/bin/systemsettings5  n/a
Sat 2021-04-10 15:43:48 CEST  2158 1000 1000 SIGABRT missing 
/usr/bin/pamac-tray-plasman/a
Sat 2021-04-10 15:43:50 CEST 11012 1000 1000 SIGABRT missing 
/usr/bin/plasmashell  n/a
Sat 2021-04-10 15:44:47 CEST 12489 1000 1000 SIGABRT missing 
/usr/lib/org_kde_powerdevil   n/a
Sat 2021-04-10 15:44:47 CEST 12490 1000 1000 SIGABRT missing  /usr/bin/kded5   
n/a
Sat 2021-04-10 15:44:47 CEST 11512 1000 1000 SIGABRT missing 
/usr/lib/org_kde_powerdevil   n/a

But the plasmashell process is definitely not running anymore, i've checked
that with the Plasma-Systemmonitor.

I've tried to attach to the running plasmashell using this command "gdb -pid
$(pidof plasmashell) -batch -ex "set logging file plasmashell.txt" -ex "set
logging on" -ex "continue" -ex "thread apply all backtrace" -ex "quit"", which
i got from here
https://community.kde.org/Plasma/Debugging#Attach_gdb_to_the_plasmashell_process

This unfortunately did not provide much, because GDB exited before i could
generate any backtrace:
The program is not being run.
[New Thread 0x7fcd256fb640 (LWP 2358)]
[Thread 0x7fcd25efc640 (LWP 2336) exited]
[Thread 0x7fcd256fb640 (LWP 2358) exited]
[New Thread 0x7fcd256fb640 (LWP 2377)]
[New Thread 0x7fcd25efc640 (LWP 2378)]
[New Thread 0x7fcca7dff640 (LWP 2379)]
[New Thread 0x7fcca75fe640 (LWP 2380)]
[New Thread 0x7fcca6dfd640 (LWP 2381)]
[New Thread 0x7fcca65fc640 (LWP 2382)]
[New Thread 0x7fcca5dfb640 (LWP 2383)]
[New Thread 0x7fcca55fa640 (LWP 2384)]
[New Thread 0x7fcca4df9640 (LWP 2385)]
[New Thread 0x7fcc9bfff640 (LWP 2386)]
[Thread 0x7fcc9bfff640 (LWP 2386) exited]
[Thread 0x7fcca4df9640 (LWP 2385) exited]
[Thread 0x7fcca5dfb640 (LWP 2383) exited]
[Thread 0x7fcca65fc640 (LWP 2382) exited]
[Thread 0x7fcca6dfd640 (LWP 2381) exited]
[Thread 0x7fcca75fe640 (LWP 2380) exited]
[Thread 0x7fcca7dff640 (LWP 2379) exited]
[Thread 0x7fcd256fb640 (LWP 2377) exited]
[Thread 0x7fcd266fd640 (LWP 1984) exited]
[Thread 0x7fcd26efe640 (LWP 1983) exited]
[Thread 0x7fcd40ff9640 (LWP 1982) exited]
[Thread 0x7fcd417fa640 (LWP 1981) exited]
[Thread 0x7fcd41ffb640 (LWP 1980) exited]
[Thread 0x7fcd427fc640 (LWP 1979) exited]
[Thread 0x7fcd42ffd640 (LWP 1978) exited]
[Thread 0x7fcd48db7640 (LWP 1976) exited]
[Thread 0x7fcd495b8640 (LWP 1975) exited]
[Thread 0x7fcd49db9640 (LWP 1974) exited]
[Thread 0x7fcd4b303640 (LWP 1973) exited]
[Thread 0x7fcd4bb04640 (LWP 1939) exited]
[Thread 0x7fcd43fff640 (LWP 1938) exited]
[Thread 0x7fcd64cf1640 (LWP 1734) exited]
[Thread 0x7fcca55fa640 (LWP 2384) exited]
[Thread 0x7fcd4c7be640 (L

[systemsettings] [Bug 445636] The buttons in the colour scheme previews pull their colour from the currently active scheme

[Nate Graham]

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

--- Comment #3 from Nate Graham  ---
Thanks. I can't reproduce the issue when I install that color scheme. Are you
sure you're using Plasma 5.23? What distro are you using?

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

[plasmashell] [Bug 445709] Rearranging apps in the task manager sometimes gets stuck on Wayland.

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

   Keywords||wayland
Summary|Rearranging apps in the |Rearranging apps in the
   |task manager is broken  |task manager sometimes gets
   ||stuck on Wayland.

--- Comment #3 from Nate Graham  ---
Thanks for the extra info.

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

[frameworks-kio] [Bug 445801] Doesn't honor the umask while saving screenshots

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 CC||kdelibs-b...@kde.org
Product|Spectacle   |frameworks-kio
  Component|General |general
   Assignee|m...@baloneygeek.com  |kio-bugs-n...@kde.org
Version|21.08.3 |unspecified

--- Comment #3 from Nate Graham  ---
Moving to KIO, then. What version of KIO or KDE frameworks do you have? I ask
because this was supposed to have been fixed with Bug 404777 in Frameworks
5.87. So are you using 5.87 or 5.88, or an older version?

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

[okular] [Bug 433003] PDF rendering on dual screen setup with different per-screen scaling appears broken

[bugzilla_noreply]

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

pfjarsc...@gmail.com changed:

   What|Removed |Added

 CC||pfjarsc...@gmail.com

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

[Discover] [Bug 445652] Plasma keeps asking for reboot since upgrading to Fedora 34

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|REPORTED|CONFIRMED

--- Comment #4 from Nate Graham  ---
Aha, that's helpful. Looks like the problem is that the
/var/lib/PackageKit/offline-update-action file didn't get cleaned up after the
last offline update transaction. So as a result Discover always thinks yo need
to reboot.

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

[valgrind] [Bug 445941] valgrind 3.18.1 crashes on RHEL 6.7 debuginfo Assertion 'in_rx' failed in libmagic.so

[Grzegorz Roszak]

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

Grzegorz Roszak  changed:

   What|Removed |Added

 CC||grzegorz.ros...@gmail.com

--- Comment #2 from Grzegorz Roszak  ---
(In reply to Paul Floyd from comment #1)
> Which compiler are you using?

(In reply to Paul Floyd from comment #1)
> Which compiler are you using?

I can confirm the same issue on RHEL6.8 (Santiago) with both code under test
and valgrind compiled with GCC 11.1.0.

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

[Discover] [Bug 445761] Discover offers me to remove code

[Nate Graham]

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

--- Comment #8 from Nate Graham  ---
OK, so let me see if I understand.

1. You manually installed "code-1.62.2-1636665099" from a file
2. You later manually installed "code-1.62.3-1637137194" from another file
3. Discover asked you if you wanted to remove "code"

Is that correct?

If so, this might be fixed by
https://invent.kde.org/plasma/discover/-/merge_requests/208. If you have the
ability to test merge requests (see
https://community.kde.org/Infrastructure/GitLab#Testing_someone_else.27s_Merge_Request),
could you try it out and see if it helps? Otherwise I'll need for you to post
the link to code-1.62.2-1636665099 somewhere so I can test.

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