[kdenlive] [Bug 432699] Effects list's filter field does not work for CJK characters

2022-05-08 Thread Eric Jiang
https://bugs.kde.org/show_bug.cgi?id=432699

Eric Jiang  changed:

   What|Removed |Added

 CC||erji...@alumni.iu.edu

--- Comment #3 from Eric Jiang  ---
Is there a way to run Kdenlive in a specific language, maybe with an
environment variable?  I tried using LANGUAGE=zh which seemed to make some
strings Chinese but most of the UI, including the effects list, was still in
English.

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

[bugs.kde.org] [Bug 453559] New: Cannot find kamera product/component

2022-05-08 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=453559

Bug ID: 453559
   Summary: Cannot find kamera product/component
   Product: bugs.kde.org
   Version: unspecified
  Platform: Other
OS: Other
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: product/component changes
  Assignee: sysad...@kde.org
  Reporter: 2wxsy5823...@opayq.com
CC: christo...@krop.fr
  Target Milestone: ---

SUMMARY

Previously, we can choose product "kio" and component "kamera" for kamera bugs,
but apparently kio is no longer available. I also checked the components of
"frameworks-kio" but "kamera" is not available.

For kamera bugs, which product/component combination should we choose?

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

[frameworks-knewstuff] [Bug 453338] Theme not installing

2022-05-08 Thread amixra
https://bugs.kde.org/show_bug.cgi?id=453338

--- Comment #8 from amixra  ---
(In reply to Alexander Lohnau from comment #7)
> That is weird, I have no other idea that running GDB and trying to find out
> where it crashed. Could you do that?

```
(gdb) run
Starting program: /usr/bin/sddmthemeinstaller -i
Downloads/ArchAbstract_Sddm.tar.gz
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[New Thread 0x73131640 (LWP 85071)]
[New Thread 0x725f1640 (LWP 85072)]
[New Thread 0x71df0640 (LWP 85073)]
[New Thread 0x715ef640 (LWP 85074)]
[Thread 0x73131640 (LWP 85071) exited]
[Thread 0x725f1640 (LWP 85072) exited]
[Thread 0x71df0640 (LWP 85073) exited]
[Thread 0x73706840 (LWP 85068) exited]
[Inferior 1 (process 85068) exited with code 0377]
(gdb) quit
```
I again checked `/usr/share/sddm/themes` it wasn't updated. I don't know
whether it was already supposed or not but i felt to update that directory it
will need root permissions and it doesn't asks me for password so i tried `sudo
sddmthemeinstaller -i /Downloads/ArchAbstract_Sddm.tar.gz`  and got following
output if that helps
```
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root'
Debug message from helper: Installing 
"/home/amit/Downloads/ArchAbstract_Sddm.tar.gz"  into  "/usr/share/sddm/themes"
Warning from helper: Postinstallation: uncompress the file
```
I rechecked /usr/share/sddm/themes/ and it was updated with that i tried
applying those changes using system settings got following
https://pasteboard.co/vIAy8TyueeXK.png
empty red popup at top
https://pasteboard.co/wgWHuLSkVpAI.png

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

[krita] [Bug 453409] Copy/Cut>Paste outputs empty layer if you do it while transforming

2022-05-08 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=453409

--- Comment #2 from acc4commissi...@gmail.com ---
Oddly this doesn't happen in krita stable plus builds. In git 90628dc, the
layer thumbnail appears temporarily empty, but the copy/cut>paste still works
and doesn't output empty layer.

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

[kid3] [Bug 451787] Edit chapters in MP4/AAC files

2022-05-08 Thread Lee
https://bugs.kde.org/show_bug.cgi?id=451787

--- Comment #10 from Lee  ---
(In reply to Urs Fleisch from comment #9)
> Thanks for the additional information. The thing with mp4v2 could be used
> with Kid3's Mp4v2Metadata plugin. Could you please provide some example
> files containing such chapter information?

i don't know how to create an example file other than using openaudible, and
all of these are copyrighted
i have asked if they can send me such a filealternatively you can use the
application to create your own if you have an audible account

or you can try to create such a file with
https://github.com/KrumpetPirate/AAXtoMP3/blob/master/AAXtoMP3 and tell it to
generate m4b files

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

[sweeper] [Bug 406644] Sweeper launch from Desktop

2022-05-08 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=406644

Bug Janitor Service  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|WAITINGFORINFO  |WORKSFORME

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

[kmymoney] [Bug 452935] I18N_ARGUMENT_MISSING in CSV import Columns screen

2022-05-08 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=452935

--- Comment #4 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 450600] plasma_session memory leak

2022-05-08 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=450600

Bug Janitor Service  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |WORKSFORME
 Status|NEEDSINFO   |RESOLVED

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

[skrooge] [Bug 452589] Skrooge 2.27.0 cannot import OFX anymore

2022-05-08 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=452589

--- 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.

[frameworks-kwayland] [Bug 453558] New: Floating (detached) Qt toolbar can't be dragged nor re-attached to window

2022-05-08 Thread Bernie Innocenti
https://bugs.kde.org/show_bug.cgi?id=453558

Bug ID: 453558
   Summary: Floating (detached) Qt toolbar can't be dragged nor
re-attached to window
   Product: frameworks-kwayland
   Version: 5.91.0
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: client
  Assignee: mgraess...@kde.org
  Reporter: ber...@codewiz.org
CC: kwin-bugs-n...@kde.org
  Target Milestone: ---

SUMMARY

I ran into this using Okular, but I believe the bug is not Okular specific.

In a Plasma Wayland session, it is possible to drag a Qt toolbar outside the
toolbar area, just like in X11. However, when the toolbar detaches and becomes
floating, it is no longer possible to drag it or re-attach it to the docking
area.

I found this workaround: change the toolbar orientation to left or right to
make dock again.

Moreover, the detached state is saved and, upon restart, the floating toolbar
is invisible (possibly a separate bug? There's a workaround for this too:
toggle the toolbar visibility in the Settings menu and the toolbar will
re-appear.

STEPS TO REPRODUCE
1. Open any document in Okular. I used a JPEG image.
2. Right-click on any toolbar to open the context menu
3. Uncheck "Lock Toolbar Positions"
4. Grab a toolbar and drag it outside the docking area
5. Release the toolbar and try grabbing it again 

OBSERVED RESULT
The toolbar can't be dragged any more!

EXPECTED RESULT
It should work just like in X11

SOFTWARE/OS VERSIONS
KDE Plasma Version: 5.24.4
KDE Frameworks Version: 5.91.0
Qt Version: 5.15.3-1.fc36

ADDITIONAL INFORMATION

This is Fedora 36 one week before the official release, but I don't think it
matters.
Not sure why Fedora 36 is releasing with KF5 5.91 instead of 5.93... THIS
should matter.

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

[kde] [Bug 453557] Black screen when waking up the computer in 4K resolution with KDE and an HDMI Edid emulator connected

2022-05-08 Thread Chema
https://bugs.kde.org/show_bug.cgi?id=453557

--- Comment #2 from Chema  ---
Sorry, I also forgot to comment that this happens indistinctly in both X11 and
Wayland, it doesn't matter which one you started, the same thing happens in
both.

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

[kde] [Bug 453557] Black screen when waking up the computer in 4K resolution with KDE and an HDMI Edid emulator connected

2022-05-08 Thread Chema
https://bugs.kde.org/show_bug.cgi?id=453557

--- Comment #1 from Chema  ---
Sorry, the link to the HDMI Edid emulator was pasted wrong. The correct link
is:

https://www.evanlak.com/products/hdmi-edid-emulator-4k-120hz

Or in Amazon:

https://www.amazon.com/EVanlak-Generrtion-Passthrough-Eliminated-Thunderbolt/dp/B07YMTMMH5?th=1

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

[kde] [Bug 453557] New: Black screen when waking up the computer in 4K resolution with KDE and an HDMI Edid emulator connected

2022-05-08 Thread Chema
https://bugs.kde.org/show_bug.cgi?id=453557

Bug ID: 453557
   Summary: Black screen when waking up the computer in 4K
resolution with KDE and an HDMI Edid emulator
connected
   Product: kde
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: rondo...@gmail.com
  Target Milestone: ---

SUMMARY
When the computer cable is connected to an HDMI Edid emulator and the screen
resolution is in 4K, when the computer sleeps from KDE and then wakes up, the
monitor does not receive HDMI video signal and only black screen is displayed.
When you switch sessions by pressing the Ctrl+Alt+F1 keys, the computer starts
sending the HDMI signal to the monitor and then you can see the screen
perfectly.

This problem does not occur on the Windows operating system nor does it occur
with the GNOME desktop environment (tested with Fedora and Manjaro). In GNOME
this works perfectly when the screen is in 4K resolution. It also does not
happen if the KDE resolution at the time of suspending the computer is set to
less than 4K resolution, but if it is 4K or higher, the problem I just
mentioned occurs.

It does not depend on the Linux kernel either, I have tried with versions 5.16,
5.17 and 5.18 and the same thing happens in all of them from KDE.

STEPS TO REPRODUCE
1. Have an HDMI Edid emulator connected to the computer (or a KVM switch) in
the HDMI input, and have the HDMI cable from the computer connected to the HDMI
Edid emulator --> (HDMI Edid emulator: https://www.evanlak.com/products
/hdmi-edid-emulator-4k-120hz).

2. Have the screen resolution in 4K mode (3840x2160).

3. Put the computer in sleep mode and wait a few seconds.

4. Wake up the computer. 

OBSERVED RESULT
When I wake up the computer, the screen is completely black, the monitor does
not receive an HDMI video signal. It doesn't react until you press (for
example) Ctrl+Alt+F1 to switch sessions. By doing so, the monitor begins to
receive the video signal and is already displayed correctly.

In KDE it works correctly with the HDMI Edid emulator connected if the screen
resolution is less than 4K, but from 4K resolution the problem that I mentioned
occurs that the screen stays black when waking up the computer.

I have tried several distros with GNOME (Fedora and Manjaro) and with this
desktop environment it works perfectly having the HDMI Edid emulator connected,
the computer can be suspended in 4K resolution and when it wakes up it shows
the screen correctly again. However, I have tried several distros with KDE
(Manjaro and KDE Neon) and in both the same thing happens, when suspending the
computer in 4K resolution with the HDMI Edid emulator connected, when waking it
up the screen is black until it is changed from session. I have also tried
several Linux kernels (5.16, 5.17 and 5.18) and the same thing happens in all
of them. It doesn't seem like a problem with the kernel, but with KDE, since as
I say in the GNOME distros it works perfectly.

In the Windows operating system it also works perfectly, if I suspend the
computer with the screen at 4K resolution, when I wake it up it is displayed
correctly.

EXPECTED RESULT
As it happens in the GNOME desktop environment, when you wake up the computer
it should correctly display the KDE screen and not get a black screen on the
monitor without receiving an HDMI signal.

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

ADDITIONAL INFORMATION
My computer is an AMD Ryzen 5 3550H with Radeon Vega Mobile GFX, the GPU is an
integrated AMD Radeon Vega 8 Graphics. Linux is using the video-linux driver
(Picasso [ATI Technologies Inc]).

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

[Discover] [Bug 453521] Discover installs wrong version of KWin script

2022-05-08 Thread Natalie Clarius
https://bugs.kde.org/show_bug.cgi?id=453521

--- Comment #2 from Natalie Clarius  ---
I did that the first view times (archiving or overwriting old versions) and it
reset the download counter to zero, making it look like the plugin has never
been downloaded before and can not be trusted, so I'd like to avoid that.

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

[Discover] [Bug 453548] Discover crashed when searching for updates in an XRDP session

2022-05-08 Thread Aleix Pol
https://bugs.kde.org/show_bug.cgi?id=453548

Aleix Pol  changed:

   What|Removed |Added

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

--- Comment #1 from Aleix Pol  ---


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

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

[Discover] [Bug 443745] Discover crashes in FlatpakBackend::findSource() when going to the Installed page

2022-05-08 Thread Aleix Pol
https://bugs.kde.org/show_bug.cgi?id=443745

--- Comment #46 from Aleix Pol  ---
*** Bug 453548 has been marked as a duplicate of this bug. ***

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

[Discover] [Bug 453521] Discover installs wrong version of KWin script

2022-05-08 Thread Aleix Pol
https://bugs.kde.org/show_bug.cgi?id=453521

Aleix Pol  changed:

   What|Removed |Added

 Status|REPORTED|CONFIRMED
 Ever confirmed|0   |1

--- Comment #1 from Aleix Pol  ---
I'll see what I can do. For now a solution would be to just offer the latest
stable version of the script.

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

[kio-extras] [Bug 453480] No image preview for .RW2 files (image/x-panasonic-rw2)

2022-05-08 Thread Andrew
https://bugs.kde.org/show_bug.cgi?id=453480

Andrew  changed:

   What|Removed |Added

 CC||liston_...@hotmail.com

--- Comment #3 from Andrew  ---
Same issue, but for me NEF files from Nikon doesn't generate thumbnails. In the
past used to work

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

[kscreenlocker] [Bug 453556] New: Left handed mouse reset to right handed after screen unlock

2022-05-08 Thread Reuben
https://bugs.kde.org/show_bug.cgi?id=453556

Bug ID: 453556
   Summary: Left handed mouse reset to right handed after screen
unlock
   Product: kscreenlocker
   Version: 5.24.4
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: k...@flavor8.com
CC: bhus...@gmail.com
  Target Milestone: ---

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


STEPS TO REPRODUCE
1. Set mouse (trackball) to left handed
2. Lock screen; unlock screen

OBSERVED RESULT

Mouse is right handed, despite "left" still being checked in kcontrol

EXPECTED RESULT

Mouse buttons should be stable

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

ADDITIONAL INFORMATION

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

[lattedock] [Bug 438427] Crash while adding a widget.

2022-05-08 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=438427

--- Comment #5 from m...@vishalsubramanyam.ml ---
Created attachment 148667
  --> https://bugs.kde.org/attachment.cgi?id=148667=edit
New crash information added by DrKonqi

latte-dock (0.10.76) using Qt 5.15.3

- What I was doing when the application crashed:
Whenever I try to add a widget, it crashes. I made two different builds of the
git cloned source code. The release build crashed far more often than the debug
build. The crash happens in the library related to Qt5 Quick.

- Custom settings of the application:
I am running mcOS Catalina Latte theme that is available as the first search
result on Google.

-- Backtrace (Reduced):
#4  QSGTexture::setFiltering (this=this@entry=0x0, filter=QSGTexture::Linear)
at /usr/include/x86_64-linux-gnu/qt5/QtCore/qglobal.h:1143
#5  0x7f9d8afcbe8f in QSGOpaqueTextureMaterialShader::updateState
(this=0x7f9d491d2270, state=..., newEffect=0x7f9d4971a5a0, oldEffect=0x0) at
scenegraph/util/qsgtexturematerial.h:64
#6  0x7f9d8afaf3d9 in QSGBatchRenderer::Renderer::renderMergedBatch
(this=0x7f9d496a9950, batch=0x7f9d496f7070) at
../../include/QtQuick/5.15.3/QtQuick/private/../../../../../src/quick/scenegraph/coreapi/qsgrenderer_p.h:197
#7  0x7f9d8afb4f8d in QSGBatchRenderer::Renderer::renderBatches
(this=this@entry=0x7f9d496a9950) at
scenegraph/coreapi/qsgbatchrenderer.cpp:4025
#8  0x7f9d8afb567a in QSGBatchRenderer::Renderer::render (this=) at scenegraph/coreapi/qsgbatchrenderer.cpp:4337

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

[lattedock] [Bug 438427] Crash while adding a widget.

2022-05-08 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=438427

m...@vishalsubramanyam.ml changed:

   What|Removed |Added

 CC||m...@vishalsubramanyam.ml

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

[kdeconnect] [Bug 453555] New: No permission available to access all files

2022-05-08 Thread Peterson Silva
https://bugs.kde.org/show_bug.cgi?id=453555

Bug ID: 453555
   Summary: No permission available to access all files
   Product: kdeconnect
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: android-application
  Assignee: albertv...@gmail.com
  Reporter: peterson@gmail.com
  Target Milestone: ---

In version 1.19.1 of the Android app, in a Galaxy M62 running Android 12, I
cannot expose the entire phone's filesystem to my desktop PC.

This is because when I am asked to choose the folder to expose, I cannot choose
the root folder. Indeed there are many folders I cannot choose (such as
Downloads).

I looked through the app's permissions (I had allowed everything) and I found I
was only able to give the app permission to access media files, not all files.
This must be the issue.

If I go to VLC's permission, yes, I have given it permission to mess with media
files only - BUT it still allows me to give it access to the entire filesystem
if I so wanted. KDE Connect (the Android app) IMO must include such an option
because without it the "browse phone's files" feature is severely limited; you
can't access all folders and the ones you do you have to manually add in the
plugin's settings, so it's extra annoying.

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

[korganizer] [Bug 364968] show event location in agenda view if there is enough free space

2022-05-08 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=364968

gjditchfi...@acm.org changed:

   What|Removed |Added

 CC||estel...@elstel.org

--- Comment #3 from gjditchfi...@acm.org ---
*** Bug 207810 has been marked as a duplicate of this bug. ***

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

[korganizer] [Bug 207810] allow displaying of location in the overview

2022-05-08 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=207810

gjditchfi...@acm.org changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
 Resolution|--- |DUPLICATE
 CC||gjditchfi...@acm.org

--- Comment #1 from gjditchfi...@acm.org ---


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

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

[korganizer] [Bug 149207] edit event location uses addressbook lookup

2022-05-08 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=149207

gjditchfi...@acm.org changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 CC||gjditchfi...@acm.org
 Status|REPORTED|RESOLVED

--- Comment #1 from gjditchfi...@acm.org ---


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

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

[korganizer] [Bug 82768] Ability to insert location of a event from a contact.

2022-05-08 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=82768

gjditchfi...@acm.org changed:

   What|Removed |Added

 CC||pal...@comcast.net

--- Comment #2 from gjditchfi...@acm.org ---
*** Bug 149207 has been marked as a duplicate of this bug. ***

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

[lattedock] [Bug 451894] Hidden dock with no compositor still leaves a line

2022-05-08 Thread smow
https://bugs.kde.org/show_bug.cgi?id=451894

smow  changed:

   What|Removed |Added

 CC||smowten...@protonmail.com

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

[okular] [Bug 453421] Okular corrupts file while saving the archive

2022-05-08 Thread Albert Astals Cid
https://bugs.kde.org/show_bug.cgi?id=453421

--- Comment #7 from Albert Astals Cid  ---
Cannot reproduce.

Which distribution are you using? (shouldn't matter but it's always good to
know)

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

[okular] [Bug 453540] Okular crashed after using the yellow marker

2022-05-08 Thread Albert Astals Cid
https://bugs.kde.org/show_bug.cgi?id=453540

Albert Astals Cid  changed:

   What|Removed |Added

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

--- Comment #1 from Albert Astals Cid  ---
Can you run the application from konsole (or other terminal) and attach the
error you get there when this crash happens?

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

[plasmashell] [Bug 453554] New: turning one monitor off kills the panel configuration of the second monitor

2022-05-08 Thread Kai Krakow
https://bugs.kde.org/show_bug.cgi?id=453554

Bug ID: 453554
   Summary: turning one monitor off kills the panel configuration
of the second monitor
   Product: plasmashell
   Version: 5.24.5
  Platform: Gentoo Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Multi-screen support
  Assignee: plasma-b...@kde.org
  Reporter: k...@kaishome.de
CC: aleix...@kde.org, notm...@gmail.com
  Target Milestone: 1.0

SUMMARY

Monitor setup (xrandr dump at the end):

Left main monitor: 4k displayport
* top plasma panel with activity switcher, global menu, date and time, systray
* bottom plasma panel with launch menu, icon window list, desktop switcher

Right small monitor: full HD HDMI connected via DP
* top plasma panel with window list, time, bluetooth applet, volume applet

TV: 4k, HDMI
* clone of left monitor (for couch gaming)

Graphics:
NVIDIA GTX 1660 Ti 6GB with Xorg

Whenever I turn off my main monitor, all its panels move over to the right
monitor. The same happens if the TV turns off or goes to sleep. Sometimes
(probably before 5.24.5), I can see two overlapping panels at the top (my main
top panel plus the simple side monitor panel) but since 5.24.5 the panel moves
consistently, replacing the configuration of the right monitor.

This was fine most of the time before 5.24.5 and consistently fine before
5.24.4: The panels were restored when I turned the main monitor back on, only
messing up if plasma crashed or shut down before turning the monitor back on.

But now it consistently throws away the plasma configuration of the right
monitor: After turning the main monitor back on, I'm left with an empty default
desktop on the right monitor, no custom background image, no panels, but all
open windows moved to this monitor.

Looking at the output of `qdbus org.kde.plasmashell /PlasmaShell
org.kde.PlasmaShell.dumpCurrentLayoutJS` I can see that each incident adds
another panel configuration in `layout.panels` but I have no way of getting it
back.

`plasmashellrc` has these lines:
```
[ScreenConnectors]
0=DP-4
1=HDMI-0
2=DP-1
```

It also had `2=:0.0` followed by `3=DP-1` but I removed that out of
desperation. It wasn't present in older backups of my system. It didn't change
anything about the behavior, tho.

STEPS TO REPRODUCE
1. Use a setup like I described above
2. Turn the displayport monitor off which seems to disconnect it from the
system (my DP monitor and HDMI TV do that when turning them off, my HDMI
monitor doesn't do it and seemingly stays connected/detected)
3. Observe the panels move over to the second screen
4. Turn first monitor back on

OBSERVED RESULT
After step 4, the panels move back to the monitor just turned back on but step
2/3 seem to have displaced the panel/desktop configuration of the second
monitor, and after step 4, plasma will replace it with an empty default
configuration.

EXPECTED RESULT
The panels should be properly restored to their respective original monitors. I
guess it's fine and wanted that disconnecting the primary monitor would move
panels over to remaining monitors, e.g. for laptop usage. But when I restore
the original monitor connection for which I configured the panels, that
configuration should be restored, or at least I should have an easy way to
choose which panel configuration I want to restore. But in my case, it's gone
for good although it still seems to live in the qdbus layout dump (and it's
piling up there because I need to recreate the layout multiple times per day).

I think Plasma should store and apply layouts like this:

Store a layout of each monitor, also store a flag if this was made on the
primary monitor. If the current monitor is the primary monitor, use the panel
layout of the original primary monitor. Otherwise fall back to the layout
originally defined for this monitor. Do not remove but swap layouts when the
primary layout flag is involved. Move the primary layout flag only when the
layout is actively edited.

SOFTWARE/OS VERSIONS
Operating System: Gentoo Linux
KDE Plasma Version: 5.24.5
KDE Frameworks Version: 5.93.0
Qt Version: 5.15.3
Kernel Version: 5.15.37-gentoo (64-bit)
Graphics Platform: X11
Processors: 20 × 12th Gen Intel® Core™ i7-12700K
Memory: 31.1 GiB of RAM
Graphics Processor: NVIDIA GeForce GTX 1660 Ti/PCIe/SSE2

ADDITIONAL INFORMATION

This behavior was triggered very rarely before 5.24.4, easily triggered with
5.24.4, and consistently triggers with 5.24.5. Given that history of behavior,
it's probably some race condition and is not intentional.

My clone monitor layout may play a role in this because I found in older
versions some months back, that sometimes plasma panels would be defined for my
TV instead of my main monitor (when I disabled the TV, all panels were gone).

I had situations when the panels actually moved to a "third" monitor right of
my 

[frameworks-knewstuff] [Bug 447884] Show version numbers for available files

2022-05-08 Thread Natalie Clarius
https://bugs.kde.org/show_bug.cgi?id=447884

--- Comment #7 from Natalie Clarius  ---
But then why does Discover have the version numbers, don't they use the same
backend?  
Or does Discover not actually have the version numbers associated with the
files and just downloads a random one and that's the reason for the linked bug?

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

[kdenlive] [Bug 453420] 4K Video Proxy is smooth on Clip Monitor but super Choppy on Project Monitor

2022-05-08 Thread Vaibhav Dhotre
https://bugs.kde.org/show_bug.cgi?id=453420

--- Comment #3 from Vaibhav Dhotre  ---
(In reply to emohr from comment #1)
> Please make following test: switch "Track Composition" from "High Quality"
> to "none"
> (https://docs.kdenlive.org/de/cutting_and_assembling/editing.
> html?highlight=high%20quality#timeline-toolbar). 
> 
> Does the playback fps rise?

But do I need to switch from None to High Quality every time before render?
I mean, will this action affect my final output if I forget to switch it back
to High Quality?

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

[kdenlive] [Bug 453420] 4K Video Proxy is smooth on Clip Monitor but super Choppy on Project Monitor

2022-05-08 Thread Vaibhav Dhotre
https://bugs.kde.org/show_bug.cgi?id=453420

--- Comment #2 from Vaibhav Dhotre  ---
(In reply to emohr from comment #1)
> Please make following test: switch "Track Composition" from "High Quality"
> to "none"
> (https://docs.kdenlive.org/de/cutting_and_assembling/editing.
> html?highlight=high%20quality#timeline-toolbar). 
> 
> Does the playback fps rise?

Superb. It works really well.

PLEASE MAKE THIS SETTING AS DEFAULT for preview in the next update.

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

[plasmashell] [Bug 453544] Plasma crash when login in system

2022-05-08 Thread Harald Sitter
https://bugs.kde.org/show_bug.cgi?id=453544

Harald Sitter  changed:

   What|Removed |Added

Summary|Plasa crash when login in   |Plasma crash when login in
   |system  |system

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

[kde] [Bug 453551] Dolphin not able to browse Nikon Z6 files

2022-05-08 Thread Harald Sitter
https://bugs.kde.org/show_bug.cgi?id=453551

Harald Sitter  changed:

   What|Removed |Added

 CC||sit...@kde.org
Product|kio-extras  |kde
Version|21.12.2 |unspecified
  Component|MTP |general

--- Comment #1 from Harald Sitter  ---
Moving bug to kde. This has nothing to do with mtp or kio-extras but kamera,
which interestingly has no product :shrug:

FWIW chances are your libgphoto is out of date, I've seen the Z6 mentioned in
the changelog.

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

[valgrind] [Bug 452802] Handle lld 9+ split RW PT_LOAD segments correctly

2022-05-08 Thread Paul Floyd
https://bugs.kde.org/show_bug.cgi?id=452802

--- Comment #14 from Paul Floyd  ---
On Fedora 34, git head and "./configure CC=clang CXX=clang++
LDFLAGS=-fuse-ld=lld" with thispatch the results look fairly similar to what I
get on FreeBSD.

I didn't get all of the problems that I had with FreeBSD .got.plt errors on
Helgrind and DRD, but I think that is because my Fedora 34 was all or mostly
built with GCC. That means that libc, libpthread etc don't have the split RW
PT_LOADS. On the other hand my FreeBSD 13 is all or mostly built with clang and
the system libs will have them split.

The situation might be different on ChromeOS and Android.

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

[kwin] [Bug 448917] NVIDIA/Wayland - Breeze Theme Has No Blur And Random Shapes Appear

2022-05-08 Thread Erik Kurzinger
https://bugs.kde.org/show_bug.cgi?id=448917

Erik Kurzinger  changed:

   What|Removed |Added

 CC||ekurzin...@nvidia.com

--- Comment #7 from Erik Kurzinger  ---
This should be fixed by
https://invent.kde.org/plasma/kwin/-/merge_requests/2358

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

[plasmashell] [Bug 453476] Plasmashell crashes on Wayland when unlocking session

2022-05-08 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=453476

i...@free.fr changed:

   What|Removed |Added

 CC||i...@free.fr

--- Comment #4 from i...@free.fr ---
Hi, I have the same problem.

Plasmashell 5.24.5 on gentoo. I Think, but not sure, that It happens since
5.24. 
If I try to re-launch with plasmashell --replace, I got the "The Wayland
connection broke. Did the Wayland compositor die?" message.
Kwin_wayland is still running fine when this happens, and others applications
are still running. I can launch some new applications  if I have a opened
konsole too.

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

[kscreensaver] [Bug 316348] kscreenlocker_greet constantly consumes around 20% CPU time

2022-05-08 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=316348

logeco...@gmail.com changed:

   What|Removed |Added

 CC||logeco...@gmail.com

--- Comment #60 from logeco...@gmail.com ---
 This solved it for me on KDE neon inside Hyper-V:

# Add to: /etc/security/pam_env.conf
# Avoid high cpu usage with sddm-greeter
# https://github.com/sddm/sddm/issues/323
QT_QUICK_BACKEND DEFAULT=software

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

[kwin] [Bug 451201] Plasma Wayland doesn't seem to recognize my GTX 1060. Think its the reason why it seems so glitchy.

2022-05-08 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=451201

--- Comment #8 from techxga...@outlook.com ---
Forgot to clarify:
* Firefox immediately crashes. 
* KRunner stopped showing up.  It would show up for less than a minute, then
stop responding.  Won't launch again after that.
* Latte dock won't load.

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

[kdemultimedia] [Bug 453553] Dolphin not caching thumbnails

2022-05-08 Thread David Karlsson
https://bugs.kde.org/show_bug.cgi?id=453553

David Karlsson  changed:

   What|Removed |Added

 CC||davika...@gmail.com

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

[kdemultimedia] [Bug 453553] New: Dolphin not caching thumbnails

2022-05-08 Thread David Karlsson
https://bugs.kde.org/show_bug.cgi?id=453553

Bug ID: 453553
   Summary: Dolphin not caching thumbnails
   Product: kdemultimedia
   Version: 22.04.0
  Platform: Archlinux Packages
OS: Microsoft Windows
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: ffmpegthumbs
  Assignee: unassigned-b...@kde.org
  Reporter: davika...@gmail.com
  Target Milestone: ---

SUMMARY
 I am using Dolphin under WSLg (with Windows 11) and have a filesystem mounted
with drvfs (9p).
And while Dolphin is generating the video thumbnails as it should, none of them
are cached under ~/.cache/thumbnails.
Caching is working as normal on the root filesystem.
(I'm assuming this is handled by ffmpegthumbs, but it could be Dolphin too).

Fully updated Arch, with KDE Plasma 5.24.5 and KDE Gear 22.04 running under
WSLg.

STEPS TO REPRODUCE
1.  Mount filesystem with drvfs.
2. Browse filesystem with Dolphin.
3. Find video files and wait for thumbnails to generate.
4. Look for cached thumbnails under ~/.cache/thumbnails/.

OBSERVED RESULT
~/.cache/thumbnails/ is empty except for folders like normal, large, x-large.
(Assuming it was emptied before browsing).

EXPECTED RESULT
There should be cached thumbnails in the folders.

SOFTWARE/OS VERSIONS
Windows:  Windows 11 with WSL/WSLg
Linux/KDE Plasma:  Arch Linux
KDE Plasma Version:  5.24.5
KDE Frameworks Version:  5.93.0
Qt Version: idk, the latest one

ADDITIONAL INFORMATION

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

[kactivitymanagerd] [Bug 453550] kactivitymanagerd flood logs with "Linking" entries

2022-05-08 Thread Ivan Čukić
https://bugs.kde.org/show_bug.cgi?id=453550

--- Comment #1 from Ivan Čukić  ---
Can you post the plasma logs so that we can tell what tries to add the
favourite so often?

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

[Discover] [Bug 433149] Please, depend on `xdg-desktop-portal-gtk` on debian package to make gtk themes work

2022-05-08 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=433149

Nate Graham  changed:

   What|Removed |Added

 Resolution|FIXED   |DOWNSTREAM

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

[frameworks-knewstuff] [Bug 447884] Show version numbers for available files

2022-05-08 Thread Alexander Lohnau
https://bugs.kde.org/show_bug.cgi?id=447884

--- Comment #6 from Alexander Lohnau  ---
>Is there anything speaking against doing it like in Discover (provided 
>https://bugs.kde.org/show_bug.cgi?id=453521 is fixed) and just installing the 
>most recent version directly?

Though this has the same issue of us not having the version information
available. I discussed with leinir what we would need to do for that and it
involves changes in the KDE Store servers. Unfortunately I am not familiar with
the infrastructure and haven't touched any php in years.

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

[filelight] [Bug 453225] Crash on launch, SIGSEGV

2022-05-08 Thread Bart Ribbers
https://bugs.kde.org/show_bug.cgi?id=453225

--- Comment #2 from Bart Ribbers  ---
I'd try but git master doesn't compile on Musl currently due to using S_BLKSIZE
(which seems to be glibc and uclibc only):

/home/bart/Documents/Git/alpine/aports/community/filelight/src/filelight-da8221a96c72f31eac095fa6d8f43b104298bbf8/src/posixWalker.cpp:
In member function 'void POSIXWalker::next()':
/home/bart/Documents/Git/alpine/aports/community/filelight/src/filelight-da8221a96c72f31eac095fa6d8f43b104298bbf8/src/posixWalker.cpp:102:44:
error: 'S_BLKSIZE' was not declared in this scope
  102 | m_entry.size = statbuf.st_blocks * S_BLKSIZE;
  |^

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

[kate] [Bug 453493] Freezes while loading php files from nfs mounted volume

2022-05-08 Thread Christoph Cullmann
https://bugs.kde.org/show_bug.cgi?id=453493

--- Comment #3 from Christoph Cullmann  ---
Ok, given NFS is a fragile thingy, any kernel update can have interesting
effects, at least that is my experience from work.

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

[kate] [Bug 453493] Freezes while loading php files from nfs mounted volume

2022-05-08 Thread Mark Stanton
https://bugs.kde.org/show_bug.cgi?id=453493

Mark Stanton  changed:

   What|Removed |Added

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

--- Comment #2 from Mark Stanton  ---
Hi @Christoph,

I agree, it seemed highly unlikely.  But I did check with various files, and
checked those files with other editors (my working fallback was "Text Editor"
from the context menu, looks Gnome-ish), and the problem was very specific.

However, since yesterday, these very specific instances do not cause the
problem.
What's changed?  My weekly update from Fedora repos. There were a whole load of
updates, including the kernel, so I don't know what, if anything made the
difference.

However, tl:dr is, I can no longer reproduce this problem.  I'll close it.

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

[dolphin] [Bug 453552] New: When Firefox tries to open a folder ("Show in folder") when there is an active dolphin tab, firefox will open a new dolphin tab but it wont pop-up

2022-05-08 Thread GJoe
https://bugs.kde.org/show_bug.cgi?id=453552

Bug ID: 453552
   Summary: When Firefox tries to open a folder ("Show in folder")
when there is an active dolphin tab, firefox will open
a new dolphin tab but it wont pop-up
   Product: dolphin
   Version: 21.12.3
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: retador...@gmail.com
CC: kfm-de...@kde.org
  Target Milestone: ---

SUMMARY
When Firefox tries to open a folder ("Show in folder") when there is an active
dolphin tab, Firefox will open a new dolphin tab but it wont pop-up and the
user won't  be aware.

STEPS TO REPRODUCE
1. Open a folder with dolphin (assuming this is the default file manager)
2. Open Firefox and go to "Downloads" tab
3. Try to open the contain folder for whatever file was downloaded

OBSERVED RESULT
The folder will open but the user won't be aware of that, if the user already
has open the folder where the file is located, dolphin only will highlight the
desire file. 

EXPECTED RESULT
Dolphin will pop-up with the desire file highlighted  

SOFTWARE/OS VERSIONS

Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 5.24.4
KDE Frameworks Version: 5.90.0
Qt Version: 5.15.3

ADDITIONAL INFORMATION
Graphics platform: Wayland
Dolphin Option activated: Open new folders in tabs

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

[Powerdevil] [Bug 392798] Power button actions should be handled from lock screen

2022-05-08 Thread Kamil Dudka
https://bugs.kde.org/show_bug.cgi?id=392798

--- Comment #21 from Kamil Dudka  ---
After upgrade to plasma 5.24.4 I can see "Sleep", "Hibernate", and "Switch
User" buttons on my lock screen.  The first two hunks of attachment #127083 are
still needed to keep the HW power button functional while the screen is locked.

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

[frameworks-knewstuff] [Bug 447884] Show version numbers for available files

2022-05-08 Thread Natalie Clarius
https://bugs.kde.org/show_bug.cgi?id=447884

--- Comment #5 from Natalie Clarius  ---
Is there anything speaking against doing it like in Discover (provided
https://bugs.kde.org/show_bug.cgi?id=453521 is fixed) and just installing the
most recent version directly? Showing old versions only leads to confusion and
normally there is no good reason for a user to use one of them, and if they do
they can still get it from the webstore.

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

[valgrind] [Bug 452802] Handle lld 9+ split RW PT_LOAD segments correctly

2022-05-08 Thread Paul Floyd
https://bugs.kde.org/show_bug.cgi?id=452802

--- Comment #13 from Paul Floyd  ---
On FreeBSD 13 amd64, OK with both clang and gcc.
On Linux Fedora 34 amd64 also OK.

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

[dolphin] [Bug 279614] The Dolphin shell panel (opened by F4) does not source .bashrc when opened by session restore

2022-05-08 Thread soredake
https://bugs.kde.org/show_bug.cgi?id=279614

soredake  changed:

   What|Removed |Added

 CC||ndrzj1...@relay.firefox.com

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

[Discover] [Bug 453236] When uninstalling an application, ask whether to delete the data

2022-05-08 Thread soredake
https://bugs.kde.org/show_bug.cgi?id=453236

soredake  changed:

   What|Removed |Added

 CC||ndrzj1...@relay.firefox.com

--- Comment #3 from soredake  ---
*** Bug 434181 has been marked as a duplicate of this bug. ***

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

[Discover] [Bug 434181] Ask to delete user data stored in ~/.var/app when removing flatpak app

2022-05-08 Thread soredake
https://bugs.kde.org/show_bug.cgi?id=434181

soredake  changed:

   What|Removed |Added

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

--- Comment #4 from soredake  ---


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

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

[Discover] [Bug 433149] Please, depend on `xdg-desktop-portal-gtk` on debian package to make gtk themes work

2022-05-08 Thread soredake
https://bugs.kde.org/show_bug.cgi?id=433149

soredake  changed:

   What|Removed |Added

URL||https://bazaar.launchpad.ne
   ||t/~kubuntu-dev/ubuntu-seeds
   ||/kubuntu.jammy/revision/154
   ||1
 Resolution|--- |FIXED
 Status|CONFIRMED   |RESOLVED

--- Comment #5 from soredake  ---
xdg-desktop-portal-gtk is now preinstalled in kubuntu.

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

[frameworks-kded] [Bug 453280] kded5 leaks X-Window connections: Maximum number of clients reached

2022-05-08 Thread Phil Hord
https://bugs.kde.org/show_bug.cgi?id=453280

--- Comment #3 from Phil Hord  ---
Interesting that it seemed to leak 2 connections at 10 minute intervals.  Last
night it leaked 4 connections at 10 minute intervals. Again, it only happened
when the screen was locked.

3 Sat 07 May 2022 05:19:48 PM PDT
4 Sat 07 May 2022 05:19:55 PM PDT
8 Sat 07 May 2022 07:28:39 PM PDT
12 Sat 07 May 2022 07:38:47 PM PDT
16 Sat 07 May 2022 07:48:58 PM PDT
20 Sat 07 May 2022 07:59:04 PM PDT
23 Sat 07 May 2022 08:09:12 PM PDT
24 Sat 07 May 2022 08:09:20 PM PDT
28 Sat 07 May 2022 08:19:23 PM PDT
32 Sat 07 May 2022 08:35:37 PM PDT
34 Sat 07 May 2022 08:45:44 PM PDT
36 Sat 07 May 2022 08:45:52 PM PDT
38 Sat 07 May 2022 08:56:00 PM PDT
40 Sat 07 May 2022 08:56:08 PM PDT
42 Sat 07 May 2022 09:06:10 PM PDT
44 Sat 07 May 2022 09:06:18 PM PDT
46 Sat 07 May 2022 09:16:20 PM PDT
48 Sat 07 May 2022 09:16:28 PM PDT
52 Sat 07 May 2022 09:26:39 PM PDT
54 Sat 07 May 2022 09:36:44 PM PDT
56 Sat 07 May 2022 09:36:52 PM PDT
60 Sat 07 May 2022 09:46:59 PM PDT
61 Sat 07 May 2022 09:47:26 PM PDT
65 Sat 07 May 2022 09:47:45 PM PDT
69 Sat 07 May 2022 09:57:55 PM PDT
73 Sat 07 May 2022 10:08:01 PM PDT
77 Sat 07 May 2022 10:18:13 PM PDT
79 Sat 07 May 2022 10:28:16 PM PDT
81 Sat 07 May 2022 10:28:25 PM PDT
84 Sat 07 May 2022 10:38:26 PM PDT
85 Sat 07 May 2022 10:38:36 PM PDT
89 Sat 07 May 2022 10:48:38 PM PDT
93 Sat 07 May 2022 10:58:47 PM PDT
97 Sat 07 May 2022 11:09:02 PM PDT
101 Sat 07 May 2022 11:19:07 PM PDT
105 Sat 07 May 2022 11:29:18 PM PDT
109 Sat 07 May 2022 11:39:27 PM PDT
113 Sat 07 May 2022 11:49:35 PM PDT
117 Sat 07 May 2022 11:59:49 PM PDT
121 Sun 08 May 2022 12:09:55 AM PDT
125 Sun 08 May 2022 12:20:05 AM PDT
127 Sun 08 May 2022 12:30:10 AM PDT
129 Sun 08 May 2022 12:30:21 AM PDT
133 Sun 08 May 2022 12:40:24 AM PDT
137 Sun 08 May 2022 12:50:34 AM PDT
140 Sun 08 May 2022 01:00:40 AM PDT
141 Sun 08 May 2022 01:00:52 AM PDT
145 Sun 08 May 2022 01:10:54 AM PDT
149 Sun 08 May 2022 01:21:03 AM PDT
151 Sun 08 May 2022 01:31:07 AM PDT
153 Sun 08 May 2022 01:31:19 AM PDT
155 Sun 08 May 2022 01:41:18 AM PDT
157 Sun 08 May 2022 01:41:30 AM PDT
161 Sun 08 May 2022 01:51:36 AM PDT
164 Sun 08 May 2022 02:01:38 AM PDT
165 Sun 08 May 2022 02:01:50 AM PDT
168 Sun 08 May 2022 02:11:48 AM PDT
169 Sun 08 May 2022 02:12:01 AM PDT
173 Sun 08 May 2022 02:22:06 AM PDT
177 Sun 08 May 2022 02:32:16 AM PDT
180 Sun 08 May 2022 02:42:20 AM PDT
181 Sun 08 May 2022 02:42:33 AM PDT
185 Sun 08 May 2022 02:52:30 AM PDT
189 Sun 08 May 2022 03:02:48 AM PDT
192 Sun 08 May 2022 03:12:49 AM PDT

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

[kio-extras] [Bug 453551] New: Dolphin not able to browse Nikon Z6 files

2022-05-08 Thread Germano Massullo
https://bugs.kde.org/show_bug.cgi?id=453551

Bug ID: 453551
   Summary: Dolphin not able to browse Nikon Z6 files
   Product: kio-extras
   Version: 21.12.2
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: MTP
  Assignee: unassigned-b...@kde.org
  Reporter: germano.massu...@gmail.com
CC: elvis.angelac...@kde.org
  Target Milestone: ---

Created attachment 148666
  --> https://bugs.kde.org/attachment.cgi?id=148666=edit
dolphin screenshot

Qdolphin is not able to browse files of Nikon Z6. See attached screenshot.
Please tell me what is the proper way to retrieve debuginfos since
kdebugsettings is not straightforward to use at all.
Thx
kio-extras 21.12.2
plasma-desktop 5.24.4
Qt 5.15.2

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

[lattedock] [Bug 451894] Hidden dock with no compositor still leaves a line

2022-05-08 Thread Kamil
https://bugs.kde.org/show_bug.cgi?id=451894

Kamil  changed:

   What|Removed |Added

 Resolution|NOT A BUG   |---
 Ever confirmed|0   |1
 Status|RESOLVED|REOPENED

--- Comment #2 from Kamil  ---
(In reply to Michail Vourlakos from comment #1)
> only thing to avoid this is to enable Behavior(advanced) -> Activate KWin
> edge after hiding

That setting does have any effect on this issue.
The line is still there no matter if KWin edge is enabled or disabled.

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

[plasmashell] [Bug 453476] Plasmashell crashes on Wayland when unlocking session

2022-05-08 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=453476

--- Comment #3 from nicod...@protonmail.com ---
(In reply to David Edmundson from comment #2)

Hi, I probably reported the bug at the wrong plasma product/component but this
is new with plasma 5.24.5.
I can also reproduce the bug when connecting/disconnecting 2-3 times the
external display.

plasmashell and kded5 are not crashing but both get terminated. kwin_wayland
still working.
I cannot restart plasmashell nor kded5 and I get this message:
"The Wayland connection broke. Did the Wayland compositor die?"

I don't know what program is causing this issue. I would need some help to find
the source of this bug.
I'm using and Intel GPU.

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

[kactivitymanagerd] [Bug 453550] New: kactivitymanagerd flood logs with "Linking" entries

2022-05-08 Thread Fabio Coatti
https://bugs.kde.org/show_bug.cgi?id=453550

Bug ID: 453550
   Summary: kactivitymanagerd flood logs with "Linking" entries
   Product: kactivitymanagerd
   Version: 5.24.5
  Platform: Gentoo Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: ivan.cu...@kde.org
  Reporter: fabio.coa...@gmail.com
CC: plasma-b...@kde.org
  Target Milestone: ---

SUMMARY
***
the issue is that kactivitymanagerd fills logs (systemd logs in my case) with
entries like this:

org.kde.kactivities.resources: Linking 
"file:///usr/share/kservices5/kcm_kscreen.desktop"  to  ":any"  from 
"org.kde.plasma.favorites.applications"

***
All the entries are the same: the line is repeated many times per second.
I tried to delete kactivitymanagerd database, search for kcm_kscreen entries
anywhere in my home dir, including .config, .cache and .local and remove any
occurence: no changes.
Interestingly, my favorites menu has no kscreen icon or entry.

running kactivitymanagerd on the foreground creates a log like this one:

org.kde.kactivities.activities: Starting the KDE Activity Manager daemon
QDateTime(2022-05-07 19:39:52.172 CEST Qt::LocalTime)
org.kde.kactivities.activities: Config timer connecting...
org.kde.kactivities.application: Plugin Name is  "org.kde.ActivityManager.SLC"
"/usr/lib64/qt5/plugins/kactivitymanagerd/1/kactivitymanagerd_plugin_slc.so"
org.kde.kactivities.application: Plugin Name is 
"org.kde.ActivityManager.ResourceScoring"
"/usr/lib64/qt5/plugins/kactivitymanagerd/1/kactivitymanagerd_plugin_sqlite.so"
org.kde.kactivities.application: Plugin Name is 
"org.kde.ActivityManager.ActivityTemplates"
"/usr/lib64/qt5/plugins/kactivitymanagerd/1/kactivitymanagerd_plugin_activitytemplates.so"
org.kde.kactivities.application: Plugin Name is 
"org.kde.ActivityManager.VirtualDesktopSwitch"
"/usr/lib64/qt5/plugins/kactivitymanagerd/1/kactivitymanagerd_plugin_virtualdesktopswitch.so"
org.kde.kactivities.application: Plugin Name is 
"org.kde.ActivityManager.GlobalShortcuts"
"/usr/lib64/qt5/plugins/kactivitymanagerd/1/kactivitymanagerd_plugin_globalshortcuts.so"
org.kde.kactivities.application: Plugin Name is 
"org.kde.ActivityManager.EventSpy"
"/usr/lib64/qt5/plugins/kactivitymanagerd/1/kactivitymanagerd_plugin_eventspy.so"
org.kde.kactivities.application: Plugin Name is 
"org.kde.ActivityManager.GtkEventSpy"
"/usr/lib64/qt5/plugins/kactivitymanagerd/1/kactivitymanagerd_plugin_gtk_eventspy.so"
org.kde.kactivities.application: Plugin Name is 
"org.kde.ActivityManager.RunApplication"
"/usr/lib64/qt5/plugins/kactivitymanagerd/1/kactivitymanagerd_plugin_runapplication.so"
org.kde.kactivities.application: Plugin Name is 
"org.kde.ActivityManager.ActivityRunner"
"/usr/lib64/qt5/plugins/kactivitymanagerd/1/kactivitymanagerd_plugin_activityrunner.so"
org.kde.kactivities.application: Found 8 enabled plugins:
org.kde.kactivities.application: [   OK   ] loaded:  
"org.kde.ActivityManager.SLC"
org.kde.kactivities.application: Setting the name of  0x5734816cb260  to 
"org.kde.ActivityManager.Resources.Scoring"
org.kde.kactivities.resources: Marking the test backup as working...
org.kde.kactivities.resources: Creating the backup of the current database...
org.kde.kactivities.resources: KActivities: Database connection: 
"kactivities_db_resources_139456787798080_readwrite"
query_only:  QVariant(qlonglong, 0)
journal_mode:QVariant(QString, "wal")
wal_autocheckpoint:  QVariant(qlonglong, 100)
synchronous: QVariant(qlonglong, 1)
org.kde.kactivities.resources: Database opened successfully
org.kde.kactivities.application: [   OK   ] loaded:  
"org.kde.ActivityManager.ResourceScoring"
org.kde.kactivities.application: Setting the name of  0x57348170baa0  to 
"org.kde.ActivityManager.ActivityTemplates"
org.kde.kactivities.application: [   OK   ] loaded:  
"org.kde.ActivityManager.ActivityTemplates"
org.kde.kactivities.application: [   OK   ] loaded:  
"org.kde.ActivityManager.GlobalShortcuts"
org.kde.kactivities.application: [   OK   ] loaded:  
"org.kde.ActivityManager.EventSpy"
org.kde.kactivities.application: [   OK   ] loaded:  
"org.kde.ActivityManager.GtkEventSpy"
org.kde.kactivities.application: Setting the name of  0x57348172e7a0  to 
"org.kde.ActivityManager.RunApplication"
org.kde.kactivities.application: [   OK   ] loaded:  
"org.kde.ActivityManager.RunApplication"
org.kde.kactivities.application: Setting the name of  0x573481737ce0  to 
"org.kde.ActivityManager.ActivityRunner"
org.kde.kactivities.application: [   OK   ] loaded:  
"org.kde.ActivityManager.ActivityRunner"
org.kde.kactivities.resources: Linking 
"file:///usr/share/kservices5/kcm_kscreen.desktop"  to  ":any"  from 
"org.kde.plasma.favorites.applications"
org.kde.kactivities.resources: Linking 
"file:///usr/share/kservices5/kcm_kscreen.desktop"  to  ":any"  from 

[plasma-systemmonitor] [Bug 451790] System Monitor Sensor breaks WeatherWidget-2 from the KDE store on KDE Framework 5.92

2022-05-08 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=451790

maycne.sona...@posteo.net changed:

   What|Removed |Added

 CC||maycne.sona...@posteo.net

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

[plasmashell] [Bug 383192] [feature request] - support changing screen for a window through the taskmanager

2022-05-08 Thread Nuno Costa
https://bugs.kde.org/show_bug.cgi?id=383192

Nuno Costa  changed:

   What|Removed |Added

 CC||sv...@nunocosta.dev

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

[plasmashell] [Bug 453476] Plasmashell crashes on Wayland when unlocking session

2022-05-08 Thread David Edmundson
https://bugs.kde.org/show_bug.cgi?id=453476

David Edmundson  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
 CC||k...@davidedmundson.co.uk
 Resolution|--- |NOT A BUG

--- Comment #2 from David Edmundson  ---
>Thread 1 "plasmashell" received signal SIGINT, Interrupt.

SIGINT?

It's not a crash, some third party process  is terminating plasmashell.

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

[plasmashell] [Bug 453546] KDE crash when login to wayland for the first time after upgrade

2022-05-08 Thread David Edmundson
https://bugs.kde.org/show_bug.cgi?id=453546

David Edmundson  changed:

   What|Removed |Added

   Keywords||wayland

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

[systemsettings] [Bug 453547] System Settings crashed after opening KDE Connect and Configuring the Run Commands plugin

2022-05-08 Thread Antonio Rojas
https://bugs.kde.org/show_bug.cgi?id=453547

Antonio Rojas  changed:

   What|Removed |Added

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

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


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

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

[kdeconnect] [Bug 453305] KDE Connect Settings closed unexpectedly when using "Execute command" function in android app

2022-05-08 Thread Antonio Rojas
https://bugs.kde.org/show_bug.cgi?id=453305

Antonio Rojas  changed:

   What|Removed |Added

 CC||nikitasan...@gmail.com

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

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

[dolphin] [Bug 453549] File previews broken, local drives are being affected by remote limit.

2022-05-08 Thread Antonio Rojas
https://bugs.kde.org/show_bug.cgi?id=453549

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 451408 ***

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

[kio-extras] [Bug 451408] File preview on some locally-mounted drives (NTFS, NFS, SMB) inappropriately use remote preview settings

2022-05-08 Thread Antonio Rojas
https://bugs.kde.org/show_bug.cgi?id=451408

Antonio Rojas  changed:

   What|Removed |Added

 CC||D-22v1nqdhv7dfv7x0asxptn355
   ||fvvydhmhm41g...@maildrop.cc

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

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

[dolphin] [Bug 453549] New: File previews broken, local drives are being affected by remote limit.

2022-05-08 Thread Anon
https://bugs.kde.org/show_bug.cgi?id=453549

Bug ID: 453549
   Summary: File previews broken, local drives are being affected
by remote limit.
   Product: dolphin
   Version: 22.04.0
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: d-22v1nqdhv7dfv7x0asxptn355fvvydhmhm41g...@maildrop.cc
CC: kfm-de...@kde.org
  Target Milestone: ---

SUMMARY
Partitions from local drives (HDD, SSD) are being affected by the remote file
preview limit which by default means all previews are disabled.

I originally had them mounted to /run/media/username/mountname which is also
used for removable drives by Artix/KDE so I mounted them to the home folder
thinking this might be the problem however this did not solve it.

They're both NTFS drives. They're both automatically mounted on startup via
fstab.

Current workaround involves setting the limit very high however this isn't
ideal as this affects true remote drives.

80% sure this started with version 22.04.0, I usually update the system every
week.

STEPS TO REPRODUCE
1. Unknown.

OBSERVED RESULT
File previews for local drives are being affected by remote limit.

EXPECTED RESULT
File previews for local drives should not be affected by remote limit.

SOFTWARE/OS VERSIONS
KDE Plasma Version: 5.24.5
KDE Frameworks Version: 5.93.0
Qt Version: 5.15.3

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

[Discover] [Bug 453548] New: Discover crashed when searching for updates in an XRDP session

2022-05-08 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=453548

Bug ID: 453548
   Summary: Discover crashed when searching for updates in an XRDP
session
   Product: Discover
   Version: 5.24.4
  Platform: Ubuntu Packages
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: discover
  Assignee: lei...@leinir.dk
  Reporter: wodenc...@gmail.com
CC: aleix...@kde.org
  Target Milestone: ---

Application: plasma-discover (5.24.4)

Qt Version: 5.15.3
Frameworks Version: 5.92.0
Operating System: Linux 5.15.0-27-generic x86_64
Windowing System: X11
Distribution: Ubuntu 22.04 LTS
DrKonqi: 5.24.4 [KCrashBackend]

-- Information about the crash:
- What I was doing when the application crashed:
I was connected to the desktop session running XRDP, via KRDC client.
I opened up Discover, and it said it was fetching updates. I clicked around a
bit in the GUI, as it seemed no updates were coming, and it crashed. I've seen
it do this before, seemingly misbehave over RDP.

The crash can be reproduced sometimes.

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

[KCrash Handler]
#4  FlatpakBackend::findSource (origin=..., installation=0x7fdbec005880,
this=0x5628526adac0) at
./libdiscover/backends/FlatpakBackend/FlatpakBackend.cpp:114
#5  FlatpakBackend::getAppForInstalledRef (this=0x5628526adac0,
installation=0x7fdbec005880, ref=0x7fdbe431dd90, freshResource=0x7ffeb3b953e7)
at ./libdiscover/backends/FlatpakBackend/FlatpakBackend.cpp:357
#6  0x7fdc046d325e in operator() (__closure=0x7fdbbc601430) at
./libdiscover/backends/FlatpakBackend/FlatpakBackend.cpp:1296
#7  QtPrivate::FunctorCall, QtPrivate::List<>, void,
FlatpakBackend::search(const
AbstractResourcesBackend::Filters&) >::call
(arg=, f=...) at
/usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:146
#8  QtPrivate::Functor::,
0>::call, void> (arg=, f=...) at
/usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:256
#9  QtPrivate::QFunctorSlotObject::, 0,
QtPrivate::List<>, void>::impl(int, QtPrivate::QSlotObjectBase *, QObject *,
void **, bool *) (which=, this_=0x7fdbbc601420, r=, a=, ret=) at
/usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:443
#10 0x7fdc7406a783 in QtPrivate::QSlotObjectBase::call (a=0x7ffeb3b954c0,
r=0x5628526adac0, this=0x7fdbbc601420) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#11 doActivate (sender=0x7fdbbd3fd520, signal_index=4,
argv=0x7ffeb3b954c0) at kernel/qobject.cpp:3886
#12 0x7fdc74063a97 in QMetaObject::activate (sender=,
m=, local_signal_index=, argv=) at
kernel/qobject.cpp:3946
#13 0x7fdc73e500f5 in QFutureWatcherBase::event (this=,
event=0x7fdbe4697130) at thread/qfuturewatcher.cpp:334
#14 0x7fdc751d1713 in QApplicationPrivate::notify_helper (this=, receiver=0x7fdbbd3fd520, e=0x7fdbe4697130) at
kernel/qapplication.cpp:3637
#15 0x7fdc74032e2a in QCoreApplication::notifyInternal2
(receiver=0x7fdbbd3fd520, event=0x7fdbe4697130) at
kernel/qcoreapplication.cpp:1064
#16 0x7fdc74035f17 in QCoreApplicationPrivate::sendPostedEvents
(receiver=0x0, event_type=0, data=0x562851e02480) at
kernel/qcoreapplication.cpp:1821
#17 0x7fdc7408ca57 in postEventSourceDispatch (s=0x562851ecfc80) at
kernel/qeventdispatcher_glib.cpp:277
#18 0x7fdc72929d1b in g_main_dispatch (context=0x7fdc68005010) at
../../../glib/gmain.c:3417
#19 g_main_context_dispatch (context=0x7fdc68005010) at
../../../glib/gmain.c:4135
#20 0x7fdc7297e6f8 in g_main_context_iterate.constprop.0
(context=context@entry=0x7fdc68005010, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at ../../../glib/gmain.c:4211
#21 0x7fdc729273c3 in g_main_context_iteration (context=0x7fdc68005010,
may_block=1) at ../../../glib/gmain.c:4276
#22 0x7fdc7408c0a8 in QEventDispatcherGlib::processEvents
(this=0x562851ed5a10, flags=...) at kernel/qeventdispatcher_glib.cpp:423
#23 0x7fdc7403174b in QEventLoop::exec (this=this@entry=0x7ffeb3b958a0,
flags=..., flags@entry=...) at
../../include/QtCore/../../src/corelib/global/qflags.h:69
#24 0x7fdc74039ce4 in QCoreApplication::exec () at
../../include/QtCore/../../src/corelib/global/qflags.h:121
#25 0x7fdc7440ee10 in QGuiApplication::exec () at
kernel/qguiapplication.cpp:1867
#26 0x7fdc751d1689 in QApplication::exec () at kernel/qapplication.cpp:2829
#27 0x562851bdb638 in main (argc=, argv=) at
./discover/main.cpp:217
[Inferior 1 (process 870014) detached]

Possible duplicates by query: bug 453440, bug 452999, bug 452469, bug 450949,
bug 450401.

Reported using DrKonqi

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

[systemsettings] [Bug 453547] New: System Settings crashed after opening KDE Connect and Configuring the Run Commands plugin

2022-05-08 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=453547

Bug ID: 453547
   Summary: System Settings crashed after opening KDE Connect and
Configuring the Run Commands plugin
   Product: systemsettings
   Version: 5.24.5
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: nikitasan...@gmail.com
  Target Milestone: ---

Application: systemsettings (5.24.5)

Qt Version: 5.15.3
Frameworks Version: 5.93.0
Operating System: Linux 5.13.0-40-generic x86_64
Windowing System: X11
Distribution: KDE neon User - 5.24
DrKonqi: 5.24.5 [KCrashBackend]

-- Information about the crash:
- What I was doing when the application crashed:
1. Open KDE Connect
2. Clicked "Configure" on plugin "Run commands"

The crash can be reproduced every time.

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

[New LWP 27367]
[New LWP 27368]
[New LWP 27369]
[New LWP 27370]
[New LWP 27371]
[New LWP 27372]
[New LWP 27373]
[New LWP 27374]
[New LWP 27375]
[New LWP 27376]
[New LWP 27377]
[New LWP 27378]
[New LWP 27379]
[New LWP 27380]
[New LWP 27381]
[New LWP 27382]
[New LWP 27388]
[New LWP 27436]
[New LWP 27440]
[New LWP 27443]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
0x7f6030dc49cf in __GI___poll (fds=0x7ffef5e336f8, nfds=1, timeout=1000) at
../sysdeps/unix/sysv/linux/poll.c:29
__preamble__
[Current thread is 1 (Thread 0x7f602c4ed9c0 (LWP 27364))]

Thread 21 (Thread 0x7f5fb5bf1700 (LWP 27443)):
#0  futex_wait_cancelable (private=, expected=0,
futex_word=0x5614b8758784) at ../sysdeps/nptl/futex-internal.h:183
#1  __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x5614b8758730,
cond=0x5614b8758758) at pthread_cond_wait.c:508
#2  __pthread_cond_wait (cond=0x5614b8758758, mutex=0x5614b8758730) at
pthread_cond_wait.c:638
#3  0x7f602263a5eb in ?? () from
/usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
#4  0x7f602263a1eb in ?? () from
/usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
#5  0x7f602f7cc609 in start_thread (arg=) at
pthread_create.c:477
#6  0x7f6030dd1163 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 20 (Thread 0x7f5fb680a700 (LWP 27440)):
#0  futex_wait_cancelable (private=, expected=0,
futex_word=0x5614b81d4f50) at ../sysdeps/nptl/futex-internal.h:183
#1  __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x5614b81d4f00,
cond=0x5614b81d4f28) at pthread_cond_wait.c:508
#2  __pthread_cond_wait (cond=0x5614b81d4f28, mutex=0x5614b81d4f00) at
pthread_cond_wait.c:638
#3  0x7f602263a5eb in ?? () from
/usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
#4  0x7f602263a1eb in ?? () from
/usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
#5  0x7f602f7cc609 in start_thread (arg=) at
pthread_create.c:477
#6  0x7f6030dd1163 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 19 (Thread 0x7f5fb7c0c700 (LWP 27436)):
#0  futex_wait_cancelable (private=, expected=0,
futex_word=0x5614b7ce58d0) at ../sysdeps/nptl/futex-internal.h:183
#1  __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x5614b7ce5880,
cond=0x5614b7ce58a8) at pthread_cond_wait.c:508
#2  __pthread_cond_wait (cond=0x5614b7ce58a8, mutex=0x5614b7ce5880) at
pthread_cond_wait.c:638
#3  0x7f602263a5eb in ?? () from
/usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
#4  0x7f602263a1eb in ?? () from
/usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
#5  0x7f602f7cc609 in start_thread (arg=) at
pthread_create.c:477
#6  0x7f6030dd1163 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 18 (Thread 0x7f5feeffd700 (LWP 27388)):
#0  0x7ffef5f12aed in clock_gettime ()
#1  0x7f6030d8f0e5 in __GI___clock_gettime (clock_id=clock_id@entry=1,
tp=tp@entry=0x7f5feeffc930) at ../sysdeps/unix/sysv/linux/clock_gettime.c:38
#2  0x7f6031396f25 in qt_clock_gettime (ts=0x7f5feeffc930, clock=1) at
kernel/qelapsedtimer_unix.cpp:175
#3  do_gettime (frac=, sec=) at
kernel/qelapsedtimer_unix.cpp:166
#4  qt_gettime () at kernel/qelapsedtimer_unix.cpp:175
#5  0x7f60313957bd in QTimerInfoList::updateCurrentTime
(this=this@entry=0x7f5fb8005130) at kernel/qtimerinfo_unix.cpp:91
#6  0x7f6031395d99 in QTimerInfoList::timerWait (this=0x7f5fb8005130,
tm=...) at kernel/qtimerinfo_unix.cpp:388
#7  0x7f60313973b6 in timerSourcePrepareHelper (timeout=0x7f5feeffc9f4,
src=) at kernel/qeventdispatcher_glib.cpp:162
#8  timerSourcePrepare (source=, timeout=0x7f5feeffc9f4) at
kernel/qeventdispatcher_glib.cpp:166
#9  0x7f602ee0e8ef in g_main_context_prepare () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#10 0x7f602ee0f29b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#11 0x7f602ee0f4a3 in g_main_context_iteration () from

[dolphin] [Bug 411349] Dolphin 100% CPU core usage

2022-05-08 Thread Emanuele Spirito
https://bugs.kde.org/show_bug.cgi?id=411349

--- Comment #20 from Emanuele Spirito  ---
> The most important information though is to find a reliable way to reproduce
> the symptoms that a developer could reproduce then.
> Until we don’t a way to reproduce or pinpoint the origin of the issue, we
> are clueless. 

I know, I was trying to explain in the most complete way the issue so maybe any
expert reading could find a clue to the solution I cannot see. 

> The recommended path to give actionable intel here, would be a trace using
> gdb or https://github.com/KDAB/hotspot. Those technics require debugging
> symbols. It might be out of your skill.

I had a look to that link but I think you are right, this is quite hard for me. 

> It still helps to update bugs to inform devs which bugs are still
> effectively hurting users and which ones are more common.
> So thanks for the effort anyway.

You are welcome, I'll stay tuned so if I can find the way to reproduce the bug
I'll tell you.

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

[kwin] [Bug 432286] transparency+blur glitching with obscured animated windows underneath

2022-05-08 Thread S. Christian Collins
https://bugs.kde.org/show_bug.cgi?id=432286

--- Comment #6 from S. Christian Collins  ---
Created attachment 148665
  --> https://bugs.kde.org/attachment.cgi?id=148665=edit
the bug with Yakuake

With Yakuake (blur+transparency enabled), this bug can also be triggered
without an animated window (see attached video):
1. Open Firefox (fullscreen).
2. Open KCalc and position it behind where Yakuake will open.
3. Open Yakuake and move mouse around the screen.

RESULT: the blur flickers and glitches where the KCalk window is.

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

[plasmashell] [Bug 453546] New: KDE crash when login to wayland for the first time after upgrade

2022-05-08 Thread Reuben
https://bugs.kde.org/show_bug.cgi?id=453546

Bug ID: 453546
   Summary: KDE crash when login to wayland for the first time
after upgrade
   Product: plasmashell
   Version: 5.24.4
  Platform: Ubuntu Packages
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: k...@flavor8.com
CC: k...@davidedmundson.co.uk
  Target Milestone: 1.0

Application: plasmashell (5.24.4)

Qt Version: 5.15.3
Frameworks Version: 5.92.0
Operating System: Linux 5.15.0-27-generic x86_64
Windowing System: Wayland
Distribution: Ubuntu 22.04 LTS
DrKonqi: 5.24.4 [KCrashBackend]

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

Upgraded to 22.04
Opened a wayland session to see if it was working better than it had before
Hard crash, cannot do anything

The crash can be reproduced every time.

-- Backtrace:
Application: Plasma (plasmashell), signal: Aborted

[KCrash Handler]
#4  __pthread_kill_implementation (no_tid=0, signo=6, threadid=140247690111424)
at ./nptl/pthread_kill.c:44
#5  __pthread_kill_internal (signo=6, threadid=140247690111424) at
./nptl/pthread_kill.c:78
#6  __GI___pthread_kill (threadid=140247690111424, signo=signo@entry=6) at
./nptl/pthread_kill.c:89
#7  0x7f8df9f74476 in __GI_raise (sig=sig@entry=6) at
../sysdeps/posix/raise.c:26
#8  0x7f8df9f5a7f3 in __GI_abort () at ./stdlib/abort.c:79
#9  0x7f8dfa416ba3 in  () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#10 0x7f8df85f33e4 in  () at /lib/x86_64-linux-gnu/libQt5WaylandClient.so.5
#11 0x7f8df85f411a in QtWaylandClient::QWaylandDisplay::flushRequests() ()
at /lib/x86_64-linux-gnu/libQt5WaylandClient.so.5
#12 0x7f8dfa6777b8 in  () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#13 0x7f8dfa69913b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib/x86_64-linux-gnu/libQt5Core.so.5
#14 0x7f8dfa63e74b in
QEventLoop::exec(QFlags) () at
/lib/x86_64-linux-gnu/libQt5Core.so.5
#15 0x7f8ddd43507f in qt_plugin_instance () at
/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kscreen/KSC_KWayland.so
#16 0x7f8dfa635a1f in  () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#17 0x7f8ddeaeab2f in
KScreen::BackendManager::loadBackendPlugin(QPluginLoader*, QString const&,
QMap const&) () at /lib/x86_64-linux-gnu/libKF5Screen.so.7
#18 0x7f8ddeaefd8e in KScreen::BackendManager::loadBackendInProcess(QString
const&) () at /lib/x86_64-linux-gnu/libKF5Screen.so.7
#19 0x7f8ddeaf03e3 in  () at /lib/x86_64-linux-gnu/libKF5Screen.so.7
#20 0x7f8ddeaf7ce6 in KScreen::GetConfigOperation::start() () at
/lib/x86_64-linux-gnu/libKF5Screen.so.7
#21 0x7f8dfa66d40e in QObject::event(QEvent*) () at
/lib/x86_64-linux-gnu/libQt5Core.so.5
#22 0x7f8dfb336713 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#23 0x7f8dfa63fe2a in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at /lib/x86_64-linux-gnu/libQt5Core.so.5
#24 0x7f8dfa642f17 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#25 0x7f8dfa699a57 in  () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#26 0x7f8df8a1bd1b in g_main_context_dispatch () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#27 0x7f8df8a706f8 in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#28 0x7f8df8a193c3 in g_main_context_iteration () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#29 0x7f8dfa6990a8 in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib/x86_64-linux-gnu/libQt5Core.so.5
#30 0x7f8dfa63e74b in
QEventLoop::exec(QFlags) () at
/lib/x86_64-linux-gnu/libQt5Core.so.5
#31 0x7f8dfa646ce4 in QCoreApplication::exec() () at
/lib/x86_64-linux-gnu/libQt5Core.so.5
#32 0x5621c007cdce in  ()
#33 0x7f8df9f5bd90 in __libc_start_call_main
(main=main@entry=0x5621c007bf70, argc=argc@entry=1,
argv=argv@entry=0x7ffc1cabb9e8) at ../sysdeps/nptl/libc_start_call_main.h:58
#34 0x7f8df9f5be40 in __libc_start_main_impl (main=0x5621c007bf70, argc=1,
argv=0x7ffc1cabb9e8, init=, fini=,
rtld_fini=, stack_end=0x7ffc1cabb9d8) at ../csu/libc-start.c:392
#35 0x5621c007cef5 in  ()
[Inferior 1 (process 1706) detached]

Possible duplicates by query: bug 453544, bug 453125, bug 451976, bug 451124,
bug 451114.

Reported using DrKonqi

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

[plasmashell] [Bug 453263] [Wayland] Minimizing the last opened window makes Plasma hang

2022-05-08 Thread Corentin Fleury
https://bugs.kde.org/show_bug.cgi?id=453263

--- Comment #4 from Corentin Fleury  ---
Created attachment 148664
  --> https://bugs.kde.org/attachment.cgi?id=148664=edit
Hotspot record

I do get a little CPU spike. Here is the hotspot record.

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

[dolphin] [Bug 453500] Metadata for audio files on remote drives not shown in tool tip or file info side panel (F11)

2022-05-08 Thread Patrick Silva
https://bugs.kde.org/show_bug.cgi?id=453500

Patrick Silva  changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 Status|REPORTED|RESOLVED
 CC||bugsefor...@gmx.com

--- Comment #2 from Patrick Silva  ---


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

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

[dolphin] [Bug 452924] Dolphin not showing metadata for files on network shares, "Details" tab in File Properties missing

2022-05-08 Thread Patrick Silva
https://bugs.kde.org/show_bug.cgi?id=452924

Patrick Silva  changed:

   What|Removed |Added

 CC||syiad.al-d...@web.de

--- Comment #15 from Patrick Silva  ---
*** Bug 453500 has been marked as a duplicate of this bug. ***

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

[kwin] [Bug 432286] transparency+blur glitching with obscured animated windows underneath

2022-05-08 Thread S. Christian Collins
https://bugs.kde.org/show_bug.cgi?id=432286

S. Christian Collins  changed:

   What|Removed |Added

 CC||s_chriscoll...@hotmail.com

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

[frameworks-networkmanager-qt] [Bug 452355] A notification asking to log-in to the network is displayed for every single network

2022-05-08 Thread Thilo-Alexander Ginkel
https://bugs.kde.org/show_bug.cgi?id=452355

Thilo-Alexander Ginkel  changed:

   What|Removed |Added

 CC||th...@ginkel.com

--- Comment #9 from Thilo-Alexander Ginkel  ---
I am also getting this behavior with up-to-date packages on Arch Linux:

KDE Plasma Version:  5.24.5
KDE Frameworks Version: 5.93.0

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

[konsole] [Bug 453545] Konsole resets font size after disconnecting from SSH session

2022-05-08 Thread Thilo-Alexander Ginkel
https://bugs.kde.org/show_bug.cgi?id=453545

--- Comment #1 from Thilo-Alexander Ginkel  ---
Just figured out that the font size is *always* reset, even if it has been set
before connecting via SSH and not been changed while the SSH session was
active.

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

[dolphin] [Bug 453500] Metadata for audio files on remote drives not shown in tool tip or file info side panel (F11)

2022-05-08 Thread Patrick Silva
https://bugs.kde.org/show_bug.cgi?id=453500

Patrick Silva  changed:

   What|Removed |Added

 CC||abdola...@zohomail.eu

--- Comment #1 from Patrick Silva  ---
*** Bug 453511 has been marked as a duplicate of this bug. ***

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

[dolphin] [Bug 453511] The Tooltip doesn't show detail for media files on external hard disk

2022-05-08 Thread Patrick Silva
https://bugs.kde.org/show_bug.cgi?id=453511

Patrick Silva  changed:

   What|Removed |Added

 CC||bugsefor...@gmx.com
 Resolution|--- |DUPLICATE
 Status|REPORTED|RESOLVED

--- Comment #2 from Patrick Silva  ---


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

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

[dolphin] [Bug 452924] Dolphin not showing metadata for files on network shares, "Details" tab in File Properties missing

2022-05-08 Thread Dustin Widmann
https://bugs.kde.org/show_bug.cgi?id=452924

Dustin Widmann <1m.0n.f...@gmail.com> changed:

   What|Removed |Added

 CC||1m.0n.f...@gmail.com

--- Comment #14 from Dustin Widmann <1m.0n.f...@gmail.com> ---
Worth noting that before a recent update to kde/dolphin, metadata display on
network share worked fine, so this is a fairly recent regression/bug.

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

[konsole] [Bug 453545] New: Konsole resets font size after disconnecting from SSH session

2022-05-08 Thread Thilo-Alexander Ginkel
https://bugs.kde.org/show_bug.cgi?id=453545

Bug ID: 453545
   Summary: Konsole resets font size after disconnecting from SSH
session
   Product: konsole
   Version: 22.04.0
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Severity: minor
  Priority: NOR
 Component: general
  Assignee: konsole-de...@kde.org
  Reporter: th...@ginkel.com
  Target Milestone: ---

SUMMARY
Konsole will reset the font size after disconnecting from a SSH session if it
has been altered while the connection was active.

STEPS TO REPRODUCE
1. Use Konsole to connect to another host via SSH
2. Increase the font size via Ctrl++ (or View -> Enlarge font)
3. Disconnect from the remote host
4. The font size is reset

OBSERVED RESULT
The font size is reset after disconnecting

EXPECTED RESULT
The font size remains the same as has been the case with older versions

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

ADDITIONAL INFORMATION

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

[systemsettings] [Bug 453543] Incorrect KCM is highlighted when I open Virtual Desktops KCM via Pager widget

2022-05-08 Thread Patrick Silva
https://bugs.kde.org/show_bug.cgi?id=453543

Patrick Silva  changed:

   What|Removed |Added

Summary|Incorrect KCM is highlithed |Incorrect KCM is
   |when I open Virtual |highlighted when I open
   |Desktops KCM via Pager  |Virtual Desktops KCM via
   |widget  |Pager widget

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

[plasmashell] [Bug 451976] Plasma Crashes On Wayland Session (using NVIDIA drivers) After Upgrading Kubuntu 21.10 -> 22.04

2022-05-08 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=451976

yureadingt...@gmail.com changed:

   What|Removed |Added

 CC||yureadingt...@gmail.com

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

[plasmashell] [Bug 451976] Plasma Crashes On Wayland Session (using NVIDIA drivers) After Upgrading Kubuntu 21.10 -> 22.04

2022-05-08 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=451976

--- Comment #17 from yureadingt...@gmail.com ---
Created attachment 148663
  --> https://bugs.kde.org/attachment.cgi?id=148663=edit
New crash information added by DrKonqi

plasmashell (5.24.4) using Qt 5.15.3

- What I was doing when the application crashed:
Starting a plasma wayland session after upgrading Ubuntu 21.04 to 22.04

- Custom settings of the application:
* This happens when I use the 5.15.0-27-lowlatency kernel image, but I also
have a 5.15.0-5.4-liquorix-amd64 kernel image which runs fine. So it might
either be a 5.15.0-27 issue, or somehow the liquorix kernel features work as a
workaround.
* On a Nvidia GeForce GTX 1050 Ti Mobile graphics card and using the 470.103.01
proprietary Nvidia driver.

-- Backtrace (Reduced):
#4  __pthread_kill_implementation (no_tid=0, signo=6, threadid=140341219895744)
at ./nptl/pthread_kill.c:44
#5  __pthread_kill_internal (signo=6, threadid=140341219895744) at
./nptl/pthread_kill.c:78
#6  __GI___pthread_kill (threadid=140341219895744, signo=signo@entry=6) at
./nptl/pthread_kill.c:89
#7  0x7fa3c0c68476 in __GI_raise (sig=sig@entry=6) at
../sysdeps/posix/raise.c:26
#8  0x7fa3c0c4e7f3 in __GI_abort () at ./stdlib/abort.c:79

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

[plasmashell] [Bug 453544] New: Plasa crash when login in system

2022-05-08 Thread Iron
https://bugs.kde.org/show_bug.cgi?id=453544

Bug ID: 453544
   Summary: Plasa crash when login in system
   Product: plasmashell
   Version: 5.24.5
  Platform: unspecified
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: ironassas...@mail.ru
CC: k...@davidedmundson.co.uk
  Target Milestone: 1.0

Application: plasmashell (5.24.5)

Qt Version: 5.15.3
Frameworks Version: 5.93.0
Operating System: Linux 5.17.5-zen1-1-zen x86_64
Windowing System: X11
Distribution: Garuda Linux
DrKonqi: 5.24.5 [KCrashBackend]

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

- Unusual behavior I noticed:
Black screen and restart systemui

- Custom settings of the application:
Custom dork, wallpaper engine for KDE, Latte

The crash can be reproduced every time.

-- Backtrace:
Application: Plasma (plasmashell), signal: Aborted

[KCrash Handler]
#4  0x7fbf229f734c in __pthread_kill_implementation () at
/usr/lib/libc.so.6
#5  0x7fbf229aa4b8 in raise () at /usr/lib/libc.so.6
#6  0x7fbf22994534 in abort () at /usr/lib/libc.so.6
#7  0x7fbf22c0b7ee in __gnu_cxx::__verbose_terminate_handler() () at
/usr/src/debug/gcc/libstdc++-v3/libsupc++/vterminate.cc:95
#8  0x7fbf22c17c4c in __cxxabiv1::__terminate(void (*)())
(handler=) at
/usr/src/debug/gcc/libstdc++-v3/libsupc++/eh_terminate.cc:48
#9  0x7fbf22c17cb9 in std::terminate() () at
/usr/src/debug/gcc/libstdc++-v3/libsupc++/eh_terminate.cc:58
#10 0x7fbf22c17f5e in __cxxabiv1::__cxa_throw(void*, std::type_info*, void
(*)(void*)) (obj=, tinfo=0x7fbf22d90858 , dest=0x7fbf22ced4a0
) at
/usr/src/debug/gcc/libstdc++-v3/libsupc++/eh_throw.cc:95
#11 0x7fbf22c10352 in
std::filesystem::status(std::filesystem::__cxx11::path const&) (p=Python
Exception : Request for member '_M_head_impl' is ambiguous
in type 'std::tuple'. Candidates are:
  'std::filesystem::__cxx11::path::_List::_Impl_deleter std::_Head_base<1,
std::filesystem::__cxx11::path::_List::_Impl_deleter, true>::_M_head_impl'
(std::tuple -> std::_Tuple_impl<0,
std::filesystem::__cxx11::path::_List::_Impl*,
std::filesystem::__cxx11::path::_List::_Impl_deleter> -> std::_Tuple_impl<1,
std::filesystem::__cxx11::path::_List::_Impl_deleter> -> std::_Head_base<1,
std::filesystem::__cxx11::path::_List::_Impl_deleter, true>)
  ' std::_Head_base<0,
std::filesystem::__cxx11::path::_List::_Impl*, false>::_M_head_impl'
(std::tuple -> std::_Tuple_impl<0,
std::filesystem::__cxx11::path::_List::_Impl*,
std::filesystem::__cxx11::path::_List::_Impl_deleter> -> std::_Head_base<0,
std::filesystem::__cxx11::path::_List::_Impl*, false>)
...) at
/usr/src/debug/gcc-build/x86_64-pc-linux-gnu/libstdc++-v3/include/ext/new_allocator.h:89
#12 0x7fbeb368b340 in wallpaper::MainHandler::loadScene() () at
/usr/lib/qt/qml/com/github/catsout/wallpaperEngineKde/libWallpaperEngineKde.so
#13 0x7fbeb369164b in
wallpaper::MainHandler::onMessageReceived(std::shared_ptr
const&) () at
/usr/lib/qt/qml/com/github/catsout/wallpaperEngineKde/libWallpaperEngineKde.so
#14 0x7fbeb3a2d073 in wallpaper::looper::Message::deliver() () at
/usr/lib/qt/qml/com/github/catsout/wallpaperEngineKde/libWallpaperEngineKde.so
#15 0x7fbeb3a2d5b0 in wallpaper::looper::Looper::loop() () at
/usr/lib/qt/qml/com/github/catsout/wallpaperEngineKde/libWallpaperEngineKde.so
#16 0x7fbeb3a2dbed in
std::thread::_State_impl)#1},
std::weak_ptr > > >::_M_run() () at
/usr/lib/qt/qml/com/github/catsout/wallpaperEngineKde/libWallpaperEngineKde.so
#17 0x7fbf22c474d4 in std::execute_native_thread_routine(void*)
(__p=0x56090bf21b70) at /usr/src/debug/gcc/libstdc++-v3/src/c++11/thread.cc:82
#18 0x7fbf229f55c2 in start_thread () at /usr/lib/libc.so.6
#19 0x7fbf22a7a584 in clone () at /usr/lib/libc.so.6

Thread 19 (Thread 0x7fbebf5ef640 (LWP 8271) "QQmlThread"):
#1  0x7fbf21461976 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7fbf214086c5 in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#3  0x7fbf230705f7 in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#4  0x7fbf2301c88b in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#5  0x7fbf22e7fa56 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#6  0x7fbf244f6d00 in  () at /usr/lib/libQt5Qml.so.5
#7  0x7fbf22e7c8cc in  () at /usr/lib/libQt5Core.so.5
#8  0x7fbf229f55c2 in start_thread () at /usr/lib/libc.so.6
#9  0x7fbf22a7a584 in clone () at /usr/lib/libc.so.6

Thread 18 (Thread 0x7fbee0ff9640 (LWP 8264) "QDBusConnection"):
#1  0x7ffd1d0c99aa in clock_gettime ()
#2  0x7fbf22a4092d in clock_gettime@GLIBC_2.2.5 () at /usr/lib/libc.so.6
#3  0x7fbf2140ad9c in g_main_context_prepare () at
/usr/lib/libglib-2.0.so.0
#4  0x7fbf214617e6 in  () at 

[valgrind] [Bug 452802] Handle lld 9+ split RW PT_LOAD segments correctly

2022-05-08 Thread Paul Floyd
https://bugs.kde.org/show_bug.cgi?id=452802

--- Comment #12 from Paul Floyd  ---
Created attachment 148662
  --> https://bugs.kde.org/attachment.cgi?id=148662=edit
Patch for reading debuginfo correctly with lld 9+

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

[kwin] [Bug 449957] KWin crash in KWin::PlacementArea() when disabling, unplugging or turning off output with windows on it

2022-05-08 Thread phrxmd
https://bugs.kde.org/show_bug.cgi?id=449957

phrxmd  changed:

   What|Removed |Added

Summary|KWin crash in   |KWin crash in
   |KWin::PlacementArea() when  |KWin::PlacementArea() when
   |turning off or unplugging   |disabling, unplugging or
   |monitor with windows on it  |turning off output with
   ||windows on it

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

[kwin] [Bug 449957] KWin crash in KWin::PlacementArea() when turning off or unplugging monitor with windows on it

2022-05-08 Thread phrxmd
https://bugs.kde.org/show_bug.cgi?id=449957

--- Comment #22 from phrxmd  ---
Upon further experimentation, I get the same crash when hitting Meta-P and
switching to the internal display, without disconnecting the monitor.

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

[systemsettings] [Bug 453543] New: Incorrect KCM is highlithed when I open Virtual Desktops KCM via Pager widget

2022-05-08 Thread Patrick Silva
https://bugs.kde.org/show_bug.cgi?id=453543

Bug ID: 453543
   Summary: Incorrect KCM is highlithed when I open Virtual
Desktops KCM via Pager widget
   Product: systemsettings
   Version: master
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: kcm_kwin_virtualdesktops
  Assignee: kwin-bugs-n...@kde.org
  Reporter: bugsefor...@gmx.com
CC: plasma-b...@kde.org
  Target Milestone: ---

Created attachment 148661
  --> https://bugs.kde.org/attachment.cgi?id=148661=edit
screen recording

STEPS TO REPRODUCE
1. please watch the attached screen recording
2. 
3. 

OBSERVED RESULT
'Virtual Desktops' is not highlighted when I open Virtual Desktops KCM via
Pager widget

EXPECTED RESULT
'Virtual Desktops' should be highlighted when we open Virtual Desktops KCM via
Pager widget

SOFTWARE/OS VERSIONS
Operating System: KDE neon Unstable Edition
KDE Plasma Version: 5.24.80
KDE Frameworks Version: 5.94.0
Qt Version: 5.15.3
Graphics Platform: Wayland

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

[KScreen] [Bug 453533] Rest Window Configuration; Whole Screen "Scrolling"

2022-05-08 Thread Méven Car
https://bugs.kde.org/show_bug.cgi?id=453533

Méven Car  changed:

   What|Removed |Added

  Component|multi-screen|common
 Ever confirmed|0   |1
 Status|REPORTED|CONFIRMED
   Assignee|kwin-bugs-n...@kde.org  |kscreen-bugs-n...@kde.org
Product|kwin|KScreen
 CC||meve...@gmail.com

--- Comment #1 from Méven Car  ---
Could you post here the zipped content of the folder ~/.local/share/kscreen/ ?
`zip kscren-config.zip  ~/.local/share/kscreen/*`

And copy here the output of `kscreen-doctor -o` run in a terminal (you may have
to install kscreen-doctor).

About your monitors, are they the same brand and do they share the same
serialnumber ? I would guess they don't.

Does it happen if you stop your PC while in linux and start again in linux ? I
would guess it does.

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

[kde] [Bug 453442] Outlook EWS provider crashes

2022-05-08 Thread mooodyhunter
https://bugs.kde.org/show_bug.cgi?id=453442

mooodyhun...@outlook.com  changed:

   What|Removed |Added

   Assignee|unassigned-b...@kde.org |kdepim-b...@kde.org

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

[marble] [Bug 453542] Marble crashed on opening

2022-05-08 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=453542

alesar...@outlook.it changed:

   What|Removed |Added

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

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

[frameworks-qqc2-desktop-style] [Bug 403153] ComboBox entry popup is not resized to delegate width

2022-05-08 Thread Patrick Silva
https://bugs.kde.org/show_bug.cgi?id=403153

Patrick Silva  changed:

   What|Removed |Added

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

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

[frameworks-qqc2-desktop-style] [Bug 403153] ComboBox entry popup is not resized to delegate width

2022-05-08 Thread Patrick Silva
https://bugs.kde.org/show_bug.cgi?id=403153

--- Comment #30 from Patrick Silva  ---
Created attachment 148660
  --> https://bugs.kde.org/attachment.cgi?id=148660=edit
new screenshot of Screen Locking KCM

This bug persists with Screen Locking KCM.

Operating System: KDE neon Unstable Edition
KDE Plasma Version: 5.24.80
KDE Frameworks Version: 5.94.0
Qt Version: 5.15.3
Graphics Platform: Wayland

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

[marble] [Bug 453542] New: Marble crashed on opening

2022-05-08 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=453542

Bug ID: 453542
   Summary: Marble crashed on opening
   Product: marble
   Version: unspecified
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: marble-b...@kde.org
  Reporter: alesar...@outlook.it
  Target Milestone: ---

Application: marble (2.2.20 (2.3 development version))

Qt Version: 5.15.3
Frameworks Version: 5.93.0
Operating System: Linux 5.17.5-arch1-1 x86_64
Windowing System: X11
Distribution: "Arch Linux"
DrKonqi: 5.24.5 [KCrashBackend]

-- Information about the crash:
- What I was doing when the application crashed:
Marble crashed right after I opened it right after I installed it

The crash can be reproduced every time.

-- Backtrace:
Application: Globo virtuale Marble (marble), signal: Aborted
Content of s_kcrashErrorMessage: {_M_t = { >> = {_M_t = std::tuple containing = {[1] = 0x0,
[2] = {}}}, }}
[KCrash Handler]
#6  0x7f879204f34c in __pthread_kill_implementation () at
/usr/lib/libc.so.6
#7  0x7f87920024b8 in raise () at /usr/lib/libc.so.6
#8  0x7f8791fec534 in abort () at /usr/lib/libc.so.6
#9  0x7f87924acee4 in qt_message_fatal (message=...,
context=...) at global/qlogging.cpp:1914
#10 QMessageLogger::fatal(char const*, ...) const
(this=this@entry=0x7ffe25c56460, msg=msg@entry=0x7f87882200c5 "%s") at
global/qlogging.cpp:893
#11 0x7f878821ad06 in
QQuickWidgetPrivate::handleContextCreationFailure(QSurfaceFormat const&)
(this=, this=, format=...) at
/usr/src/debug/qtdeclarative/src/quickwidgets/qquickwidget.cpp:886
#12 QQuickWidgetPrivate::createContext() (this=) at
/usr/src/debug/qtdeclarative/src/quickwidgets/qquickwidget.cpp:916
#13 0x7f878821e105 in QQuickWidget::resizeEvent(QResizeEvent*)
(this=0x56280a65c5c0, e=) at
/usr/src/debug/qtdeclarative/src/quickwidgets/qquickwidget.cpp:1262
#14 0x7f8791edc32e in
QtWebEngineCore::RenderWidgetHostViewQtDelegateWidget::resizeEvent(QResizeEvent*)
(this=0x56280a65c5c0, resizeEvent=) at
/usr/src/debug/qtwebengine/src/webenginewidgets/render_widget_host_view_qt_delegate_widget.cpp:357
#15 0x7f87931464fe in QWidget::event(QEvent*) (this=0x56280a65c5c0,
event=0x7ffe25c566a0) at kernel/qwidget.cpp:8823
#16 0x7f87931102c6 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
(this=, receiver=0x56280a65c5c0, e=0x7ffe25c566a0) at
kernel/qapplication.cpp:3637
#17 0x7f87926995aa in QCoreApplication::notifyInternal2(QObject*, QEvent*)
(receiver=0x56280a65c5c0, event=0x7ffe25c566a0) at
kernel/qcoreapplication.cpp:1064
#18 0x7f8793141210 in QWidgetPrivate::sendPendingMoveAndResizeEvents(bool,
bool) (this=this@entry=0x56280a60a7a0, recursive=recursive@entry=false,
disableUpdates=, disableUpdates@entry=false) at
kernel/qwidget.cpp:7725
#19 0x7f8793145048 in QWidgetPrivate::show_helper()
(this=this@entry=0x56280a60a7a0) at kernel/qwidget.cpp:7776
#20 0x7f87931456ad in QWidgetPrivate::setVisible(bool)
(this=0x56280a60a7a0, visible=) at kernel/qwidget.cpp:8125
#21 0x7f87896a47f1 in
QtWebEngineCore::WebContentsAdapter::initialize(content::SiteInstance*) () at
/usr/lib/libQt5WebEngineCore.so.5
#22 0x7f87896a52b9 in
QtWebEngineCore::WebContentsAdapter::load(QWebEngineHttpRequest const&) () at
/usr/lib/libQt5WebEngineCore.so.5
#23 0x7f87896a6417 in QtWebEngineCore::WebContentsAdapter::load(QUrl
const&) () at /usr/lib/libQt5WebEngineCore.so.5
#24 0x7f8793f980ee in Marble::PopupItem::PopupItem(QObject*)
(parent=0x56280a3262e0, this=0x56280a31c2a0) at
/usr/src/debug/marble-22.04.0/src/lib/marble/PopupItem.cpp:70
#25 Marble::PopupLayer::Private::Private(Marble::MarbleWidget*,
Marble::PopupLayer*) (q=0x56280a3262e0, marbleWidget=0x562809f30470,
this=0x56280a3155d0) at
/usr/src/debug/marble-22.04.0/src/lib/marble/layers/PopupLayer.cpp:50
#26 Marble::PopupLayer::PopupLayer(Marble::MarbleWidget*, QObject*)
(this=0x56280a3262e0, marbleWidget=0x562809f30470, parent=,
this=, marbleWidget=, parent=) at
/usr/src/debug/marble-22.04.0/src/lib/marble/layers/PopupLayer.cpp:59
#27 0x7f8793fbaf4b in Marble::MarbleWidgetPrivate::construct()
(this=0x562809f1e360) at
/usr/src/debug/marble-22.04.0/src/lib/marble/MarbleWidget.cpp:236
#28 0x7f8793fbc315 in Marble::MarbleWidget::MarbleWidget(QWidget*)
(this=this@entry=0x562809f30470, parent=parent@entry=0x562809f2af80,
this=, parent=) at
/usr/src/debug/marble-22.04.0/src/lib/marble/MarbleWidget.cpp:148
#29 0x5628091dab8b in Marble::ControlView::ControlView(QWidget*)
(parent=0x562809f277d0, this=) at
/usr/src/debug/marble-22.04.0/src/apps/marble-ui/ControlView.cpp:89
#30 Marble::MarblePart::MarblePart(QWidget*, QObject*, QList const&)
(arguments=..., parent=0x562809f277d0, parentWidget=0x562809f277d0,
this=0x562809eab7a0, __in_chrg=, __vtt_parm=) at

[frameworks-ktexteditor] [Bug 453541] New: .kateconfig kate-wildcard(...) does not allow path separators

2022-05-08 Thread David Hurka
https://bugs.kde.org/show_bug.cgi?id=453541

Bug ID: 453541
   Summary: .kateconfig kate-wildcard(...) does not allow path
separators
   Product: frameworks-ktexteditor
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kwrite-bugs-n...@kde.org
  Reporter: david.hu...@mailbox.org
CC: david.hu...@mailbox.org
  Target Milestone: ---

SUMMARY
I am trying to configure Kate to follow the indentation style of a git
repository which does not use my usual indentation style.
So I put a .kateconfig file in the parent directory, which uses the
kate-wildcard(subdir/*) rule.
This does not work.

My current workaround is to use .git/info/exclude to allow .kateconfig in the
git repository itself.

STEPS TO REPRODUCE
1. Add this to a .kateconfig file, assuming replace-tabs is on by default:

> kate-wildcard(subdir/*): replace-tabs off;

2. Open a file from the current directory.
3. Open a file from the subdir directory.

OBSERVED RESULT
Both files use replace-tabs on.
(In Kate status bar displayed as soft tabs.)

EXPECTED RESULT
The file in subdir directory uses replace-tabs off.
(In Kate status bar displayed as Indent/Tab)

SOFTWARE/OS VERSIONS
Operating System: KDE neon 5.24
KDE Plasma Version: 5.24.5
KDE Frameworks Version: 5.93.0
Qt Version: 5.15.3

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

  1   2   >