[kwin] [Bug 453506] Need to kick hotkeys on release, not press

2023-10-31 Thread Yevhen
https://bugs.kde.org/show_bug.cgi?id=453506

--- Comment #8 from Yevhen  ---
(In reply to George from comment #7)
> (In reply to Yevhen from comment #6)
> > Is there a chance to have this bug fixed on Wayland?
> > For KWin Wayland I'm not aware of any workarounds. Old XKB patch
> > (https://aur.archlinux.org/cgit/aur.git/tree/freedesktop-bug-865.
> > patch?h=xorg-server-bug865) doesn't help on Wayland.
> 
> It will most likely never be fixed by Wayland because it inherited
> libxkbcommon, that employs this very bug/behaviour. As it was never fixed in
> Xorg, because the specification is just old and bad (but it worked for
> 40-something years and people are afraid to change something like that with
> no new spec in sight).
> 
> There may be some kind of a solution by the KDE team, as was discussed here
> and elsewhere, but I doubt that, given little numbers of people who care or
> whatever. And there's also this argument that you can change your hotkeys to
> something like Win+Space (or any other ungodly combination) and pretend that
> this bug doesn`t exist. I know, it's sad, but even I did it in the end.
> 
> Anyway, you can try and submit a bug as per Andrey's request. I'll gladly
> join the discussion.

Thanks for the answer and suggestion.
The new issue is here  → https://bugs.kde.org/show_bug.cgi?id=476353

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

[frameworks-kservice] [Bug 442721] kf.service.services: KApplicationTrader: mimeType "x-scheme-handler/file" not found

2023-10-31 Thread AntoineVDV
https://bugs.kde.org/show_bug.cgi?id=442721

AntoineVDV  changed:

   What|Removed |Added

 CC|antoine.vandeve...@gmail.co |
   |m   |

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

[LabPlot2] [Bug 474732] Number of generated values from generate data with stdev or similar column statistic functions seems to be wrong

2023-10-31 Thread Martin
https://bugs.kde.org/show_bug.cgi?id=474732

Martin  changed:

   What|Removed |Added

 CC||martin.marmso...@gmail.com
 Status|CONFIRMED   |RESOLVED
 Resolution|--- |FIXED

--- Comment #7 from Martin  ---
This problem was fixed in:
https://invent.kde.org/education/labplot/-/merge_requests/373

Can you test with the latest development release if it fits your needs?

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

[kdeconnect] [Bug 476354] New: The app will not connect my laptop to my phone a second time. It only works the first time

2023-10-31 Thread Wayne
https://bugs.kde.org/show_bug.cgi?id=476354

Bug ID: 476354
   Summary: The app will not connect my laptop to my phone a
second time. It only works the first time
Classification: Applications
   Product: kdeconnect
   Version: 23.08.2
  Platform: Android
OS: Android 13.x
Status: REPORTED
  Severity: crash
  Priority: NOR
 Component: android-application
  Assignee: albertv...@gmail.com
  Reporter: wkipkurui5...@gmail.com
CC: andrew.g.r.hol...@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. Pair phone with pc on the same network.
2. Disconnect both devices from the network
3. Reconnect both devices to same network
4. Try to connect KDE Application 

OBSERVED RESULT
The two devices will not reconnect 

EXPECTED RESULT
The two devices reconnect automatically.


SOFTWARE/OS VERSIONS
Windows: windows 10 pro 22H2
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 5.109.0
Qt Version: 5.15.10

ADDITIONAL INFORMATION
This happens when the PC disconnects, and everything it happens  I have to
reinstall the app on my phone for it to work

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

[frameworks-kwallet] [Bug 458085] Wallet system takes about 1 minute to start

2023-10-31 Thread Vit Pelcak
https://bugs.kde.org/show_bug.cgi?id=458085

Vit Pelcak  changed:

   What|Removed |Added

 CC||v...@pelcak.org

--- Comment #67 from Vit Pelcak  ---
Hello.

Is there any progress?

I have kwallet 5.111 and the issue is still there.

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

[frameworks-kwallet] [Bug 458085] Wallet system takes about 1 minute to start

2023-10-31 Thread Vit Pelcak
https://bugs.kde.org/show_bug.cgi?id=458085

Vit Pelcak  changed:

   What|Removed |Added

Version|5.97.0  |5.111.0
   Platform|Archlinux   |openSUSE

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

[LabPlot2] [Bug 476355] New: Diagram two y-axis not opened correctly.

2023-10-31 Thread Thomas
https://bugs.kde.org/show_bug.cgi?id=476355

Bug ID: 476355
   Summary: Diagram two y-axis not opened correctly.
Classification: Applications
   Product: LabPlot2
   Version: 2.10.1
  Platform: Microsoft Windows
OS: Microsoft Windows
Status: REPORTED
  Keywords: reproducible, usability
  Severity: wishlist
  Priority: NOR
 Component: backend
  Assignee: alexander.se...@web.de
  Reporter: thwil...@gmail.com
  Target Milestone: ---

Created attachment 162758
  --> https://bugs.kde.org/attachment.cgi?id=162758&action=edit
Result opeing a diagram with 2 y axis

As far as I read, labplot supports a second y-axis. It also supports the import
or opening of Origin Lab projects (Origin Lab 2021b). However, if I open an
Origin Lab project with two y-axes, two graphs are created instead of one
graph. I don't know if I must consider my request a wish or a bug. Anyway, it
should be able to open diagrams with a second y-axis correctly. Origin is
created to increase and improve the diagram design possibilities.  Else, one
can always use Excel. Thus, Labplot should be better than Excel concerning
special features like that. Origin Lab has to be paid on a yearly basis and is
very expensive (in part > 1000 Euro), unaffordable for any private person. As
far as I see, there is no open-source equivalent to Origin Lab. SciDaVis is the
worst - probably too old or even intentionally bad (being a clone of Origin
Lab...). Labplot seems to be the best of those, but most programs, Labplot
included, do only achieve basic things. However, due to Excel which also does
all such things well, such a program does only become interesting, if it can
also create and open diagrams with advanced features: A diagram with a second
y-axis, with categories on the x-axis AND two y-axis etc. 
Compared to Origin Lab this is still very little, in view of the mathematic
capabilities.

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

[kdeconnect] [Bug 475955] Media control of mobile music player doesn't remain in Desktop

2023-10-31 Thread Reza Zarchi
https://bugs.kde.org/show_bug.cgi?id=475955

Reza Zarchi  changed:

   What|Removed |Added

 Status|REPORTED|CONFIRMED
 Ever confirmed|0   |1

--- Comment #1 from Reza Zarchi  ---
And still issue remains after updating my phone to Android 14.0 (One UI 6)
Media player notification dismissed suddenly in Desktop

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

[plasmashell] [Bug 476339] Allow a floating auto-hide panel to perform grab on fullscreen windows

2023-10-31 Thread Lassi Väätämöinen
https://bugs.kde.org/show_bug.cgi?id=476339

Lassi Väätämöinen  changed:

   What|Removed |Added

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

--- Comment #2 from Lassi Väätämöinen  ---
(In reply to Niccolò Venerandi from comment #1)
> Hi! This is actually intentional. The panel grabs the mouse input of events
> between the panel and the screen to make sure that Fitt's law is preserved
> (e.g. moving the mouse to the very border above an applet and clicking will
> still trigger that applet, similarly to when the panel is not floating).

I don't know Fitt's law, but visually this is quite counter-intuitive, as well
as the behavior is a bit asymmetric: the panel gets hidden immediately when you
move the pointer just outside the panel are (Meaning, you cannot interact with
the panel when mouse pointer is just moved outside the visible panel).

BUT: then as contrary. the pointer will interact with the panel elements, if
the pointer is *above* the visible panel, but not pointing to the actual panel
anymore.

Also, auto-hide affects how the floating panel looks like. If auto-hide = off,
then I as user would expect the mentioned behavior that pointing above the
panel item would have a function; this is when the panel does not have a gap at
the top.

But, when auto-hide is off, there is a gap at the top of the screen, and it is
quite weird that the mouse actyally points to the panel items (again, when
moving the mouse pointer out below the panel, there is no "Fitts law margin",
but the panel gets immediately hidden.)

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

[plasmashell] [Bug 476339] Allow a floating auto-hide panel to perform grab on fullscreen windows

2023-10-31 Thread Lassi Väätämöinen
https://bugs.kde.org/show_bug.cgi?id=476339

--- Comment #3 from Lassi Väätämöinen  ---
Created attachment 162759
  --> https://bugs.kde.org/attachment.cgi?id=162759&action=edit
Floating panel, auto-hide = on

This image illustrates  floating panel with auto-hide = on. There is a gap
where mouse pointer very well fits, but instead of how this is visualized, the
panel action item below the pointer gets activated.

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

[plasmashell] [Bug 476339] Allow a floating auto-hide panel to perform grab on fullscreen windows

2023-10-31 Thread Lassi Väätämöinen
https://bugs.kde.org/show_bug.cgi?id=476339

--- Comment #4 from Lassi Väätämöinen  ---
Created attachment 162760
  --> https://bugs.kde.org/attachment.cgi?id=162760&action=edit
Floating panel, auto-hide = off

Floating panel with auto-hide = OFF.

Here as a user I would more expect that the panel item is activated, as there
is no visual gap between the panel and the top of the screen. So there is no
windows or other UI items visually observed as being accessible just above the
panel, as there is no vertical gap.

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

[kwin] [Bug 475653] Primary monitor is switched when coming back from suspend/rebooting

2023-10-31 Thread James North
https://bugs.kde.org/show_bug.cgi?id=475653

--- Comment #10 from James North  ---
Sorry for the late response. Awful week.

I *tried* to run the Live ISO for KDE Neon Unstable, but it defaults to X11 in
the live session and won't let me choose Wayland. For some reason, the graphics
processor in About this System is detected as NV166 despite being a NVIDIA RTX
2060S.

I'll see if I can find a secondary drive somewhere to install it on.

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

[digikam] [Bug 398582] Notarization of Windows Installer as Windows Store package - Use Craft Continuous Deployment System.

2023-10-31 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=398582

--- Comment #43 from caulier.gil...@gmail.com ---
Hi Maik,

All main dependencies from KF6 compile fine under VCPKG (VSCode 2022) with Qt
6.6.0, except Marble ported to Qt6 (by myself).

https://i.imgur.com/xiwF6vT.png

This broken compilation touches plenty of cpp files with exactly the same
error. Look at the screenshot in the StyleBuilder.cpp. Its due to the
OsmPlacemarkData.h include which define the problematic QHash definitions:

https://invent.kde.org/education/marble/-/blob/marble-qt6/src/lib/marble/osm/OsmPlacemarkData.h?ref_type=heads#L161

I suspect that somewhere, a forward declaration of class OsmPlacemarkData
breaks the compilation. As the class usage is a big puzzle, it's not simple to
solve.

This kind of code is untouched with my qt6 port. I mostly fix the broken Qt API
calls and the famous QString from char* constructors calls.
Marble qt5 compile fine under Windows with MSVC 2019:

https://binary-factory.kde.org/view/Windows%2064-bit/job/Marble_Nightly_win64/1016/

The qt6 port of Marble compiles fine under Linux with Qt6.5.3 + G++ and Clang.
I haven't yet tested Qt6.6.0, but I suspect more of a problem with MSVC
compiler version 2022.

If you have some ideas, let me know.

Gilles

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

[plasmashell] [Bug 476339] Allow a floating auto-hide panel to perform grab on fullscreen windows

2023-10-31 Thread Lassi Väätämöinen
https://bugs.kde.org/show_bug.cgi?id=476339

--- Comment #5 from Lassi Väätämöinen  ---
(In reply to Lassi Väätämöinen from comment #3)
> Created attachment 162759 [details]
> Floating panel, auto-hide = on
> 
> This image illustrates  floating panel with auto-hide = on. There is a gap
> where mouse pointer very well fits, but instead of how this is visualized,
> the panel action item below the pointer gets activated.

Or if the gap is only a visual gimmick, I think the gap should be made so small
that there is no possibility for a user to assume that the area below would be
pointable.

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

[plasmashell] [Bug 476189] Quote in window title cuts title too early in task manager

2023-10-31 Thread Gaëtan Gilbert
https://bugs.kde.org/show_bug.cgi?id=476189

--- Comment #3 from Gaëtan Gilbert  ---
Yes X11.

I don't have time to test wayland.

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

[plasma-systemmonitor] [Bug 476160] Choppy scrolling in "Configure columns" dialog

2023-10-31 Thread Arjen Hiemstra
https://bugs.kde.org/show_bug.cgi?id=476160

--- Comment #2 from Arjen Hiemstra  ---
Scrolling has always been a bit problematic, partly due to ProcessModel not
being properly threaded. It's one of those things that I'd love to fix but
which isn't severe enough to warrant the massive amount of work it takes.

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

[kwin] [Bug 475653] Primary monitor is switched when coming back from suspend/rebooting

2023-10-31 Thread James North
https://bugs.kde.org/show_bug.cgi?id=475653

--- Comment #11 from James North  ---
The installer failed after about 20 seconds, which is probably not a good sign.
The ISO I downloaded was from a week ago, so maybe it's fixed now. I'll see if
I can download the latest KDE Neon Unstable ISO and try that.

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

[digikam] [Bug 398582] Notarization of Windows Installer as Windows Store package - Use Craft Continuous Deployment System.

2023-10-31 Thread Maik Qualmann
https://bugs.kde.org/show_bug.cgi?id=398582

--- Comment #44 from Maik Qualmann  ---
Hi Gilles,

just an idea at the moment. A QHash Key must have a globally defined qHash()
function. This is present in GeoDataCoordinates.h. In Qt5 the return value was
uint, in Qt6 it is size_t. The Microsoft compiler may be bothered by this.

Maik

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

[ksysguard] [Bug 475722] On Wayland, Total Memory Column incorrectly shows CGroup instead

2023-10-31 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=475722

fanzhuyi...@gmail.com changed:

   What|Removed |Added

  Latest Commit||https://invent.kde.org/plas
   ||ma/libksysguard/-/commit/55
   ||7c7a7e3506d7fa699eae038c068
   ||8d973014186
 Status|ASSIGNED|RESOLVED
 Resolution|--- |FIXED

--- Comment #6 from fanzhuyi...@gmail.com ---
Git commit 557c7a7e3506d7fa699eae038c0688d973014186 by Yifan Zhu.
Committed on 31/10/2023 at 02:18.
Pushed by ahiemstra into branch 'master'.

Make headings correspond to their strings.

Always insert all heading strings.

Previously on wayland some heading strings are not inserted.
This creates a discrepancy between heading strings and actual headings,
leading to values being displayed under the wrong column names in
systemmonitor.

M  +2-6processui/ProcessModel.cpp

https://invent.kde.org/plasma/libksysguard/-/commit/557c7a7e3506d7fa699eae038c0688d973014186

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

[digikam] [Bug 398582] Notarization of Windows Installer as Windows Store package - Use Craft Continuous Deployment System.

2023-10-31 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=398582

--- Comment #45 from caulier.gil...@gmail.com ---
yes i thinking about the inline hash function too, but the error from compiler
is about the value OsmPlacemarkData, not the key.

I will try to fix it and see.

Nota: Just seen on SN: "Final date for #Plasma6 release confirmed! Our
countdown clock will reach zero on the 28th of February 2024"

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

[LabPlot2] [Bug 474732] Number of generated values from generate data with stdev or similar column statistic functions seems to be wrong

2023-10-31 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=474732

--- Comment #8 from pcfreak...@gmail.com ---
(In reply to Martin from comment #7)
> This problem was fixed in:
> https://invent.kde.org/education/labplot/-/merge_requests/373
> 
> Can you test with the latest development release if it fits your needs?

This works, thanks! 
Although, if the target column is smaller than my source column, the target
column is unnecessarily expanded.
Also, if i use the automatic recalculation feature and then manually expand my
target, the new cells are left empty. Here i would expect the automatic
recalculation to also fill these new cells.

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

[digikam] [Bug 398582] Notarization of Windows Installer as Windows Store package - Use Craft Continuous Deployment System.

2023-10-31 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=398582

--- Comment #46 from caulier.gil...@gmail.com ---
The size_t patch for the inline qHash function declaration do not fix the
problem...

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

[kid3] [Bug 473556] After Snap install, unable to run any of the supplied scripts

2023-10-31 Thread Scarlett Moore
https://bugs.kde.org/show_bug.cgi?id=473556

Scarlett Moore  changed:

   What|Removed |Added

   Assignee|ufleisch@users.sourceforge. |sgmo...@kde.org
   |net |
 Ever confirmed|0   |1
 CC||sgmo...@kde.org
 Status|REPORTED|ASSIGNED

--- Comment #2 from Scarlett Moore  ---
I will fix this in the next build. Thanks!

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

[KDE Itinerary] [Bug 476356] New: Cancelled trains not indicated as such in itinerary view

2023-10-31 Thread reportthebug
https://bugs.kde.org/show_bug.cgi?id=476356

Bug ID: 476356
   Summary: Cancelled trains not indicated as such in itinerary
view
Classification: Applications
   Product: KDE Itinerary
   Version: unspecified
  Platform: Android
OS: Android 13.x
Status: REPORTED
  Severity: major
  Priority: NOR
 Component: general
  Assignee: vkra...@kde.org
  Reporter: chris.seife...@onenetbeyond.org
  Target Milestone: ---

Description: In KDE Itinerary, when viewing an itinerary, cancelled trains are
not indicated as such. The only way to know if a train has been cancelled is by
clicking on the connection and looking for the text that the train is
cancelled. This can be inconvenient and time-consuming, especially when
planning a trip with multiple trains and connections.

Steps to reproduce:

- Open KDE Itinerary and create a new itinerary or open an existing one.
- Add a train connection to the itinerary that has been cancelled.
- View the itinerary in the main window.
- Observe that the cancelled train is not indicated as such in the itinerary
view.
- Click on the connection (or "connection view") to view the details of the
train.
- Observe that the train is marked as cancelled

Expected behavior:

- Cancelled trains should be indicated as such in the itinerary view, using a
clear and visible marker such as a red "X" or strikethrough text.
- The marker should be displayed next to the train connection in the itinerary
view, so that it's easily visible without having to click on the connection.

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

[KPipeWire] [Bug 476279] With NVIDIA GPU on Wayland, viewing Task Manager previews freezes the panel

2023-10-31 Thread Deniil
https://bugs.kde.org/show_bug.cgi?id=476279

--- Comment #3 from Deniil  ---
Hi, thank you for looking into this.
When panel freezes, only panel and nothing else is affected, desktop icons
work, apps work

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

[KPipeWire] [Bug 476279] With NVIDIA GPU on Wayland, viewing Task Manager previews freezes the panel

2023-10-31 Thread Deniil
https://bugs.kde.org/show_bug.cgi?id=476279

--- Comment #4 from Deniil  ---
My version of KPipeWire:
extra/kpipewire 5.27.9-1 (plasma) [installed]
Components relating to pipewire use in Plasma

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

[krita] [Bug 476326] White Frames/Missing Frames during Recording

2023-10-31 Thread Florian Reiser
https://bugs.kde.org/show_bug.cgi?id=476326

--- Comment #1 from Florian Reiser  ---
Hi,

I've digged a little bit deeper and I fear, this seems to be a hard one. I'm
not quite sure what issues this bug, but I have an educated guess.

In the `recorder_writer.cpp`, the data of the current image is read into an
internal buffer
https://invent.kde.org/graphics/krita/-/blob/master/plugins/dockers/recorder/recorder_writer.cpp?ref_type=heads#L135

Due to the fact, that I only see the bug on a high performance system, where we
really can hold the 10Hz capturing, in combination with the usage of big
brushes (which means, Krita has something to do updating the canvas and
therefore writing continously the internal data), my guess is, that we have
maybe a race condition somewhere in the internals of the Krita data managment.

I debugged a little bit this morning and found myself in the
`KisTiledDataManager`. But the corresponding read operation is locked by a Read
Mutex:
https://invent.kde.org/graphics/krita/-/blob/master/libs/image/tiles3/kis_tiled_data_manager.cc?ref_type=heads#L699

So, maybe I'm on the totally wrong position. But maybe not. Could it be, that
we keep the Datamanger so busy in reading data, that we do not release the
mutex often enough? Maybe, its internal data can not be updated anymore? But to
give an anwser to this question, I have not enough epxerience with Krita. 
Do you have any ideas, where we could add traces in the code to track down this
nasty little beast?

Florian

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

[drkonqi] [Bug 476357] New: Automatically add version information when reporting a bug through Launch Bug Report Wizard

2023-10-31 Thread Gert Oja
https://bugs.kde.org/show_bug.cgi?id=476357

Bug ID: 476357
   Summary: Automatically add version information when reporting a
bug through Launch Bug Report Wizard
Classification: Applications
   Product: drkonqi
   Version: 5.27.9
  Platform: Archlinux
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: ge...@pm.me
  Target Milestone: ---

SUMMARY
Dr Konqi and the KDE Bugzilla should be able to include version numbers
automatically in the SOFTWARE/OS VERSIONS section of a bug report.

STEPS TO REPRODUCE
1. Open for example Dolphin
2. Hamburger menu -> Help -> Report Bug -> Launch Bug Report Wizard

OBSERVED RESULT
Versions must be entered manually.

EXPECTED RESULT
Relevant versions are automatically filled out.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Arch Linux
KDE Plasma Version: 5.27.9
KDE Frameworks Version: 5.111.0
Qt Version: 5.15.11

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

[digikam] [Bug 398582] Notarization of Windows Installer as Windows Store package - Use Craft Continuous Deployment System.

2023-10-31 Thread Maik Qualmann
https://bugs.kde.org/show_bug.cgi?id=398582

--- Comment #47 from Maik Qualmann  ---
Hmm, yes it's about the value of the QHash. The QHash is defined within the
OsmPlacemarkData class itself. For the compiler it could not exist at all as
long as the last "}" has not yet been completed.

Maik

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

[NeoChat] [Bug 476358] New: %n times string causes unambiguity for some languages

2023-10-31 Thread Emir SARI
https://bugs.kde.org/show_bug.cgi?id=476358

Bug ID: 476358
   Summary: %n times string causes unambiguity for some languages
Classification: Applications
   Product: NeoChat
   Version: 23.08.2
  Platform: Other
OS: Other
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: General
  Assignee: fe...@posteo.de
  Reporter: emir_s...@icloud.com
CC: c...@carlschwan.eu
  Target Milestone: ---

The %n times string that indicates how many times a user left/entered the room
seems to be appended to the very end of the string. However, for languages with
different word ordering, this causes unambiguity.

The strings that indicate room enter/leave status need to explicitly spelled
with %n times incorporated to them.

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

[frameworks-kservice] [Bug 430157] KDE .desktop parser complains about files that have Type= "Application" but no Exec line, although this situation is normal.

2023-10-31 Thread Yaroslav Sidlovsky
https://bugs.kde.org/show_bug.cgi?id=430157

Yaroslav Sidlovsky  changed:

   What|Removed |Added

 CC||zawer...@gmail.com

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

[frameworks-kservice] [Bug 430157] KDE .desktop parser complains about files that have Type= "Application" but no Exec line, although this situation is normal.

2023-10-31 Thread Yaroslav Sidlovsky
https://bugs.kde.org/show_bug.cgi?id=430157

--- Comment #10 from Yaroslav Sidlovsky  ---
It still spams as hell after fix from this line:
https://invent.kde.org/frameworks/kservice/-/blob/25917d20effad77ac6976a672430a3aac19575d2/src/services/kservice.cpp#L939

Also not only qemu.desktop affected, both
/usr/share/applications/bookmarks.desktop and
/usr/share/applications/org.freedesktop.Xwayland.desktop gives such message
too.

(/usr/share/applications/bookmarks.desktop goes with konqueror).

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

[frameworks-kservice] [Bug 430157] KDE .desktop parser complains about files that have Type= "Application" but no Exec line, although this situation is normal.

2023-10-31 Thread Yaroslav Sidlovsky
https://bugs.kde.org/show_bug.cgi?id=430157

Yaroslav Sidlovsky  changed:

   What|Removed |Added

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

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

[frameworks-kservice] [Bug 430157] KDE .desktop parser complains about files that have Type= "Application" but no Exec line, although this situation is normal.

2023-10-31 Thread Yaroslav Sidlovsky
https://bugs.kde.org/show_bug.cgi?id=430157

Yaroslav Sidlovsky  changed:

   What|Removed |Added

Version|5.76.0  |5.111.0

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

[frameworks-kservice] [Bug 430157] KDE .desktop parser complains about files that have Type= "Application" but no Exec line, although this situation is normal.

2023-10-31 Thread Yaroslav Sidlovsky
https://bugs.kde.org/show_bug.cgi?id=430157

--- Comment #11 from Yaroslav Sidlovsky  ---
Example output from journalctl:
```
Oct 31 12:36:38 rapidus kactivitymanagerd[4618]: kf.service.services: The
desktop entry file "/usr/share/applications/org.freedesktop.Xwayland.desktop"
has Type= "Application" but has no Exec field.
Oct 31 12:36:38 rapidus kactivitymanagerd[4618]: kf.service.services: The
desktop entry file "/usr/share/applications/bookmarks.desktop" has Type=
"Application" but has no Exec field.
Oct 31 12:36:38 rapidus kactivitymanagerd[4618]: kf.service.services: The
desktop entry file "/usr/share/applications/qemu.desktop" has Type=
"Application" but has no Exec field.
...
```

I've counted 684 of this warnings logged in 1 second, it looks like too much
for me.

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

[kde] [Bug 476359] New: kde connect fails to connect over hotspot if it is interrupted

2023-10-31 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=476359

Bug ID: 476359
   Summary: kde connect fails to connect over hotspot if it is
interrupted
Classification: I don't know
   Product: kde
   Version: unspecified
  Platform: Android
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: abimboladip...@gmail.com
  Target Milestone: ---

SUMMARY
***
After a fresh system boot kde connect on my laptop connects to my android phone
over hotspot but if i disable then re-enable the hotspot my laptop connects to
the hotspot but kde connects fails to discover my phone
***


STEPS TO REPRODUCE
1. reboot the laptop.
2. connect to a previously paired android device over it's hotspot.
3. after kde connect discovers the android device turn off the hotspot.
4. turn the hotspot back on again.
5. wait for the laptop to connect.

OBSERVED RESULT
Kde connect fails to discover the device

EXPECTED RESULT
the two devices should connect succesfully

SOFTWARE/OS VERSIONS
Linux:nobara 38 on kernal 6.5.9-200.fsync.fc38.x86_64 
(available in About System)
KDE Plasma Version: 5.27.8
KDE Frameworks Version: 5.110.0
Qt Version: 5.15.10
kde connect version on linux: 23.08.1
kde connect version on android: 1.29.0

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

[NeoChat] [Bug 476360] New: Invalid username or password error seems to be using English text

2023-10-31 Thread Emir SARI
https://bugs.kde.org/show_bug.cgi?id=476360

Bug ID: 476360
   Summary: Invalid username or password error seems to be using
English text
Classification: Applications
   Product: NeoChat
   Version: 23.08.2
  Platform: Other
OS: All
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: General
  Assignee: fe...@posteo.de
  Reporter: emir_s...@icloud.com
CC: c...@carlschwan.eu
  Target Milestone: ---

The error message has been translated for my language (tr_TR) for some time,
but the error message displayed in English nevertheless.

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

[kdeconnect] [Bug 476123] KDE Connect randomly starting playback of paused/stopped media on PC side

2023-10-31 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=476123

--- Comment #2 from k...@sausenthaler.de ---
Looks like KDE was also causing playback stops on VLC. If a video file has
elapsed more than 10 minutes and I hit pause, sometimes the video stopped.
Or if a video was in a paused state it just stops at some time.

Familiar with any 10 minute timer or timeout in KDE-Connect? That causes
problems.

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

[kdenlive] [Bug 475311] Video-File with multiple Audio Streams uses only the first one regardless of choice

2023-10-31 Thread Jean-Baptiste Mardelle
https://bugs.kde.org/show_bug.cgi?id=475311

Jean-Baptiste Mardelle  changed:

   What|Removed |Added

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

--- Comment #2 from Jean-Baptiste Mardelle  ---


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

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

[kdenlive] [Bug 475233] Loading a video with multiple audio tracks duplicates the first deleting all other

2023-10-31 Thread Jean-Baptiste Mardelle
https://bugs.kde.org/show_bug.cgi?id=475233

Jean-Baptiste Mardelle  changed:

   What|Removed |Added

 CC||kde_...@brunodevries.xyz

--- Comment #4 from Jean-Baptiste Mardelle  ---
*** Bug 475311 has been marked as a duplicate of this bug. ***

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

[kdenlive] [Bug 475233] Loading a video with multiple audio tracks duplicates the first deleting all other

2023-10-31 Thread Jean-Baptiste Mardelle
https://bugs.kde.org/show_bug.cgi?id=475233

Jean-Baptiste Mardelle  changed:

   What|Removed |Added

 CC||amwilliams...@gmail.com

--- Comment #5 from Jean-Baptiste Mardelle  ---
*** Bug 476349 has been marked as a duplicate of this bug. ***

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

[kdenlive] [Bug 476349] Multiple Audio Tracks not Working

2023-10-31 Thread Jean-Baptiste Mardelle
https://bugs.kde.org/show_bug.cgi?id=476349

Jean-Baptiste Mardelle  changed:

   What|Removed |Added

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

--- Comment #1 from Jean-Baptiste Mardelle  ---


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

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

[systemsettings] [Bug 476078] 'View sent data' files are all empty even though I set the User Feedback slider to the maximum

2023-10-31 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=476078

--- Comment #4 from kdereport.fireha...@slmail.me ---
Ok weird: I disabled firejail and moved all the files in the
plasmashell/kuserfeedback/audit directory to know immediately when a new one
was created and:

- If I now open the files they contain some info but as I said the last one is
from May 2022.
- Even though I used my system everyday since reporting no other file has been
created in plasmashell/kuserfeedback/audit.

So I guess the bug now is that kuserfeedback is not creating feedback files. 

I'll wait for further instructions for things I can try.

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

[systemsettings] [Bug 476078] 'View sent data' files are all empty even though I set the User Feedback slider to the maximum

2023-10-31 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=476078

--- Comment #5 from kdereport.fireha...@slmail.me ---
I don't know how to edit my previous comment. 
Just to be clear when I say "If I now open the files they contain some info" I
mean the files I moved i.e. the ones which I said were empty previously, there
are no other files since new ones are not being created.

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

[kwin] [Bug 475653] Primary monitor is switched when coming back from suspend/rebooting

2023-10-31 Thread James North
https://bugs.kde.org/show_bug.cgi?id=475653

--- Comment #12 from James North  ---
Alright, I tried with the 29th October build of KDE Neon, and finally got it
working. Had to workaround it to get the installer working, but nonetheless.

After launching Wayland, plasmashell immediately crashed. System settings also
wouldn't launch, so I can't set my display configuration up and setup display
scaling.

Running `systemsettings` from Konsole gets me:

> systemsettings: error while loading shared libraries: libKF6Kirigami2.so.6: 
> cannot open shared object file: No such file or directory

On the plus side, it detected my primary monitor correctly the first time. I
suspended, and when I came back, the primary monitor was still detected
correctly.

So, issue fixed maybe?

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

[digikam] [Bug 398582] Notarization of Windows Installer as Windows Store package - Use Craft Continuous Deployment System.

2023-10-31 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=398582

--- Comment #48 from caulier.gil...@gmail.com ---
Git commit 1bd658c9e60fce91fe120f2b198a2c9c321197cc by Gilles Caulier.
Committed on 31/10/2023 at 11:54.
Pushed by cgilles into branch 'marble-qt6'.

Fix broken compilation with Qt6.6 and MSVC2022 under Windows 10.

MSVC is not able to build the hash-table of class where the key is not fully
defined previously. All function to play the hash-tables are now hosted in a
dedicated container outside OsmPlacemarkData.

The previous code compiled fine with MSVC2019 (and also G++ or Clang). Sounds
like a new restriction introduced in the new Microsoft compiler.

M  +64   -55   src/lib/marble/osm/OsmPlacemarkData.cpp
M  +62   -25   src/lib/marble/osm/OsmPlacemarkData.h
M  +2-2src/plugins/runner/osm/OsmWay.cpp

https://invent.kde.org/education/marble/-/commit/1bd658c9e60fce91fe120f2b198a2c9c321197cc

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

[frameworks-kiconthemes] [Bug 445804] Obeying icon themes' fallback icon themes causes inconsistent icons

2023-10-31 Thread Konrad Materka
https://bugs.kde.org/show_bug.cgi?id=445804

Konrad Materka  changed:

   What|Removed |Added

 CC|mate...@gmail.com   |

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

[kwin] [Bug 476353] Trigger keyboard layout switch shortcuts on release, not press

2023-10-31 Thread Yevhen
https://bugs.kde.org/show_bug.cgi?id=476353

Yevhen  changed:

   What|Removed |Added

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

--- Comment #1 from Yevhen  ---
Accidentally found older bug report
https://bugs.kde.org/show_bug.cgi?id=420493
So, I'm marking this one as a duplicate.

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

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

[frameworks-kglobalaccel] [Bug 420493] Events fire only on key-press instead of on key-release, impossible to blank screen on keypress.

2023-10-31 Thread Yevhen
https://bugs.kde.org/show_bug.cgi?id=420493

Yevhen  changed:

   What|Removed |Added

 CC||xalt7x.serv...@gmail.com

--- Comment #6 from Yevhen  ---
*** Bug 476353 has been marked as a duplicate of this bug. ***

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

[konsole] [Bug 471439] Konsole and other KDE applications crash on startup with global app menu enabled and more than one monitor connected

2023-10-31 Thread Yurii
https://bugs.kde.org/show_bug.cgi?id=471439

--- Comment #14 from Yurii  ---
For me it only happens when i plug in my second monitor via USB Type
C/Thunderbolt dockstation. When monitor is connected directly to the laptop
then there is no crashes.

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

[frameworks-kirigami] [Bug 476361] New: Kirigami.OverlaySheet crashes a program when its parent window is closed

2023-10-31 Thread Fushan Wen
https://bugs.kde.org/show_bug.cgi?id=476361

Bug ID: 476361
   Summary: Kirigami.OverlaySheet crashes a program when its
parent window is closed
Classification: Frameworks and Libraries
   Product: frameworks-kirigami
   Version: Master
  Platform: Compiled Sources
OS: Other
Status: REPORTED
  Keywords: drkonqi, qt6, regression
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdelibs-b...@kde.org
  Reporter: qydwhotm...@gmail.com
CC: m...@ratijas.tk, notm...@gmail.com
  Target Milestone: Not decided

SUMMARY
Kirigami.OverlaySheet without a parent set still happens when its parent window
is closed while the sheet is opened.


STEPS TO REPRODUCE
1. Open OverlaySheet without a parent (e.g. the one in KNewStuff)
2. While the sheet is opened, close the parent window
3. Boom

OBSERVED RESULT
Crash

EXPECTED RESULT
No crash

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: kirigmi at 4e83a29fd4318ace22899c5f85405e1d43bb6696
Qt Version: 6.6.0

ADDITIONAL INFORMATION
(gdb) bt
#0  QQmlPropertyCache::propertyCount() const (this=0x0)
at
/usr/src/debug/qtdeclarative-everywhere-src-6.6.0/build/include/QtQml/6.6.0/QtQml/private/../../../../../../src/qml/qml/qqmlpropertycache_p.h:436
#1  QQmlPropertyCache::property(int) const (index=, this=0x0)
at
/usr/src/debug/qtdeclarative-everywhere-src-6.6.0/build/include/QtQml/6.6.0/QtQml/private/../../../../../../src/qml/qml/qqmlpropertycache_p.h:334
#2  QQmlInterceptorMetaObject::doIntercept(QMetaObject::Call, int, void**)
(this=this@entry=0x7fc794015f40, c=c@entry=QMetaObject::WriteProperty,
id=id@entry=10, a=a@entry=0x7ffd6c985560)
at
/usr/src/debug/qtdeclarative-everywhere-src-6.6.0/src/qml/qml/qqmlvmemetaobject.cpp:279
#3  0x7fc7a91928fd in
QQmlInterceptorMetaObject::intercept(QMetaObject::Call, int, void**)
(a=0x7ffd6c985560, id=10, c=QMetaObject::WriteProperty,
this=0x7fc794015f40)
at
/usr/src/debug/qtdeclarative-everywhere-src-6.6.0/src/qml/qml/qqmlvmemetaobject_p.h:126
#4  QQmlVMEMetaObject::metaCall(QObject*, QMetaObject::Call, int, void**)
(this=0x7fc794015f40, o=, c=QMetaObject::WriteProperty,
_id=10, a=0x7ffd6c985560)
at
/usr/src/debug/qtdeclarative-everywhere-src-6.6.0/src/qml/qml/qqmlvmemetaobject.cpp:686
#5  0x7fc7a9078eba in
QQmlPropertyData::doMetacall<(QMetaObject::Call)2>(QObject*, int, void**) const
(this=, argv=0x7ffd6c985560, idx=,
object=)
at
/usr/src/debug/qtdeclarative-everywhere-src-6.6.0/build/include/QtQml/6.6.0/QtQml/private/../../../../../../src/qml/qml/qqmlpropertydata_p.h:320
#6  QQmlPropertyData::writeProperty(QObject*, void*,
QFlags) const
(this=, target=, value=,
flags=...)
at
/usr/src/debug/qtdeclarative-everywhere-src-6.6.0/build/include/QtQml/6.6.0/QtQml/private/../../../../../../src/qml/qml/qqmlpropertydata_p.h:340
#7  0x7fc7a912e089 in tryConvertAndAssign
(isUrl=, variantMetaType=..., propertyMetaType=...,
flags=..., value=, property=, object=)
at
/usr/src/debug/qtdeclarative-everywhere-src-6.6.0/src/qml/qml/qqmlproperty.cpp:1416
#8  QQmlPropertyPrivate::write(QObject*, QQmlPropertyData const&, QVariant
const&, QQmlRefPointer const&,
QFlags) (object=0x7fc79400b5a0, property=...,
value=..., context=..., flags=...)
at
/usr/src/debug/qtdeclarative-everywhere-src-6.6.0/src/qml/qml/qqmlproperty.cpp:1555
#9  0x7fc7a912f86e in QQmlPropertyPrivate::writeValueProperty(QObject*,
QQmlPropertyData const&, QQmlPropertyData const&, QVariant const&,
QQmlRefPointer const&, QFlags)
(object=, core=, valueTypeData=, value=..., context=..., flags=...)
at
/usr/src/debug/qtdeclarative-everywhere-src-6.6.0/src/qml/qml/qqmlproperty.cpp:1324
#10 0x7fc7a912f8dd in QQmlPropertyPrivate::writeValueProperty(QVariant
const&, QFlags)
(this=0x489fde0, value=..., flags=...) at
/usr/src/debug/qtdeclarative-everywhere-src-6.6.0/src/qml/qml/qqmlproperty.cpp:1269
#11 0x7fc7a912f9b1 in QQmlPropertyPrivate::write(QQmlProperty const&,
QVariant const&, QFlags)
(that=..., value=..., flags=..., flags@entry=...) at
/usr/src/debug/qtdeclarative-everywhere-src-6.6.0/src/qml/qml/qqmlproperty.cpp:1860
#12 0x7fc7a912f9c7 in QQmlProperty::write(QVariant const&) const
(this=this@entry=0x7ffd6c9857a0, value=...) at
/usr/include/qt6/QtCore/qflags.h:73
#13 0x7fc7a912fa05 in QQmlProperty::write(QObject*, QString const&,
QVariant const&) (object=, name=..., value=...)
at
/usr/src/debug/qtdeclarative-everywhere-src-6.6.0/src/qml/qml/qqmlproperty.cpp:1793
#14 0x7fc7a2d374dc in QQuickPopupPrivate::hideOverlay() (this=0x4e70090)
at
/usr/src/debug/qtdeclarative-everywhere-src-6.6.0/src/quicktemplates/qquickpopup.cpp:928
#15 QQuickPopupPrivate::hideOverlay() (this=0x4e70090) at
/usr/src/debug/qtdeclarative-everywhere-src-6.6.0/src/

[kwin] [Bug 453506] Need to kick hotkeys on release, not press

2023-10-31 Thread Yevhen
https://bugs.kde.org/show_bug.cgi?id=453506

--- Comment #9 from Yevhen  ---
As it turns out, there was an even older related bug report:
https://bugs.kde.org/show_bug.cgi?id=420493

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

[kwin] [Bug 476362] New: Alt+Tab doesn't register if a menu is currently showing

2023-10-31 Thread John Veness
https://bugs.kde.org/show_bug.cgi?id=476362

Bug ID: 476362
   Summary: Alt+Tab doesn't register if a menu is currently
showing
Classification: Plasma
   Product: kwin
   Version: 5.27.9
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: tabbox
  Assignee: kwin-bugs-n...@kde.org
  Reporter: john@pelago.org.uk
  Target Milestone: ---

SUMMARY
If a menu is currently open, Alt+Tab will navigate through the menu options
instead of switching between windows.

STEPS TO REPRODUCE
0. Open a few windows of any sort
1. Run System Settings
2. Click on the hamburger menu button once, to bring up the menu
3. Hold Alt
4. Press and release Tab while still holding Alt

OBSERVED RESULT
First item in the hamburger menu is highlighted. Subsequent presses of Tab
(with Alt still held down) highlight subsequent menu items.

EXPECTED RESULT
The Alt+Tab switcher to appear, with the next window highlighted. Subsequent
presses of Tab (with Alt still held down) to highlight subsequent windows.
(I.e. "normal" Alt+Tab behaviour).

SOFTWARE/OS VERSIONS
Operating System: openSUSE Tumbleweed 20231029
KDE Plasma Version: 5.27.9
KDE Frameworks Version: 5.111.0
Qt Version: 5.15.11
Kernel Version: 6.5.9-1-default (64-bit)
Graphics Platform: X11
Processors: 4 × Intel® Core™ i5-7200U CPU @ 2.50GHz
Memory: 15.5 GiB of RAM
Graphics Processor: Mesa Intel® HD Graphics 620
Manufacturer: HP
Product Name: HP ProBook 450 G4

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

[plasmashell] [Bug 466920] plasmashell crashes in ContainmentConfigView::~ContainmentConfigView() in mouse action config

2023-10-31 Thread Fushan Wen
https://bugs.kde.org/show_bug.cgi?id=466920

Fushan Wen  changed:

   What|Removed |Added

 Resolution|FIXED   |DUPLICATE

--- Comment #4 from Fushan Wen  ---


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

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

[frameworks-kirigami] [Bug 476361] Kirigami.OverlaySheet crashes a program when its parent window is closed

2023-10-31 Thread Fushan Wen
https://bugs.kde.org/show_bug.cgi?id=476361

Fushan Wen  changed:

   What|Removed |Added

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

--- Comment #1 from Fushan Wen  ---
*** Bug 466920 has been marked as a duplicate of this bug. ***

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

[Elisa] [Bug 476363] New: Elisa on Android (10) can't access the storage even after I'm manually allowing it.

2023-10-31 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=476363

Bug ID: 476363
   Summary: Elisa on Android (10) can't access the storage even
after I'm manually allowing it.
Classification: Applications
   Product: Elisa
   Version: 23.08.2
  Platform: Android
OS: Android 10.x
Status: REPORTED
  Severity: critical
  Priority: NOR
 Component: general
  Assignee: matthieu_gall...@yahoo.fr
  Reporter: paninomaninod...@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. Select the Music Folder
2. 
3. 

OBSERVED RESULT
Elisa can't find/scan any files

EXPECTED RESULT
Scan the Music folder and show the files to play

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

ADDITIONAL INFORMATION
I pointed to the Music folder, gave permission to access it, added storage
permission manually, changed the indexer, tried to rescan, but nothing works.

Maybe it's because on my phone I "fused" the internal storage with the SD Card
into a single pool?

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

[kde] [Bug 476364] New: Incorrectly styled font selector

2023-10-31 Thread Patrick Silva
https://bugs.kde.org/show_bug.cgi?id=476364

Bug ID: 476364
   Summary: Incorrectly styled font selector
Classification: I don't know
   Product: kde
   Version: unspecified
  Platform: Neon
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: bugsefor...@gmx.com
  Target Milestone: ---

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

STEPS TO REPRODUCE
1. open Digital Clock settings
2. set "Text display" to "Manual"
3. click on "Choose style..." button

OBSERVED RESULT
Incorrectly styled font selector seen in the attached screenshot

EXPECTED RESULT
Correctly styled font selector

SOFTWARE/OS VERSIONS
Operating System: KDE neon Unstable Edition
KDE Plasma Version: 5.27.80
KDE Frameworks Version: 5.240.0
Qt Version: 6.6.0
Graphics Platform: Wayland

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

[kde] [Bug 476364] Incorrectly styled font selector

2023-10-31 Thread Patrick Silva
https://bugs.kde.org/show_bug.cgi?id=476364

Patrick Silva  changed:

   What|Removed |Added

   Keywords||qt6

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

[plasmashell] [Bug 476365] New: [UX Desktop] Once a widget draws over an icon, the widget needs to be moved.

2023-10-31 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=476365

Bug ID: 476365
   Summary: [UX Desktop] Once a widget draws over an icon, the
widget needs to be moved.
Classification: Plasma
   Product: plasmashell
   Version: master
  Platform: Ubuntu
OS: Linux
Status: REPORTED
  Severity: minor
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: jaku...@protonmail.com
CC: k...@davidedmundson.co.uk
  Target Milestone: 1.0

Created attachment 162762
  --> https://bugs.kde.org/attachment.cgi?id=162762&action=edit
Can't quickly move the icon out of the way.

SUMMARY
User can drag and drop a file onto a desktop into a fairly hard to reach spot.
Yes this was dragged and dropped with the note already in place, yes I didn't
demonstrate that sorry.

STEPS TO REPRODUCE
1. Drag and drop an icon/place a widget on top of an icon.

OBSERVED RESULT
Icon is now inaccessible.

EXPECTED RESULT
I propose 2 solutions to this, let me know what you think of this Nate.
Number 1:
You know how the `super` button is by default set to move around windows
from any position within the window. What if that's how selecting a set of
icons on a desktop and click `super` worked? What if that's how the user could
move around widgets.
Number 2:
   1. Widgets now reserve space and push out icons/icons also reserve space and
restrict the resize ability of widgets.
   2. The user now needs to hold the resize to grow the widget over said size.
   On top of that widgets are no longer pinned to a desktop position when a
scroll-able desktop is concerned.
You know how when you stack a row of icons and push them lower than the screen
can place them plasmashell turns your desktop into a scroll-able desktop.
What if the widgets were tied to a position within the desktop space just like
icons are rather than pinned to an absolute screen position, this way the user
can also use it's desktop as a large sticky note board.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Kubuntu 23.10/KDE 5.27.0
KDE Plasma Version: 5.27.0
KDE Frameworks Version:  5.110.0
Qt Version: 5.15.10

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

[plasmashell] [Bug 476365] [UX Desktop] Once a widget draws over an icon, the widget needs to be moved.

2023-10-31 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=476365

jaku...@protonmail.com changed:

   What|Removed |Added

 CC||jaku...@protonmail.com

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

[kwin] [Bug 476362] Alt+Tab doesn't register if a menu is currently showing

2023-10-31 Thread Zamundaaa
https://bugs.kde.org/show_bug.cgi?id=476362

Zamundaaa  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
 Resolution|--- |FIXED
 CC||xaver.h...@gmail.com

--- Comment #1 from Zamundaaa  ---
This is an inherent problem with X11 - context menus grab all keys, so things
like alt+tab and screen lockers don't work when you have one open, and that
can't be fixed. On Wayland this behaves as you'd expect

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

[kwin] [Bug 476352] No app window shown - vscode / Chrome/ Electron - Wayland, KDE6

2023-10-31 Thread Zamundaaa
https://bugs.kde.org/show_bug.cgi?id=476352

Zamundaaa  changed:

   What|Removed |Added

 CC||xaver.h...@gmail.com
   See Also||https://bugs.kde.org/show_b
   ||ug.cgi?id=473887

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

[kwin] [Bug 473887] Can't log in to a Wayland session in VirtualBox

2023-10-31 Thread Zamundaaa
https://bugs.kde.org/show_bug.cgi?id=473887

Zamundaaa  changed:

   What|Removed |Added

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

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

[kwin] [Bug 473887] Can't log in to a Wayland session in VirtualBox

2023-10-31 Thread Fushan Wen
https://bugs.kde.org/show_bug.cgi?id=473887

--- Comment #1 from Fushan Wen  ---
See also https://gitlab.freedesktop.org/mesa/drm/-/issues/83

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

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

2023-10-31 Thread Nicolas Fella
https://bugs.kde.org/show_bug.cgi?id=475423

--- Comment #3 from Nicolas Fella  ---
This seems to only happen while in a Zoom meeting

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

[krusader] [Bug 476366] New: Krusader closes when a selected file changes

2023-10-31 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=476366

Bug ID: 476366
   Summary: Krusader closes when a selected file changes
Classification: Applications
   Product: krusader
   Version: unspecified
  Platform: Archlinux
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: krusader-bugs-n...@kde.org
  Reporter: threedeema...@gmail.com
CC: krusader-bugs-n...@kde.org
  Target Milestone: ---

Application: krusader (2.9.0-dev "Bleeding Edge" (gitrev: 3ccb4966))

Qt Version: 5.15.11
Frameworks Version: 5.111.0
Operating System: Linux 6.5.9-arch2-1 x86_64
Windowing System: Wayland
Distribution: Arch Linux
DrKonqi: 5.27.9 [KCrashBackend]

-- Information about the crash:
It crashes when I try to reduce a size with ghostscript from a terminal and
especially when the file was selected.

The crash can be reproduced every time.

-- Backtrace:
Application: Krusader (krusader), signal: Segmentation fault

[KCrash Handler]
#4  0x7f68529e8c6c in QAbstractItemView::currentChanged(QModelIndex const&,
QModelIndex const&) () at /usr/lib/libQt5Widgets.so.5
#5  0x7f6852a57e8b in QTreeView::currentChanged(QModelIndex const&,
QModelIndex const&) () at /usr/lib/libQt5Widgets.so.5
#6  0x7f6851ad1253 in  () at /usr/lib/libQt5Core.so.5
#7  0x7f6851a6892f in QItemSelectionModel::currentChanged(QModelIndex
const&, QModelIndex const&) () at /usr/lib/libQt5Core.so.5
#8  0x7f6851a64be3 in QItemSelectionModel::setCurrentIndex(QModelIndex
const&, QFlags) () at
/usr/lib/libQt5Core.so.5
#9  0x7f68529da6bf in QAbstractItemView::setCurrentIndex(QModelIndex
const&) () at /usr/lib/libQt5Widgets.so.5
#10 0x559b59cd8e16 in  ()
#11 0x559b59cdf2b4 in  ()
#12 0x7f6851ad1097 in  () at /usr/lib/libQt5Core.so.5
#13 0x559b59db6fe4 in  ()
#14 0x559b59dc157f in  ()
#15 0x559b59db9b48 in  ()
#16 0x7f6851ad1097 in  () at /usr/lib/libQt5Core.so.5
#17 0x7f6852f82c67 in KDirWatch::dirty(QString const&) () at
/usr/lib/libKF5CoreAddons.so.5
#18 0x7f6851ac3bd4 in QObject::event(QEvent*) () at
/usr/lib/libQt5Core.so.5
#19 0x7f68527788ff in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /usr/lib/libQt5Widgets.so.5
#20 0x7f6851a9c168 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at /usr/lib/libQt5Core.so.5
#21 0x7f6851aa10cb in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () at /usr/lib/libQt5Core.so.5
#22 0x7f6851ae7138 in  () at /usr/lib/libQt5Core.so.5
#23 0x7f685050df69 in  () at /usr/lib/libglib-2.0.so.0
#24 0x7f685056c327 in  () at /usr/lib/libglib-2.0.so.0
#25 0x7f685050c162 in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#26 0x7f6851aeaf7c in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#27 0x7f6851a9ae74 in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#28 0x7f6851a9c313 in QCoreApplication::exec() () at
/usr/lib/libQt5Core.so.5
#29 0x559b59c5ef82 in  ()
#30 0x7f6851245cd0 in  () at /usr/lib/libc.so.6
#31 0x7f6851245d8a in __libc_start_main () at /usr/lib/libc.so.6
#32 0x559b59c60cc5 in  ()
[Inferior 1 (process 11122) detached]

Reported using DrKonqi

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

[krusader] [Bug 476366] Krusader closes when a selected file changes

2023-10-31 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=476366

threedeema...@gmail.com changed:

   What|Removed |Added

Version|unspecified |Git

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

[plasma-browser-integration] [Bug 476367] New: Default-Browser

2023-10-31 Thread Thomas Vatter
https://bugs.kde.org/show_bug.cgi?id=476367

Bug ID: 476367
   Summary: Default-Browser
Classification: Plasma
   Product: plasma-browser-integration
   Version: unspecified
  Platform: openSUSE
OS: Linux
Status: REPORTED
  Severity: grave
  Priority: NOR
 Component: general
  Assignee: k...@privat.broulik.de
  Reporter: thomas_vat...@gmx.net
  Target Milestone: ---

Welcome-Dialog is not using the settings for the default-browser.

OpenSuSE 15.1.1

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

[plasma-browser-integration] [Bug 476367] Default-Browser

2023-10-31 Thread Thomas Vatter
https://bugs.kde.org/show_bug.cgi?id=476367

Thomas Vatter  changed:

   What|Removed |Added

 CC||thomas_vat...@gmx.net

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

[k3b] [Bug 476311] K3B projects not saving with .k3b extension; Fedora 38

2023-10-31 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=476311

--- Comment #2 from awfs...@charter.net ---
Gnome Desktop exhibits the same ostensibly incorrect behavior, at least on my
one other F38 that has Gnome, a fully updated and stable desktop machine.

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

[k3b] [Bug 476311] K3B projects not saving with .k3b extension; Fedora 38

2023-10-31 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=476311

--- Comment #3 from awfs...@charter.net ---
(In reply to Patrick Silva from comment #1)
> Cannot reproduce with K3b 23.08.2 on Arch Linux. Possibly it's an issue
> related to gtk save dialog in Cinnamon DE.

Thank You Patrick for assisting to narrow this down. See my comment below.

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

[systemsettings] [Bug 476368] New: Output mapping of identical touchscreen devices doesn't remain after reboot

2023-10-31 Thread Niels Ruitenbeek
https://bugs.kde.org/show_bug.cgi?id=476368

Bug ID: 476368
   Summary: Output mapping of identical touchscreen devices
doesn't remain after reboot
Classification: Applications
   Product: systemsettings
   Version: 5.27.9
  Platform: Archlinux
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: kcm_touchscreen
  Assignee: plasma-b...@kde.org
  Reporter: n.ruitenb...@gmail.com
CC: nicolas.fe...@gmx.de
  Target Milestone: ---

SUMMARY
When two identical touchscreen devices are connected, it is not possible to
configure their output mappings properly due to them having the exact same
name. Looking at ~/.config/kcminputrc, the problem seems to be that when the
first touch input is configured, the configuration for the second touch input
simply overwrites the first entry due to the identical device names.

Strangely enough, directly after the changes from the system settings are
applied, everything seems fine. The problem occurs when the configuration is
loaded after a reboot, where both touch inputs seem to be mapped to one
display.

It seems like extra information is needed to uniquely identify identical touch
input devices.


STEPS TO REPRODUCE
1. Have two identical touchscreen displays connected
2. Map each touch input to their corresponding display output (through trial
and error because both devices have the same name)
3. Observe how the mappings seem to be correct
4. Reboot
5. Observe how the mappings are no longer correct

OBSERVED RESULT
Both touchscreen inputs are mapped to the same display output.

EXPECTED RESULT
The touchscreen inputs are mapped to their corresponding display output, as was
the case before the reboot.

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

[Powerdevil] [Bug 476369] New: Power Devil Restart Loop

2023-10-31 Thread Altamush Nayyer Khan
https://bugs.kde.org/show_bug.cgi?id=476369

Bug ID: 476369
   Summary: Power Devil Restart Loop
Classification: Plasma
   Product: Powerdevil
   Version: 5.27.9
  Platform: Archlinux
OS: Linux
Status: REPORTED
  Severity: major
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: theatt...@gmail.com
CC: m...@ratijas.tk, natalie_clar...@yahoo.de
  Target Milestone: ---

SUMMARY
***
Powerdevil updated to 5.27.9-2 with ddcutil to 2.0.0-1. Update was 2 days ago.
The Power module is broken every since. Using journalctl I got the following
for you.

"org.kde.powerdevil: org.kde.powerdevil.chargethresholdhelper.getthreshold
failed “Charge thresholds are not supported by the kernel for this hardware”
Oct 30 10:51:46 attish-archLinux org_kde_powerdevil[3705]: org.kde.powerdevil:
org.kde.powerdevil.backlighthelper.brightness failed
Oct 30 10:51:51 attish-archLinux systemd[901]: plasma-powerdevil.service: start
operation timed out. Terminating.
Oct 30 10:51:51 attish-archLinux systemd[901]: plasma-powerdevil.service:
Failed with result ‘timeout’.
Oct 30 10:51:51 attish-archLinux systemd[901]: plasma-powerdevil.service:
Consumed 1.745s CPU time.
Oct 30 10:51:51 attish-archLinux systemd[901]: plasma-powerdevil.service:
Scheduled restart job, restart counter is at 46."

This restart loop never ends. Downgrading to previous versions work. After
downgrade, this is what pacman spits out after using pacman -Syu so you know
which version I am using currently.

warning: ddcutil: ignoring package upgrade (1.4.1-1 => 2.0.0-1)
warning: powerdevil: ignoring package upgrade (5.27.8-2 => 5.27.9-2)
***


STEPS TO REPRODUCE
1. Upgrade ddcutil and powerdevil to the versions that I have stated above.

OBSERVED RESULT
The power devil service always crashes and tries to restart itself and whenever
it does, it freezes the computer for a second. Restart loop causes this every 5
or so seconds.


EXPECTED RESULT
The power devil module and service should work fine after update and the power
module should be loaded in System Settings

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

ADDITIONAL INFORMATION
In order to make it work I have to use the following commands:

killall org_kde_powerdevil

kstart5 /usr/lib/org_kde_powerdevil

It spits out:

org.kde.powerdevil: org.kde.powerdevil.chargethresholdhelper.getthreshold
failed “Charge thresholds are not supported by the kernel for this hardware”
org.kde.powerdevil: org.kde.powerdevil.backlighthelper.brightness failed
org.kde.powerdevil: Handle button events action could not check for screen
configuration
org.kde.powerdevil: org.kde.powerdevil.chargethresholdhelper.getthreshold
failed “Charge thresholds are not supported by the kernel for this hardware”

The restart loop breaks this way.

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

[Spectacle] [Bug 476370] New: Rectangular region corrupts screen content: view seems to be duplicated and shifted

2023-10-31 Thread Raman Gupta
https://bugs.kde.org/show_bug.cgi?id=476370

Bug ID: 476370
   Summary: Rectangular region corrupts screen content: view seems
to be duplicated and shifted
Classification: Applications
   Product: Spectacle
   Version: 23.08.1
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: General
  Assignee: noaha...@gmail.com
  Reporter: rocketra...@gmail.com
CC: k...@david-redondo.de
  Target Milestone: ---

SUMMARY

When choosing a screenshot of a rectangular region, the view is corrupted. Some
part of the content on the middle monitor is shown overlaid and shifted right.

I have 3 monitors, the issue appears to be with the content on the middle
monitor, but some of the "shifted" content overlays the left part of the right
monitor.

See attached video.

This seems related to https://bugs.kde.org/show_bug.cgi?id=385885 but that
seems to be marked as fixed, and also that issue is related to mixed-DPI
screens. In my case, I do use HiDPI, but with global scaling rather than mixed.

This is a new problem after recent updates. This was always fine before.


STEPS TO REPRODUCE
1. Open KSpectacle and choose rectangular region

SOFTWARE/OS VERSIONS
Operating System: Fedora Linux 38
KDE Plasma Version: 5.27.8
KDE Frameworks Version: 5.110.0
Qt Version: 5.15.10
Kernel Version: 6.5.8-200.fc38.x86_64 (64-bit)
Graphics Platform: X11
Processors: 24 × 12th Gen Intel® Core™ i9-12900KS
Memory: 125.0 GiB of RAM
Graphics Processor: AMD Radeon RX 6600 XT
Manufacturer: ASUS

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

[kdenlive] [Bug 476371] New: Video Resolution and fps change when working on different pc

2023-10-31 Thread Jim
https://bugs.kde.org/show_bug.cgi?id=476371

Bug ID: 476371
   Summary: Video Resolution and fps change when working on
different pc
Classification: Applications
   Product: kdenlive
   Version: 23.08.1
  Platform: Other
OS: Microsoft Windows
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Video Display & Export
  Assignee: j...@kdenlive.org
  Reporter: jamesichrist...@hotmail.com
  Target Milestone: ---

SUMMARY

Created Project on Notebook A (NBA) and did some work on it.
Moved Project to Notebook B (NBB) and did some more work on it.
Finished up work on NBB and moved Project back to NBA.
Project was setup as 1920x1080 30.00fps on NBA
When working on NBB it took it in as the same.
But when reading the *.kdelive file back to NBA it changed it to 1832x964
20.00fps and flagged a point in the file it did not like. 
Removed the flagged area and reloaded still not reading the correct  Res or fps

File header reads:
 

NBA is a HP ZBook Workstation Notebook; NBB is a HP ENVY Notebook. Both are
setup exactly the same drive wise. to be able to do this. NBA has 4k
Capabilities , running 4k on main screen 1080 on two dual monitors, NBB is
running 1080 single display 

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.  Repeated several times and different revision of my project file.
2. 
3. 

OBSERVED RESULT
in correct resolution and frame per second

EXPECTED RESULT


SOFTWARE/OS VERSIONS
Windows: NBA is 11 Pro, NBB is 11 Home
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 23.08.1
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION

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

[systemsettings] [Bug 449486] GUI for configuring DNS over TLS

2023-10-31 Thread username981618
https://bugs.kde.org/show_bug.cgi?id=449486

username981618  changed:

   What|Removed |Added

 CC||accou...@rack.re

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

[frameworks-kiconthemes] [Bug 476084] When an icon isn't found in the theme, look in its fallback theme before falling back to a more generic icon in the current theme

2023-10-31 Thread Kristen McWilliam
https://bugs.kde.org/show_bug.cgi?id=476084

--- Comment #11 from Kristen McWilliam  ---
Agreed, I can see value to both. I am not sure how to reconcile that.

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

[systemsettings] [Bug 449486] GUI for configuring DNS over TLS

2023-10-31 Thread username981618
https://bugs.kde.org/show_bug.cgi?id=449486

--- Comment #11 from username981618  ---
Just wanted to add that this would be a great feature to have that no other
Linux desktop environment offers at the moment but that's well known from e.g.
Android ("Private DNS") and already supported by systemd.

I think it could be as simple as setting the values in
`/etc/systemd/resolved.conf` for `DNS=0.0.0.0#example.com` and
`DNSoverTLS=[opportunistic/yes/no]` and maybe `DNSSEC=[yes/no]`. 

Optionally we could have some pre-populated providers like NextDNS, Cloudflare,
Adguard or Quad9.

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

[Spectacle] [Bug 476370] Rectangular region corrupts screen content: view seems to be duplicated and shifted

2023-10-31 Thread Raman Gupta
https://bugs.kde.org/show_bug.cgi?id=476370

--- Comment #1 from Raman Gupta  ---
Created attachment 162763
  --> https://bugs.kde.org/attachment.cgi?id=162763&action=edit
Video of screen corruption

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

[Spectacle] [Bug 476372] New: Spectacle crashed when I wanted to edit the annotations

2023-10-31 Thread Dan Dascalescu
https://bugs.kde.org/show_bug.cgi?id=476372

Bug ID: 476372
   Summary: Spectacle crashed when I wanted to edit the
annotations
Classification: Applications
   Product: Spectacle
   Version: 23.08.1
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: General
  Assignee: noaha...@gmail.com
  Reporter: ddascalescu+...@gmail.com
CC: k...@david-redondo.de
  Target Milestone: ---

Application: spectacle (23.08.1)

Qt Version: 5.15.10
Frameworks Version: 5.110.0
Operating System: Linux 6.5.6-200.fc38.x86_64 x86_64
Windowing System: Wayland
Distribution: Fedora Linux 38 (KDE Plasma)
DrKonqi: 5.27.8 [KCrashBackend]

-- Information about the crash:
While capturing the screenshot, I added some text annotations.

Then I pushed the image into Spectacle because I wanted to edit one of the
texts.

That's when Spectacle crashed.

The reporter is unsure if this crash is reproducible.

-- Backtrace:
Application: Spectacle (spectacle), signal: Segmentation fault

[KCrash Handler]
#4  0x7f57c0808c19 in QFont::operator==(QFont const&) const () from
/lib64/libQt5Gui.so.5
#5  0x7f57c15aa192 in QQuickValueTypeProvider::equal(int, void const*,
QVariant const&) () from /lib64/libQt5Quick.so.5
#6  0x7f57c11136d3 in QQmlValueTypeProvider::equalValueType(int, void
const*, QVariant const&) () from /lib64/libQt5Qml.so.5
#7  0x7f57c10987a0 in QQmlVMEMetaObject::metaCall(QObject*,
QMetaObject::Call, int, void**) () from /lib64/libQt5Qml.so.5
#8  0x7f57c1120608 in QV4::QQmlValueTypeWrapper::write(QObject*, int) const
() from /lib64/libQt5Qml.so.5
#9  0x7f57c111a0be in GenericBinding<0>::write(QV4::Value const&, bool,
QFlags) () from /lib64/libQt5Qml.so.5
#10 0x7f57c111b59d in
QQmlNonbindingBinding::doUpdate(QQmlJavaScriptExpression::DeleteWatcher const&,
QFlags, QV4::Scope&) () from /lib64/libQt5Qml.so.5
#11 0x7f57c1118d15 in
QQmlBinding::update(QFlags) () from
/lib64/libQt5Qml.so.5
#12 0x7f57c0fc46e2 in
QV4::QObjectWrapper::getProperty(QV4::ExecutionEngine*, QObject*,
QQmlPropertyData*) () from /lib64/libQt5Qml.so.5
#13 0x7f57c0fa0d37 in
QV4::QQmlContextWrapper::lookupScopeObjectProperty(QV4::Lookup*,
QV4::ExecutionEngine*, QV4::Value*) () from /lib64/libQt5Qml.so.5
#14 0x7f57a44f3f69 in ?? ()
#15 0x in ?? ()
[Inferior 1 (process 65025) detached]

Reported using DrKonqi

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

[drkonqi] [Bug 476373] New: "Submitting bug report..." never finishes

2023-10-31 Thread Dan Dascalescu
https://bugs.kde.org/show_bug.cgi?id=476373

Bug ID: 476373
   Summary: "Submitting bug report..." never finishes
Classification: Applications
   Product: drkonqi
   Version: 5.27.8
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: ddascalescu+...@gmail.com
  Target Milestone: ---

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

Spectacle crashed, so I went through the process of submitting a bug report.
But it's been 5+ minutes and the process looks like in the screenshot.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Fedora 38
KDE Plasma Version: 5.27.8
KDE Frameworks Version: 5.110.0
Qt Version: 5.15.10

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

[systemsettings] [Bug 476368] Output mapping of identical touchscreen devices doesn't remain after reboot

2023-10-31 Thread Nicolas Fella
https://bugs.kde.org/show_bug.cgi?id=476368

--- Comment #1 from Nicolas Fella  ---
Can you please attach the output of "sudo libinput list-devices" when the two
devices are connected?

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

[digikam] [Bug 476374] New: Cursor focus jumps when in Preview and entering a tag

2023-10-31 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=476374

Bug ID: 476374
   Summary: Cursor focus jumps when in Preview and entering a tag
Classification: Applications
   Product: digikam
   Version: 8.1.0
  Platform: Ubuntu
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Usability-Keyboard
  Assignee: digikam-bugs-n...@kde.org
  Reporter: john-d-sm...@hotmail.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. From thumbnail view, highlight a photo and press F3 to enter Preview
2. Press "T" to start entering a tag
3. begin typing (full words)

OBSERVED RESULT
After one, two, or three characters (and at random), the focus will jump back
to the main window. Typing in the tag pane stops, and digikam now responds as
if I was issuing keyboard shortcuts (i.e. hitting backspace will move to the
previous photo) 

EXPECTED RESULT
The cursor remains focused in the tag pane until I am finished adding tags and
either hit Esc or F3, or click into another pane.

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: Ubuntu 22.04
(available in About System)
Gnome Version: 42.9

ADDITIONAL INFORMATION

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

[kwin] [Bug 466771] Some windows are painted black on X11, processes freeze

2023-10-31 Thread King Kang Kong
https://bugs.kde.org/show_bug.cgi?id=466771

King Kang Kong  changed:

   What|Removed |Added

 CC||r2b2x3+kde...@gmail.com

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

[Keysmith] [Bug 475785] Add a filter bar

2023-10-31 Thread Igor
https://bugs.kde.org/show_bug.cgi?id=475785

Igor  changed:

   What|Removed |Added

 CC||igorpa...@tutanota.com

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

[digikam] [Bug 476374] Cursor focus jumps when in Preview and entering a tag

2023-10-31 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=476374

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

   What|Removed |Added

 CC||caulier.gil...@gmail.com

--- Comment #1 from caulier.gil...@gmail.com ---
It's reproducible using digiKam 8.2.0 pre-release App-image bundle available
here ?

https://files.kde.org/digikam/

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

[Keysmith] [Bug 475427] Import/export functionality

2023-10-31 Thread Igor
https://bugs.kde.org/show_bug.cgi?id=475427

Igor  changed:

   What|Removed |Added

 CC||igorpa...@tutanota.com

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

[kwin] [Bug 440235] CSD windows have huge black outline when compositing is disabled on X11

2023-10-31 Thread King Kang Kong
https://bugs.kde.org/show_bug.cgi?id=440235

King Kang Kong  changed:

   What|Removed |Added

 CC||r2b2x3+kde...@gmail.com

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

[systemsettings] [Bug 476368] Output mapping of identical touchscreen devices doesn't remain after reboot

2023-10-31 Thread Niels Ruitenbeek
https://bugs.kde.org/show_bug.cgi?id=476368

--- Comment #2 from Niels Ruitenbeek  ---
Created attachment 162765
  --> https://bugs.kde.org/attachment.cgi?id=162765&action=edit
Output of 'sudo libinput list-devices'

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

[systemsettings] [Bug 476368] Output mapping of identical touchscreen devices doesn't remain after reboot

2023-10-31 Thread Niels Ruitenbeek
https://bugs.kde.org/show_bug.cgi?id=476368

--- Comment #3 from Niels Ruitenbeek  ---
(In reply to Nicolas Fella from comment #1)
> Can you please attach the output of "sudo libinput list-devices" when the
> two devices are connected?

I have added the output of that command in the attachments. In this case, the
problem lies with the two 'ILITEK...' devices.

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

[Spectacle] [Bug 467590] Cannot crop screenshots from annotation view in main window anymore

2023-10-31 Thread Alexander Trufanov
https://bugs.kde.org/show_bug.cgi?id=467590

Alexander Trufanov  changed:

   What|Removed |Added

 CC||trufano...@gmail.com

--- Comment #7 from Alexander Trufanov  ---
Kubuntu 23.10. No crop feature anymore.
Workaround is downgrade:

cd /tmp
wget
http://archive.ubuntu.com/ubuntu/pool/universe/k/kde-spectacle/kde-spectacle_22.12.3-0ubuntu1_amd64.deb
sudo dpkg -i kde-spectacle_22.12.3-0ubuntu1_amd64.deb
sudo apt-mark hold kde-spectacle

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

[frameworks-kglobalaccel] [Bug 420493] Events fire only on key-press instead of on key-release, impossible to blank screen on keypress.

2023-10-31 Thread Andrey
https://bugs.kde.org/show_bug.cgi?id=420493

Andrey  changed:

   What|Removed |Added

 CC||butir...@gmail.com

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

[kwin] [Bug 322148] Rendering goes wrong - some windows miss decorations some black

2023-10-31 Thread King Kang Kong
https://bugs.kde.org/show_bug.cgi?id=322148

King Kang Kong  changed:

   What|Removed |Added

 CC||r2b2x3+kde...@gmail.com

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

[kwin] [Bug 453506] Need to kick hotkeys on release, not press

2023-10-31 Thread Andrey
https://bugs.kde.org/show_bug.cgi?id=453506

Andrey  changed:

   What|Removed |Added

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

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

[frameworks-kglobalaccel] [Bug 420493] Events fire only on key-press instead of on key-release, impossible to blank screen on keypress.

2023-10-31 Thread Andrey
https://bugs.kde.org/show_bug.cgi?id=420493

Andrey  changed:

   What|Removed |Added

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

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

[Powerdevil] [Bug 476375] New: Powerdevil fails to start, spikes cpu usage to max every few seconds

2023-10-31 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=476375

Bug ID: 476375
   Summary: Powerdevil fails to start, spikes cpu usage to max
every few seconds
Classification: Plasma
   Product: Powerdevil
   Version: 5.27.9
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: knuteir...@gmail.com
CC: m...@ratijas.tk, natalie_clar...@yahoo.de
  Target Milestone: ---

journalctl -b 0 | grep -i 'powerdevil'

ct 31 16:12:57 zxc systemd[879]: Starting Powerdevil...
Oct 31 16:12:57 zxc org_kde_powerdevil[2441]: org.kde.powerdevil:
org.kde.powerdevil.chargethresholdhelper.getthreshold failed "Charge thresholds
are not supported by the kernel for this hardware"
Oct 31 16:12:57 zxc org_kde_powerdevil[2441]: org.kde.powerdevil:
org.kde.powerdevil.backlighthelper.brightness failed
Oct 31 16:13:02 zxc systemd[879]: plasma-powerdevil.service: start operation
timed out. Terminating.
Oct 31 16:13:02 zxc systemd[879]: plasma-powerdevil.service: Failed with result
'timeout'.
Oct 31 16:13:02 zxc systemd[879]: Failed to start Powerdevil.
Oct 31 16:13:02 zxc systemd[879]: plasma-powerdevil.service: Consumed 2.770s
CPU time.
Oct 31 16:13:02 zxc systemd[879]: plasma-powerdevil.service: Scheduled restart
job, restart counter is at 25.
Oct 31 16:13:02 zxc systemd[879]: Starting Powerdevil...
Oct 31 16:13:03 zxc org_kde_powerdevil[2455]: org.kde.powerdevil:
org.kde.powerdevil.chargethresholdhelper.getthreshold failed "Charge thresholds
are not supported by the kernel for this hardware"
Oct 31 16:13:03 zxc org_kde_powerdevil[2455]: org.kde.powerdevil:
org.kde.powerdevil.backlighthelper.brightness failed
Oct 31 16:13:08 zxc systemd[879]: plasma-powerdevil.service: start operation
timed out. Terminating.
Oct 31 16:13:08 zxc systemd[879]: plasma-powerdevil.service: Failed with result
'timeout'.
Oct 31 16:13:08 zxc systemd[879]: Failed to start Powerdevil.
Oct 31 16:13:08 zxc systemd[879]: plasma-powerdevil.service: Consumed 2.787s
CPU time.
Oct 31 16:13:08 zxc systemd[879]: plasma-powerdevil.service: Scheduled restart
job, restart counter is at 26.
Oct 31 16:13:08 zxc systemd[879]: Starting Powerdevil...
Oct 31 16:13:08 zxc org_kde_powerdevil[2469]: org.kde.powerdevil:
org.kde.powerdevil.chargethresholdhelper.getthreshold failed "Charge thresholds
are not supported by the kernel for this hardware"
Oct 31 16:13:08 zxc org_kde_powerdevil[2469]: org.kde.powerdevil:
org.kde.powerdevil.backlighthelper.brightness failed
Oct 31 16:13:13 zxc systemd[879]: plasma-powerdevil.service: start operation
timed out. Terminating.
Oct 31 16:13:13 zxc systemd[879]: plasma-powerdevil.service: Failed with result
'timeout'.
Oct 31 16:13:13 zxc systemd[879]: Failed to start Powerdevil.
Oct 31 16:13:13 zxc systemd[879]: plasma-powerdevil.service: Consumed 2.792s
CPU time.
Oct 31 16:13:13 zxc systemd[879]: plasma-powerdevil.service: Scheduled restart
job, restart counter is at 27.
Oct 31 16:13:13 zxc systemd[879]: Starting Powerdevil...
Oct 31 16:13:13 zxc org_kde_powerdevil[2485]: org.kde.powerdevil:
org.kde.powerdevil.chargethresholdhelper.getthreshold failed "Charge thresholds
are not supported by the kernel for this hardware"
Oct 31 16:13:13 zxc org_kde_powerdevil[2485]: org.kde.powerdevil:
org.kde.powerdevil.backlighthelper.brightness failed

this just keeps repeating.


SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Arch Linux
(available in About System)
KDE Plasma Version: 5.27.9
KDE Frameworks Version: 5.111.0
Qt Version: 5.15.11

ADDITIONAL INFORMATION

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

[systemsettings] [Bug 476368] Output mapping of identical touchscreen devices doesn't remain after reboot

2023-10-31 Thread Niels Ruitenbeek
https://bugs.kde.org/show_bug.cgi?id=476368

--- Comment #4 from Niels Ruitenbeek  ---
Some version information about my system I forgot to add in the original
report:

KDE Plasma Version: 5.27.9
KDE Frameworks Version: 5.111.0
Qt Version: 5.15.11
Kernel Version: 6.5.9-arch2-1 (64-bit)
Graphics Platform: Wayland

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

[okular] [Bug 449464] UPDATE: Can't Delete Highlights in Windows version Okular Version 23.08.1

2023-10-31 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=449464

profetiktrip...@gmail.com changed:

   What|Removed |Added

 Ever confirmed|0   |1
Summary|Add a "clear" tool to   |UPDATE: Can't Delete
   |remove highlighted and  |Highlights in Windows
   |underlined text |version  Okular Version
   ||23.08.1
 CC||profetiktrip...@gmail.com
 Status|REPORTED|CONFIRMED

--- Comment #4 from profetiktrip...@gmail.com ---
Formally titled: 
Add a "clear" tool to remove highlighted and underlined text 

Updated Title since that is a Feature Request. 

Update seems to be an actual bug. 

Cannot delete using "browse tool". 

I still believe we could benefit from "clear" highlight - or give a quick way
to right click any highlight and delete.

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

[systemsettings] [Bug 476368] Output mapping of identical touchscreen devices doesn't remain after reboot

2023-10-31 Thread Nicolas Fella
https://bugs.kde.org/show_bug.cgi?id=476368

--- Comment #5 from Nicolas Fella  ---
Thanks.

This is a tough one. Currently the identification is done via (USB?)
vendor/product/name triple. I'm not sure what else we could use to identify a
device that isn't inherently unstable/volatile

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

[Discover] [Bug 476376] New: Changing source on Kdenlive triggers sources to duplicate

2023-10-31 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=476376

Bug ID: 476376
   Summary: Changing source on Kdenlive triggers sources to
duplicate
Classification: Applications
   Product: Discover
   Version: 5.24.7
  Platform: Kubuntu
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: discover
  Assignee: plasma-b...@kde.org
  Reporter: domojes...@gmail.com
CC: aleix...@kde.org
  Target Milestone: ---

Created attachment 162766
  --> https://bugs.kde.org/attachment.cgi?id=162766&action=edit
Kdenlive's sources dropdown after selecting a different source a few times

SUMMARY
When selecting a different source on an application, sometimes Discover will
slightly hang, and then when everything appears normal, the sources option has
duplicates. This can happen in sequence, and seemingly resets after closing and
restarting Discover.


STEPS TO REPRODUCE & OBSERVED RESULT
1. Open Discover and select an app (I personally experienced this with
Kdenlive).
2. Select sources; none of them will be selected, and the top one's radio
button will seem slightly deformed.
3. Select the ubuntu-jammy source. Discover will hang.
4. Select sources again: there are duplicate ubuntu-jammy and flatpak sources.
5. Select the flatpak source. Discover will hang.
6. Select sources again: there are another set of duplicate ubuntu-jammy and
flatpak sources, and a new snap duplicate.
7. Select *one of* the ubuntu-jammy sources. I say "one of" because some will
do nothing, but there is one that will duplicate everything again.
8. Continue. On every refresh of the sources, there will be one source that
triggers a duplication.

EXPECTED RESULT
The source simply changes

SOFTWARE/OS VERSIONS
Kubuntu Version: 22.04.3 LTS
KDE Plasma Version: 5.24.7
KDE Frameworks Version: 5.92.0
Qt Version: 5.15.3
Kernel version: 6.2.0-35-generic (64-bit)
Flatpak version: 1.12.7

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

  1   2   >