[gwenview] [Bug 307124] Crash while saving pictures

2022-10-16 Thread pceres
https://bugs.kde.org/show_bug.cgi?id=307124

pceres  changed:

   What|Removed |Added

Version|2.8.5   |21.12.1
   Platform|Ubuntu  |Slackware

--- Comment #10 from pceres  ---
I tried to rotate 100 and 200 pictures, and save all of them in a single step.
This led to crash in old versions, in fact I was forced to fraction the
multiple rotations into batches of no more than 50 images. This time, with
Gwenview 21.12.1 on Slackware 15.0, I was not able to replicate the crash, so
it seems apparently fixed in latest versions

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

[kalarm] [Bug 460389] After 08.10.2020 Kalarm, Korganizer, Calendar dont work correctly.

2022-10-16 Thread David Jarvie
https://bugs.kde.org/show_bug.cgi?id=460389

--- Comment #13 from David Jarvie  ---
Just to be sure that I understand you correctly, please confirm that you
downgraded the libical package to version 3.0.14, and that the faults still
occurred.

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

[plasmashell] [Bug 460513] Plasmashell crashes on Wayland

2022-10-16 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=460513

--- Comment #4 from space9...@proton.me ---
(In reply to Jason Playne from comment #3)
> quick question - when kwin_wayland crashes, does it just leave you with a
> black screen + movable cursor?

To clarify, kwin_wayland didn't crash - I killed it manually.
But yes, I just got a black screen + movable cursor. (testing this now after
killing plasmashell, I get the same)

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

[neon] [Bug 415130] Lock and login screens: entering incorrect password or moving focus away breaks using return/enter key to submit password

2022-10-16 Thread Nick
https://bugs.kde.org/show_bug.cgi?id=415130

Nick  changed:

   What|Removed |Added

 CC||nick.craig@gmail.com

--- Comment #64 from Nick  ---
I can also confirm that this bug has recently re-appeared.

Operating System: KDE neon 5.25
KDE Plasma Version: 5.25.5
KDE Frameworks Version: 5.98.0
Qt Version: 5.15.6
Kernel Version: 5.15.0-48-generic (64-bit)
Graphics Platform: X11
Processors: 20 × 12th Gen Intel® Core™ i7-12700H
Memory: 15.3 GiB of RAM
Graphics Processor: Mesa Intel® Graphics
Manufacturer: Novatech
Product Name: NP5x_NP6x_NP7xPNP
System Version: Not Applicable

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

[plasmashell] [Bug 460550] New: Icons-Only Task Manager has inconsistent padding on left and right

2022-10-16 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=460550

Bug ID: 460550
   Summary: Icons-Only Task Manager has inconsistent padding on
left and right
Classification: Plasma
   Product: plasmashell
   Version: master
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Task Manager and Icons-Only Task Manager
  Assignee: plasma-b...@kde.org
  Reporter: nat...@upchur.ch
  Target Milestone: 1.0

Created attachment 152907
  --> https://bugs.kde.org/attachment.cgi?id=152907&action=edit
See rulers between spacers and Tasks-Only Icon Manager

SUMMARY
The Icons-Only Task Manager widget has inconsistent padding on left and right,
making the panel appear uneven when populated with one or more icons.


STEPS TO REPRODUCE
1. Create a panel with an Icons-Only Task Manager widget
2. Observe the difference in padding between the left and right ends of the
widget

OBSERVED RESULT
Widget has inconsistent padding on left and right sides

EXPECTED RESULT
Icons appear centered in panel

SOFTWARE/OS VERSIONS
Operating System: Manjaro Linux
KDE Plasma Version: 5.25.5
KDE Frameworks Version: 5.98.0
Qt Version: 5.15.6

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

[kalarm] [Bug 460389] After 08.10.2020 Kalarm, Korganizer, Calendar dont work correctly.

2022-10-16 Thread ali_deda
https://bugs.kde.org/show_bug.cgi?id=460389

--- Comment #14 from ali_deda  ---
I did the downgrade as advised but calarm still doesn't work and there is no
icon in the arch panel. Now the contact icon and the error it reports have
appeared.
The error is as follows;
file:///usr/share/plasma/plasmoids/org.kde.kalendar.contact/contents/ui/main.qml:10:1:
plugin cannot be loaded for module "org.kde.kalendar.contact": Cannot load
library /usr/lib/qt/qml/org/kde/kalendar/contact/libkalendar_contact_plugin.so:
(libicuuc.so.70: cannot open shared object file: No such file or directory)
I think that the system is made in such a way that it will be impossible to
repair it without a total reinstallation.

-- Comment #13 from David Jarvie  ---
Just to be sure that I understand you correctly, please confirm that you
downgraded the libical package to version 3.0.14, and that the faults still
occurred.

Hey, thanks for the advice and help, I've checked the downgrade 100 times, the
system doesn't work, that doesn't help, there are too many connected and
dependent files

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

[dragonplayer] [Bug 459326] UX bug - "play file" dialog uses inonvenient default for "Files of type" input

2022-10-16 Thread Harald Sitter
https://bugs.kde.org/show_bug.cgi?id=459326

--- Comment #12 from Harald Sitter  ---
Can you reproduce this on Plasma, GNOME or XFCE?

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

[neon] [Bug 415130] Lock and login screens: entering incorrect password or moving focus away breaks using return/enter key to submit password

2022-10-16 Thread Nick
https://bugs.kde.org/show_bug.cgi?id=415130

--- Comment #65 from Nick  ---
Created attachment 152908
  --> https://bugs.kde.org/attachment.cgi?id=152908&action=edit
apt-cache show plasma-workspace

As requested by Nate Graham. https://bugs.kde.org/show_bug.cgi?id=415130#c4

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

[systemsettings] [Bug 460551] New: The corner is highlighted when it shouldn't

2022-10-16 Thread Dmitry
https://bugs.kde.org/show_bug.cgi?id=460551

Bug ID: 460551
   Summary: The corner is highlighted when it shouldn't
Classification: Applications
   Product: systemsettings
   Version: 5.26.0
  Platform: Archlinux
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: zalimann...@mail.ru
  Target Milestone: ---

Created attachment 152909
  --> https://bugs.kde.org/attachment.cgi?id=152909&action=edit
The corner is highlighted when it shouldn't

SUMMARY
If the option "Changing the desktop when moving the mouse over the edge of the
screen" is in the "Always" mode, the edges of the screen are always highlighted
when the mouse approaches. Even if there is only one desktop and the function
for the edge of the screen is not assigned. This happens only for corners

STEPS TO REPRODUCE
Set the parameters as in the screenshot

OBSERVED RESULT
The corners are highlighted

EXPECTED RESULT
Nothing happens

SOFTWARE/OS VERSIONS
Operating System: Arch Linux
KDE Plasma Version: 5.26.0
KDE Frameworks Version: 5.99.0
Qt Version: 5.15.6
Kernel Version: 6.0.1-zen2-1-zen (64-bit)
Graphics Platform: Wayland

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

[dragonplayer] [Bug 459326] UX bug - "play file" dialog uses inonvenient default for "Files of type" input

2022-10-16 Thread Harald Sitter
https://bugs.kde.org/show_bug.cgi?id=459326

--- Comment #13 from Harald Sitter  ---
Nevermind

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

[dragonplayer] [Bug 459326] UX bug - "play file" dialog uses inonvenient default for "Files of type" input

2022-10-16 Thread Harald Sitter
https://bugs.kde.org/show_bug.cgi?id=459326

Harald Sitter  changed:

   What|Removed |Added

  Latest Commit||https://invent.kde.org/mult
   ||imedia/dragon/commit/87a127
   ||e33a4210d47fad12af7a3080e36
   ||ab99094
 Status|REPORTED|RESOLVED
 Resolution|--- |FIXED

--- Comment #14 from Harald Sitter  ---
Git commit 87a127e33a4210d47fad12af7a3080e36ab99094 by Harald Sitter.
Committed on 16/10/2022 at 18:47.
Pushed by sitter into branch 'master'.

make sure the native qt dialog shows octet-stream as mime option

otherwise it'd refuse to accept our default value and just pick the
first value in the list

M  +4-1src/app/mainWindow.cpp

https://invent.kde.org/multimedia/dragon/commit/87a127e33a4210d47fad12af7a3080e36ab99094

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

[konqueror] [Bug 379771] konqueror crashed for a particular address

2022-10-16 Thread Stefano Crocco
https://bugs.kde.org/show_bug.cgi?id=379771

--- Comment #18 from Stefano Crocco  ---
(In reply to przxqgl from comment #17)
> (In reply to Stefano Crocco from comment #16)
> > It's an old version of Konqueror, and many things have changed in the new
> > releases.
> 
> it's an old story which keeps coming back to haunt me...
> 
> > Could you please verify which is your default web browser engine?
> > (You can find in the General tab of Konqueror settings dialog, right below
> > the "Home page settings": it can be WebEngine, WebKit or KHTML).
> 
> well, my version of konqueror has a "settings" menu, but i don't know how to
> get to a "General tab of Konqueror settings dialog", so you'll have to do a
> better job of telling me what you want.
>From the "Settings" menu, choose the "Configure Konqueror" entry to display the
settings dialog. On the left, there's a tree (I'm working from memory, as this
dialog has changed much in more recent versions of Konqueror). In these trees
there's at least one, but most likely two "General" entries: you need the first
(which should be, if I remember correctly, under the "Web behavior" entry).
Clicking on it will display in the right side of the dialog a page with several
configuration options: the third is labeled "Default web browser engine" (or
something very similar). You should check what is selected for that option.
Another way to do the same is opening any web page, then going to the "View"
menu, choosing the "View mode" submenu and looking at the checked entry.

Another thing you can check (which I forgot in my last answer) are the settings
in the "KDE Performance" page of the settings dialog. You can access it as
described above: the page is one of the first in the tree on the left (I think
the second one). Ensure that both entries in the page ("Preload an instance
after desktop startup" and "Always try to have one preloaded instance") are
unchecked. These options were quite broken in old versions of Konqueror and
could lead to strange behaviors.

> > Could you
> > please also try creating a new user and seeing whether you have the same
> > problems?
> 
> i could probably do that, with step-by-step instructions, but it is beyond
> my current capabilities as a user.
In that case, it's better not to try. It's not that difficult, but since it
requires superuser access, a mistake could damage your system. A simpler, but
less complete test, is to ensure that Konqueror isn't running (to do so, from a
terminal run `killall konqueror`), then rename he file ~/.config/konquerorrc
and the directory ~/.local/share/konqueror to something else (for example,
~/.config/konquerorrc_old and ~/.local/share/konqueror_old): this will reset
your Konqueror configuration to the default values. You can then try running
Konqueror again and see whether you have the same problems or not. If things
not work correctly, there was something broken in your configuration files.

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

[dragonplayer] [Bug 459326] UX bug - "play file" dialog uses inonvenient default for "Files of type" input

2022-10-16 Thread Alex Kh
https://bugs.kde.org/show_bug.cgi?id=459326

--- Comment #15 from Alex Kh  ---
Thanks a lot Harald

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

[frameworks-kitemmodels] [Bug 459321] Tests fail when building statically

2022-10-16 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=459321

Bug Janitor Service  changed:

   What|Removed |Added

 Status|REPORTED|ASSIGNED
 Ever confirmed|0   |1

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

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

[plasma-systemmonitor] [Bug 460469] System monitor has fallen back to software rendering on Lenovo Legion 5 17ACH6

2022-10-16 Thread Nikolay Fedorov
https://bugs.kde.org/show_bug.cgi?id=460469

--- Comment #2 from Nikolay Fedorov  ---
Hi.
Default installation OS: Kubuntu 22.04.1 LTS x86_64
X11
I've installed the NVida driver from the nvidia site, instead of Ubuntu
provided.
Now the system monitor works fine. but I've got new issues :)

Best Regards.

On Sun, Oct 16, 2022, 4:18 AM Nate Graham  wrote:

> https://bugs.kde.org/show_bug.cgi?id=460469
>
> Nate Graham  changed:
>
>What|Removed |Added
>
> 
>  CC||n...@kde.org
> Version|unspecified |5.18.7
>  Status|REPORTED|NEEDSINFO
>  Resolution|--- |WAITINGFORINFO
>
> --- Comment #1 from Nate Graham  ---
> Can you provide some more information? Does anything else on the system use
> software rendering? Are you using Wayland or X11?
>
> --
> You are receiving this mail because:
> You reported the bug.

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

[kdeconnect] [Bug 460552] New: SMS integration not working as expected

2022-10-16 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=460552

Bug ID: 460552
   Summary: SMS integration not working as expected
Classification: Applications
   Product: kdeconnect
   Version: unspecified
  Platform: Android
OS: Android 8.x
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: android-application
  Assignee: albertv...@gmail.com
  Reporter: rob.d...@telus.net
  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
***
Scenario - Android device has received an SMS with a file attached such as a
photo. The photo thumbnail is touched and the photo is opened.
The problem is that when touching the share icon, "send to device" shows as
well as a list of devices. Choosing a device does nothing. If the file is
copied from the message into the file system it can be shared using kde
connect.

If the intent was to be able to share files directly from SMS then it should be
fixed. If this was never the intent then the "send to device" option should not
appear.

STEPS TO REPRODUCE
1. open an SMS attachement
2. touch the share icon. paired device list appears
3. choose a device
4. observe that no notification appears on the intended recipient
5. scan through the Downloads folder
6. the file is not found
7. observe that the android device shows an upload in the status line 

OBSERVED RESULT
The file was not transferred

EXPECTED RESULT
The recipient desktop should receive a notification. The file should now be
found in the Downloads folder

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: Fedora 36 on desktop, 8.1 on android
(available in About System)
KDE Plasma Version: 5.25.5
KDE Frameworks Version: 5.98
Qt Version: 5.15.6

ADDITIONAL INFORMATION
Using a file manager on the android device, a file can be shared as expected
using kde connect.
The desktop widget can browse the android device file system and can download a
file.

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

[kwin] [Bug 460248] plasmashell with high CPU usage in Wayland session

2022-10-16 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=460248

--- Comment #11 from guimarcalsi...@gmail.com ---
Unfortunately, I couldn't find a way to get perf data from a specific process,
but this is the output of perf top -K:

Samples: 184K of event 'cycles', 4000 Hz, Event count (approx.): 22948410615
lost: 0/0 drop: 0/0
Overhead  Shared Object   Symbol
   2,13%  libQt5Core.so.5.15.6[.]
QCoreApplicationPrivate::sendThroughApplicationEventFilters
   1,65%  libc.so.6   [.] malloc
   1,56%  libc.so.6   [.] cfree
   1,46%  libc.so.6   [.] __libc_calloc
   1,40%  libc.so.6   [.] pthread_mutex_lock
   1,10%  [vdso]  [.] __vdso_clock_gettime
   0,97%  libQt5Core.so.5.15.6[.] QMetaObject::activate
   0,85%  libwayland-client.so.0.21.0 [.]
wl_proxy_marshal_array_flags
   0,78%  [vdso]  [.] 0x0695
   0,74%  libQt5Core.so.5.15.6[.] QMutex::lock
   0,71%  libwayland-client.so.0.21.0 [.] wl_display_read_events
   0,65%  libQt5Core.so.5.15.6[.]
QEventDispatcherUNIX::processEvents
   0,61%  libc.so.6   [.] clock_gettime
   0,61%  libQt5Widgets.so.5.15.6 [.] QApplication::notify
   0,57%  libQt5Core.so.5.15.6[.] QMutex::unlock
   0,57%  libffi.so.8.1.1 [.] 0x2318
   0,55%  libglib-2.0.so.0.7400.0 [.] g_mutex_lock
   0,54%  libQt5Core.so.5.15.6[.]
QObjectPrivate::maybeSignalConnected
   0,54%  libglib-2.0.so.0.7400.0 [.] g_main_context_check
   0,49%  libQt5Core.so.5.15.6[.] QObject::~QObject
   0,48%  libglib-2.0.so.0.7400.0 [.] g_mutex_unlock
   0,46%  libQt5Core.so.5.15.6[.]
QCoreApplicationPrivate::sendPostedEvents
   0,45%  libglib-2.0.so.0.7400.0 [.] g_source_ref
   0,43%  libc.so.6   [.] 0x00153840
   0,43%  libQt5Widgets.so.5.15.6 [.]
QApplicationPrivate::notify_helper
   0,41%  libc.so.6   [.] pthread_getspecific
   0,41%  libQt5Core.so.5.15.6[.]
QCoreApplication::notifyInternal2
   0,41%  libc.so.6   [.] 0x0008b472
   0,40%  perf[.] hpp__sort_overhead
   0,39%  libc.so.6   [.] pthread_cond_wait
   0,38%  libc.so.6   [.] pthread_mutex_unlock
   0,38%  libglib-2.0.so.0.7400.0 [.] g_main_context_prepare
   0,38%  perf[.] rb_next
   0,38%  libc.so.6   [.] __poll
   0,37%  ld-linux-x86-64.so.2[.] __tls_get_addr

libQt5Core.so.5.15.6 [.]
QCoreApplicationPrivate::sendThroughApplicationEventFilters is always on top.
If I "zoom" into it using the perf tool I get:

Samples: 70K of event 'cycles', 4000 Hz, Event count (approx.): 10027589808,
DSO: libQt5Core.so.5.15.6 lost: 0/0 drop: 0/0
Overhead  Symbol
   1,59%  [.] QCoreApplicationPrivate::sendThroughApplicationEventFilters   
   0,82%  [.] QMetaObject::activate 
   0,67%  [.] QObjectPrivate::maybeSignalConnected  
   0,61%  [.] 0x0029452b
   0,53%  [.] 0x00346f54
   0,52%  [.] QMutex::lock  
   0,48%  [.] 0x002bd2f4
   0,43%  [.] QEventDispatcherUNIX::processEvents   
   0,37%  [.] QObject::~QObject 
   0,36%  [.] QCoreApplication::notifyInternal2 
   0,35%  [.] QMutex::unlock
   0,34%  [.] 0x002bd2d8
   0,32%  [.] 0x002bd360
   0,30%  [.] QCoreApplicationPrivate::sendPostedEvents 
   0,30%  [.] 0x002bd385
   0,29%  [.] QHashData::nextNode   
   0,27%  [.] QArrayData::allocate  
   0,25%  [.] QObject::event
   0,21%  [.] QIODevice::read   
   0,21%  [.] 0x002bd096
   0,20%  [.] 0x002b83ac
   0,20%  [.]

[kwin] [Bug 460248] plasmashell with high CPU usage in Wayland session

2022-10-16 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=460248

--- Comment #12 from guimarcalsi...@gmail.com ---
Sönke Holz is right. Re-enabling the option to paste with a middle click on the
general behavior KCM makes the CPU usage go back to normal. Disabling it makes
the CPU usage go up.

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

[frameworks-kconfig] [Bug 422529] Put config files inside a kde subdirectory in ~/.config, ~/.local/share, and ~/.cache

2022-10-16 Thread Nejc Bertoncelj
https://bugs.kde.org/show_bug.cgi?id=422529

Nejc Bertoncelj  changed:

   What|Removed |Added

 CC||n...@bertoncelj.eu.org

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

[kwin] [Bug 460553] New: Kwin crashes in Plasma 5.26 if xdg-desktop-portal-gnome is installed and running and you attempt to screen share or use OBS

2022-10-16 Thread p d
https://bugs.kde.org/show_bug.cgi?id=460553

Bug ID: 460553
   Summary: Kwin crashes in Plasma 5.26 if
xdg-desktop-portal-gnome is installed and running and
you attempt to screen share or use OBS
Classification: Plasma
   Product: kwin
   Version: 5.26.0
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: crash
  Priority: NOR
 Component: wayland-generic
  Assignee: kwin-bugs-n...@kde.org
  Reporter: pizzad...@linuxmail.org
  Target Milestone: ---

SUMMARY
If xdg-desktop-portal-gnome is installed and running (and it is by default on
Fedora 36): Since KDE 5.26, using OBS or screen sharing causes the KDE session
to crash and restart (tested in Wayland), and removing xdg-desktop-portal-gnome
fixes this.

STEPS TO REPRODUCE
1. Be on Fedora 36 KDE with wayland session
2. Have xdg-desktop-portal-gnome installed and running (it is by default)
3. Try to screen share in telegram or screen record in OBS
4. Instant crash

OBSERVED RESULT

Kwin crash when sharing / recording screen

EXPECTED RESULT

There to be no crash.


SOFTWARE/OS VERSIONS
Operating System: Fedora Linux 36
KDE Plasma Version: 5.26.0
KDE Frameworks Version: 5.98.0
Qt Version: 5.15.6
Kernel Version: 5.19.15-201.fc36.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 4 × Intel® Core™ i5-7300U CPU @ 2.60GHz
Memory: 7.6 GiB of RAM
Graphics Processor: Mesa Intel® HD Graphics 620

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

[frameworks-kconfig] [Bug 459337] Some tests fail when built statically

2022-10-16 Thread Alexander Lohnau
https://bugs.kde.org/show_bug.cgi?id=459337

Alexander Lohnau  changed:

   What|Removed |Added

   Assignee|matt...@mjdsystems.ca   |alexander.loh...@gmx.de
 CC||alexander.loh...@gmx.de
 Status|REPORTED|CONFIRMED
 Ever confirmed|0   |1

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

[plasmashell] [Bug 429211] [X11] Digital clock/whole panel sometimes stops updating until there is user interaction with Plasma

2022-10-16 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=429211

network...@rkmail.ru changed:

   What|Removed |Added

 CC||network...@rkmail.ru

--- Comment #38 from network...@rkmail.ru ---
Regarding wayland session: it is not just clock stops updating, it's plasma
freezing a whole. Hotkey volume control does not work as well until you hover
mouse over a plasma panel. And more: a qt5-based amarok stops switching tracks
when it's minimized!

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

[systemsettings] [Bug 460103] Margins for headers in System Settings tabs differs for different components.

2022-10-16 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=460103

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

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

[plasmashell] [Bug 459774] Make "resident" notifications the default.

2022-10-16 Thread Carlos Solís
https://bugs.kde.org/show_bug.cgi?id=459774

Carlos Solís  changed:

   What|Removed |Added

 CC||csol...@azkware.net

--- Comment #17 from Carlos Solís  ---
Regarding the implementation, I was under the impression that the hints boolean
values, which include the "resident" and "transient" values, worked like this:

- Resident: the notification is not dismissed until the user manually closes
it. Similar to permanent notifications on Android.
- Transient: the notification is automatically dismissed and furthermore, is
not stored in the tray when it times out.

Our issue currently comes with the behavior for the default case (no resident
hint, no transient hint either), which seems to be left up to each
implementation as per the specs. (See
https://specifications.freedesktop.org/notification-spec/notification-spec-latest.html#hints
). They explicitly state that "Neither clients nor notification servers are
required to support any hints". However, besides of these boolean values
there's also the urgency level, which does include a recommended implementation
cue - regarding critical urgency notifications, "They should only be closed
when the user dismisses them, for example, by clicking on the notification."

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

[kolourpaint] [Bug 460069] My Color Bar Disapered

2022-10-16 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=460069

--- Comment #6 from nevatro...@gmail.com ---
that is how it looks except mine is not marked, how do i fix it

On Sat, Oct 15, 2022 at 4:31 PM Martin Koller 
wrote:

> https://bugs.kde.org/show_bug.cgi?id=460069
>
> --- Comment #5 from Martin Koller  ---
> Created attachment 152868
>   --> https://bugs.kde.org/attachment.cgi?id=152868&action=edit
> screenshot of right-click on menu
>
> See attached screenshot.
> If that is not how your window looks like, please attach a screenshot
>
> --
> You are receiving this mail because:
> You reported the bug.

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

[kwin] [Bug 460248] plasmashell with high CPU usage in Wayland session

2022-10-16 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=460248

76montan...@proton.me changed:

   What|Removed |Added

 CC||76montan...@proton.me

--- Comment #13 from 76montan...@proton.me ---
I believe that I am experiencing this same bug.

After rebooting the system and logging in, the computer sat idle on the desktop
for 30 minutes. The CPU fan had been running non-stop since login. After
sitting idle for 30 minutes, I opened the System Monitor and found that my CPU
was running 30% - 40%. Plasmashell was running 20% - 25% and kwin_wayland was
running 10% - 15% constantly.

This is a brand-new fresh installation of Arch Linux as of yesterday (Saturday,
October 15, 2022).

Operating System: Arch Linux
KDE Plasma Version: 5.26.0
KDE Frameworks Version: 5.99.0
Qt Version: 5.15.6
Kernel Version: 6.0.1-arch2-1 (64-bit)
Graphics Platform: Wayland
Processors: 4 × 11th Gen Intel® Core™ i3-1115G4 @ 3.00GHz
Memory: 31.0 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics
Manufacturer: Intel(R) Client Systems
Product Name: NUC11TNKi3
System Version: M11929-403

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

[kwin] [Bug 460248] plasmashell with high CPU usage in Wayland session

2022-10-16 Thread Cihan Işık
https://bugs.kde.org/show_bug.cgi?id=460248

--- Comment #14 from Cihan Işık  ---
Can also confirm, CPU usage goes up when "paste selected text" is unticked.
Ticking it makes the problem go away instantly.

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

[dolphin] [Bug 460508] Dolphin search crosses file system boundary when Baloo is disabled

2022-10-16 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=460508

tagwer...@innerjoin.org changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|REPORTED|CONFIRMED

--- Comment #3 from tagwer...@innerjoin.org ---
(In reply to tagwerk19 from comment #1)
> ... I would need to check behaviours with mounts "under" $HOME ...
Looks like, If you've an sshfs mount in your home directory:

Baloo will index it ...
Dolphin's recursive search with delve down into it ...

Every day a learning day!

Don't have a feeling for what "people would expect to happen" here but flagging
"Confirmed"

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

[plasmashell] [Bug 458038] Widgets become slightly misplaced (misaligned) after login

2022-10-16 Thread Damian C
https://bugs.kde.org/show_bug.cgi?id=458038

Damian C  changed:

   What|Removed |Added

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

--- Comment #2 from Damian C  ---
(In reply to Nate Graham from comment #1)
> 
> *** This bug has been marked as a duplicate of bug 413645 ***

Hello,

I've seen that in bug 413645 this has been marked as fixed with 5.26.
I am now running 5.26 and I'm afraid this behavior as described in this bug
report persist.
Issuing plasmashell --replace restores the widgets to their intended position
(previous to reboot).

Thank you,

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

[kolourpaint] [Bug 460069] My Color Bar Disapered

2022-10-16 Thread Martin Koller
https://bugs.kde.org/show_bug.cgi?id=460069

--- Comment #7 from Martin Koller  ---
When kolourpaint is not running, remove the file ~/.config/kolourpaintrc
That should show kolourpaint in its default state the next time you start it,
including the colors

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

[kwin] [Bug 460248] plasmashell with high CPU usage in Wayland session

2022-10-16 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=460248

--- Comment #15 from 76montan...@proton.me ---
Solution:

Enable the Middle Click: [_] Paste selected text option on the System Settings
-> Workspace Behavior -> General Behavior KCM.

System Settings -> Workspace Behavior -> General Behavior

Middle Click: [X] Paste selected text




I can confirm as well that this solution works.

After rebooting and logging in again, just sitting idle at the desktop,
everything is back to normal. In the System Monitor, plasmashell shows only
about 1%, and kwin_wayland isn't registering any CPU usage.

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

[kdenlive] [Bug 460003] Incorrect 3D FFT Denoiser variable labeling

2022-10-16 Thread erjiang
https://bugs.kde.org/show_bug.cgi?id=460003

erjiang  changed:

   What|Removed |Added

 Resolution|--- |FIXED
  Latest Commit||https://invent.kde.org/mult
   ||imedia/kdenlive/commit/edde
   ||c8f7eeed78810212aa2911d238b
   ||a4ce2de1d
 Status|REPORTED|RESOLVED

--- Comment #3 from erjiang  ---
Git commit eddec8f7eeed78810212aa2911d238ba4ce2de1d by Eric Jiang.
Committed on 16/10/2022 at 20:34.
Pushed by erjiang into branch 'fftdenoiz-param-names'.

Fix naming of 3D FFT Denoiser parameters

Sigma, amount, block, overlap are the names used by the filter and the
filter's documentation.

M  +8-8data/effects/avfilter/avfilter_fftdnoiz.xml

https://invent.kde.org/multimedia/kdenlive/commit/eddec8f7eeed78810212aa2911d238ba4ce2de1d

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

[kmymoney] [Bug 460554] New: Crashed while working with the app

2022-10-16 Thread Dawid Wróbel
https://bugs.kde.org/show_bug.cgi?id=460554

Bug ID: 460554
   Summary: Crashed while working with the app
Classification: Applications
   Product: kmymoney
   Version: git (master)
  Platform: Other
OS: Other
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kmymoney-de...@kde.org
  Reporter: m...@dawidwrobel.com
  Target Milestone: ---

SUMMARY
I had a ledger open in the background while I was working with another app in
the foreground. I switched back to kmymoney and the app crashed — I believe I
also attempted to move its window, although not sure if this could be related

>From the terminal output:

qt.core.qabstractitemmodel.checkindex: Index
QModelIndex(-1,-1,0x0,QObject(0x0)) is not valid (expected valid)
ASSERT: "checkIndex(index, CheckIndexOption::IndexIsValid)" in file
/Users/cromo/Documents/Sourcecode/vcpkg/buildtrees/qt5-base/src/5.15.6-98c6389ac2.clean/src/corelib/itemmodels/qconcatenatetablesproxymodel.cpp,
line 192

The error message is quite vague, I'm reporting it nonetheless to see if I can
reproduce it.

SOFTWARE/OS VERSIONS
macOS: 12.6
KDE Frameworks Version: 5.98
Qt Version: 5.15.6

ADDITIONAL INFORMATION

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

[kolourpaint] [Bug 460069] My Color Bar Disapered

2022-10-16 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=460069

--- Comment #8 from nevatro...@gmail.com ---
i'm on linux, where do i find the file

On Sun, Oct 16, 2022 at 3:13 PM Martin Koller 
wrote:

> https://bugs.kde.org/show_bug.cgi?id=460069
>
> --- Comment #7 from Martin Koller  ---
> When kolourpaint is not running, remove the file ~/.config/kolourpaintrc
> That should show kolourpaint in its default state the next time you start
> it,
> including the colors
>
> --
> You are receiving this mail because:
> You reported the bug.

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

[digikam] [Bug 460555] New: Result of drag and drop of a thumbnail in Windows (URI or Windows path)

2022-10-16 Thread husch
https://bugs.kde.org/show_bug.cgi?id=460555

Bug ID: 460555
   Summary: Result of drag and drop of a thumbnail in Windows (URI
or Windows path)
Classification: Applications
   Product: digikam
   Version: 7.8.0
  Platform: Microsoft Windows
OS: Microsoft Windows
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: digikam-bugs-n...@kde.org
  Reporter: hugo-schou...@outlook.com
  Target Milestone: ---

SUMMARY
***
You can drag and drop a thumbnail to another program (e.g. Paint, VLC, Blender,
…). Some programs understand the generated URI from Digikam eg
File:///my-dir/my-file.
Some programs however (eg Blender)  need a genuine Windows file path
(c:\my-dir\my-file).
Can a setting be provided to choose between a URI or a common Windows path?
***


STEPS TO REPRODUCE
Drag & drop a thumbnail into a program such as Microsoft Word or Blender Video
Sequence Editor.

OBSERVED RESULT
A URI such as File:///my-dir/my-file

EXPECTED RESULT
A common windows path

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

ADDITIONAL INFORMATION

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

[kmymoney] [Bug 460556] New: Crahsed when clicking bugdets or viewing accounts

2022-10-16 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=460556

Bug ID: 460556
   Summary: Crahsed when clicking bugdets or viewing accounts
Classification: Applications
   Product: kmymoney
   Version: 5.1.1
  Platform: Debian testing
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kmymoney-de...@kde.org
  Reporter: ryan9...@yahoo.com
  Target Milestone: ---

Application: kmymoney (5.1.1)

Qt Version: 5.15.4
Frameworks Version: 5.98.0
Operating System: Linux 5.19.0-2-amd64 x86_64
Windowing System: X11
Distribution: Debian GNU/Linux bookworm/sid
DrKonqi: 5.25.5 [KCrashBackend]

-- Information about the crash:
Opened Kmymoney and when I clicked budgets programed crashed. Appears to be
related to a recent update, don't recall this happening a week ago.

The crash can be reproduced every time.

-- Backtrace:
Application: KMyMoney (kmymoney), signal: Segmentation fault

[KCrash Handler]
#4  0x7fb969cd6070 in QList::at (i=0, this=0x0) at
/usr/include/x86_64-linux-gnu/qt5/QtCore/qlist.h:542
#5  AccountsViewProxyModel::filterAcceptsColumn (this=,
source_column=0, source_parent=...) at
/home/ryan/Downloads/kmymoney-5.1.1/kmymoney/widgets/accountsviewproxymodel.cpp:73
#6  0x7fb967a7e77e in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7fb967a88504 in
QSortFilterProxyModel::setSourceModel(QAbstractItemModel*) () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7fb969cd232f in KMyMoneyAccountTreeView::init (this=0x558c6ace2c70,
view=view@entry=View::Budget) at
/home/ryan/Downloads/kmymoney-5.1.1/kmymoney/widgets/kmymoneyaccounttreeview.cpp:182
#9  0x7fb9540b420a in KBudgetViewPrivate::init
(this=this@entry=0x558c6a49ac80) at
/home/ryan/Downloads/kmymoney-5.1.1/kmymoney/plugins/views/budget/kbudgetview_p.h:141
#10 0x7fb9540aec18 in KBudgetView::showEvent (this=0x558c6a52c240,
event=0x7ffdf6526830) at
/home/ryan/Downloads/kmymoney-5.1.1/kmymoney/plugins/views/budget/kbudgetview.cpp:59
#11 0x7fb9687a4cb8 in QWidget::event(QEvent*) () from
/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#12 0x7fb968762f4e in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#13 0x7fb967ab1618 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /lib/x86_64-linux-gnu/libQt5Core.so.5
#14 0x7fb9687a18e3 in QWidgetPrivate::show_helper() () from
/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#15 0x7fb9687a1849 in QWidgetPrivate::showChildren(bool) () from
/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#16 0x7fb9687a18bf in QWidgetPrivate::show_helper() () from
/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#17 0x7fb9687a4823 in QWidgetPrivate::setVisible(bool) () from
/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#18 0x7fb968789300 in QStackedLayout::setCurrentIndex(int) () from
/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#19 0x7fb96893ca90 in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#20 0x7fb967ae89dc in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#21 0x7fb968919ffe in QTabBar::currentChanged(int) () from
/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#22 0x7fb9689208d5 in QTabBar::mousePressEvent(QMouseEvent*) () from
/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#23 0x7fb9687a4cb8 in QWidget::event(QEvent*) () from
/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#24 0x7fb968762f4e in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#25 0x7fb96876b4f2 in QApplication::notify(QObject*, QEvent*) () from
/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#26 0x7fb967ab1618 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /lib/x86_64-linux-gnu/libQt5Core.so.5
#27 0x7fb9687695fe in QApplicationPrivate::sendMouseEvent(QWidget*,
QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool, bool) ()
from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#28 0x7fb9687bdac8 in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#29 0x7fb9687c0e50 in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#30 0x7fb968762f4e in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#31 0x7fb967ab1618 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /lib/x86_64-linux-gnu/libQt5Core.so.5
#32 0x7fb967f3d625 in
QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*)
() from /lib/x86_64-linux-gnu/libQt5Gui.so.5
#33 0x7fb967f11ddc in
QWindowSystemInterface::sendWindowSystemEvents(QFlags)
() from /lib/x86_64-linux-gnu/libQt5Gui.so.5
#34 0x7fb95df93e4a in ?? () from /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#35 0x7fb9623da739 in g_main_context_dispatch () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#36 0x7fb9623da9c8 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#37 0x7fb9623daa5c in g

[digikam] [Bug 460520] [FEATURE REQUEST] Ignore rest of not tagged faces in picture

2022-10-16 Thread Maik Qualmann
https://bugs.kde.org/show_bug.cgi?id=460520

Maik Qualmann  changed:

   What|Removed |Added

  Latest Commit||https://invent.kde.org/grap
   ||hics/digikam/commit/d60d31f
   ||7e010f22d738dc2cf753b17b023
   ||de8252
   Version Fixed In||8.0.0
 Resolution|DUPLICATE   |FIXED

--- Comment #2 from Maik Qualmann  ---
Git commit d60d31f7e010f22d738dc2cf753b17b023de8252 by Maik Qualmann.
Committed on 16/10/2022 at 20:57.
Pushed by mqualmann into branch 'master'.

add function to mark all unknown faces as ignored in the preview
Related: bug 457461
FIXED-IN: 8.0.0

M  +2-2NEWS
M  +17   -3core/app/views/preview/itempreviewview.cpp
M  +15   -0core/utilities/facemanagement/items/facegroup.cpp
M  +5-0core/utilities/facemanagement/items/facegroup.h

https://invent.kde.org/graphics/digikam/commit/d60d31f7e010f22d738dc2cf753b17b023de8252

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

[digikam] [Bug 457461] Ability to ignore all faces except tag marked

2022-10-16 Thread Maik Qualmann
https://bugs.kde.org/show_bug.cgi?id=457461

Maik Qualmann  changed:

   What|Removed |Added

  Latest Commit||https://invent.kde.org/grap
   ||hics/digikam/commit/d60d31f
   ||7e010f22d738dc2cf753b17b023
   ||de8252
 Resolution|--- |FIXED
 Status|REPORTED|RESOLVED
   Version Fixed In||8.0.0

--- Comment #2 from Maik Qualmann  ---
Git commit d60d31f7e010f22d738dc2cf753b17b023de8252 by Maik Qualmann.
Committed on 16/10/2022 at 20:57.
Pushed by mqualmann into branch 'master'.

add function to mark all unknown faces as ignored in the preview
Related: bug 460520
FIXED-IN: 8.0.0

M  +2-2NEWS
M  +17   -3core/app/views/preview/itempreviewview.cpp
M  +15   -0core/utilities/facemanagement/items/facegroup.cpp
M  +5-0core/utilities/facemanagement/items/facegroup.h

https://invent.kde.org/graphics/digikam/commit/d60d31f7e010f22d738dc2cf753b17b023de8252

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

[kolourpaint] [Bug 460069] My Color Bar Disapered

2022-10-16 Thread Martin Koller
https://bugs.kde.org/show_bug.cgi?id=460069

--- Comment #9 from Martin Koller  ---
~/.config/kolourpaintrc

~ is an abbreviation for your home directory.
Assume your login name is nevatron12 then your home directory is most likely
/home/nevatron12 so the file
is then /home/nevatron12/.config/kolourpaintrc

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

[krita] [Bug 460557] New: Selection content deleted after transform but remains on screen until canvas area is "refreshed"

2022-10-16 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=460557

Bug ID: 460557
   Summary: Selection content deleted after transform but remains
on screen until canvas area is "refreshed"
Classification: Applications
   Product: krita
   Version: 5.0.2
  Platform: Kubuntu
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Tools/Transform
  Assignee: krita-bugs-n...@kde.org
  Reporter: ecen.cronze...@gmail.com
  Target Milestone: ---

Created attachment 152913
  --> https://bugs.kde.org/attachment.cgi?id=152913&action=edit
Krita System Information for Kubuntu

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. Draw a line and a triangle.
2. Use the freehand selection tool (select with hotkey) to select the triangle. 
3. Select the transform tool (select with hotkey) and do multiple transforms to
the selection (rotation, scaling and translation).
4. Press enter to apply the transformations. Note that the selection lines
jumps here.
5. Select freehand selection tool (select with hotkey) and click on the canvas
to remove selection.
6. Draw on top of the transformed triangle. Note that the triangle lines are
disappearing around newly drawn lines.
7. "Refresh" the canvas by hiding and unhiding the layer to reveal that the
entire selection has actually disappeared.

OBSERVED RESULT
The content in the selected area has disappeared. In step 6, drawing new lines
on top of the triangle causes white squares around the new lines to be removed
from the old triangle lines.

EXPECTED RESULT
The selected area is transformed.

SOFTWARE/OS VERSIONS
Windows: Windows 10
Linux/KDE Plasma: Kubuntu, Manjaro KDE Edition

ADDITIONAL INFORMATION
Video here: https://www.youtube.com/watch?v=rBUyZqPR1pE

The video is from Kubuntu Linux using Krita 5.0.2 (the latest snap). But I have
the same issue on Windows with Krita 5.0.0 and 5.1.0, and on Manjaro Linux
using Krita 5.0.2 and 5.1.0. I have had this issue since the I tried the Krita
5.0 beta on my then new 4k screen.

In step 4, only translation does not trigger the bug, but any other set of
transforms often does. Multiple transforms seems to almost always trigger it.

Undoing (ctrl+z) to undo the transformation makes the deleted content
re-appear.

Workaround: Between step 4 and 5, draw a line inside the selection, the undo
the line. Now the bug will usually not happen (transforms succeeds maybe 80% of
the time), but still happens occasionally. When that happens, undo the
transform, do it again and retry the workaround.

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

[krita] [Bug 460557] Selection content deleted after transform but remains on screen until canvas area is "refreshed"

2022-10-16 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=460557

--- Comment #1 from ecen.cronze...@gmail.com ---
Created attachment 152914
  --> https://bugs.kde.org/attachment.cgi?id=152914&action=edit
Krita Usage Log for the session recorded in video

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

[frameworks-kconfig] [Bug 460260] On a multi screen setup on Wayland, KDE app windows do not remember the size they had if the primary monitor is not the leftmost one.

2022-10-16 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=460260

indecisiveautoma...@gmail.com changed:

   What|Removed |Added

 CC||indecisiveautomator@gmail.c
   ||om

--- Comment #3 from indecisiveautoma...@gmail.com ---
My leftmost monitor is my primary monitor and this is affecting me as well.

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

[kwin] [Bug 448567] [Wayland] Text in Overview effect for desktops list and window titles is blocky on scaled displays

2022-10-16 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=448567

--- Comment #10 from indecisiveautoma...@gmail.com ---
Unfortunately still present in 5.26.0, though other similar issues were fixed
for my specific use-case (blurry and blocky text has been fixed almost
everywhere else throughout Plasma on 5.26).

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

[kwin] [Bug 454067] [wayland] Some System Settings text appears blocky when opened on scaled display until it is moved to a non-scaled display and back again

2022-10-16 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=454067

--- Comment #4 from indecisiveautoma...@gmail.com ---
The behaviour is changed slightly in 5.26.

If you open Info Center from Kickoff, it looks fine. But if you view About this
System from the System Settings, it looks blocky until you move it between
displays.

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

[konqueror] [Bug 379771] konqueror crashed for a particular address

2022-10-16 Thread przxqgl
https://bugs.kde.org/show_bug.cgi?id=379771

--- Comment #19 from przxqgl  ---
(In reply to Stefano Crocco from comment #18)
> (In reply to przxqgl from comment #17)
> > well, my version of konqueror has a "settings" menu, but i don't know how to
> > get to a "General tab of Konqueror settings dialog", so you'll have to do a
> > better job of telling me what you want.
> From the "Settings" menu, choose the "Configure Konqueror" entry to display
> the settings dialog. On the left, there's a tree (I'm working from memory,
> as this dialog has changed much in more recent versions of Konqueror). In
> these trees there's at least one, but most likely two "General" entries: you
> need the first (which should be, if I remember correctly, under the "Web
> behavior" entry). Clicking on it will display in the right side of the
> dialog a page with several configuration options: the third is labeled
> "Default web browser engine" (or something very similar). You should check
> what is selected for that option. Another way to do the same is opening any
> web page, then going to the "View" menu, choosing the "View mode" submenu
> and looking at the checked entry.

on my version of konqueror (version 5.0.97), when i select "Configure
Konqueror" from the "Settings" menu, i do not get a tree on the left. i get
selections for "Performance" and "Bookmarks" on the left: the choices for
"Performance" are "Preload an instance after desktop startup" and "Always try
to have one preloaded instance". the selections for "Bookmarks" are "Number of
columns to show", "Show folder backgrounds", "Show bookmarks without folder",
"Flatten bookmarks tree", "Show system places" and settings for a "Pixmap
Cache"...

i am not sure what to do next.

> Another thing you can check (which I forgot in my last answer) are the
> settings in the "KDE Performance" page of the settings dialog. You can
> access it as described above: the page is one of the first in the tree on
> the left (I think the second one). Ensure that both entries in the page
> ("Preload an instance after desktop startup" and "Always try to have one
> preloaded instance") are unchecked. These options were quite broken in old
> versions of Konqueror and could lead to strange behaviors.

when i select "Configure Konqueror" from the "Settings" menu, in the
"Performance" section, "Always try to have one preloaded instance" was checked.
i unchecked it. "Preload an instance after desktop startup" was not checked,
and i left it that way.

> A simpler,
> but less complete test, is to ensure that Konqueror isn't running (to do so,
> from a terminal run `killall konqueror`), then rename he file
> ~/.config/konquerorrc and the directory ~/.local/share/konqueror to
> something else (for example, ~/.config/konquerorrc_old and
> ~/.local/share/konqueror_old): this will reset your Konqueror configuration
> to the default values. You can then try running Konqueror again and see
> whether you have the same problems or not. If things not work correctly,
> there was something broken in your configuration files.

using this method, the problems are the same as originally reported.

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

[kwin] [Bug 448565] [Wayland] Overview effect does not animate on other displays when a desktop is clicked

2022-10-16 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=448565

--- Comment #2 from indecisiveautoma...@gmail.com ---
It would be nice if this was fixed in a future release of Plasma. It isn't
critical but clicking on another display and having all other displays just
suddenly "pop" onto the other desktop is a bit jarring

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

[Spectacle] [Bug 451838] [wayland] Rectangle Select displays notifications on top

2022-10-16 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=451838

--- Comment #2 from indecisiveautoma...@gmail.com ---
Still present in 5.26.0. I tested Plasma X11 5.23.5 on my Steam Deck and the
issue is not present there.

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

[plasmashell] [Bug 451259] Desktop Context Menu text is pixelated until interacted with on scaled displays

2022-10-16 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=451259

--- Comment #3 from indecisiveautoma...@gmail.com ---
Still affecting me on Plasma 5.26.0

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

[kwin] [Bug 456555] Dragging windows across monitors sometimes makes them invisible until you let go of them

2022-10-16 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=456555

--- Comment #2 from indecisiveautoma...@gmail.com ---
This is fixed in Plasma 5.26.0

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

[gwenview] [Bug 448011] [Wayland] Gwenview crashes when trying to crop

2022-10-16 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=448011

--- Comment #4 from indecisiveautoma...@gmail.com ---
This is still fixed in Plasma 5.26.0 stable.

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

[kmymoney] [Bug 460554] Crashed while working with the app

2022-10-16 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=460554

Bug Janitor Service  changed:

   What|Removed |Added

   Severity|normal  |crash

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

[frameworks-baloo] [Bug 460460] Baloo lies about its status when writing to its database

2022-10-16 Thread Adam Fontenot
https://bugs.kde.org/show_bug.cgi?id=460460

--- Comment #6 from Adam Fontenot  ---
(In reply to tagwerk19 from comment #5)
> (In reply to Adam Fontenot from comment #4)
> > (In reply to tagwerk19 from comment #3)
> > ... there are a million Baloo bugs for i/o thrashing, memory
> > use, hanging on specific files, incorrect indexing, etc...
> OK :-/
> 
> I'd say though that my experience triaging reports is that the number
> reported has settled down *remarkably* over the last two years. Older
> versions of baloo that are disappearing as people update their distro's.
> Maybe also that I/O load is not so visible with SSD's.
Sorry, I didn't mean to be saucy about it. I certainly appreciate the amount of
effort that's gone into improving Baloo and understand that it's not easy work.
"Millions" was obviously an exaggeration.

It's just that Baloo is the one component of KDE in which I encounter
show-stopping bugs, over and over again. Other components are at least working
well enough that I can "dogfood" and improve them. Baloo I'm forced to keep
disabled; once a year or so I give it a try to see if things are better.
Judging by user reports on places like the KDE subreddit, I don't think my
experience is too far from the norm:
https://old.reddit.com/r/kde/search?q=baloo&restrict_sr=on You'll find reports
here that are hair-raising to say the least.

I do think file name search (Baloo with content indexing disabled) has gotten
better; I managed to have it enabled the last few months with not too much
trouble... before the combination of Bug 460509 and Bug 437754 forced me to
disable it again.

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

[frameworks-baloo] [Bug 437754] "balooctl status" can trigger high memory use

2022-10-16 Thread Adam Fontenot
https://bugs.kde.org/show_bug.cgi?id=437754

Adam Fontenot  changed:

   What|Removed |Added

 CC||adam.m.fontenot+kde@gmail.c
   ||om

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

[kwin] [Bug 460404] [Regression]: Kwin 5.26.0 uses software renderer instead of GLX

2022-10-16 Thread Simon Vogl
https://bugs.kde.org/show_bug.cgi?id=460404

Simon Vogl  changed:

   What|Removed |Added

 CC||simon.v...@gmx.net

--- Comment #1 from Simon Vogl  ---
Can confirm this on my desktop system, RTX 2070 Super + i9-9900K

It seems like the automatic detection of what render to use is broken, because
if I go to the "Plasma-Renderer" app and manually change the output module to
"OpenGL" hardware-accelerated rendering works completely fine and the
performance regression is gone.

Does anyone have an idea as to why OGL detection might be broken on at least
some NVIDIA GPUs in 5.26?

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

[frameworks-baloo] [Bug 437754] "balooctl status" can trigger high memory use

2022-10-16 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=437754

tagwer...@innerjoin.org changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|REPORTED|CONFIRMED

--- Comment #6 from tagwer...@innerjoin.org ---
Flagging as Confirmed on the basis of Bug 460460

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

[kstars] [Bug 460558] New: I can't solve any object because the telescope coordinates are fixed and never change

2022-10-16 Thread Eduard
https://bugs.kde.org/show_bug.cgi?id=460558

Bug ID: 460558
   Summary: I can't solve any object because the telescope
coordinates are fixed and never change
Classification: Applications
   Product: kstars
   Version: 3.6.1
  Platform: Mint (Ubuntu based)
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: mutla...@ikarustech.com
  Reporter: valldor...@gmail.com
  Target Milestone: ---

Created attachment 152915
  --> https://bugs.kde.org/attachment.cgi?id=152915&action=edit
Image of the Solver Control screen showing the immovable numbers 23 and 180.

Hello

I'm working with Kstars V 3.6.1 stable in Linux mint and an LX200

The problem I have is when I want to use the Solver Control because when I look
for a star and I center it in the telescope and in kstars, the same numbers
always appear in telescope coordinates 23:56:00 and 180:00:00. And they are
always fixed.

I have connected first the telescope and then kstars, then the other way around
and I have changed the star. And I've tried all the combinations.

But the numbers I have written are fixed and do not change. They never change
when changing celestial objects. For this reason it is not possible to solve
any object 

STEPS TO REPRODUCE
1. 
2. 
3. 

OBSERVED RESULT


EXPECTED RESULT

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

[okular] [Bug 436742] Involuntary scrolling when annotations encounter edge of page

2022-10-16 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=436742

Bug Janitor Service  changed:

   What|Removed |Added

 Status|CONFIRMED   |ASSIGNED

--- Comment #3 from Bug Janitor Service  ---
A possibly relevant merge request was started @
https://invent.kde.org/graphics/okular/-/merge_requests/664

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

[kwin] [Bug 455507] Overview effect search box almost always causes hard system lockup

2022-10-16 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=455507

--- Comment #16 from indecisiveautoma...@gmail.com ---
This is still affecting me in Plasma 5.26.0, however the behaviour has changed
slightly it seems like.

The first time I tested this again today, a few seconds after the lockup,
Plasma restarted itself. The screen went black, then my wallpapers showed up,
then my panels. So I tried entering some text into the search box again, and
Plasma froze *with the Overview effect open* - Previously, it would only freeze
when the Overview effect closed.

I restarted my machine and tested three more times, but I could not reproduce
Plasma restarting itself. I guess Plasma restarting itself was a fluke, but
I'll be testing into the future and I'll see if I can reproduce that behaviour
again.

So the lockup still occurs, and KRunner is still fine, but now the lockup can
occur whilst still in the Overview effect.

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

[plasmashell] [Bug 459774] Make "resident" notifications the default.

2022-10-16 Thread Naxdy
https://bugs.kde.org/show_bug.cgi?id=459774

--- Comment #18 from Naxdy  ---
(In reply to Carlos Solís from comment #17)
> Regarding the implementation, I was under the impression that the hints
> boolean values, which include the "resident" and "transient" values, worked
> like this:
> 
> - Resident: the notification is not dismissed until the user manually closes
> it. Similar to permanent notifications on Android.
> - Transient: the notification is automatically dismissed and furthermore, is
> not stored in the tray when it times out.
> 
> Our issue currently comes with the behavior for the default case (no
> resident hint, no transient hint either), which seems to be left up to each
> implementation as per the specs. (See
> https://specifications.freedesktop.org/notification-spec/notification-spec-
> latest.html#hints ). They explicitly state that "Neither clients nor
> notification servers are required to support any hints". However, besides of
> these boolean values there's also the urgency level, which does include a
> recommended implementation cue - regarding critical urgency notifications,
> "They should only be closed when the user dismisses them, for example, by
> clicking on the notification."

That's correct. I do apologize for the confusion, because the problem I've
outlined isn't actually that notifications aren't "resident" by default
(although this would solve the problem at the cost of producing others), but
simply that they lose their interactive functionalities once the popup
disappears and they are stored in history only.

Resident notifications aren't expired the same way "normal" notifications are,
which is why they keep their interactive features - therefore I initially
thought making all notifications resident should be the default behavior.

The implementation I've submitted seeks to establish a middle-ground of sorts,
by initially treating "resident" notifications and those with interactive
features the same way: To not formally "expire" them when the popup is gone,
but rather mark them expired, so the popup disappears, but the notification is
technically kept open.

The treatment of notifications then differs: Resident notifications are kept
open no matter how many times a user interacts with them (as was the case
before), but regular notifications are then properly expired (because most seem
to lose their functionality after one interaction anyway). This then also
causes any interactive buttons in the history to disappear (since they would
lose functionality anyway most of the time).

There is currently one situation in which this would produce an unexpected
result however: If the application that fired an interactive notification (e.g.
Discord) is closed before the notification has been interacted with, the
interaction would of course not produce any results, since there is no client
to handle the event.

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

[kde] [Bug 459670] Cursor theme changes to Adwaita when interacting with GTK applications

2022-10-16 Thread Guillaume Castagnino
https://bugs.kde.org/show_bug.cgi?id=459670

--- Comment #4 from Guillaume Castagnino  ---
(In reply to jamesxmcintosh from comment #2)
> (In reply to Paul from comment #1)
> > Does anyone have a workable temporary fix for this until the issue is
> > resolved?
> 
> Try editing/creating: /usr/share/icons/default/index.theme
> 
> Add this:
> [Icon Theme]
> Inherits=Oxygen_White

Indeed, this workaround is working. Thank’s a lot.

It looks like it’s a recent regression since very few times. Maybe since kde
frameworks 5.98. But not really sure about this. This is my best guess
considering my upgrade history

Currently still having the issue with:
Operating System: Gentoo Linux 2.9
KDE Plasma Version: 5.26.0
KDE Frameworks Version: 5.99.0
Qt Version: 5.15.5
Kernel Version: 6.0.2-gentoo (64-bit)
Graphics Platform: X11

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

[kdeconnect] [Bug 460559] New: "Night Mode" is not detected as Dark theme

2022-10-16 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=460559

Bug ID: 460559
   Summary: "Night Mode" is not detected as Dark theme
Classification: Applications
   Product: kdeconnect
   Version: unspecified
  Platform: Android
OS: Android 9.x
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: android-application
  Assignee: albertv...@gmail.com
  Reporter: stde...@gmail.com
  Target Milestone: ---

Samsung S8 has this "Night Mode" feature, akin to "Dark Theme". 

Sadly, KDE Connect does not detect the "system default" to be a dark theme, and
instead uses the Light Theme. 

Device has Android 9 version.

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

[KScreen] [Bug 460560] New: Primary monitor to becomes disabled when secondary monitor is plugged in

2022-10-16 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=460560

Bug ID: 460560
   Summary: Primary monitor to becomes disabled when secondary
monitor is plugged in
Classification: Plasma
   Product: KScreen
   Version: 5.26.0
  Platform: Archlinux
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: common
  Assignee: kscreen-bugs-n...@kde.org
  Reporter: chriswhitlock...@gmail.com
  Target Milestone: ---

SUMMARY
***
I have a dual monitor setup using an xorg.conf that has never been a problem,
but after an update, my primary monitor does not work, and KDE ignores my
/etc/X11/xorg.conf and everything in /etc/X11/xorg.conf.d/. The primary monitor
is listed as "Disabled" under System Settings > Hardware > Display and Monitor
> Display Configuration and, after login, only shows a black screen for about
half a second before going to sleep, while the secondary monitor becomes the
only working monitor. Enabling the monitor and hitting "Apply" just makes it
show a black screen briefly again before going back to sleep. The same happens
when using the nvidia-settings GUI to try to do the same thing, or running
xrandr. If I only have one monitor plugged in, then either works fine
***


STEPS TO REPRODUCE
1. Enable KScreen 2 under System Settings > Workspace > Startup and Shutdown >
Background Services
2. 
3. 

OBSERVED RESULT

Only my secondary monitor works, while the primary one becomes "Disabled", only
shows a black screen, and goes to sleep a second or two after login.

EXPECTED RESULT

Dual monitor setup functioning normally with both screens working and aligned
properly.

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

ADDITIONAL INFORMATION

Distro: Arch 
Kernel: 5.15.74-1-lts
GPU: Nvidia RTX 2060 Super
GPU Drivers: nvidia-lts 1:520.56.06-4
Monitor 1: Asus VG27AQ 2560x1440 165hz
Monitor 2: Dell ST2410 1920x1080 60hz
Display Manager: sddm 0.19.0-8

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

[kwin] [Bug 460258] Heavy graphical glitches when letting XWayland applications scale themselves

2022-10-16 Thread kskot
https://bugs.kde.org/show_bug.cgi?id=460258

--- Comment #4 from kskot <288pat0...@mailcatch.com> ---
Turns out the glitches only appear when the display is scaled to something
higher than 100%. With 75% scaling or 100% scaling no bugs are present.

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

[gwenview] [Bug 459478] [FR] please allow to disable/resize the Description field, it takes half of screen unnecessarily

2022-10-16 Thread Alex
https://bugs.kde.org/show_bug.cgi?id=459478

Alex  changed:

   What|Removed |Added

 Status|REPORTED|ASSIGNED
 CC||schwimmbe...@gmail.com
 Ever confirmed|0   |1

--- Comment #1 from Alex  ---
Yes, I see what you mean, that is unnecessarily large. I think it would be nice
to have a splitter let you grab that divider line in the middle of the sidebar,
letting you move that up and down. (And it should remember where it last was,
too...)
I think I can implement that, it'd be a fun first patch for gwenview on my end.

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

[Discover] [Bug 458531] Discover crashed in FlatpakBackend::findSource() after click on 'Installed'

2022-10-16 Thread Aleix Pol
https://bugs.kde.org/show_bug.cgi?id=458531

--- Comment #10 from Aleix Pol  ---
Sorry Patrick, wrong instructions.

My patch wasn't meant to fix it but to add some debug information that should
help us nail down where the problem is coming from. Can you run it from the
terminal and see what the messages I added say?

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

[neon] [Bug 415130] Lock and login screens: entering incorrect password or moving focus away breaks using return/enter key to submit password

2022-10-16 Thread Nick
https://bugs.kde.org/show_bug.cgi?id=415130

--- Comment #66 from Nick  ---
Same problem in this version too:
Operating System: KDE neon 5.26
KDE Plasma Version: 5.26.0
KDE Frameworks Version: 5.98.0
Qt Version: 5.15.6
Kernel Version: 5.15.0-50-generic (64-bit)
Graphics Platform: X11
Processors: 20 × 12th Gen Intel® Core™ i7-12700H
Memory: 15.3 GiB of RAM
Graphics Processor: Mesa Intel® Graphics
Manufacturer: Novatech
Product Name: NP5x_NP6x_NP7xPNP
System Version: Not Applicable

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

[plasma-systemmonitor] [Bug 460561] New: Memory leak

2022-10-16 Thread Onyx
https://bugs.kde.org/show_bug.cgi?id=460561

Bug ID: 460561
   Summary: Memory leak
Classification: Plasma
   Product: plasma-systemmonitor
   Version: 5.26.0
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: ksysguard-b...@kde.org
  Reporter: onyx...@gmail.com
CC: ahiems...@heimr.nl, plasma-b...@kde.org
  Target Milestone: ---

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

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.  Leave system monitor going for a long period
2. 
3. 

OBSERVED RESULT


EXPECTED RESULT


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

ADDITIONAL INFORMATION

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

[systemsettings] [Bug 460103] Margins for headers in System Settings tabs differs for different components.

2022-10-16 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=460103

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

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

[plasma-systemmonitor] [Bug 460561] Memory leak

2022-10-16 Thread Onyx
https://bugs.kde.org/show_bug.cgi?id=460561

Onyx  changed:

   What|Removed |Added

 CC||onyx...@gmail.com

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

[systemsettings] [Bug 460103] Margins for headers in System Settings tabs differs for different components.

2022-10-16 Thread Ismael Asensio
https://bugs.kde.org/show_bug.cgi?id=460103

--- Comment #4 from Ismael Asensio  ---
Git commit c4a60bfd5d8ede30808b3312857226727bd3c84f by Ismael Asensio.
Committed on 16/10/2022 at 19:51.
Pushed by iasensio into branch 'master'.

AbstractPageHeader: reduce minimum title left padding

The current minimum left padding for the title text (when there
are no other UI elements, like navigation tools) is set `gridUnit`,
which can be a huge amount (18px on default settings) and is not
comparable with that of the QtWidgets equivalent.

Reduce this value to `largeSpacing`, which also aligns better with
the contents within the page

M  +2-2src/controls/private/globaltoolbar/AbstractPageHeader.qml

https://invent.kde.org/frameworks/kirigami/commit/c4a60bfd5d8ede30808b3312857226727bd3c84f

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

[kmymoney] [Bug 460562] New: Unable to import 'C:/Users/rodho/Downloads/EXPORT (1).OFX' using the OFX importer plugin. The plugin returned the following error: Unable to parse file

2022-10-16 Thread Rodney
https://bugs.kde.org/show_bug.cgi?id=460562

Bug ID: 460562
   Summary: Unable to import 'C:/Users/rodho/Downloads/EXPORT
(1).OFX' using the OFX importer plugin. The plugin
returned the following error: Unable to parse file
Classification: Applications
   Product: kmymoney
   Version: 5.1.3
  Platform: Microsoft Windows
OS: Microsoft Windows
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kmymoney-de...@kde.org
  Reporter: r...@gci.net
  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. Unable to import 'C:/Users/rodho/Downloads/EXPORT (1).OFX' using the OFX
importer plugin. The plugin returned the following error:
Unable to parse file
2. 
3. 

OBSERVED RESULT


EXPECTED RESULT


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

ADDITIONAL INFORMATION

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

[kwin] [Bug 460553] Kwin crashes in Plasma 5.26 if xdg-desktop-portal-gnome is installed and running and you attempt to screen share or use OBS

2022-10-16 Thread p d
https://bugs.kde.org/show_bug.cgi?id=460553

--- Comment #1 from p d  ---
I upgraded to Fedora 37 KDE with KDE 5.26 from the kdesig copr and now it seems
to crash for a different reason (when attempting to record screen in OBS on
Wayland):

Oct 16 19:09:08 fedora-t580 kwin_wayland_wrapper[4491]: No provider of
eglQueryDmaBufModifiersEXT found.  Requires one of:
Oct 16 19:09:08 fedora-t580 kwin_wayland_wrapper[4491]:   
EGL_EXT_image_dma_buf_import_modifiers

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

[plasmashell] [Bug 460415] Digital Clock 5.26: font too tiny to read

2022-10-16 Thread rb
https://bugs.kde.org/show_bug.cgi?id=460415

--- Comment #9 from rb  ---
Created attachment 152918
  --> https://bugs.kde.org/attachment.cgi?id=152918&action=edit
fixed.png

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

[plasmashell] [Bug 460415] Digital Clock 5.26: font too tiny to read

2022-10-16 Thread rb
https://bugs.kde.org/show_bug.cgi?id=460415

--- Comment #8 from rb  ---
Hi nate,

Just FYI the solution was simple. (with Arch back on the machine with 
the 5.26 upgrade),  I simply removed the digital clock in the panel and 
replaced it and then reconfigured the custom date format.  The font now 
scales when the panel height is deceased/increased.  The panel 
configuration files in my home directory must have caused the issue but 
in all fairness, this has never happened any Plasma ugrades with 
versions 5.18 thru 5.25. It seems like breakage to me even though the 
solution was simple. The user does not expect that the previous digital 
clock in the panel should be broken after an upgrade and logging back in 
again.  No other elements on the desktop configuration was not affected.

Thanks again, Rob.


On 10/14/22 3:40 PM, Nate Graham wrote:
> https://bugs.kde.org/show_bug.cgi?id=460415
>
> Nate Graham  changed:
>
> What|Removed |Added
> 
> Keywords||regression
>  Version|unspecified |5.26.0
>Component|general |Digital Clock
> Assignee|unassigned-b...@kde.org  |plasma-b...@kde.org
>   CC||n...@kde.org
>  Product|kde |plasmashell
> Target Milestone|--- |1.0
>   Resolution|--- |WAITINGFORINFO
>   Status|REPORTED|NEEDSINFO
>
> --- Comment #2 from Nate Graham  ---
> I'm going to have to ask you to upgrade again so we can debug a bit. After
> you've done that, please attach screenshots of:
> 1. How it looks when it's not readable
> 2. The "Appearance" page of the settings window for the Digital Clock that's
> got too-small text
>
> Also, what is your panel's thickness set to?
>

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

[kdenlive] [Bug 459429] The "scratchlines" effect does not work on Windows

2022-10-16 Thread erjiang
https://bugs.kde.org/show_bug.cgi?id=459429

erjiang  changed:

   What|Removed |Added

Summary|The "scratchlines" effect   |The "scratchlines" effect
   |does not work   |does not work on Windows

--- Comment #4 from erjiang  ---
It looks like the oldfilm/lines effect is generating invalid X positions on
Windows, which get saved into the XML. For example, on Linux it may generate a
reasonable value like line5=920px, while on Windows it may generate
line5=92142796. It may be a bug in MLT, but not sure.

I tested and was able to reproduce on Windows standalone 22.08.1. Because the
generated random numbers are saved in the XML, opening a project with
scratchlines created on Linux will work fine.

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

[kalarm] [Bug 460389] After 08.10.2020 Kalarm, Korganizer, Calendar dont work correctly.

2022-10-16 Thread David Jarvie
https://bugs.kde.org/show_bug.cgi?id=460389

--- Comment #15 from David Jarvie  ---
When you downgraded libical, no other packages should have been changed. There
are evidently missing dependencies, which should not have happened when just
libical was supposed to have been changed. I'm not familiar with the package
system on Manjaro/ArchLinux, so I can't help with how to do it correctly, but
it looks like you must have used a wrong command or something.

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

[digikam] [Bug 460555] Result of drag and drop of a thumbnail in Windows (URI or Windows path)

2022-10-16 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=460555

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

   What|Removed |Added

  Component|general |Usability-Drag&Drop
 CC||caulier.gil...@gmail.com

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

[krita] [Bug 459899] Add a selection mode (similar to eraser mode) for brushes so that you can easily paint on the selections

2022-10-16 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=459899

--- Comment #5 from rave...@o2.pl ---
(In reply to Deif Lou from comment #4)
> You can use the "Show global selection mask"
> action/shortcut/button-in-the-toolbar to activate/deactivate the global
> selection and paint on it. The effect is very similar to what you propose.

It's not the same though and it's clunky (you have to have the selection mask
layer selected, for example, also it's based on the color value - the lighter
the color, the stronger the selection, instead of the alpha, meaning that you'd
need to switch to white if you want to paint on selection)

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

[plasmashell] [Bug 460513] Plasmashell crashes on Wayland

2022-10-16 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=460513

--- Comment #5 from space9...@proton.me ---
I managed to generate a backtrace by recompiling the plasma-workspace package
with options=(debug !strip), and using
gdb -p $(pidof plasmashell) --command=debug-script

debug-script:
```set logging file plasmashell.gdb
set logging enabled

break checkWaylandError(wl_display*)
continue
# backtrace
bt

# generate coredump
gcore
```

(I identified the source of the message "The Wayland connection broke. Did the
Wayland compositor die?" with `strings --print-file-name *.so* | grep -i
'compositor die?'`, traced it to libQt5WaylandClient.so, and
downloaded+searched the source for that string. 
The function is
https://github.com/qt/qtwayland/blob/2303ee38ead0a4eafa9f8af629fd8495c45d1442/src/client/qwaylanddisplay.cpp#L66
static void checkWaylandError(struct wl_display *display))


Thread 1 "plasmashell" hit Breakpoint 1, checkWaylandError
(display=0x55b3ab934160) at
/usr/src/debug/qtwayland/src/client/qwaylanddisplay.cpp:91
91  {
#0  checkWaylandError(wl_display*) (display=0x55b3ab934160) at
/usr/src/debug/qtwayland/src/client/qwaylanddisplay.cpp:91
#1  0x7fb211122b7c in QtWaylandClient::EventThread::readAndDispatchEvents()
(this=)
at /usr/src/debug/qtwayland/src/client/qwaylanddisplay.cpp:141
#2  QtWaylandClient::QWaylandDisplay::flushRequests() (this=) at
/usr/src/debug/qtwayland/src/client/qwaylanddisplay.cpp:419
#3  0x7fb2106b0520 in QObject::event(QEvent*) () at
/usr/lib/libQt5Core.so.5
#4  0x7fb211378b1c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /usr/lib/libQt5Widgets.so.5
#5  0x7fb21068cb88 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at /usr/lib/libQt5Core.so.5
#6  0x7fb21068d693 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () at /usr/lib/libQt5Core.so.5
#7  0x7fb2106d3728 in  () at /usr/lib/libQt5Core.so.5
#8  0x7fb20ed1981b in g_main_context_dispatch () at
/usr/lib/libglib-2.0.so.0
#9  0x7fb20ed6fec9 in  () at /usr/lib/libglib-2.0.so.0
#10 0x7fb20ed180d2 in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#11 0x7fb2106d750c in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#12 0x7fb21068532c in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#13 0x7fb21068fe59 in QCoreApplication::exec() () at
/usr/lib/libQt5Core.so.5
#14 0x55b3ab3521a3 in main(int, char**) (argc=,
argv=) at
/usr/src/debug/plasma-workspace-5.26.0/shell/main.cpp:233
warning: Memory read failed for corefile section, 4096 bytes at
0xff60.
Saved corefile core.158040

I'm not sure how useful this is.

I also recompiled+installed the package qt5-wayland, which may explain the
source file in the backtrace
#0  checkWaylandError(wl_display*) (display=0x55b3ab934160) at
/usr/src/debug/qtwayland/src/client/qwaylanddisplay.cpp:91
instead of a binary
#3  0x7fb2106b0520 in QObject::event(QEvent*) () at
/usr/lib/libQt5Core.so.5

I don't know which way is preferred for debugging.

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

[kwin] [Bug 460336] kwin_wayland lockup / black screen / clients disconnected

2022-10-16 Thread Jason Playne
https://bugs.kde.org/show_bug.cgi?id=460336

Jason Playne  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|WAITINGFORINFO  |DUPLICATE

--- Comment #8 from Jason Playne  ---


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

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

[plasmashell] [Bug 460513] Plasmashell crashes on Wayland

2022-10-16 Thread Jason Playne
https://bugs.kde.org/show_bug.cgi?id=460513

--- Comment #6 from Jason Playne  ---
*** Bug 460336 has been marked as a duplicate of this bug. ***

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

[plasmashell] [Bug 460415] Digital Clock 5.26: font too tiny to read

2022-10-16 Thread rb
https://bugs.kde.org/show_bug.cgi?id=460415

--- Comment #10 from rb  ---
Hey nate,

On a final note:

I have found the exact cause of the issue.  The 
/home/$user/.config/plasma-org.kde.plasma.desktop-appletsrc file 
contained this under Appearance [ ] section for the digital clock applet:

[Containments][2][Applets][21][Configuration][Appearance]
autoFontAndSize=false   ( <<< https://bugs.kde.org/show_bug.cgi?id=460415
>
> Nate Graham  changed:
>
> What|Removed |Added
> 
> Keywords||regression
>  Version|unspecified |5.26.0
>Component|general |Digital Clock
> Assignee|unassigned-b...@kde.org |plasma-b...@kde.org
>   CC||n...@kde.org
>  Product|kde |plasmashell
> Target Milestone|--- |1.0
>   Resolution|--- |WAITINGFORINFO
>   Status|REPORTED|NEEDSINFO
>
> --- Comment #2 from Nate Graham  ---
> I'm going to have to ask you to upgrade again so we can debug a bit. After
> you've done that, please attach screenshots of:
> 1. How it looks when it's not readable
> 2. The "Appearance" page of the settings window for the Digital Clock that's
> got too-small text
>
> Also, what is your panel's thickness set to?
>

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

[amarok] [Bug 348244] Embed Lyrics aren't readed and saved at all (regression)

2022-10-16 Thread Justin Zobel
https://bugs.kde.org/show_bug.cgi?id=348244

Justin Zobel  changed:

   What|Removed |Added

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

--- Comment #3 from Justin Zobel  ---
Thank you for reporting this bug in KDE software. As it has been a while since
this issue was reported, can we please ask you to see if you can reproduce the
issue with a recent software version?

If you can reproduce the issue, please change the status to "CONFIRMED" when
replying. Thank you!

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

[konqueror] [Bug 350032] can't select the youtube search bar

2022-10-16 Thread Justin Zobel
https://bugs.kde.org/show_bug.cgi?id=350032

Justin Zobel  changed:

   What|Removed |Added

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

--- Comment #1 from Justin Zobel  ---
Thank you for reporting this bug in KDE software. As it has been a while since
this issue was reported, can we please ask you to see if you can reproduce the
issue with a recent software version?

If you can reproduce the issue, please change the status to "CONFIRMED" when
replying. Thank you!

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

[amarok] [Bug 342092] Space (%20) appended to the end of search strings passed to populate function of service scripts

2022-10-16 Thread Justin Zobel
https://bugs.kde.org/show_bug.cgi?id=342092

Justin Zobel  changed:

   What|Removed |Added

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

--- Comment #2 from Justin Zobel  ---
Thank you for reporting this bug in KDE software. As it has been a while since
this issue was reported, can we please ask you to see if you can reproduce the
issue with a recent software version?

If you can reproduce the issue, please change the status to "CONFIRMED" when
replying. Thank you!

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

[amarok] [Bug 327918] Statistic synchronisation leaves some of the tracks unmatched

2022-10-16 Thread Justin Zobel
https://bugs.kde.org/show_bug.cgi?id=327918

Justin Zobel  changed:

   What|Removed |Added

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

--- Comment #17 from Justin Zobel  ---
Thank you for reporting this bug in KDE software. As it has been a while since
this issue was reported, can we please ask you to see if you can reproduce the
issue with a recent software version?

If you can reproduce the issue, please change the status to "CONFIRMED" when
replying. Thank you!

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

[knotes] [Bug 343505] find feature gives no results

2022-10-16 Thread Justin Zobel
https://bugs.kde.org/show_bug.cgi?id=343505

Justin Zobel  changed:

   What|Removed |Added

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

--- Comment #4 from Justin Zobel  ---
Thank you for reporting this bug in KDE software. As it has been a while since
this issue was reported, can we please ask you to see if you can reproduce the
issue with a recent software version?

If you can reproduce the issue, please change the status to "CONFIRMED" when
replying. Thank you!

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

[calligrawords] [Bug 316292] Problem inserting large image

2022-10-16 Thread Justin Zobel
https://bugs.kde.org/show_bug.cgi?id=316292

Justin Zobel  changed:

   What|Removed |Added

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

--- Comment #3 from Justin Zobel  ---
Thank you for reporting this bug in KDE software. As it has been a while since
this issue was reported, can we please ask you to see if you can reproduce the
issue with a recent software version?

If you can reproduce the issue, please change the status to "CONFIRMED" when
replying. Thank you!

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

[kmahjongg] [Bug 345474] not making matches, piece notresponding

2022-10-16 Thread Justin Zobel
https://bugs.kde.org/show_bug.cgi?id=345474

Justin Zobel  changed:

   What|Removed |Added

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

--- Comment #1 from Justin Zobel  ---
Thank you for reporting this bug in KDE software. As it has been a while since
this issue was reported, can we please ask you to see if you can reproduce the
issue with a recent software version?

If you can reproduce the issue, please change the status to "CONFIRMED" when
replying. Thank you!

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

[konqueror] [Bug 343185] konqueror, open box are same size that konqueror window

2022-10-16 Thread Justin Zobel
https://bugs.kde.org/show_bug.cgi?id=343185

Justin Zobel  changed:

   What|Removed |Added

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

--- Comment #3 from Justin Zobel  ---
Thank you for reporting this bug in KDE software. As it has been a while since
this issue was reported, can we please ask you to see if you can reproduce the
issue with a recent software version?

If you can reproduce the issue, please change the status to "CONFIRMED" when
replying. Thank you!

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

[kdelibs] [Bug 299710] HTML5 Drag and drop doesn't work in Facebook's Words With Friends in rekonq.

2022-10-16 Thread Justin Zobel
https://bugs.kde.org/show_bug.cgi?id=299710

Justin Zobel  changed:

   What|Removed |Added

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

--- Comment #6 from Justin Zobel  ---
Thank you for reporting this bug in KDE software. As it has been a while since
this issue was reported, can we please ask you to see if you can reproduce the
issue with a recent software version?

If you can reproduce the issue, please change the status to "CONFIRMED" when
replying. Thank you!

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

[kmines] [Bug 352060] KMines uses uninitialized value MineFieldItem:m_cellSize on startup

2022-10-16 Thread Justin Zobel
https://bugs.kde.org/show_bug.cgi?id=352060

Justin Zobel  changed:

   What|Removed |Added

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

--- Comment #1 from Justin Zobel  ---
Thank you for reporting this bug in KDE software. As it has been a while since
this issue was reported, can we please ask you to see if you can reproduce the
issue with a recent software version?

If you can reproduce the issue, please change the status to "CONFIRMED" when
replying. Thank you!

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

[amarok] [Bug 329574] Amarok seems not to update the iPOD database when adding or removing songs

2022-10-16 Thread Justin Zobel
https://bugs.kde.org/show_bug.cgi?id=329574

Justin Zobel  changed:

   What|Removed |Added

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

--- Comment #14 from Justin Zobel  ---
Thank you for reporting this bug in KDE software. As it has been a while since
this issue was reported, can we please ask you to see if you can reproduce the
issue with a recent software version?

If you can reproduce the issue, please change the status to "CONFIRMED" when
replying. Thank you!

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

[amarok] [Bug 339618] Playback stops after changing position in a track

2022-10-16 Thread Justin Zobel
https://bugs.kde.org/show_bug.cgi?id=339618

Justin Zobel  changed:

   What|Removed |Added

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

--- Comment #8 from Justin Zobel  ---
Thank you for reporting this bug in KDE software. As it has been a while since
this issue was reported, can we please ask you to see if you can reproduce the
issue with a recent software version?

If you can reproduce the issue, please change the status to "CONFIRMED" when
replying. Thank you!

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

[kiten] [Bug 353581] Kanji overlaps hiragana in search results

2022-10-16 Thread Justin Zobel
https://bugs.kde.org/show_bug.cgi?id=353581

Justin Zobel  changed:

   What|Removed |Added

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

--- Comment #2 from Justin Zobel  ---
Thank you for reporting this bug in KDE software. As it has been a while since
this issue was reported, can we please ask you to see if you can reproduce the
issue with a recent software version?

If you can reproduce the issue, please change the status to "CONFIRMED" when
replying. Thank you!

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

[kdelibs] [Bug 342394] Trash when browsing FTP misfunctions

2022-10-16 Thread Justin Zobel
https://bugs.kde.org/show_bug.cgi?id=342394

Justin Zobel  changed:

   What|Removed |Added

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

--- Comment #1 from Justin Zobel  ---
Thank you for reporting this bug in KDE software. As it has been a while since
this issue was reported, can we please ask you to see if you can reproduce the
issue with a recent software version?

If you can reproduce the issue, please change the status to "CONFIRMED" when
replying. Thank you!

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

[calligrawords] [Bug 345656] No undo action for adding/removing header or footer

2022-10-16 Thread Justin Zobel
https://bugs.kde.org/show_bug.cgi?id=345656

Justin Zobel  changed:

   What|Removed |Added

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

--- Comment #1 from Justin Zobel  ---
Thank you for reporting this bug in KDE software. As it has been a while since
this issue was reported, can we please ask you to see if you can reproduce the
issue with a recent software version?

If you can reproduce the issue, please change the status to "CONFIRMED" when
replying. Thank you!

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

[calligrawords] [Bug 353540] Calligra Words does not render Nafees Urdu fonts properly

2022-10-16 Thread Justin Zobel
https://bugs.kde.org/show_bug.cgi?id=353540

Justin Zobel  changed:

   What|Removed |Added

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

--- Comment #4 from Justin Zobel  ---
Thank you for reporting this bug in KDE software. As it has been a while since
this issue was reported, can we please ask you to see if you can reproduce the
issue with a recent software version?

If you can reproduce the issue, please change the status to "CONFIRMED" when
replying. Thank you!

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

[kdelibs] [Bug 315321] kde4_add_app_icon search breaks when more than one set of icon is present

2022-10-16 Thread Justin Zobel
https://bugs.kde.org/show_bug.cgi?id=315321

Justin Zobel  changed:

   What|Removed |Added

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

--- Comment #1 from Justin Zobel  ---
Thank you for reporting this bug in KDE software. As it has been a while since
this issue was reported, can we please ask you to see if you can reproduce the
issue with a recent software version?

If you can reproduce the issue, please change the status to "CONFIRMED" when
replying. Thank you!

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

[kdelibs] [Bug 207184] Message appears that application failed to start, though application window appears

2022-10-16 Thread Justin Zobel
https://bugs.kde.org/show_bug.cgi?id=207184

Justin Zobel  changed:

   What|Removed |Added

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

--- Comment #17 from Justin Zobel  ---
Thank you for reporting this bug in KDE software. As it has been a while since
this issue was reported, can we please ask you to see if you can reproduce the
issue with a recent software version?

If you can reproduce the issue, please change the status to "CONFIRMED" when
replying. Thank you!

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

<    1   2   3   4   5   >