[kdeconnect] [Bug 450135] kio crash after a send file stopped by lack of wifi signal and tried to send it again

2023-03-03 Thread Eric Seynaeve
https://bugs.kde.org/show_bug.cgi?id=450135

Eric Seynaeve  changed:

   What|Removed |Added

 CC||e...@seynaeve.be

--- Comment #2 from Eric Seynaeve  ---
I had the same problem this morning. Send 14 files. Transfer stopped on file 3.

Resending crashed KDE connect.

Removing the (partial) transferred files caused the upload of the same files to
succeed.

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

[dolphin] [Bug 466814] New: dolphin rename file selects part of the extension when name contains composed glyphs (diacritics, emojis)

2023-03-03 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=466814

Bug ID: 466814
   Summary: dolphin rename file selects part of the extension when
name contains composed glyphs (diacritics, emojis)
Classification: Applications
   Product: dolphin
   Version: 22.08.2
  Platform: Other
OS: Other
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: view-engine: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: kdeb...@toeai.com
CC: kfm-de...@kde.org
  Target Milestone: ---

SUMMARY
Dolphin improperly counts characters when attempting to select everything but
the ".ext".

STEPS TO REPRODUCE
1. Make a file named "épée.txt"
[NB: each é is composed of U+0065 (lowercase letter e) plus U+0301 (combining
acute accent).  The filename does NOT use the precomposed character U+00E9.]
2. Select the file and hit F2 (or right-click and select Rename...)

OBSERVED RESULT
Dolphin selects "épée.t"

EXPECTED RESULT
Dolphin should select "épée"

SOFTWARE/OS VERSIONS
Kubuntu 22.10
KDE Plasma Version: 5.25.5
KDE Frameworks Version: 5.98.0
Qt Version: 5.15.6

ADDITIONAL INFORMATION

Second example, but with emojis:
"zz❤️❤️.txt" (NB: each of the two hearts is composed of U+2764 followed by
U+FE0F)

Without looking at the code, I'm guessing someone did something naive like
QTextCursor.movePosition() by a certain number of characters.  The programmer
should understanding that Qt counts cursor positions in QChar (always 16-bit,
so sometimes partial characters), however movePosition jumps over
composed/joined characters as a unit, so neither setPosition() nor
movePosition() are suitable for placing the cursor at a given character offset.
 You must first encode the string you want to select as utf-16 and divide the
resulting length in bytes by 2.  This number is what you use to determine a
QChar offset which can be passed to setPosition.

[If done right, that should put you in front of the period (.) which is safe
enough.  In other contexts, you would want to also make sure that your moving
by x number of characters doesn't land you in the middle of a composed glyph. 
You can do that by using movePosition to advance 1 character and then again to
go back 1 character.  If you weren't in the middle of a glyph, this doesn't
move you, but if you were, it safely puts you in front of whatever you were
in.]

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

[Powerdevil] [Bug 466808] Powerdevil repeatedly crashes when logged in via xorgrdp session

2023-03-03 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=466808

--- Comment #2 from tagwer...@innerjoin.org ---
(In reply to tagwerk19 from comment #1)
> ... I think the same as Bug 466697
and maybe Bug 466620

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

[KScreen] [Bug 460341] On X11 with proprietary NVIDIA GPU drivers, external monitor disabled after reboot or wake-from-sleep

2023-03-03 Thread Sebastian Turzański
https://bugs.kde.org/show_bug.cgi?id=460341

--- Comment #161 from Sebastian Turzański  ---
For me 5.27.2 still does not work as expected
at least I can reproduce 100% times the bug i reported
https://bugs.kde.org/show_bug.cgi?id=466208 so It might be a separate one?
Maybe worth to reopen 466208?

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

[plasmashell] [Bug 448833] Overlapping entries when filtering and deleting and filtering again several times

2023-03-03 Thread Sebastian Turzański
https://bugs.kde.org/show_bug.cgi?id=448833

--- Comment #12 from Sebastian Turzański  ---
It might be related to clipboard containing copy-paste from Calc Spreadsheet
where text contains tabs and line breaks? Just a guess

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

[Powerdevil] [Bug 466697] Permanent crashes of Powerdevil at launch in a VNC session

2023-03-03 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=466697

--- Comment #7 from tagwer...@innerjoin.org ---
Possibly should be reopened as it affects a different group of systems (X11 and
not Wayland, there's a backtrace included in Bug 466808)...

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

[Discover] [Bug 466813] New: Can't find Snap-only applications from the "All Applications" page

2023-03-03 Thread Mingcong Bai
https://bugs.kde.org/show_bug.cgi?id=466813

Bug ID: 466813
   Summary: Can't find Snap-only applications from the "All
Applications" page
Classification: Applications
   Product: Discover
   Version: 5.27.2
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Snap Backend
  Assignee: plasma-b...@kde.org
  Reporter: jeff...@aosc.io
CC: aleix...@kde.org
  Target Milestone: ---

Created attachment 156987
  --> https://bugs.kde.org/attachment.cgi?id=156987=edit
Snap search issue.

SUMMARY

While attempting to search for an application that is only shipped from Snap
(for instance, Gitea) from the "All Applications" page, Discover returns an
error stating that "'gitea' was not found in the 'All Applications' category"
with a button to "Search in All Categories." Hitting that button returns a
search result.

This issue also occurs when attempting to search from within any categories -
Gitea is listed on Snapcraft under the "Development" category, but searching
for Gitea from said category returns no result, with the same button to search
in "all categories."

Searching from "Home" does not exhibit this issue.  I have attached a screen
recording to better illustrate this issue.

STEPS TO REPRODUCE

1. Open Discover.
2. Click on "All Applications."
3. Search for "Gitea."

OBSERVED RESULT

Discover returns an error stating that "'gitea' was not found in the 'All
Applications' category" with a button to "Search in All Categories." Hitting
that button returns a search result.

EXPECTED RESULT

Gitea should show up as one of the results.

SOFTWARE/OS VERSIONS

Operating System: AOSC OS 10.1.0
KDE Plasma Version: 5.27.2
KDE Frameworks Version: 5.103.0
Qt Version: 5.15.5
Kernel Version: 6.2.1-aosc-main (64-bit)

Flatpak: 1.14.3
Snapd: 2.58.3
snapd-glib: 1.63

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

[neon] [Bug 466254] Error while installing package 'libjpeg.so.8.2.2' - latest release

2023-03-03 Thread Colin Griffith
https://bugs.kde.org/show_bug.cgi?id=466254

--- Comment #2 from Colin Griffith  ---
I should also mention that I'm using the User edition, rather than the Testing
edition.

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

[neon] [Bug 466254] Error while installing package 'libjpeg.so.8.2.2' - latest release

2023-03-03 Thread Colin Griffith
https://bugs.kde.org/show_bug.cgi?id=466254

Colin Griffith  changed:

   What|Removed |Added

 CC||tyna...@gmail.com

--- Comment #1 from Colin Griffith  ---
KDE Neon only recently started packaging its own copy of libjpeg, and ever
since then I've avoided running updates because it keeps wanting to remove
things I don't want it to remove. If I stay on the version of libjpeg that
comes from Ubuntu's packages, the result is having to keep all of these
packages at their old versions:

digikam
digikam-data
gwenview
libjpeg-dev
libjpeg-turbo8
libjpeg-turbo8-dev
libokular5core10
libpoppler-cpp0v5
libpoppler-glib8
libpoppler-qt5-1
libpoppler126
libxsimd-dev
okular
okular-backends
okular-extra-backends
poppler-utils
showfoto

Additionally, because of the way that the packages depend on each other (which
is vastly different in the Neon packages compared to the versions in the Ubuntu
repositories), you can't have a different version of the i386 libraries and the
x86-64 libraries. Since KDE Neon's repositories do not provide an :i386
package, this breaks a number of i386 packages, including Wine. Here are the
packages that need to be removed if I try to upgrade to Neon's libjpeg:

gstreamer1.0-plugins-good:i386
libavcodec-extra58:i386
libgd3:i386
libgdk-pixbuf-2.0-0:i386
libgdk-pixbuf-xlib-2.0-0:i386
libgdk-pixbuf2.0-0:i386
libgphoto2-6:i386
libjpeg-turbo8:i386
libjpeg8
libjpeg8:i386
librsvg2-2:i386
librsvg2-common:i386
libtiff5:i386
libv4l-0:i386
libv4lconvert0:i386
libwine:i386
wine32:i386
libjpeg8-dev

You'll note that libjpeg8 itself is in that list, and that's because libjpeg8
and libjpeg-turbo8 are separate packages, though libjpeg8 seems to mostly exist
so that packages have something to point to if they depend on it, and it in
turn just depends on libjpeg-turbo8. Removing it doesn't seem to cause any harm
directly though; the harm comes from the lack of an i386 package with the same
version number as the x86-64 package.

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

[Powerdevil] [Bug 466808] Powerdevil repeatedly crashes when logged in via xorgrdp session

2023-03-03 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=466808

tagwer...@innerjoin.org changed:

   What|Removed |Added

 CC||tagwer...@innerjoin.org

--- Comment #1 from tagwer...@innerjoin.org ---
(In reply to Alexander Fritz from comment #0)
> STEPS TO REPRODUCE
> 1. Log into system over xrdp using xorg session. 
Thank you for the backtrace, I think the same as Bug 466697...

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

[kwin] [Bug 466812] New: Scroling direction is inconsistent between horizontal and vertical scrolling when using the scroll wheels the mouse

2023-03-03 Thread Manuel Vögele
https://bugs.kde.org/show_bug.cgi?id=466812

Bug ID: 466812
   Summary: Scroling direction is inconsistent between horizontal
and vertical scrolling when using the scroll wheels
the mouse
Classification: Plasma
   Product: kwin
   Version: 5.27.2
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: libinput
  Assignee: kwin-bugs-n...@kde.org
  Reporter: deve...@manuel-voegele.de
  Target Milestone: ---

SUMMARY
When using a mouse that has a dedicated horizontal scroll wheel like the
Lotitech MX Master series has, the scrolling direction of the horizontal and
vertical scrolling is inconsistent.

When "inverted scrolling" is disabled:
Scrolling vertically moves the scrollbar in the same direction as the finger on
the mouse wheel
Scrolling horizontally moves the scrollbar in the *inverted* direction of the
finger movement

Activating "inverted scrolling" switches both options around:
Scrolling vertically moves the scrollbar in the *inverted* direction of the
finger movement
Scrolling horizontally moves the scrollbar in the same direction as the finger
on the mouse wheel

EXPECTED RESULT
When "inverted scrolling" is disabled, both scrolling directions should be
moving the scroll bar in the direction of the finger and when "inverted
scrolling" is enabled, both scroll directions should be moving the scroll bar
in the direction opposed to the finger movement.

I think ideally, there should be dedicated settings for "inverted vertical
scrolling" and "inverted horizontal scrolling" so users can mix and match to
get their ideal scrolling style.

SOFTWARE/OS VERSIONS
Operating System: Arch Linux 
KDE Plasma Version: 5.27.2
KDE Frameworks Version: 5.103.0
Qt Version: 5.15.8
Kernel Version: 6.2.2-zen1-1-zen (64-bit)
Graphics Platform: X11
Processors: 8 × AMD Ryzen 5 3500U with Radeon Vega Mobile Gfx
Memory: 13.5 GiB of RAM
Graphics Processor: AMD Radeon Vega 8 Graphics
Manufacturer: LENOVO
Product Name: 20NFCTO1WW
System Version: ThinkPad E595

ADDITIONAL INFORMATION
I'm using the Logitech MX Master 3s

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

[kdevelop] [Bug 438249] fresh kdevelop build from git master source crashes while importing a project

2023-03-03 Thread Igor Kushnir
https://bugs.kde.org/show_bug.cgi?id=438249

Igor Kushnir  changed:

   What|Removed |Added

 CC||anonymous11oneeleven@gmail.
   ||com

--- Comment #29 from Igor Kushnir  ---
*** Bug 466791 has been marked as a duplicate of this bug. ***

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

[kdevelop] [Bug 466791] Background parser causes crash

2023-03-03 Thread Igor Kushnir
https://bugs.kde.org/show_bug.cgi?id=466791

Igor Kushnir  changed:

   What|Removed |Added

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

--- Comment #2 from Igor Kushnir  ---
The C++ backtrace is the same as in Bug 438249. Marking as a duplicate. The
second backtrace is different and should be logged against kdev-php, which is
most likely the culprit.

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

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

[forum.kde.org] [Bug 466811] CAR TYRES BEDFORD

2023-03-03 Thread ipcarservicesuk
https://bugs.kde.org/show_bug.cgi?id=466811

ipcarservicesuk  changed:

   What|Removed |Added

URL||https://www.ipcarservices.c
   ||o.uk/

--- Comment #1 from ipcarservicesuk  ---
Are you trying to find Bedford's greatest auto tyres? All types of Tyres
Bedford, including summer, winter, all-season, performance, 4x4 and run-flat
tyres, are available at IP Cars Services in Bedford at premium, mid-range, and
low prices.

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

[forum.kde.org] [Bug 466811] New: CAR TYRES BEDFORD

2023-03-03 Thread ipcarservicesuk
https://bugs.kde.org/show_bug.cgi?id=466811

Bug ID: 466811
   Summary: CAR TYRES BEDFORD
Classification: Websites
   Product: forum.kde.org
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: forum-ad...@kde.org
  Reporter: ipcarservice...@gmail.com
  Target Milestone: ---

IP Cars Services is your local family run tyre outlet providing all your car
and van tyres, including new Car Tyres Bedford, van tyres and commercial tyres.

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

[digikam] [Bug 466651] Thumbnails from 16 bit float tif files are displayed very darkly in Digikam

2023-03-03 Thread Maik Qualmann
https://bugs.kde.org/show_bug.cgi?id=466651

--- Comment #7 from Maik Qualmann  ---
By "optimizations" I meant more code quality, but most of that is already done.

Maik

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

[plasmashell] [Bug 466463] Different scaling on HiDpi display for applications in 5.27.1

2023-03-03 Thread Michael Hamilton
https://bugs.kde.org/show_bug.cgi?id=466463

--- Comment #19 from Michael Hamilton  ---
(In reply to Nate Graham from comment #16)
> *** Bug 466506 has been marked as a duplicate of this bug. ***

In answer to the question from Bug 466506: 
> Can you try again with Plasma 5.27.2? We removed some unnecessary font size 
> handling stuff in that bugfix release.

Tumbleweed updated to 5.27.2 didn't help, it's the same as I described in Bug
466506.  

Disabling the GNOME/GTK Settings Synchronisations Service remains an easy
workaround.

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

[kwin] [Bug 466810] text-input-v1 not working with fcitx5 on chromium

2023-03-03 Thread Yiyang Wu
https://bugs.kde.org/show_bug.cgi?id=466810

--- Comment #1 from Yiyang Wu  ---
Created attachment 156986
  --> https://bugs.kde.org/attachment.cgi?id=156986=edit
(weston) logs running chromium with `WAYLAND_DEBUG=1`

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

[kwin] [Bug 466810] New: text-input-v1 not working with fcitx5 on chromium

2023-03-03 Thread Yiyang Wu
https://bugs.kde.org/show_bug.cgi?id=466810

Bug ID: 466810
   Summary: text-input-v1 not working with fcitx5 on chromium
Classification: Plasma
   Product: kwin
   Version: 5.27.2
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: wayland-generic
  Assignee: kwin-bugs-n...@kde.org
  Reporter: xgreenlandfor...@gmail.com
  Target Milestone: ---

Created attachment 156985
  --> https://bugs.kde.org/attachment.cgi?id=156985=edit
logs running chromium with `WAYLAND_DEBUG=1`

Even with text-input-v1 implemented on kwin
(https://invent.kde.org/plasma/kwin/-/merge_requests/3403), `chromium
--enable-features=UseOzonePlatform --ozone-platform=wayland
--enable-wayland-ime` still cannot use fcitx5 to input Chinese (no input box
popup).

This bug is observed on Debian sid, and there's no sign of debian packaging
turning off text-input-v1 feature. Using weston `chromium
--enable-features=UseOzonePlatform --ozone-platform=wayland
--enable-wayland-ime` works without issue, so the bug shouldn't be on
fcitx5/chromium package.

STEPS TO REPRODUCE
1. Install plasma-desktop, kwin_wayland, plasma-workspace-wayland on debian sid
2. `export $(dbus-launch); startplasma-wayland` on tty
3. Start up fcitx5
4. `chromium --enable-features=UseOzonePlatform --ozone-platform=wayland
--enable-wayland-ime`
5. Switch to Chinese input method and type

SOFTWARE/OS VERSIONS
Linux/KDE Plasma
KDE Plasma Version: Debian 5.27.2-1
KDE Frameworks Version: Debian 5.103.0-1
Qt Version: Debian 5.15.8+dfsg-3

The attachment are logs running chromium with `WAYLAND_DEBUG=1`, then choose
the text_input_v1 related information `grep text_input_v1`; for better diff
comparison, timestamps and some numbers are changed to be the same. It can be
seen that weston has more output, generating desired Chinese characters, while
on plasma, it only detects the keyboard action, but not generating input box,
thus cannot type Chinese characters.

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

[kmymoney] [Bug 466809] New: .ofx and .qfx files imported into wrong account

2023-03-03 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=466809

Bug ID: 466809
   Summary: .ofx and .qfx files imported into wrong account
Classification: Applications
   Product: kmymoney
   Version: 5.1.3
  Platform: Microsoft Windows
OS: Microsoft Windows
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: importer
  Assignee: kmymoney-de...@kde.org
  Reporter: m...@ms0.info
  Target Milestone: ---

Created attachment 156984
  --> https://bugs.kde.org/attachment.cgi?id=156984=edit
pdf series of five screenshots showing problem

SUMMARY:  

Background:  I started with version 4.7.2 in approximately 2013.  After a few
years, the previously working account update feature stopped working, first for
American Express, then for every credit card, banking, and brokerage service. 
So I just download .qfx, .ofx, or .csv files from each institution's website
each month one by one into a dedicated separate folder, one per institution,
and import them into KMyMoney.  When I go to import them, the first time,
KMyMoney asks me to pick the account into which to import the first time - then
for all subsequent months, when I choose the downloaded file from its folder,
KMyMoney remembers that the folder from which the file has been downloaded
corresponds to the correct account and imports it without having to navigate
again to the correct account.  After a few years, I added a new Liability
account , credit card type, to the dozen or so I already had.  

BUG#1:  The first time I went to import it, I clicked on the WRONG account. 
Every subsequent month, KMyMoney associates any file in that folder with this
WRONG account when I go to import.  OK, no big deal.  Version 4.7.2 allows me
to click the dropdown arrow and choose the correct account, and imports it into
the correct account.

BUG#2:  On 3/3/2023, I copied my KMyMoney .kmy database to a different
computer, both prior and current computers are Windows10Professional Operating
Systems.  I downloaded the current version 5.1.3 of KMyMoney to my current
computer, opened it, and directed it to open my copied .kmy database.  Then for
the Liability credit card account in question, I downloaded this month's
statement .ofx file, and imported it (I copied the folder into an identical
tree structure as the prior computer).  The new v5.1.3 instance of KMyMoney
dialog box asked into which account I wished the data to be imported (instead
of version 4.7.2 defaulting to the WRONG account it always associates with this
folder), and I navigated to the correct account.  However, KMyMoney imported it
into the same WRONG account as it did on my prior computer.  I have to open the
WRONG account, and select every transaction, right click to move them to the
correct account.  I tried multiple times to choose the correct account from the
drop down list, and version 5.1.3 ignores my selection and imports it into the
WRONG account I mistakenly chose many years ago the first time I imported the
first statement.  Somehow the database is remembering the folder in the tree
structure, and associating it with this WRONG KMyMoney account, and ignoring
the correct account I select from the drop down list.
***
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. 
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.

[kdeconnect] [Bug 461046] Totally can't use in iOS 16.0.3

2023-03-03 Thread Bruce
https://bugs.kde.org/show_bug.cgi?id=461046

--- Comment #19 from Bruce  ---
I think I finally found where the problem from, it's because my iOS system
language is Chinese, I've switched the system language to English, it's normal
now, Kde on my iPhone and Kde on my android(MIUI13.0.11) can discover each
other and can send file to each other.

But it still can not discover soduto(kde client on my macOS), and soduto can
not discover kde on my iPhone too.

But soduto and kde on my android can discover each other and send files to each
other. 

soduto: https://soduto.com/

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

[Powerdevil] [Bug 466808] New: Powerdevil repeatedly crashes when logged in via xorgrdp session

2023-03-03 Thread Alexander Fritz
https://bugs.kde.org/show_bug.cgi?id=466808

Bug ID: 466808
   Summary: Powerdevil repeatedly crashes when logged in via
xorgrdp session
Classification: Plasma
   Product: Powerdevil
   Version: 5.27.2
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: spamfre...@hotmail.com
CC: m...@ratijas.tk
  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. Log into system over xrdp using xorg session. 

OBSERVED RESULT
Powerdevil crashes repeatedly upon logging in remotely using xrdp.  Shows crash
icon in taskbar which disappears and reappears.  Clicking it opens up kde crash
reporter which closes off seconds later.
Functions correctly when logging in locally with same user account.

EXPECTED RESULT
System should log in as normal and not cause the program to crash but function
normally.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Fedora Linux 37 Kernel 6.1.14
(available in About System)
KDE Plasma Version: 5.27.2
KDE Frameworks Version: 5.103.0
Qt Version: 5.15.8

ADDITIONAL INFORMATION

Backtrace using coredumpctl gdb

#0  __pthread_kill_implementation (threadid=,
signo=signo@entry=6, no_tid=no_tid@entry=0) at pthread_kill.c:44
#1  0x7fe1b34afec3 in __pthread_kill_internal (signo=6, threadid=) at pthread_kill.c:78
#2  0x7fe1b345fa76 in __GI_raise (sig=sig@entry=6) at
../sysdeps/posix/raise.c:26
#3  0x7fe1b34497fc in __GI_abort () at abort.c:79
#4  0x7fe1b36d7e80 in std::__glibcxx_assert_fail(char const*, int, char
const*, char const*)
(file=file@entry=0x7fe1a00330a9 "/usr/include/c++/12/optional",
line=line@entry=477, function=function@entry=0x7fe1a00332a0 "constexpr _Tp&
std::_Optional_base_impl<_Tp, _Dp>::_M_get() [with _Tp = bool; _Dp =
std::_Optional_base]",
condition=condition@entry=0x7fe1a0033093 "this->_M_is_engaged()") at
../../../../../libstdc++-v3/src/c++11/debug.cc:60
#5  0x7fe1a0032347 in std::_Optional_base_impl >::_M_get() (this=) at
/usr/include/c++/12/optional:475
#6  std::_Optional_base_impl
>::_M_get() (this=0x5623cee79a90) at /usr/include/c++/12/optional:475
#7  std::optional::operator*() & (this=0x5623cee79a90) at
/usr/include/c++/12/optional:974
#8  KScreen::AbstractDpmsHelper::isSupported() (this=0x5623cee79a80) at
/usr/src/debug/libkscreen-qt5-5.27.2-1.fc37.x86_64/src/libdpms/abstractdpmshelper_p.h:32
#9  KScreen::Dpms::isSupported() const (this=) at
/usr/src/debug/libkscreen-qt5-5.27.2-1.fc37.x86_64/src/libdpms/dpms.cpp:45
#10 0x7fe1b495536f in PowerDevil::ActionPool::init(PowerDevil::Core*)
(this=0x5623cee3b790, parent=parent@entry=0x5623ced32e20) at
/usr/src/debug/powerdevil-5.27.2-1.fc37.x86_64/daemon/powerdevilactionpool.cpp:93
#11 0x7fe1b495cded in PowerDevil::Core::onBackendReady() (this=) at
/usr/src/debug/powerdevil-5.27.2-1.fc37.x86_64/daemon/powerdevilcore.cpp:191
#12 0x7fe1b3cd0e96 in QtPrivate::QSlotObjectBase::call(QObject*, void**)
(a=0x7ffec5743860, r=, this=0x5623cee2e840) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#13 doActivate(QObject*, int, void**) (sender=0x5623cee2efc0,
signal_index=9, argv=0x7ffec5743860) at kernel/qobject.cpp:3923
#14 0x7fe1b3ccbe27 in QMetaObject::activate(QObject*, QMetaObject const*,
int, void**)
(sender=sender@entry=0x5623cee2efc0, m=m@entry=0x7fe1b49828a0
,
local_signal_index=local_signal_index@entry=6, argv=argv@entry=0x0) at
kernel/qobject.cpp:3983
#15 0x7fe1b4953157 in PowerDevil::BackendInterface::backendReady()
(this=this@entry=0x5623cee2efc0)
at
/usr/src/debug/powerdevil-5.27.2-1.fc37.x86_64/redhat-linux-build/daemon/powerdevilcore_autogen/EWIEGA46WW/moc_powerdevilbackendinterface.cpp:385
#16 0x7fe1b4956b90 in
PowerDevil::BackendInterface::setBackendIsReady(QHash const&,
QFlags)
(this=this@entry=0x5623cee2efc0, availableBrightnessControls=...,
supportedSuspendMethods=..., supportedSuspendMethods@entry=...) at
/usr/src/debug/powerdevil-5.27.2-1.fc37.x86_64/daemon/powerdevilbackendinterface.cpp:198
#17 0x7fe1a0422afa in PowerDevilUPowerBackend::initWithBrightness(bool)
(this=, screenBrightnessAvailable=)
at
/usr/src/debug/powerdevil-5.27.2-1.fc37.x86_64/daemon/backends/upower/powerdevilupowerbackend.cpp:284
#18 0x7fe1b3cd0e96 in QtPrivate::QSlotObjectBase::call(QObject*, void**)
(a=0x7ffec5743a70, r=, this=0x5623cee32250) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#19 doActivate(QObject*, int, void**) (sender=0x5623cee2efc0,
signal_index=14, argv=0x7ffec5743a70) at kernel/qobject.cpp:3923
#20 0x7fe1b3ccbe27 in QMetaObject::activate(QObject*, QMetaObject const*,
int, void**)
  

[plasmashell] [Bug 466807] Plasma crash when editing system tray in a panel

2023-03-03 Thread Luis
https://bugs.kde.org/show_bug.cgi?id=466807

--- Comment #1 from Luis  ---
Created attachment 156983
  --> https://bugs.kde.org/attachment.cgi?id=156983=edit
New crash information added by DrKonqi

DrKonqi auto-attaching complete backtrace.

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

[plasmashell] [Bug 466807] New: Plasma crash when editing system tray in a panel

2023-03-03 Thread Luis
https://bugs.kde.org/show_bug.cgi?id=466807

Bug ID: 466807
   Summary: Plasma crash when editing system tray in a panel
Classification: Plasma
   Product: plasmashell
   Version: 5.24.7
  Platform: FreeBSD Ports
OS: FreeBSD
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: ltri...@yahoo.com
CC: k...@davidedmundson.co.uk
  Target Milestone: 1.0

Application: plasmashell (5.24.7)

Qt Version: 5.15.7
Frameworks Version: 5.101.0
Operating System: FreeBSD 13.1-RELEASE-p3 amd64
Windowing System: X11
Distribution (Platform): FreeBSD Ports
DrKonqi: 5.24.7 [KCrashBackend]

-- Information about the crash:
- What I was doing when the application crashed:
Editing the configuration of the system tray settings in the entries menu,
was disabling one of the applications


- Unusual behavior I noticed:
system settings window close on its own, computer freezzed on the desktop
momentarily after a minute or so was able to use the system again.
The small panel that slides from the top when in edit mode for the desktop
freeze and was unresponsive

The reporter is unsure if this crash is reproducible.

-- Backtrace (Reduced):


Possible duplicates by query: bug 466757, bug 466711, bug 466634, bug 466631,
bug 466629.

Reported using DrKonqi

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

[digikam] [Bug 466799] Showfoto/Setup/Misc/Sort images by Name/Reverse ordering: sorts ascending rather than descending.

2023-03-03 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=466799

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

   What|Removed |Added

Summary|showfoto >configure |Showfoto/Setup/Misc/Sort
   |>miscellaneous >sort images |images by Name/Reverse
   |by Name >Reverse ordering   |ordering: sorts ascending
   |>sorts ascending rather |rather than descending.
   |than descending |
   Severity|normal  |wishlist

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

[Spectacle] [Bug 465781] Spectacle doesn't follow image format when copying image

2023-03-03 Thread Unknown
https://bugs.kde.org/show_bug.cgi?id=465781

[object Object]  changed:

   What|Removed |Added

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

--- Comment #6 from [object Object]  ---
I've tried some other apps - QT (neochat, just uses the PNG) and GTK (nautilus,
doesn't let me paste at all), so this might just be issue on the app's side

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

[systemsettings] [Bug 466806] New: [Flatpak Permissions KCM] Clicking on app doesn't show permission settings

2023-03-03 Thread Samuel Reddy
https://bugs.kde.org/show_bug.cgi?id=466806

Bug ID: 466806
   Summary: [Flatpak Permissions KCM] Clicking on app doesn't show
permission settings
Classification: Applications
   Product: systemsettings
   Version: 5.27.2
  Platform: Kubuntu
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: kcm_flatpak
  Assignee: plasma-b...@kde.org
  Reporter: samuelsumukhre...@gmail.com
CC: joshiesuha...@gmail.com
  Target Milestone: ---

SUMMARY
When using the flatpak permission settings in system settings, clicking on a
app does not show the permissions or allow you to change the settings.

STEPS TO REPRODUCE
1. Open system settings
2. Click applications
3. Click on flatpak permission settings
4. Click on an app you want to change the permissions of
5. No page is shown to change the permission or view the permission of the app


OBSERVED RESULT
The page in the kcm to change the permissions does not show up when I click an
app

EXPECTED RESULT
The page to show the permissions and change the permissions should show up when
I click on an app

SOFTWARE/OS VERSIONS
Operating System: Kubuntu 22.10 (With backports PPA)
KDE Plasma Version: 5.27.2
KDE Frameworks Version: 5.103.0
Qt Version: 5.15.6
Kernel Version: 5.19.0-35-generic (64-bit)
Graphics Platform: Wayland
Processors: 12 × AMD Ryzen 5 5600X 6-Core Processor
Memory: 15.5 GiB of RAM
Graphics Processor: NAVI22
Manufacturer: ASUS

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

[kwin] [Bug 465790] Resizing an Aurorae-decorated window leads to malformed decorations

2023-03-03 Thread arbitar
https://bugs.kde.org/show_bug.cgi?id=465790

--- Comment #29 from arbitar  ---
(In reply to Nate Graham from comment #21)
> For people who can still reproduce the issue, can you be specific about what
> scaling settings, window decoration themes, and GPU you're using?

Definitely still happening for me.
Scaling settings: 100% on 3840x2160 60Hz display
Window decoration theme: Reactionary (https://store.kde.org/p/1252059)
GPU: RX 580 (Ellesmere 1002:67df) /w amdgpu on Wayland

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

[digikam] [Bug 466799] showfoto >configure >miscellaneous >sort images by Name >Reverse ordering >sorts ascending rather than descending

2023-03-03 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=466799

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

   What|Removed |Added

  Component|Showfoto-Core   |Showfoto-Setup
 CC||caulier.gil...@gmail.com

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

[krita] [Bug 464255] X11 connection broken on startup.

2023-03-03 Thread Ralek Kolemios
https://bugs.kde.org/show_bug.cgi?id=464255

Ralek Kolemios  changed:

   What|Removed |Added

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

--- Comment #10 from Ralek Kolemios  ---
Recently the latest nightly builds (I've tried 8eccca2) have begun to give the
same or similar error again, so I'll be reopening this bug.

> The X11 connection broke: No error (code 0)
> XIO:  fatal IO error 22 (Invalid argument) on X server ":0"
>   after 481 requests (481 known processed) with 0 events remaining.

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

[frameworks-kio] [Bug 161017] enqueue kio transfer operations

2023-03-03 Thread Ahmed
https://bugs.kde.org/show_bug.cgi?id=161017

--- Comment #26 from Ahmed  ---
This request is so old.

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

[konsole] [Bug 466782] main window placed directly over old window when all toolbars and menubars are disabled

2023-03-03 Thread Antonio Russo
https://bugs.kde.org/show_bug.cgi?id=466782

--- Comment #1 from Antonio Russo  ---
As a workaround, you can set, in the [General] section of ~/.config/konsolerc ,

AllowKDEAppsToRememberWindowPositions=false

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

[kde] [Bug 466379] New KDE is really sluggish

2023-03-03 Thread Rajinder Yadav
https://bugs.kde.org/show_bug.cgi?id=466379

--- Comment #7 from Rajinder Yadav  ---
Created attachment 156982
  --> https://bugs.kde.org/attachment.cgi?id=156982=edit
atop display

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

[kde] [Bug 466379] New KDE is really sluggish

2023-03-03 Thread Rajinder Yadav
https://bugs.kde.org/show_bug.cgi?id=466379

--- Comment #6 from Rajinder Yadav  ---
I've attached a screen shot from atop, don't see anything off.

I also notice now that spectacle also is a slight sluggish, because I could
rapid hit my shortcuts and get screen captures. Now I notice, when I use my
shortcut, there is a slight delay. So if I am fliping threw tab and capturing
something. It will miss something, which was not the case before.

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

[krita] [Bug 466794] Unable to edit Basic-1 in Brush Editor

2023-03-03 Thread Tiar
https://bugs.kde.org/show_bug.cgi?id=466794

Tiar  changed:

   What|Removed |Added

 Resolution|--- |NOT A BUG
 CC||tamtamy.tym...@gmail.com
 Status|REPORTED|RESOLVED

--- Comment #1 from Tiar  ---
It is actually working correctly. Krita's brushes are categorized in so called
"engines", every engine has different code and different set of options.
Basic-1 brush uses "Quick engine" (you can see the lighting bolt underneath the
brush preset name), which has very limited set of options to make super extra
fast (you can make it very big and it will still be nearly instant). If you
want to have more options, just edit a brush like Basic-2 Opacity, just disable
the Opacity being affected by Pressure to have the same effect as on Basic-1.
You can also unhide the left panel of the brush editor and press the [+] button
underneath all brushes, and choose "Pixel", that will create a new brush preset
for you that you can edit and save.

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

[kalendar] [Bug 466805] New: kalendar fails to start

2023-03-03 Thread Luis
https://bugs.kde.org/show_bug.cgi?id=466805

Bug ID: 466805
   Summary: kalendar fails to start
Classification: Applications
   Product: kalendar
   Version: 22.12.0
  Platform: Other
OS: FreeBSD
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: claudio.cam...@kde.org
  Reporter: ltri...@yahoo.com
CC: c...@carlschwan.eu
  Target Milestone: ---

Created attachment 156981
  --> https://bugs.kde.org/attachment.cgi?id=156981=edit
Automated bug subrutine crasher

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. Start Kalendar from application launcher
2. Start Kalendar from terminal
3. Start Kalendar from terminal issuing the following comand: dbus-launch
kalendar

OBSERVED RESULT
1. Kalendar initiates but fails to start with out producing any errors or
messages
2. Kalendar fails to launch from terminal and reports the following error on
screen:
kf.dbusaddons: Couldn't register name 'org.kde.kalendarac' with DBUS - another
process owns it already!
3. Kalendar fails to launch and crashes using the dbus launch. Attached crash
log. Besides crashing, then the application is locking kmail to access the
akonadi service, my best guest, since Kmail stops to work


EXPECTED RESULT
Kalendar application launches


SOFTWARE/OS VERSIONS
FreeBSD /KDE Plasma: 13.1-p3
(available in About System)
KDE Plasma Version:  5.24.7
KDE Frameworks Version: 5.101.0
Qt Version: 5.15.7

ADDITIONAL INFORMATION
Graphics platform: X11, 1.21.1.4
Reviewed some of the related bugs IDS: 446805 and 453016.  446805 seems to be
specific to ARCH linux, so not aplicable in this case. Bug ID 453016 suggest to
install kdepim-runtime as a solution. That is already installed on my machine,
version 22.12.0

Thanks,

Luis

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

[plasmashell] [Bug 465177] Taskbar crashes opening Gimp

2023-03-03 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=465177

Bug Janitor Service  changed:

   What|Removed |Added

 Resolution|BACKTRACE   |WORKSFORME
 Status|NEEDSINFO   |RESOLVED

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

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

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

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

[plasma-integration] [Bug 466804] New: OpacityMask feature in QML broken rendering apps unusable

2023-03-03 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=466804

Bug ID: 466804
   Summary: OpacityMask feature in QML broken rendering apps
unusable
Classification: Plasma
   Product: plasma-integration
   Version: 5.27.2
  Platform: Archlinux
OS: Linux
Status: REPORTED
  Severity: major
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: benmorde...@protonmail.com
  Target Milestone: ---

Created attachment 156980
  --> https://bugs.kde.org/attachment.cgi?id=156980=edit
Opacity Mask Failure

Examples of problem apps are Kasts and Nextcloud Desktop Client. Opacity mask
fails to work causing opaque rectangles to obscure the program's important
content. Initially filed bug report to Kasts
(https://bugs.kde.org/show_bug.cgi?id=466274) but discovered that same problem
shows up in other apps. With both Nextcloud and Kasts I was able to disable the
opacity mask in the source code and prove the content was there but covered by
an opaque rectangle. 

The Nextcloud AppImage does not have the bug, but the official repositories do. 

Discussion and troubleshooting steps on the Arch Linux here: bbs:
https://bbs.archlinux.org/viewtopic.php?id=283774

Other apps like Neochat and Monero Gui also have visual bugs, but I have done
no similar troubleshooting. As mentioned in the Arch bbs post, the visual bug
can also be eliminated by setting QT_QPA_PLATFORMTHEME=gtk3 before executing
kasts.





STEPS TO REPRODUCE
1. Install a program that uses QML OpacityMask
2. Run program


OBSERVED RESULT
Opaque rectangles.

EXPECTED RESULT
Transparent rectangles for proper UI.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 5.27.2
(available in About System)
KDE Plasma Version: 5.27.2
KDE Frameworks Version: 5.103.0
Qt Version: 5.15.8

ADDITIONAL INFORMATION
Exclusive X11 system. Nvidia drivers.

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

[systemsettings] [Bug 465931] kde setup crash

2023-03-03 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=465931

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

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

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

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

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

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

[kwin] [Bug 465848] Window decorations are very grainy and the entire system is acting "zoomed in", ie all the window decorations are enlarged all the widows are enlarged, the docks are enlarged etc.

2023-03-03 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=465848

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

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

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

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

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

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

[Spectacle] [Bug 461432] Spectacle takes screenshot of ghost screen

2023-03-03 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=461432

Bug Janitor Service  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED

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

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

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

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

[systemsettings] [Bug 465152] Steam deck Dr Konqi crash

2023-03-03 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=465152

Bug Janitor Service  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |WORKSFORME
 Status|NEEDSINFO   |RESOLVED

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

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

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

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

[okular] [Bug 368758] Grayscale option ignored when generating print data for PDF document

2023-03-03 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=368758

Bug Janitor Service  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|WAITINGFORINFO  |WORKSFORME

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

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

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

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

[plasmashell] [Bug 465823] Brave Icons wrong & Webapp Icons Missing

2023-03-03 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=465823

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

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

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

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

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

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

[Spectacle] [Bug 465781] Spectacle doesn't follow image format when copying image

2023-03-03 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=465781

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

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

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

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

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

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

[frameworks-plasma] [Bug 465690] When using wayland, Popup dialogs show up in the middle, or middle/bottom of the desktop

2023-03-03 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=465690

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

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

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

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

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

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

[Tokodon] [Bug 465056] Tokodon crash when opening "conversation"

2023-03-03 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=465056

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

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

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

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

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

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

[NeoChat] [Bug 463538] NeoChat Flatpak crashes when logging in on Linux Mint 21.1

2023-03-03 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=463538

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

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

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

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

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

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

[valgrind] [Bug 446236] Issues with Valgrind 3.8.1 version, after compiler upgrade

2023-03-03 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=446236

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

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

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

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

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

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

[systemsettings] [Bug 420866] Hotkeys including the ñ key doesn't work

2023-03-03 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=420866

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

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

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

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

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

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

[plasmashell] [Bug 452660] Random Plasma crashes caused by `reuseItems: true` in DelegateModel

2023-03-03 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=452660

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

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

[systemsettings] [Bug 465951] No visual indicator to show that checkboxes have focus

2023-03-03 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=465951

Nate Graham  changed:

   What|Removed |Added

  Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas
   |ma/flatpak-kcm/commit/00ed5 |ma/flatpak-kcm/commit/09dc8
   |9163d416c88f9410802853e4ecd |ccce3dc1f2b57a7d4d38f9e4111
   |cb06bbd8|b8af3c0a

--- Comment #5 from Nate Graham  ---
Git commit 09dc8ccce3dc1f2b57a7d4d38f9e4111b8af3c0a by Nate Graham.
Committed on 04/03/2023 at 03:24.
Pushed by ngraham into branch 'Plasma/5.27'.

Re-add default list item highlight

Typically we remove these hover and highlight effects for list items
that arenon-interactive where hover and keyboard navigation don't make
sense.

But that's not the case here; these list items are interactive (clicking
them toggles their checkbox) and therefore keyboard navigation does make
sense.

Accordingly, let's stop removing the default list item hover and
highlight effects to make this interactivity obvious and allow keyboard
navigation to be usable.
FIXED-IN: 5.27.3


(cherry picked from commit 00ed59163d416c88f9410802853e4ecdcb06bbd8)

M  +0-3package/contents/ui/permissions.qml

https://invent.kde.org/plasma/flatpak-kcm/commit/09dc8ccce3dc1f2b57a7d4d38f9e4111b8af3c0a

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

[systemsettings] [Bug 465951] No visual indicator to show that checkboxes have focus

2023-03-03 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=465951

Nate Graham  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|ASSIGNED|RESOLVED
   Version Fixed In||5.27.3
  Latest Commit||https://invent.kde.org/plas
   ||ma/flatpak-kcm/commit/00ed5
   ||9163d416c88f9410802853e4ecd
   ||cb06bbd8

--- Comment #4 from Nate Graham  ---
Git commit 00ed59163d416c88f9410802853e4ecdcb06bbd8 by Nate Graham.
Committed on 04/03/2023 at 03:22.
Pushed by ngraham into branch 'master'.

Re-add default list item highlight

Typically we remove these hover and highlight effects for list items
that arenon-interactive where hover and keyboard navigation don't make
sense.

But that's not the case here; these list items are interactive (clicking
them toggles their checkbox) and therefore keyboard navigation does make
sense.

Accordingly, let's stop removing the default list item hover and
highlight effects to make this interactivity obvious and allow keyboard
navigation to be usable.
FIXED-IN: 5.27.3

M  +0-3package/contents/ui/permissions.qml

https://invent.kde.org/plasma/flatpak-kcm/commit/00ed59163d416c88f9410802853e4ecdcb06bbd8

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

[kde] [Bug 466379] New KDE is really sluggish

2023-03-03 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=466379

--- Comment #5 from benmorde...@protonmail.com ---
I recently had extreme sluggishness on my system which I eventually found via
atop identifying that my SSD disk was very slow because it needed an fstrim.
The report you are giving is very broad which makes it difficult to identify
any culprit.

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

[Discover] [Bug 466742] Show an error in the UI when the external "Software Sources" app can't be launched

2023-03-03 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=466742

Bug Janitor Service  changed:

   What|Removed |Added

 Status|CONFIRMED   |ASSIGNED

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

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

[Haruna] [Bug 456482] hardware decoding doesn't work

2023-03-03 Thread Arthur Kasimov
https://bugs.kde.org/show_bug.cgi?id=456482

Arthur Kasimov  changed:

   What|Removed |Added

 CC||kodemeis...@outlook.com

--- Comment #16 from Arthur Kasimov  ---
Just wanted to note that QT_XCB_GL_INTEGRATION="xcb_egl" works perfectly for me
on discrete graphics (AMD Radeon RX 6700 XT). Without this variable, Haruna
falls back to suboptimal "vaapi-copy" driver instead of proper "vaapi".

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

[Discover] [Bug 466742] Show an error in the UI when the external "Software Sources" app can't be launched

2023-03-03 Thread Aleix Pol
https://bugs.kde.org/show_bug.cgi?id=466742

Aleix Pol  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|REPORTED|CONFIRMED

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

[Haruna] [Bug 466803] New: Haruna doesn't open .TS videos on startup

2023-03-03 Thread Arthur Kasimov
https://bugs.kde.org/show_bug.cgi?id=466803

Bug ID: 466803
   Summary: Haruna doesn't open .TS videos on startup
Classification: Applications
   Product: Haruna
   Version: 0.10.3
  Platform: Archlinux
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: generic
  Assignee: georgefb...@gmail.com
  Reporter: kodemeis...@outlook.com
  Target Milestone: ---

SUMMARY
Haruna doesn't play any .TS videos if I open them from a file manager or supply
them via command line. No picture, no sound. It basically acts as if no videos
were opened at all. However, it does play .TS files well when I use "Open File"
from the app itself.

STEPS TO REPRODUCE
1. Download any .TS file, e.g. from https://filesamples.com/formats/ts
2. Try to open the downloaded file via command line: haruna
~/Videos/sample_1280x720_surfing_with_audio.ts

OBSERVED RESULT
Video is not loaded and played.

EXPECTED RESULT
Playback should start upon startup.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Arch Linux / KDE Plasma on X11
KDE Plasma Version: 5.27.2
KDE Frameworks Version: 5.103.0
Qt Version: 5.15.8

ADDITIONAL INFORMATION
This doesn't seem to be related to https://bugs.kde.org/show_bug.cgi?id=464963
I tried different filenames without fancy characters - no luck. The latest
version from master also has the same issue.

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

[krita] [Bug 466648] Color management issue - docker overview on second display

2023-03-03 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=466648

--- Comment #5 from i...@cgidesign.de ---
(In reply to Halla Rempt from comment #4)
> Dockers are always associated with the canvas from the window they come
> from, so your original question would be really hard to solve. I'm glad you
> found the way we did intend to make it possible to view the same image on
> two monitors. I will close the report.

Ok and thanks.

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

[ksmserver] [Bug 466802] New: Multiple users logout bug wayland

2023-03-03 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=466802

Bug ID: 466802
   Summary: Multiple users logout bug wayland
Classification: Plasma
   Product: ksmserver
   Version: 5.27.2
  Platform: Archlinux
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: mrantonsae...@gmail.com
CC: plasma-b...@kde.org
  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
***
When you log in with multiple users and then try to log out with one of them,
screen stays black with cursor blinking, you can switch tty no problem to
another user, but it's no convenient. If you log out with all users sddm log in
screen appears, like it should.


STEPS TO REPRODUCE
1. Log in with multiple users
2. Log out with one of them

OBSERVED RESULT
Black screen with cursor, keyboard is not responsive

EXPECTED RESULT
New sddm session.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Arch linux
(available in About System)
KDE Plasma Version: 5.27.2
KDE Frameworks Version: 5.103.0
Qt Version: 5.15.8

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

[kde] [Bug 466379] New KDE is really sluggish

2023-03-03 Thread Rajinder Yadav
https://bugs.kde.org/show_bug.cgi?id=466379

--- Comment #4 from Rajinder Yadav  ---
I've checked my disk, memory and CPU.
12 core CPU is 1% load.
62 GB free ram.
4TB free disk space.

I tired opening a few app they seem to be opening fine, much better than when I
created this bug.

Definitely KRunner, it's not as responsive as it was before. Maybe this is it.
I use it to do spell checks, conversions and running apps. The typing just
seems poor. Sometime it misses key-strokes, backspace at odd time are delayed.

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

[kde] [Bug 466379] New KDE is really sluggish

2023-03-03 Thread Rajinder Yadav
https://bugs.kde.org/show_bug.cgi?id=466379

--- Comment #3 from Rajinder Yadav  ---
It's not the system, it's the KDE desktop it is just sluggish. I am doing
nothing out of  the ordinary, happens all the time after. I've done is after a
fresh reboot. It is not as responsive as it was in the past, before all the
recent upgrades?

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

[dolphin] [Bug 466801] New: Setting the app to "automatically open with this app" in dialog doesnt work

2023-03-03 Thread Henning
https://bugs.kde.org/show_bug.cgi?id=466801

Bug ID: 466801
   Summary: Setting the app to "automatically open with this app"
in dialog doesnt work
Classification: Applications
   Product: dolphin
   Version: 22.12.2
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: amanita+kdeb...@mailbox.org
CC: kfm-de...@kde.org
  Target Milestone: ---

SUMMARY
Changing the default app for filetypes seems to not work through the new popup.
It works when using the menu in the systemsettings.


STEPS TO REPRODUCE
1. Open dolphin
2. Open a file not with the default application but choose "other application"
3. Select "always open with" and the wanted application
4. reopen that file, look at what is the default app to open it 
5. Try to set it through systemsettings file associations

OBSERVED RESULT
Setting the default app doesnt work?

EXPECTED RESULT
Setting the default app through the "open with other app" is really useful and
should work 

SOFTWARE/OS VERSIONS
Operating System: Fedora Linux 37
KDE Plasma Version: 5.27.2
KDE Frameworks Version: 5.103.0
Qt Version: 5.15.8
Kernel Version: 6.1.14-200.fc37.x86_64 (64-bit)
Graphics Platform: Wayland

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

[Powerdevil] [Bug 466800] New: power management crashed when attempting to unlock screen with monitor sleeping

2023-03-03 Thread George Avrunin
https://bugs.kde.org/show_bug.cgi?id=466800

Bug ID: 466800
   Summary: power management crashed when attempting to unlock
screen with monitor sleeping
Classification: Plasma
   Product: Powerdevil
   Version: 5.27.2
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: avru...@math.umass.edu
CC: m...@ratijas.tk
  Target Milestone: ---

Application: org_kde_powerdevil (5.27.2)

Qt Version: 5.15.8
Frameworks Version: 5.103.0
Operating System: Linux 6.1.14-200.fc37.x86_64 x86_64
Windowing System: Wayland
Distribution: Fedora Linux 37 (Workstation Edition)
DrKonqi: 5.27.2 [KCrashBackend]

-- Information about the crash:
kf5-plasma-5.103.0-1.fc37.x86_64, etc., kernel 6.1.14

The reporter is unsure if this crash is reproducible.

-- Backtrace:
Application: KDE Power Management System (org_kde_powerdevil), signal:
Segmentation fault

[KCrash Handler]
#4  0x7f097f9ceba7 in wl_proxy_marshal_array_flags () at
/lib64/libwayland-client.so.0
#5  0x7f097f9cf219 in wl_proxy_marshal_flags () at
/lib64/libwayland-client.so.0
#6  0x7f09705ba9c7 in DpmsManager::addScreen(QScreen*) () at
/lib64/libKF5ScreenDpms.so.8
#7  0x7f09705bb390 in
QtPrivate::QFunctorSlotObject, void>::impl(int, QtPrivate::QSlotObjectBase*, QObject*,
void**, bool*) () at /lib64/libKF5ScreenDpms.so.8
#8  0x7f0984cd0e96 in void doActivate(QObject*, int, void**) () at
/lib64/libQt5Core.so.5
#9  0x7f0972326617 in
QtWaylandClient::QWaylandDisplay::addRegistryListener(void (*)(void*,
wl_registry*, unsigned int, QString const&, unsigned int), void*) () at
/lib64/libQt5WaylandClient.so.5
#10 0x7f0972343a2e in QWaylandClientExtension::addRegistryListener() () at
/lib64/libQt5WaylandClient.so.5
#11 0x7f0984cabcda in QMetaMethod::invoke(QObject*, Qt::ConnectionType,
QGenericReturnArgument, QGenericArgument, QGenericArgument, QGenericArgument,
QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument,
QGenericArgument, QGenericArgument, QGenericArgument) const () at
/lib64/libQt5Core.so.5
#12 0x7f0984cace1e in QMetaObject::invokeMethod(QObject*, char const*,
Qt::ConnectionType, QGenericReturnArgument, QGenericArgument, QGenericArgument,
QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument,
QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument) () at
/lib64/libQt5Core.so.5
#13 0x7f09705ba80b in WaylandDpmsHelper::blockUntilSupported() () at
/lib64/libKF5ScreenDpms.so.8
#14 0x7f09705bc318 in KScreen::Dpms::isSupported() const () at
/lib64/libKF5ScreenDpms.so.8
#15 0x7f0985a3f36f in PowerDevil::ActionPool::init(PowerDevil::Core*) () at
/lib64/libpowerdevilcore.so.2
#16 0x7f0985a46ded in PowerDevil::Core::onBackendReady() () at
/lib64/libpowerdevilcore.so.2
#17 0x7f0984cd0e96 in void doActivate(QObject*, int, void**) () at
/lib64/libQt5Core.so.5
#18 0x7f09705f0afa in PowerDevilUPowerBackend::initWithBrightness(bool) ()
at /usr/lib64/qt5/plugins/kf5/powerdevil/powerdevilupowerbackend.so
#19 0x7f0984cd0e96 in void doActivate(QObject*, int, void**) () at
/lib64/libQt5Core.so.5
#20 0x7f09705e7f53 in
PowerDevilUPowerBackend::brightnessSupportQueried(bool) () at
/usr/lib64/qt5/plugins/kf5/powerdevil/powerdevilupowerbackend.so
#21 0x7f0984cd0e96 in void doActivate(QObject*, int, void**) () at
/lib64/libQt5Core.so.5
#22 0x7f09858be3d9 in KJob::result(KJob*, KJob::QPrivateSignal) () at
/lib64/libKF5CoreAddons.so.5
#23 0x7f09858c3e3b in KJob::finishJob(bool) () at
/lib64/libKF5CoreAddons.so.5
#24 0x7f0984cd0e96 in void doActivate(QObject*, int, void**) () at
/lib64/libQt5Core.so.5
#25 0x7f0970889863 in KAuth::DBusHelperProxy::qt_static_metacall(QObject*,
QMetaObject::Call, int, void**) [clone .part.0] () at
/usr/lib64/qt5/plugins/kauth/helper/kauth_helper_plugin.so
#26 0x7f0970889f41 in
KAuth::DBusHelperProxy::qt_metacall(QMetaObject::Call, int, void**) () at
/usr/lib64/qt5/plugins/kauth/helper/kauth_helper_plugin.so
#27 0x7f09851920bb in QDBusConnectionPrivate::deliverCall(QObject*, int,
QDBusMessage const&, QVector const&, int) () at /lib64/libQt5DBus.so.5
#28 0x7f0984cc8134 in QObject::event(QEvent*) () at /lib64/libQt5Core.so.5
#29 0x7f0984c9d4e8 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at /lib64/libQt5Core.so.5
#30 0x7f0984ca0854 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () at /lib64/libQt5Core.so.5
#31 0x7f0984ceeb07 in postEventSourceDispatch(_GSource*, int (*)(void*),
void*) () at /lib64/libQt5Core.so.5
#32 0x7f0983918c7f in g_main_context_dispatch () at /lib64/libglib-2.0.so.0
#33 0x7f098396f118 in g_main_context_iterate.constprop () at
/lib64/libglib-2.0.so.0
#34 0x7f0983915f00 

[Powerdevil] [Bug 466181] powerdevil crashes in KScreen::AbstractDpmsHelper::isSupported()

2023-03-03 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=466181

Nate Graham  changed:

   What|Removed |Added

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

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

[kmymoney] [Bug 466798] Deleting SQLite source and clearing recent list crashes on launch

2023-03-03 Thread Jack
https://bugs.kde.org/show_bug.cgi?id=466798

Jack  changed:

   What|Removed |Added

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

--- Comment #3 from Jack  ---
In general, it's best to start with one of the methods from
https://kmymoney.org/support.html when asking for help, unless it really does
seem like the program is misbehaving.  I'll have to check the source to see why
it crashed in this case, instead of just telling you it didn't know of any data
source to use, so I'll wait until I've done that to either close or reword it
for that particular problem.

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

[kmymoney] [Bug 466798] Deleting SQLite source and clearing recent list crashes on launch

2023-03-03 Thread Drew
https://bugs.kde.org/show_bug.cgi?id=466798

--- Comment #2 from Drew  ---
Jack - thanks for the quick response and explanation.  It's my first time
reporting a bug in the KDE system. :)  Your solution worked great!  Ran KMM
through the terminal which got it to launch just fine and I was able to set up
a new data source.

Ok to mark as resolved and close.

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

[digikam] [Bug 466799] New: showfoto >configure >miscellaneous >sort images by Name >Reverse ordering >sorts ascending rather than descending

2023-03-03 Thread D. Murrell
https://bugs.kde.org/show_bug.cgi?id=466799

Bug ID: 466799
   Summary: showfoto >configure >miscellaneous >sort images by
Name >Reverse ordering >sorts ascending rather than
descending
Classification: Applications
   Product: digikam
   Version: 7.9.0
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Showfoto-Core
  Assignee: digikam-bugs-n...@kde.org
  Reporter: dmgt...@gmail.com
  Target Milestone: ---

SUMMARY
***
When sorting images by Name, Showfoto defaults to a reverse ordered display.
When configuring Miscellaneous Settings Behaviour -Sort images by Name -Reverse
ordering, the files are sorted in an ascending order.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 
KDE Plasma Version: 5.27.2
KDE Frameworks Version: 5.103.0
Qt Version: 5.15.8

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

[frameworks-kio] [Bug 161017] enqueue kio transfer operations

2023-03-03 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=161017

Bug Janitor Service  changed:

   What|Removed |Added

   Priority|NOR |VHI

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

[kmymoney] [Bug 466798] Deleting SQLite source and clearing recent list crashes on launch

2023-03-03 Thread Jack
https://bugs.kde.org/show_bug.cgi?id=466798

Jack  changed:

   What|Removed |Added

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

--- Comment #1 from Jack  ---
By default, when you start KMyMoney, it tries to open the last data source it
used.  That's likely why it's crashing, although it should certainly be able to
recover from that situation.  The way to get going again is to launch from
command line, with "kmymoney -n" where the -n tells it not to open any data
source.  Then you can create a new data file.   It shouldn't matter in this
case, but it's generally a good idea to state with OS/Distribution you are
using.
Clearing the recently used file list doesn't really clear it completely, as it
always keeps the currently open file on the list when it closes.

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

[korganizer] [Bug 466722] Unable to create bi-weekly/bi-monthly reminders

2023-03-03 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=466722

gjditchfi...@acm.org changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
 Resolution|--- |NOT A BUG
 CC||gjditchfi...@acm.org

--- Comment #1 from gjditchfi...@acm.org ---
To create an event the recurs every two weeks, in the recurrence tab
of the new event dialog, choose Repeats: Weekly every 2 weeks.

To create an event that recurs on two days of a week,
choose Repeats: Weekly, and on the list of days that is immediately
underneath, choose the days you want.

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

[dolphin] [Bug 466796] Opening search sometimes messes up layout (sidebar sizes)

2023-03-03 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=466796

Bug Janitor Service  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|REPORTED|ASSIGNED

--- Comment #1 from Bug Janitor Service  ---
A possibly relevant merge request was started @
https://invent.kde.org/system/dolphin/-/merge_requests/520

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

[frameworks-kio] [Bug 161017] enqueue kio transfer operations

2023-03-03 Thread Patrick Silva
https://bugs.kde.org/show_bug.cgi?id=161017

Patrick Silva  changed:

   What|Removed |Added

 CC||ahmed@tutanota.com

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

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

[dolphin] [Bug 466706] [Feature request] Queue copy/move operations instead of doing all of them at the same time

2023-03-03 Thread Patrick Silva
https://bugs.kde.org/show_bug.cgi?id=466706

Patrick Silva  changed:

   What|Removed |Added

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

--- Comment #1 from Patrick Silva  ---


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

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

[kmymoney] [Bug 466798] New: Deleting SQLite source and clearing recent list crashes on launch

2023-03-03 Thread Drew
https://bugs.kde.org/show_bug.cgi?id=466798

Bug ID: 466798
   Summary: Deleting SQLite source and clearing recent list
crashes on launch
Classification: Applications
   Product: kmymoney
   Version: 5.1.3
  Platform: Other
OS: Other
Status: REPORTED
  Severity: critical
  Priority: NOR
 Component: database
  Assignee: kmymoney-de...@kde.org
  Reporter: drewm...@hotmail.com
  Target Milestone: ---

SUMMARY: I wanted to start fresh with a new source so I deleted the SQLite file
I was using and also cleared the Recent sources list in the File menu and now
on launch it throws an error with the storage manager component. Clicking OK on
error closes KMM.
***
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. Clear recent sources list in File menu
2. Delete the SQLite db file
3. Launch KMM
4. Click close on Currency window (actually selecting US $ also gets the same
error)
5. Click OK in Error window and program closes

OBSERVED RESULT
Uncaught error. Please report the details to the developers
Unknown account id 'AStd::Asset'
/build/kmymoney/src/kmymoney-5.1.3/kmymoney/mymoney/storage/mymoneystoragemgr.cpp:132

EXPECTED RESULT
Not error out

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

ADDITIONAL INFORMATION
I tried uninstalling and reinstalling KMyMoney but get the same error.

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

[plasmashell] [Bug 448833] Overlapping entries when filtering and deleting and filtering again several times

2023-03-03 Thread Patrick Silva
https://bugs.kde.org/show_bug.cgi?id=448833

Patrick Silva  changed:

   What|Removed |Added

 CC||dpba...@wp.pl

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

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

[plasmashell] [Bug 466766] corrupted preview

2023-03-03 Thread Patrick Silva
https://bugs.kde.org/show_bug.cgi?id=466766

Patrick Silva  changed:

   What|Removed |Added

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

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


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

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

[korganizer] [Bug 466797] New: Problem connecting to calendar and contact with CalDAV protocol (in addition to problems with WebDAV and CardDAV)

2023-03-03 Thread Troupal
https://bugs.kde.org/show_bug.cgi?id=466797

Bug ID: 466797
   Summary: Problem connecting to calendar and contact with CalDAV
protocol (in addition to problems with WebDAV and
CardDAV)
Classification: Applications
   Product: korganizer
   Version: 5.22.3
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: trou...@mailoo.org
  Target Milestone: ---

Created attachment 156979
  --> https://bugs.kde.org/attachment.cgi?id=156979=edit
Server access configuration & Result of an attempt to connect to a CalDAV
server

SUMMARY
Problem connecting to calendar and contact with CalDAV protocol (plus problems
with WebDAV and CardDAV)

STEPS TO REPRODUCE
1.  Adding a new calendar
2. Adding a Resource for DAV groupware
3. Enter the credentials (see the attached image named "server access
configuration")
4. Choose to configure the resource manually
5. Complete and add a server configuration (see attached image "Server access
configuration")
6. And try to connect…

OBSERVED RESULT
There was a problem with the request. Invalid username or password (401).
See attached image "esult of an attempt to connect to a CalDAV server"

EXPECTED RESULT
Connecting to my CalDAV calendar

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 6.2.1-zen1-1-zen
(available in About System)
KDE Plasma Version: 5.27.2
KDE Frameworks Version: 5.103.0
Qt Version: 5.15.8
DistrOS: Garuda Linux x86_64

ADDITIONAL INFORMATION
The same problems occur with CardDAV, WebDAV on KOrganizer, Dolphin, Akonadi,
etc.

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

[systemsettings] [Bug 466781] Systemsettings crashed when switching KCMs

2023-03-03 Thread Nicolas Fella
https://bugs.kde.org/show_bug.cgi?id=466781

--- Comment #1 from Nicolas Fella  ---
#0  0x7621ef4a in
QRhiResourceUpdateBatchPrivate::merge(QRhiResourceUpdateBatchPrivate*)
(this=0x7fffb80a9010, other=0x7fff0001)
at /usr/src/debug/qt6-qtbase-6.4.2-4.fc37.x86_64/src/gui/rhi/qrhi.cpp:6050
#1  0x7621f28f in
QRhiResourceUpdateBatch::merge(QRhiResourceUpdateBatch*)
(this=this@entry=0x1886870, other=) at
/usr/src/debug/qt6-qtbase-6.4.2-4.fc37.x86_64/src/gui/rhi/qrhi.cpp:5711
#2  0x74b82900 in
QSGRhiTextureGlyphCache::commitResourceUpdates(QRhiResourceUpdateBatch*)
(this=this@entry=0x236d4e0, mergeInto=0x1886870)
at
/usr/src/debug/qt6-qtdeclarative-6.4.2-1.fc37.x86_64/src/quick/scenegraph/qsgrhitextureglyphcache.cpp:222
#3  0x74b50b1b in
QSGTextMaskRhiShader::updateUniformData(QSGMaterialShader::RenderState&,
QSGMaterial*, QSGMaterial*)
(this=, state=..., newMaterial=newMaterial@entry=0x28ed310,
oldMaterial=oldMaterial@entry=0x0)
at
/usr/src/debug/qt6-qtdeclarative-6.4.2-1.fc37.x86_64/src/quick/scenegraph/qsgdefaultglyphnode_p.cpp:131
#4  0x74b50f2e in
QSG24BitTextMaskRhiShader::updateUniformData(QSGMaterialShader::RenderState&,
QSGMaterial*, QSGMaterial*) (this=, state=...,
newMaterial=0x28ed310, oldMaterial=0x0)
at
/usr/src/debug/qt6-qtdeclarative-6.4.2-1.fc37.x86_64/src/quick/scenegraph/qsgdefaultglyphnode_p.cpp:212
#5  0x74b1408e in
QSGBatchRenderer::Renderer::updateMaterialDynamicData(QSGBatchRenderer::ShaderManagerShader*,
QSGMaterialShader::RenderState&, QSGMaterial*, QSGBatchRenderer::Batch const*,
QSGBatchRenderer::Element*, int, int) (this=0x1cd8ec0, sms=,
renderState=..., material=0x28ed310, batch=0x26e33b0, e=0x1cdec08,
ubufOffset=0, ubufRegionSize=156)
at
/usr/src/debug/qt6-qtdeclarative-6.4.2-1.fc37.x86_64/src/quick/scenegraph/coreapi/qsgbatchrenderer.cpp:2804
#6  0x74b156e2 in
QSGBatchRenderer::Renderer::prepareRenderMergedBatch(QSGBatchRenderer::Batch*,
QSGBatchRenderer::Renderer::PreparedRenderBatch*)
(this=0x1cd8ec0, batch=0x26e33b0, renderBatch=0x7fffcc90) at
/usr/src/debug/qt6-qtdeclarative-6.4.2-1.fc37.x86_64/src/quick/scenegraph/coreapi/qsgbatchrenderer.cpp:3100
#7  0x74b176a5 in
QSGBatchRenderer::Renderer::prepareRenderPass(QSGBatchRenderer::Renderer::RenderPassContext*)
(this=, ctx=0x1cd9208)
at
/usr/src/debug/qt6-qtdeclarative-6.4.2-1.fc37.x86_64/src/quick/scenegraph/coreapi/qsgbatchrenderer.cpp:3735
#8  0x74b19756 in QSGBatchRenderer::Renderer::render() (this=0x1cd8ec0)
at
/usr/src/debug/qt6-qtdeclarative-6.4.2-1.fc37.x86_64/src/quick/scenegraph/coreapi/qsgbatchrenderer.cpp:3491
#9  QSGBatchRenderer::Renderer::render() (this=0x1cd8ec0) at
/usr/src/debug/qt6-qtdeclarative-6.4.2-1.fc37.x86_64/src/quick/scenegraph/coreapi/qsgbatchrenderer.cpp:3484
#10 0x74b30591 in QSGRenderer::renderScene() (this=0x1cd8ec0) at
/usr/src/debug/qt6-qtdeclarative-6.4.2-1.fc37.x86_64/src/quick/scenegraph/coreapi/qsgrenderer.cpp:136
#11 QSGRenderer::renderScene() (this=0x1cd8ec0) at
/usr/src/debug/qt6-qtdeclarative-6.4.2-1.fc37.x86_64/src/quick/scenegraph/coreapi/qsgrenderer.cpp:111
#12 0x74ad8c52 in QQuickWindowPrivate::renderSceneGraph(QSize const&,
QSize const&) (this=this@entry=0xc029c0, size=..., surfaceSize=...)
at
/usr/src/debug/qt6-qtdeclarative-6.4.2-1.fc37.x86_64/src/quick/items/qquickwindow.cpp:662
#13 0x74a6f563 in QQuickRenderControl::render() (this=)
at
/usr/src/debug/qt6-qtdeclarative-6.4.2-1.fc37.x86_64/src/quick/items/qquickrendercontrol.cpp:428
#14 0x75c60808 in QQuickWidgetPrivate::render(bool) (this=0xd11ca0,
needsSync=) at
/usr/src/debug/qt6-qtdeclarative-6.4.2-1.fc37.x86_64/src/quickwidgets/qquickwidget.cpp:363
#15 0x75c609ff in QQuickWidgetPrivate::renderSceneGraph()
(this=0xd11ca0) at
/usr/src/debug/qt6-qtdeclarative-6.4.2-1.fc37.x86_64/src/quickwidgets/qquickwidget.cpp:402
#16 0x757ba1d5 in QObject::event(QEvent*) (this=0xdba610,
e=0x7fffd080) at
/usr/src/debug/qt6-qtbase-6.4.2-4.fc37.x86_64/src/corelib/kernel/qobject.cpp:1400
#17 0x76dbaa65 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
(this=, receiver=0xdba610, e=0x7fffd080)
at
/usr/src/debug/qt6-qtbase-6.4.2-4.fc37.x86_64/src/widgets/kernel/qapplication.cpp:3315
#18 0x75768068 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
(receiver=0xdba610, event=0x7fffd080)
at
/usr/src/debug/qt6-qtbase-6.4.2-4.fc37.x86_64/src/corelib/kernel/qcoreapplication.cpp:1026
#19 0x759073c9 in QTimerInfoList::activateTimers() (this=0x489b50) at
/usr/src/debug/qt6-qtbase-6.4.2-4.fc37.x86_64/src/corelib/kernel/qtimerinfo_unix.cpp:610
#20 0x75a22f2c in timerSourceDispatch(GSource*, GSourceFunc, gpointer)
(source=) at
/usr/src/debug/qt6-qtbase-6.4.2-4.fc37.x86_64/src/corelib/kernel/qeventdispatcher_glib.cpp:149
#21 0x73ce5c7f in g_main_dispatch (context=0x49d110) at
../glib/gmain.c:3454
#22 g_main_context_dispatch 

[Powerdevil] [Bug 466181] powerdevil crashes in KScreen::AbstractDpmsHelper::isSupported()

2023-03-03 Thread Chema
https://bugs.kde.org/show_bug.cgi?id=466181

--- Comment #28 from Chema  ---
Sorry, not true, the new kernel doesn't fix the Powerdevil problem. Please look
at the bug:

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

Where you can find an explanation of what happened when I did the test and why
it worked for me.

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

[systemsettings] [Bug 466793] Missing audio control icon in System preferences

2023-03-03 Thread feveal
https://bugs.kde.org/show_bug.cgi?id=466793

--- Comment #2 from feveal  ---
Yes. But I have already managed to make it appear using these commands

sudo touch /usr/share/pipewire/media-session.d/with-pulseaudio
systemctl --user restart pipewire-session-manager

The whole problem started because yesterday I reinstalled Kubuntu 22.04 with
Plasma to do a general cleanup. Before I also had the same version installed,
but with successive updates since 20.04. So everything was working fine.
now when connecting the TV via HDMI it does not detect the audio output and the
TV can be seen but not heard.
Trying to fix it I had broken something, but I finally managed to get to the
beginning.
Now I still have the problem that it does not detect the HDMI audio
I have tried connecting and disconnecting the HDMI cable, reinstalling
pavucontrol, etc.
I'm looking for solutions on the web but I can't find the right solution

Thanks



De: Nicolas Fella 
Enviado: viernes, 3 de marzo de 2023 22:31
Para: fev...@hotmail.com 
Asunto: [systemsettings] [Bug 466793] Missing audio control icon in System
preferences

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

Nicolas Fella  changed:

   What|Removed |Added

 CC||nicolas.fe...@gmx.de
 Status|REPORTED|NEEDSINFO
 Resolution|--- |WAITINGFORINFO

--- Comment #1 from Nicolas Fella  ---
Is plasma-pa installed?

--
You are receiving this mail because:
You reported the bug.

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

[xdg-desktop-portal-kde] [Bug 466108] Quickly clicking "Show All Installed Apps" repeatedly in the app chooser makes it confuse states

2023-03-03 Thread Harald Sitter
https://bugs.kde.org/show_bug.cgi?id=466108

Harald Sitter  changed:

   What|Removed |Added

 Status|ASSIGNED|RESOLVED
 Resolution|--- |FIXED
  Latest Commit||https://invent.kde.org/plas
   ||ma/xdg-desktop-portal-kde/c
   ||ommit/207c96aaeaf448c9a8c77
   ||f52e809611c6e5763cd

--- Comment #4 from Harald Sitter  ---
Git commit 207c96aaeaf448c9a8c77f52e809611c6e5763cd by Harald Sitter.
Committed on 03/03/2023 at 22:04.
Pushed by sitter into branch 'master'.

don't react on clicks for checkable buttons

clicked is distinct from doubleclicked and not the correct handler to
use for checkable buttons because of that. use toggle instead.

M  +1-3src/AppChooserDialog.qml

https://invent.kde.org/plasma/xdg-desktop-portal-kde/commit/207c96aaeaf448c9a8c77f52e809611c6e5763cd

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

[kdiff3] [Bug 466522] docked windows arrangement not stored/restored

2023-03-03 Thread michael
https://bugs.kde.org/show_bug.cgi?id=466522

michael  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|REPORTED|CONFIRMED

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

[Powerdevil] [Bug 466620] powerdevil continues to crash in KScreen::AbstractDpmsHelper::isSupported() when HDMI signal is lost

2023-03-03 Thread Chema
https://bugs.kde.org/show_bug.cgi?id=466620

--- Comment #17 from Chema  ---
Sorry, not true, the new kernel doesn't fix the Powerdevil problem...

I explain what has happened. I have a bi-directional EDID emulator connected to
the HDMI output. This small connector is used to fool the computer into
thinking that it is still receiving the HDMI signal from the monitor even if
the HDMI cable is disconnected or other computer is active on a KVM switch.

It is mainly used with KVM switches since it allows you to switch between
computers instantly since it does not have to recover or readapt the video
signal on the monitor when you change computers since the EDID emulator has it
saved. It also has another function and that is to be able to use the computer
with the monitor disconnected for remote control sessions with applications
such as VNC, AnyDesk, etc.

That's why the test worked for me, because I didn't realize when I did it that
I had this little connector connected and then even if I changed the computer
on the KVM switch, the Powerdevil continued to detect the HDMI signal and
that's why it didn't fail. You can buy one of these plugs, it will solve the
problem of the Powerdevil and they are not expensive at all.

What is clear with this test is that the failure is in the interruption of the
HDMI signal, at the moment it is cut, the Powerdevil crashes. If the EDID
emulator is connected and the computer is still receiving a 'ghost' HDMI signal
(provided by the EDID emulator), the Powerdevil does not fail and you can
switch between computers without problem.

What is certain is that with this version of the kernel one of the errors that
it had has been fixed. With the version prior to 6.2.2, if the KDE + Wayland
computer was suspended while having the bi-directional EDID emulator, switched
to the Windows computer, and then went back to the Linux computer and woke it
up, the KDE + Wayland session was completely locked and it was impossible to
recover it (in X11 it worked fine). After installing kernel 6.2.2 now this
problem in Wayland seems to be fixed.

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

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

2023-03-03 Thread Enrique
https://bugs.kde.org/show_bug.cgi?id=451050

--- Comment #6 from Enrique  ---
Created attachment 156977
  --> https://bugs.kde.org/attachment.cgi?id=156977=edit
New crash information added by DrKonqi

dolphin (21.12.3) using Qt 5.15.3

- What I was doing when the application crashed:
Connecting to an online CIFS share
1. Entered the path: smb://sharename.domain.extension
2. Entered username and password
3. Crashed when clicking ok

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

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

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

2023-03-03 Thread Enrique
https://bugs.kde.org/show_bug.cgi?id=451050

Enrique  changed:

   What|Removed |Added

 CC||enrique2...@esarmiento.com

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

[dolphin] [Bug 466745] Android over USB in dolphin have missing functionality .

2023-03-03 Thread Patrick Silva
https://bugs.kde.org/show_bug.cgi?id=466745

Patrick Silva  changed:

   What|Removed |Added

 CC||bugsefor...@gmx.com

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

[dolphin] [Bug 466796] New: Opening search sometimes messes up layout (sidebar sizes)

2023-03-03 Thread Christian
https://bugs.kde.org/show_bug.cgi?id=466796

Bug ID: 466796
   Summary: Opening search sometimes messes up layout (sidebar
sizes)
Classification: Applications
   Product: dolphin
   Version: 22.12.3
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: view-engine: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: k...@fuchsnet.ch
CC: kfm-de...@kde.org
  Target Milestone: ---

Created attachment 156976
  --> https://bugs.kde.org/attachment.cgi?id=156976=edit
Video of the issue, first half is as it should be, second half is the bug

SUMMARY
Opening the search bar in dolphin sometimes messes up your layout (the width of
the sidebars) and doesn't restore them after closing the search, so you need to
manually re-adjust them every time

STEPS TO REPRODUCE
1. Open dolphin
2. Have at least one sidebar
3. Seems to be easier to reproduce in a folder with many items
4. Open the search

OBSERVED RESULT
Your preferred layout (e.g. sidebar width) is modified, sidebars are being made
a lot thinner  (second half of video)

EXPECTED RESULT
Your preferred layout stays as is, and the search doesn't take more space than
it is allowed to (first half of video)

Operating System: Fedora Linux 37
KDE Plasma Version: 5.27.2
KDE Frameworks Version: 5.103.0
Qt Version: 5.15.8
Kernel Version: 6.1.14-200.fc37.x86_64 (64-bit)
Graphics Platform: X11
Processors: 8 × Intel® Core™ i5-8365U CPU @ 1.60GHz
Memory: 15.3 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics 620
Manufacturer: LENOVO
Product Name: 20NQS5TD01
System Version: ThinkPad X390 Yoga

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

[i18n] [Bug 466587] Wrong German translation "Aktualisierung ausgewählt"

2023-03-03 Thread Frederik Schwarzer
https://bugs.kde.org/show_bug.cgi?id=466587

--- Comment #4 from Frederik Schwarzer  ---
Thanks, Nate. :)

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

[i18n] [Bug 466790] Many Plasma 5.27 localization strings missing

2023-03-03 Thread Luigi Toscano
https://bugs.kde.org/show_bug.cgi?id=466790

--- Comment #6 from Luigi Toscano  ---
Hi! Happy to hear from you. I understand that things can happen, but maybe you
can guide and train the other translators in performing those periodic tasks?

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

[Discover] [Bug 450381] Discover does not find updates from Arch repos

2023-03-03 Thread Patrick Silva
https://bugs.kde.org/show_bug.cgi?id=450381

Patrick Silva  changed:

   What|Removed |Added

 CC||kel...@yahoo.com

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

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

[Discover] [Bug 466783] Discover does not find all updates for EndeavourOS (Arch)

2023-03-03 Thread Patrick Silva
https://bugs.kde.org/show_bug.cgi?id=466783

Patrick Silva  changed:

   What|Removed |Added

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

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


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

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

[Powerdevil] [Bug 466181] powerdevil crashes in KScreen::AbstractDpmsHelper::isSupported()

2023-03-03 Thread Chema
https://bugs.kde.org/show_bug.cgi?id=466181

Chema  changed:

   What|Removed |Added

 Status|RESOLVED|REPORTED
 Resolution|FIXED   |---
 Ever confirmed|1   |0

--- Comment #27 from Chema  ---
As I just wrote in this related bug:

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

After installing the new kernel 6.2.2 my problems with the Powerdevil on
Wayland have disappeared. Please, try yourselves to see if with luck this also
solves you.

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

[kwin] [Bug 466749] Glitching cursor and browser content when Firefox is in full screen using a fractional scaling factor

2023-03-03 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=466749

6ot3tj...@mozmail.com changed:

   What|Removed |Added

 CC||6ot3tj...@mozmail.com

--- Comment #1 from 6ot3tj...@mozmail.com ---
I'm having the same problem, but only for scaling factors below 150%. This
might be because it's my secondary 1080p monitor and my primary 4K monitor is
set to 200% scale.
The problem also happens in Chromium browsers, but not consistently, and only
after the "press Esc to exit fullscreen" popup has disappeared.

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

[kwin] [Bug 466660] KWin Big Icons TabBox jitters when notifications arrive

2023-03-03 Thread Ismael Asensio
https://bugs.kde.org/show_bug.cgi?id=40

Ismael Asensio  changed:

   What|Removed |Added

  Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas
   |ma/kwin/commit/e89c09a62e38 |ma/kwin/commit/619e2863d2a8
   |91abc6c85e79bc770ce1c8549ea |bff9a5e13b0d4cacca4a57872b2
   |d   |2

--- Comment #6 from Ismael Asensio  ---
Git commit 619e2863d2a8bff9a5e13b0d4cacca4a57872b22 by Ismael Asensio.
Committed on 03/03/2023 at 18:48.
Pushed by iasensio into branch 'Plasma/5.27'.

TabBox: Avoid unnecesary resets of the client model

When the tabbox switcher is shown and any window is added or
removed, its client model is fully reset, even if this window
is not included in the model.

This can be a bit expensive and also produce small visual quirks
on certain switchers, so let's check if the window list changes
before resetting the model.
FIXED-IN: 5.27.3


(cherry picked from commit e89c09a62e3891abc6c85e79bc770ce1c8549ead)

M  +32   -16   src/tabbox/clientmodel.cpp
M  +4-4src/tabbox/clientmodel.h

https://invent.kde.org/plasma/kwin/commit/619e2863d2a8bff9a5e13b0d4cacca4a57872b22

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

[kasts] [Bug 466795] New: Playback jumps back when manually syncing while episode is playing

2023-03-03 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=466795

Bug ID: 466795
   Summary: Playback jumps back when manually syncing while
episode is playing
Classification: Applications
   Product: kasts
   Version: unspecified
  Platform: Microsoft Windows
OS: Microsoft Windows
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: b...@mogwai.be
  Reporter: benmorde...@protonmail.com
  Target Milestone: ---

KASTS VERSION 23.,03.70

STEPS TO REPRODUCE
1. Set up Nextcloud gpoddersync backend 
2. Play an episode
3. Manually trigger sync

OBSERVED RESULT
Playback jumps back a few seconds, likely drawing from the server the saved
position that was pushed to the server when sync was initiated.

EXPECTED RESULT
Playback continue as normal



SOFTWARE/OS VERSIONS
Windows: 11

KDE Frameworks Version: 5.103.0
Qt Version: 5.15.8

ADDITIONAL INFORMATION
Currently subscribed to 20 podcasts. 
Using Nextcloud gpoddersync 
Example was with a downloaded, not streamed episode.
No errors in error log. 
VLC Player Backend

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

[krita] [Bug 466794] New: Unable to edit Basic-1 in Brush Editor

2023-03-03 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=466794

Bug ID: 466794
   Summary: Unable to edit Basic-1 in Brush Editor
Classification: Applications
   Product: krita
   Version: 5.1.5
  Platform: Microsoft Windows
OS: Microsoft Windows
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Brush engines
  Assignee: krita-bugs-n...@kde.org
  Reporter: wyte...@gmail.com
  Target Milestone: ---

Created attachment 156975
  --> https://bugs.kde.org/attachment.cgi?id=156975=edit
Missing Brush Editor elements

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
***
Unable to edit Basic-1 (Krita_4_Default_Resources.bundle) in Brush Editor. 
Nearly all brush options are unavailable.

STEPS TO REPRODUCE
1.  Select Basic-1
2. Click Brush Editor
3. Froth at the mouth because basic brush options aren't available.

OBSERVED RESULT
Brush options (soften, sharpen, etc) aren't available.

EXPECTED RESULT
Brush options (soften, sharpen) should be available.

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.

[i18n] [Bug 466790] Many Plasma 5.27 localization strings missing

2023-03-03 Thread Lasse Liehu
https://bugs.kde.org/show_bug.cgi?id=466790

--- Comment #5 from Lasse Liehu  ---
Hi. Sorry for forgetting about this. I'm still alive and well but haven't done
anything KDE related recently. I should still have a working environment for
KDE localization on one of my machines.

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

[systemsettings] [Bug 466793] Missing audio control icon in System preferences

2023-03-03 Thread Nicolas Fella
https://bugs.kde.org/show_bug.cgi?id=466793

Nicolas Fella  changed:

   What|Removed |Added

 CC||nicolas.fe...@gmx.de
 Status|REPORTED|NEEDSINFO
 Resolution|--- |WAITINGFORINFO

--- Comment #1 from Nicolas Fella  ---
Is plasma-pa installed?

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

[Powerdevil] [Bug 466620] powerdevil continues to crash in KScreen::AbstractDpmsHelper::isSupported() when HDMI signal is lost

2023-03-03 Thread Chema
https://bugs.kde.org/show_bug.cgi?id=466620

Chema  changed:

   What|Removed |Added

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

--- Comment #16 from Chema  ---
I have good news! I just installed the new kernel 6.2.2, and with this version
the Powedevil problem is solved, at least for me in Wayland, which was where it
crashed! I hope it works for others too.

Going through the kernel changelog, I can only find these reviews that I see
that may have had something to do with it:

commit 83d403e773a851c9447e4d1847a6f1df91604d43
Author: Stylon Wang 
Date:   Tue Jan 10 14:38:33 2023 +0800

drm/amd/display: Properly reuse completion structure

commit 0cf8307adbc6beb5ff3b8a76afedc6e4e0b536a9 upstream.

[Why]
Connecting displays to TBT3 docks often produces invalid
replies for DPIA AUX requests. It turns out the completion
structure was not re-initialized before reusing it, resulting
in immature wake up to completion.

[How]
Properly call reinit_completion() on reused completion structure.

Cc: sta...@vger.kernel.org
Reviewed-by: Solomon Chiu 
Acked-by: Alan Liu 
Signed-off-by: Stylon Wang 
Tested-by: Daniel Wheeler 
Signed-off-by: Alex Deucher 
Cc: "Limonciello, Mario" 
Signed-off-by: Greg Kroah-Hartman 

commit 9c591e6a027053460b61d63c239df4391fbce98f
Author: Nicholas Kazlauskas 
Date:   Mon Jan 23 14:59:28 2023 -0500

drm/amd/display: Move DCN314 DOMAIN power control to DMCUB

commit e383b12709e32d6494c948422070c2464b637e44 upstream.

[Why]
DOMAIN power gating control is now required to be done via firmware
due to interlock with other power features. This is to avoid
intermittent issues in the LB memories.

[How]
If the firmware supports the command then use the new firmware as
the sequence can avoid potential display corruption issues.

The command will be ignored on firmware that does not support DOMAIN
power control and the pipes will remain always on - frequent PG cycling
can cause the issue to occur on the old sequence, so we should avoid it.

Reviewed-by: Hansen Dsouza 
Acked-by: Qingqing Zhuo 
Signed-off-by: Nicholas Kazlauskas 
Tested-by: Daniel Wheeler 
Signed-off-by: Alex Deucher 
Cc: "Limonciello, Mario" 
Signed-off-by: Greg Kroah-Hartman 

commit 8417e002b7165bdde96ef6af48708ad8de6fe194
Author: Thomas Weißschuh 
Date:   Mon Feb 20 06:46:12 2023 +

vc_screen: don't clobber return value in vcs_read

commit ae3419fbac845b4d3f3a9fae4cc80c68d82cdf6e upstream.

Commit 226fae124b2d ("vc_screen: move load of struct vc_data pointer in
vcs_read() to avoid UAF") moved the call to vcs_vc() into the loop.

While doing this it also moved the unconditional assignment of

ret = -ENXIO;

This unconditional assignment was valid outside the loop but within it
it clobbers the actual value of ret.

To avoid this only assign "ret = -ENXIO" when actually needed.

[ Also, the 'goto unlock_out" needs to be just a "break", so that it
  does the right thing when it exits on later iterations when partial
  success has happened - Linus ]

Reported-by: Storm Dragon 
Link: https://lore.kernel.org/lkml/y%2fks6vdql2pis...@hotmail.com/
Fixes: 226fae124b2d ("vc_screen: move load of struct vc_data pointer in
vcs_read() to avoid UAF")
Signed-off-by: Thomas Weißschuh 
Link:
https://lore.kernel.org/lkml/64981d94-d00c-4b31-9063-43ad0a384...@t-8ch.de/
Signed-off-by: Linus Torvalds 
Signed-off-by: Greg Kroah-Hartman 


I don't know if any of these fixes could really solve the problem, but it's the
only thing I see that makes any sense related to the Powerdevil problem.

Now I only have to solve the KDE problems with the HDMI, if one day I get
it

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

  1   2   3   >