[dolphin] [Bug 477526] NFS Mounts with all_squash,root_squash,anonuid=0,anongid=0 not able to modify files anymore

[bugzilla_noreply]

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

matej...@gmail.com changed:

   What|Removed |Added

 CC||matej...@gmail.com

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

[kwin] [Bug 481460] With fractional scale factors on Wayland, Zoom window enlarges continuously without user interaction

[bugzilla_noreply]

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

--- Comment #13 from fanzhuyi...@gmail.com ---
Currently toXNative [0] rounds halfs away from 0, and we get increasing window
sizes. If we change it to round halfs towards 0, we get decreasing window
sizes. If we change it to round halfs to even, the problem seems to disappear.

It seems the scale 1.25 is special because it can exactly generate integer +
0.5 when multiplied by an integer. I have no idea what the root cause of the
problem is though. (This hypothesis is consistent with the problem also being
reported for scale=1.5 and and scale=2.5).

[0]
https://invent.kde.org/plasma/kwin/-/blob/master/src/utils/xcbutils.cpp?ref_type=heads#L624

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

[systemsettings] [Bug 422401] Can't assign shortcut to F24 key

[bugzilla_noreply]

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

--- Comment #20 from gudvinr+...@gmail.com ---
(In reply to fanzhuyifan from comment #19)
> That is controlled by the user configurable keymap. When a keycode is
> unmapped, currently we cannot handle it in shortcuts.

Is that any different on Wayland? I can live with that on X11 but I don't think
that manual remapping is correct (as in user friendly) way to do things moving
forward.

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

[Discover] [Bug 473472] Discover crashes when refreshing updates

[wgalen]

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

wgalen  changed:

   What|Removed |Added

 CC||k...@waynegalen.com

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

[yakuake] [Bug 385882] Yakuake Wayland: when launching Yakuake the second time it appears in the middle of the screen

[Firestar-Reimu]

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

--- Comment #20 from Firestar-Reimu <1900011...@pku.edu.cn> ---
According to me, this issue does not appear every time.

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

[korganizer] [Bug 484041] New: Changes don't get synced with google

[Martin Tlustos]

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

Bug ID: 484041
   Summary: Changes don't get synced with google
Classification: Applications
   Product: korganizer
   Version: 6.0.0
  Platform: Neon
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: martin.tlus...@gmail.com
  Target Milestone: ---

SUMMARY
***
Neither new events/tasks nor changes to existing events/tasks get synced to
google.
***


STEPS TO REPRODUCE
1. Change any event in a google resource
2. sync manually or wait for two years or so
3. 

OBSERVED RESULT
Nothing

EXPECTED RESULT
Changes should get synced

SOFTWARE/OS VERSIONS
Operating System: KDE neon 6.0
KDE Plasma Version: 6.0.2
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2
Kernel Version: 6.5.0-26-generic (64-bit)
Graphics Platform: Wayland
Processors: 6 × AMD Ryzen 5 4500U with Radeon Graphics
Memory: 15,0 GiB of RAM
Graphics Processor: AMD Radeon Graphics
Manufacturer: Acer
Product Name: Aspire A515-44G
System Version: V1.12

ADDITIONAL INFORMATION

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

[korganizer] [Bug 484040] New: Filters don't work

[Martin Tlustos]

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

Bug ID: 484040
   Summary: Filters don't work
Classification: Applications
   Product: korganizer
   Version: 6.0.0
  Platform: Neon
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: martin.tlus...@gmail.com
  Target Milestone: ---

SUMMARY
***
I have two filters, one to hide completed tasks, and the other to hide
everything unless it's active. Both don't do anything since 6.0
***


STEPS TO REPRODUCE
1. Create a filter that hides completed tasks
2. enable the filter in "view"
3. 

OBSERVED RESULT
Nothing happens

EXPECTED RESULT


SOFTWARE/OS VERSIONS
Operating System: KDE neon 6.0
KDE Plasma Version: 6.0.2
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2
Kernel Version: 6.5.0-26-generic (64-bit)
Graphics Platform: Wayland
Processors: 6 × AMD Ryzen 5 4500U with Radeon Graphics
Memory: 15,0 GiB of RAM
Graphics Processor: AMD Radeon Graphics
Manufacturer: Acer
Product Name: Aspire A515-44G
System Version: V1.12
ADDITIONAL INFORMATION

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

[kdeconnect] [Bug 484039] New: Discovery and Pairing Issue - possibly to do with Xaiomi HyperOS

[Scott]

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

Bug ID: 484039
   Summary: Discovery and Pairing Issue - possibly to do with
Xaiomi HyperOS
Classification: Applications
   Product: kdeconnect
   Version: unspecified
  Platform: Android
OS: Android 13.x
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: android-application
  Assignee: albertv...@gmail.com
  Reporter: shagooser...@gmail.com
CC: andrew.g.r.hol...@gmail.com
  Target Milestone: ---

SUMMARY
***
Problems began after installing Xiaomi HyperOS on one device on my network.
That device sees no other devices on my LAN but causes unpairing of other
paired devices on my LAN. My other devices do not see the HyperOS except one
other Android phone which can pair for about 10 seconds before unpairing.
***


STEPS TO REPRODUCE
1.  Attempt to use kdeconnect
2. 
3. 

OBSERVED RESULT
AS above

EXPECTED RESULT
That all devices on my LAN can see and connect to each other and not unpair by
themselves.

SOFTWARE/OS VERSIONS
It affects Android 13 and kubuntu 23.10.

ADDITIONAL INFORMATION

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

[krita] [Bug 483317] Disabling multiple layers at once is displayed incrementally

[Manga Tengu]

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

--- Comment #2 from Manga Tengu  ---
Hi Nick,

Definitely not a bug but a perf issue indeed.  I must have missed the category
(still can't see where it is set up though).
I have a few points:
- If it can be all toggled at once when in a group layer, maybe it can be even
without it? If so, why not improve it as it would mean it's handled in a not
optimal way?
- 6 10kpx*10kpx layers takes roughly 3 seconds on my machine. (The laptop
itself is in good shape and performs very well when I paint or do computing
stuff) If I reduce the image to 500*500, things get instant.
- I think I remember there are quite some macOS perf issues and artifacts. I
believe you will observe it way better on macOS. To name a couple that are
still bugging: https://bugs.kde.org/show_bug.cgi?id=434131 and
https://bugs.kde.org/show_bug.cgi?id=398689
- Even half a second totally ruins the toggling effect to me. In fact, this
really feels long and sluggish when working. Seems our opinions diverge there.

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

[Spectacle] [Bug 484038] New: Make it clear that screen recording isn't supported on X11

[bugzilla_noreply]

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

Bug ID: 484038
   Summary: Make it clear that screen recording isn't supported on
X11
Classification: Applications
   Product: Spectacle
   Version: 24.02.0
  Platform: Arch Linux
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: General
  Assignee: noaha...@gmail.com
  Reporter: jackmacwindowsli...@gmail.com
CC: k...@david-redondo.de
  Target Milestone: ---

SUMMARY
Spectacle does not alert users that the new screen recording function is only
available on Wayland, not X11. This makes it frustrating for users who cannot
use the Wayland backend yet, and try to record video with Spectacle.

Symptoms include:
- recording shortcuts working normally, with the status bar icon appearing
- stopping a recording simply makes the icon disappear, with no notification
and no file output
- recording settings appear normally, but the format/extension dropdown doesn't
work

STEPS TO REPRODUCE
1. Launch Plasma in an X11 workspace
2. Press Alt+Meta+R to activate recording
3. Notice there are no errors, and the recording appears to work
4. Click the recording button in the status bar to stop recording
5. Check the configured location (`~/Videos/Screencasts`) and notice no new
video (as expected on X11)

OBSERVED RESULT
The recording appears to work without error, but no file is produced.

EXPECTED RESULT
An error appears at some point, notifying the user that Spectacle does not
support recording on X11.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Arch Linux latest (6.8.1-zen1-1-zen kernel)
KDE Plasma Version: 6.0.2
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2

ADDITIONAL INFORMATION
I can't use Wayland on my system due to issues with the NVIDIA driver and
redrawing window contents - web browser windows on Chromium and Firefox often
get "stuck" or flicker black. This is why I'm using X11, despite Wayland being
the default as of KDE/Plasma 6.0.

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

[systemsettings] [Bug 482280] Error while communicating with the global shortcuts service on deiban trixie

[Bug Janitor Service]

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

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

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

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

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

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

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

[kate] [Bug 480241] Auto-complete needlessly obscures text cursor

[Bug Janitor Service]

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

Bug Janitor Service  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|WAITINGFORINFO  |WORKSFORME

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

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

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

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

[plasmashell] [Bug 482452] Wallpaper all of a sudden becomes incorrectly sized

[Bug Janitor Service]

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

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

[libalkimia] [Bug 386939] Search variable on Price and Date Online Quotes parameters

[Bug Janitor Service]

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

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

[kde] [Bug 478925] System randomly crashes

[Bug Janitor Service]

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

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

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

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

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

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

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

[konqueror] [Bug 128156] [test case] Yahoo TV Listings fail to redraw correctly on refresh.

[Bug Janitor Service]

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

--- Comment #12 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 484037] New: Primary display loses its resolution configuration when resuming from sleep

[bugzilla_noreply]

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

Bug ID: 484037
   Summary: Primary display loses its resolution configuration
when resuming from sleep
Classification: Plasma
   Product: kwin
   Version: 6.0.2
  Platform: openSUSE
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: multi-screen
  Assignee: kwin-bugs-n...@kde.org
  Reporter: smis...@flyzipper.com
  Target Milestone: ---

Created attachment 167494
  --> https://bugs.kde.org/attachment.cgi?id=167494=edit
Screenshot of the display settings after resuming from sleep

SUMMARY
Randomly, when resuming from sleep, the primary display will be running at
640x480 rather than its usual 4K resolution. The resolution can be reverted to
4K and the screen can be repositioned using Display Configuration in System
Settings.

STEPS TO REPRODUCE
1. allow the system to sleep
2. resume from sleep

OBSERVED RESULT
Randomly observe the primary display losing its resolution settings.

EXPECTED RESULT
Displays would retain their configuration when resuming from sleep.

SOFTWARE/OS VERSIONS
Linux: openSUSE Tumbleweed 20240318
(available in About System)
KDE Plasma Version: 6.0.2
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2

ADDITIONAL INFORMATION
Kernel Version: 6.7.9-1-default (64-bit)
Graphics Platform: Wayland
Processors: 8 × 11th Gen Intel® Core™ i5-1135G7 @ 2.40GHz
Memory: 62.5 GiB of RAM
Graphics Processor: Mesa Intel® Xe Graphics
Manufacturer: Intel(R) Client Systems
Product Name: NUC11PAHi5
System Version: M15533-302

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

[Tokodon] [Bug 484036] New: Share images and other content types to Tokodon

[Joshua Goins]

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

Bug ID: 484036
   Summary: Share images and other content types to Tokodon
Classification: Applications
   Product: Tokodon
   Version: unspecified
  Platform: Other
OS: Other
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: j...@redstrate.com
CC: c...@carlschwan.eu, j...@redstrate.com
  Target Milestone: ---

You can only share URLs to Tokodon right now, it would be cool to send images
directly and other content types

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

[Tokodon] [Bug 481781] Following notifications sometimes don't look right

[Joshua Goins]

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

Joshua Goins  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
 Resolution|--- |FIXED
   Version Fixed In||24.02
  Latest Commit||b99f1dc5fb4d5438146efbb63c1
   ||0d732f166d9db

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

[Discover] [Bug 484035] Discover

[bugzilla_noreply]

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

--- Comment #3 from scram...@gmail.com ---
In: /usr/src/debug/knewstuff/knewstuff-6.0.0/src/core/resultsstream.cpp:70

(Untested Suggestion)...
void ResultsStream::fetch()
{
if (d->request.filter != Provider::Installed) {
// when asking for installed entries, never use the cache
Entry::List cacheEntries =
d->engine->cache()->requestFromCache(d->request);
if (!cacheEntries.isEmpty()) {
Q_EMIT entriesFound(cacheEntries);
return;
}
}

for (const QSharedPointer  :
std::as_const(d->providers)) {
// Check if the shared pointer is not null and the provider is
initialized
if (p && p->isInitialized()) {
p->loadEntries(d->request);
} else if (p) {
// If p is not null but the provider is not initialized, set up a
connection to call loadEntries when the provider is initialized.
connect(p.get(), ::Provider::providerInitialized, this,
[this, p] {
disconnect(p.get(), ::Provider::providerInitialized,
this, nullptr);
if (p->isInitialized()) {
p->loadEntries(d->request);
}
});
} else {
qWarning() << "Encountered a null provider in
ResultsStream::fetch.";
}
}
}

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

[Discover] [Bug 484035] Discover

[bugzilla_noreply]

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

--- Comment #2 from scram...@gmail.com ---
0x7fffc4070d4a in KNSCore::ResultsStream::fetch (this=0x56e182e0) at
/usr/src/debug/knewstuff/knewstuff-6.0.0/src/core/resultsstream.cpp:70
70  if (p->isInitialized()) {   
(gdb) bt
#0  0x7fffc4070d4a in KNSCore::ResultsStream::fetch (this=0x56e182e0)
at /usr/src/debug/knewstuff/knewstuff-6.0.0/src/core/resultsstream.cpp:70
#1  0x7fffc6f2ed81 in KNSResultsStream::setRequest (this=,
request=...) at
/usr/src/debug/discover/discover-6.0.2/libdiscover/backends/KNSBackend/KNSBackend.cpp:107
#2  0x7fffc6f2fb1d in operator() (__closure=0x56814de0) at
/usr/src/debug/discover/discover-6.0.2/libdiscover/backends/KNSBackend/KNSBackend.cpp:479
#3  QtPrivate::FunctorCall, QtPrivate::List<>, void,
KNSBackend::search(const AbstractResourcesBackend::Filters&)::
>::call (arg=, f=...)
at /usr/include/qt6/QtCore/qobjectdefs_impl.h:137
#4  QtPrivate::Functor, 0>::call,
void> (arg=, f=...)
at /usr/include/qt6/QtCore/qobjectdefs_impl.h:339
#5  QtPrivate::QCallableObject, QtPrivate::List<>,
void>::impl(int, QtPrivate::QSlotObjectBase *, QObject *, void **, bool *)
(which=, this_=0x56814dd0, r=, a=, ret=) at /usr/include/qt6/QtCore/qobjectdefs_impl.h:522
#6  0x7577c2c7 in QObject::event (this=0x56814950,
e=0x56814e80) at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/corelib/kernel/qobject.cpp:1437
#7  0x776f438b in QApplicationPrivate::notify_helper (this=, receiver=0x56814950, e=0x56814e80)
at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/widgets/kernel/qapplication.cpp:3296
#8  0x75739818 in QCoreApplication::notifyInternal2
(receiver=0x56814950, event=event@entry=0x56814e80)
at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/corelib/kernel/qcoreapplication.cpp:1121
#9  0x75739b9b in QCoreApplication::sendEvent (event=0x56814e80,
receiver=)
at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/corelib/kernel/qcoreapplication.cpp:1539
#10 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0,
data=0x555f6890)
at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/corelib/kernel/qcoreapplication.cpp:1901
#11 0x759758a4 in QCoreApplication::sendPostedEvents (receiver=0x0,
event_type=0) at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/corelib/kernel/qcoreapplication.cpp:1760
#12 postEventSourceDispatch (s=0x555fb3c0) at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/corelib/kernel/qeventdispatcher_glib.cpp:243
#13 0x74941f69 in g_main_dispatch (context=0x7fffe8000ef0) at
../glib/glib/gmain.c:3476
#14 0x749a03a7 in g_main_context_dispatch_unlocked
(context=0x7fffe8000ef0) at ../glib/glib/gmain.c:4284
#15 g_main_context_iterate_unlocked.isra.0
(context=context@entry=0x7fffe8000ef0, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at ../glib/glib/gmain.c:4349
#16 0x74940162 in g_main_context_iteration (context=0x7fffe8000ef0,
may_block=1) at ../glib/glib/gmain.c:4414
#17 0x759739c4 in QEventDispatcherGlib::processEvents
(this=0x55613290, flags=...)
at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/corelib/kernel/qeventdispatcher_glib.cpp:393
#18 0x75743d6e in QEventLoop::processEvents (flags=...,
this=0x7fffcb80) at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/corelib/kernel/qeventloop.cpp:100
#19 QEventLoop::exec (this=0x7fffcb80, flags=...) at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/corelib/kernel/qeventloop.cpp:182
#20 0x7573c2b8 in QCoreApplication::exec () at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/corelib/global/qflags.h:74
#21 0x776f0f0a in QApplication::exec () at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/widgets/kernel/qapplication.cpp:2574
#22 0x5556d89f in main (argc=, argv=) at
/usr/src/debug/discover/discover-6.0.2/discover/main.cpp:218
(gdb) info threads
  Id   Target IdFrame 
* 1Thread 0x70bca9c0 (LWP 164658) "plasma-discover" 0x7fffc4070d4a
in KNSCore::ResultsStream::fetch (this=0x56e182e0)
at /usr/src/debug/knewstuff/knewstuff-6.0.0/src/core/resultsstream.cpp:70
  2Thread 0x706006c0 (LWP 164661) "QDBusConnection" 0x765190bf
in __GI___poll (fds=0x55605050, nfds=3, timeout=-1) at
../sysdeps/unix/sysv/linux/poll.c:29
  3Thread 0x7fffef4006c0 (LWP 164662) "WaylandEventThr" 0x764a5ebe
in __futex_abstimed_wait_common64 (private=0, cancel=true, abstime=0x0, op=393,
expected=0, 
futex_word=0x55678ae4) at futex-internal.c:57
  4Thread 0x7fffeea006c0 (LWP 164663) "WaylandEventThr" 0x765190bf
in __GI___poll (fds=fds@entry=0x7fffee9ffb70, nfds=nfds@entry=2,
timeout=timeout@entry=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
  5

[plasmashell] [Bug 351175] "Auto-Hide" mode does not work when panel is on an edge between two screens

[U de Recife]

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

U de Recife  changed:

   What|Removed |Added

 Status|RESOLVED|VERIFIED
 CC||u.de.rec...@telegmail.com

--- Comment #78 from U de Recife  ---
I have this bug also. I've wondered myself why the panel never auto-hided when
I configured it to do so. Now I know why.

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

[Discover] [Bug 484035] Discover

[bugzilla_noreply]

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

--- Comment #1 from scram...@gmail.com ---
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
Core was generated by `/usr/bin/plasma-discover'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  __pthread_kill_implementation (threadid=,
signo=signo@entry=11, no_tid=no_tid@entry=0) at pthread_kill.c:44
44return INTERNAL_SYSCALL_ERROR_P (ret) ? INTERNAL_SYSCALL_ERRNO
(ret) : 0;
[Current thread is 1 (Thread 0x7dcae13489c0 (LWP 163594))]

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

[kscreenlocker] [Bug 483130] Unlocking with fingerprint leads to other PAM session authentication failure

[Jure Repinc]

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

Jure Repinc  changed:

   What|Removed |Added

 CC||j...@holodeck1.com

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

[Discover] [Bug 484035] Discover

[bugzilla_noreply]

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

scram...@gmail.com changed:

   What|Removed |Added

 CC||scram...@gmail.com

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

[Discover] [Bug 484035] New: Discover

[bugzilla_noreply]

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

Bug ID: 484035
   Summary: Discover
Classification: Applications
   Product: Discover
   Version: 6.0.2
  Platform: Arch Linux
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: discover
  Assignee: plasma-b...@kde.org
  Reporter: scram...@gmail.com
CC: aleix...@kde.org
  Target Milestone: ---

Application: plasma-discover (6.0.2)

Qt Version: 6.6.2
Frameworks Version: 6.0.0
Operating System: Linux 6.7.9-zen1-1-zen x86_64
Windowing System: Wayland
Distribution: "Arch Linux"
DrKonqi: 6.0.2 [CoredumpBackend]

-- Information about the crash:
Steps to reproduce on my system:
1. ) open discover
2. ) goto search and attempt to search = crash
3. ) goto installed packages = crash


Things I have tried:
- Disabled all flatpak repos (restarted and then tried above)
- Got rid of packagekit entirely just flew with only flatpaks, same result

The crash can be reproduced every time.

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


This GDB supports auto-downloading debuginfo from the following URLs:
  
Enable debuginfod for this session? (y or [n]) [answered N; input not from
terminal]
Debuginfod has been disabled.
To make this setting permanent, add 'set debuginfod enabled off' to .gdbinit.
[New LWP 160538]
[New LWP 160542]
[New LWP 160540]
[New LWP 160546]
[New LWP 160554]
[New LWP 160543]
[New LWP 160567]
[New LWP 160557]
[New LWP 160571]
[New LWP 160570]
[New LWP 160558]
[New LWP 160569]
[New LWP 160662]
[New LWP 160573]
[New LWP 160555]
[New LWP 160547]
[New LWP 160544]
[New LWP 160539]
[New LWP 160559]
[New LWP 160649]
[New LWP 160568]
[New LWP 160661]
[New LWP 160664]
[New LWP 160556]
[New LWP 160667]
[New LWP 160545]
[New LWP 160668]
[New LWP 160684]
[New LWP 160663]
[New LWP 160659]
[New LWP 160660]
[New LWP 160666]
[New LWP 160669]
[New LWP 160650]
[New LWP 160665]
[New LWP 160541]
[New LWP 160768]
[New LWP 160670]
[New LWP 160671]
[New LWP 160566]
[New LWP 160685]
[New LWP 160651]
[New LWP 160652]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
Core was generated by `/usr/bin/plasma-discover'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x7d04bf6ab32c in ?? () from /usr/lib/libc.so.6
[Current thread is 1 (Thread 0x7d04b9e149c0 (LWP 160538))]
Cannot QML trace cores :(
[Current thread is 1 (Thread 0x7d04b9e149c0 (LWP 160538))]

Thread 43 (Thread 0x7d04550006c0 (LWP 160652)):
#0  0x7d04bf6a5ebe in ??? () at /usr/lib/libc.so.6
#1  0x7d04bf6a8a65 in pthread_cond_timedwait () at /usr/lib/libc.so.6
#2  0x7d04beaa3ba4 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at
/usr/lib/libQt6Core.so.6
#3  0x7d04beaa64aa in ??? () at /usr/lib/libQt6Core.so.6
#4  0x7d04beaa0bd3 in ??? () at /usr/lib/libQt6Core.so.6
#5  0x7d04bf6a955a in ??? () at /usr/lib/libc.so.6
#6  0x7d04bf726a3c in ??? () at /usr/lib/libc.so.6

Thread 42 (Thread 0x7d0455a006c0 (LWP 160651)):
#0  0x7d04bf6a5ebe in ??? () at /usr/lib/libc.so.6
#1  0x7d04bf6a8a65 in pthread_cond_timedwait () at /usr/lib/libc.so.6
#2  0x7d04beaa3ba4 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at
/usr/lib/libQt6Core.so.6
#3  0x7d04beaa64aa in ??? () at /usr/lib/libQt6Core.so.6
#4  0x7d04beaa0bd3 in ??? () at /usr/lib/libQt6Core.so.6
#5  0x7d04bf6a955a in ??? () at /usr/lib/libc.so.6
#6  0x7d04bf726a3c in ??? () at /usr/lib/libc.so.6

Thread 41 (Thread 0x7d041e0006c0 (LWP 160685)):
#0  0x7d04bf719616 in ppoll () at /usr/lib/libc.so.6
#1  0x7d04bea98f6b in qt_safe_poll(pollfd*, unsigned long, timespec const*)
() at /usr/lib/libQt6Core.so.6
#2  0x7d04be35c758 in ??? () at /usr/lib/libQt6Network.so.6
#3  0x7d04be3071b9 in ??? () at /usr/lib/libQt6Network.so.6
#4  0x7d04be2ff18e in QAbstractSocket::waitForReadyRead(int) () at
/usr/lib/libQt6Network.so.6
#5  0x7d04c06c79da in ??? () at /usr/lib/libKF6KIOCore.so.6
#6  0x7d04c07a7a9d in ??? () at /usr/lib/libKF6KIOCore.so.6
#7  0x7d04c0783632 in ??? () at /usr/lib/libKF6KIOCore.so.6
#8  0x7d04beaa0bd3 in ??? () at /usr/lib/libQt6Core.so.6
#9  0x7d04bf6a955a in ??? () at /usr/lib/libc.so.6
#10 0x7d04bf726a3c in ??? () at /usr/lib/libc.so.6

Thread 40 (Thread 0x7d046ea006c0 (LWP 160566)):
#0  0x7d04bf7190bf in poll () at /usr/lib/libc.so.6
#1  0x7d04bdc262f6 in ??? () at /usr/lib/libglib-2.0.so.0
#2  0x7d04bdbc6162 in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#3  0x7d04beb739c4 in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt6Core.so.6
#4  0x7d04be943d6e in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt6Core.so.6
#5  0x7d04bea2116f in QThread::run() () at /usr/lib/libQt6Core.so.6
#6  

[systemsettings] [Bug 484034] SDDM cannot apply plasma settings of scaling and cursor

[Firestar-Reimu]

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

--- Comment #1 from Firestar-Reimu <1900011...@pku.edu.cn> ---
Also, I use breeze-cursors theme in plasma, but SDDM uses adwaita by default

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

[systemsettings] [Bug 484034] New: SDDM cannot apply plasma settings of scaling and cursor

[Firestar-Reimu]

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

Bug ID: 484034
   Summary: SDDM cannot apply plasma settings of scaling and
cursor
Classification: Applications
   Product: systemsettings
   Version: 6.0.2
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: kcm_sddm
  Assignee: plasma-b...@kde.org
  Reporter: 1900011...@pku.edu.cn
CC: k...@david-redondo.de, k...@davidedmundson.co.uk
  Target Milestone: ---

I use a 2560x1600 screen and scaled at 200%, cursor size=18

I use Wayland session.

I set the "Apply Plasma Settings" in systemsettings >> Colors & Themes >> Login
Screen (SDDM)

But the SDDM still use 100% scaling which is too small for me.

Then I Make a file called hidpi.conf

Put this in the file.
```
[General]
GreeterEnvironment=QT_SCREEN_SCALE_FACTORS=2,QT_FONT_DPI=192

[Wayland]
EnableHiDPI=true

[X11]
EnableHiDPI=true
ServerArguments=-nolisten tcp -dpi 192
```
Put the file in /etc/sddm.conf.d/

Now the screen has scaled 200% but the cursor is still too small

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

[Discover] [Bug 481993] Discover fails to launch after upgrade to Neon 6.0

[jonzn4SUSE]

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

--- Comment #20 from jonzn4SUSE  ---
System info:
Operating System: openSUSE Tumbleweed 20240315
KDE Plasma Version: 6.0.2
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2
Kernel Version: 6.7.9-1-default (64-bit)
Graphics Platform: X11
Processors: 16 × AMD Ryzen 7 5825U with Radeon Graphics
Memory: 62.1 GiB of RAM
Graphics Processor: AMD Radeon Graphics
Manufacturer: HP
Product Name: HP ProBook 455 15.6 inch G9 Notebook PC

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

[Discover] [Bug 481993] Discover fails to launch after upgrade to Neon 6.0

[jonzn4SUSE]

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

jonzn4SUSE  changed:

   What|Removed |Added

 CC||jonzn4s...@hotmail.com

--- Comment #19 from jonzn4SUSE  ---
Created attachment 167493
  --> https://bugs.kde.org/attachment.cgi?id=167493=edit
Discover crash

The app also goes BOOM for me.  Here is the data being shown in KsystemLog
before being erased.  Also below video shows the issue.
https://youtu.be/rmLTl6oYdDc

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

[plasmashell] [Bug 483590] Plasmashell Crash

[Harald Sitter]

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

Harald Sitter  changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 CC||sit...@kde.org
 Status|REPORTED|RESOLVED

--- Comment #1 from Harald Sitter  ---


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

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

[plasmashell] [Bug 483584] plasmashell crashing on startup after boot

[Harald Sitter]

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

Harald Sitter  changed:

   What|Removed |Added

 CC||kde.o9...@passinbox.com

--- Comment #3 from Harald Sitter  ---
*** Bug 483590 has been marked as a duplicate of this bug. ***

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

[plasmashell] [Bug 483584] plasmashell crashing on startup after boot

[Harald Sitter]

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

Harald Sitter  changed:

   What|Removed |Added

 CC||cxfighte...@gmail.com

--- Comment #2 from Harald Sitter  ---
*** Bug 483834 has been marked as a duplicate of this bug. ***

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

[plasmashell] [Bug 483584] plasmashell crashing on startup after boot

[Harald Sitter]

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

Harald Sitter  changed:

   What|Removed |Added

 CC||bsnapc...@gmail.com

--- Comment #1 from Harald Sitter  ---
*** Bug 484030 has been marked as a duplicate of this bug. ***

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

[plasmashell] [Bug 484030] Black screen on Plasma 6 login after changing theme

[Harald Sitter]

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

Harald Sitter  changed:

   What|Removed |Added

 CC||sit...@kde.org
 Resolution|--- |DUPLICATE
 Status|REPORTED|RESOLVED

--- Comment #1 from Harald Sitter  ---


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

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

[plasmashell] [Bug 483834] KDE 6 crash

[Harald Sitter]

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

Harald Sitter  changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 CC||sit...@kde.org
 Status|REPORTED|RESOLVED

--- Comment #1 from Harald Sitter  ---


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

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

[kwin] [Bug 481460] With fractional scale factors on Wayland, Zoom window enlarges continuously without user interaction

[bugzilla_noreply]

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

--- Comment #12 from fanzhuyi...@gmail.com ---
As mentioned in Bug 483605, a necessary condition is checking Legacy
Applications Apply Scaling themselves.

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

[systemsettings] [Bug 483115] Lost hotkey assignment and reappearing deleted hotkey entries in KDE 6

[Nelson]

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

--- Comment #3 from Nelson  ---
(In reply to Nicolas Fella from comment #1)
> Can you please attach your .config/kglobalshortcutsrc?

Certainly. I have added it as an attachment now.

I noticed that when I set the Dolphin shortcut, an entry gets added to this
file with the hotkey; but upon restart, it's no longer there.

I also didn't see any reference in it to the extra entries I cannot get rid of.

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

[kwin] [Bug 481460] With fractional scale factors on Wayland, Zoom window enlarges continuously without user interaction

[bugzilla_noreply]

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

fanzhuyi...@gmail.com changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|REPORTED|CONFIRMED

--- Comment #11 from fanzhuyi...@gmail.com ---
(In reply to fanzhuyifan from comment #10)
> *** Bug 483605 has been marked as a duplicate of this bug. ***

I can also reproduce  with 250%, as reported in 483605.

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

[kwin] [Bug 481460] With fractional scale factors on Wayland, Zoom window enlarges continuously without user interaction

[bugzilla_noreply]

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

fanzhuyi...@gmail.com changed:

   What|Removed |Added

 CC||rronnan...@gmail.com

--- Comment #10 from fanzhuyi...@gmail.com ---
*** Bug 483605 has been marked as a duplicate of this bug. ***

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

[kwin] [Bug 483605] Pop-up Windows Resizing Themselves Automatically

[bugzilla_noreply]

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

fanzhuyi...@gmail.com changed:

   What|Removed |Added

 CC||fanzhuyi...@gmail.com
 Resolution|WAITINGFORINFO  |DUPLICATE
 Status|NEEDSINFO   |RESOLVED

--- Comment #3 from fanzhuyi...@gmail.com ---


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

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

[systemsettings] [Bug 483115] Lost hotkey assignment and reappearing deleted hotkey entries in KDE 6

[Nelson]

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

--- Comment #2 from Nelson  ---
Created attachment 167492
  --> https://bugs.kde.org/attachment.cgi?id=167492=edit
kglobalshortcutsrc config file

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

[valgrind] [Bug 452387] valgrind: m_debuginfo/readelf.c:717 (get_elf_symbol_info): Assertion 'in_rx' failed. [ARMV7]

[bugzilla_noreply]

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

--- Comment #7 from tdk2...@gmail.com ---
(In reply to Paul Floyd from comment #6)
> It is hitting an assert when reading ld-2.15.so
> 
> The program headers say that this only has 312 bytes of executable code
> 
> PT_LOAD[1]:   p_offset 0, p_filesz 312, perms r-x
> then it tris to look at _dl_start
> 
> raw symbol [  32]: LOC FUN : svma 0x0039d5, sz 1296  _dl_start
> 
> which is 1296 bytes.
> 
> Can you tell us why you are using ld-2.15.so in /tmp instead of somewhere
> more 'standard' like /lib or /usr/lib?
> 
> And can you tell us if this is a copy of the system ld-2.15.so which I
> assume will be in one of those directories?

Thanks for your reply.

If use standard /lib/ld-2.15.so, the output is the following, /tmp/ld-2.15.so
isn't stripped

[root@test ~] $ /tmp/valgrind/bin/valgrind -d -d -d --trace-symtab=yes
--error-limit=no --leak-check=full --tool=memcheck  /usr/bin/last
--1986:1:debuglog DebugLog system started by Stage 1, level 3 logging requested
--1986:1:launcher tool 'memcheck' requested
--1986:2:launcher   selecting platform for '/usr/bin/last'
--1986:2:launcher   opened '/usr/bin/last'
--1986:2:launcher   read 4096 bytes from '/usr/bin/last'
--1986:2:launcher   selected platform 'arm-linux'
--1986:1:launcher selected platform 'arm-linux'
--1986:1:launcher launching /tmp/valgrind/libexec/valgrind/memcheck-arm-linux
--1986:1:debuglog DebugLog system started by Stage 2 (main), level 3 logging
requested
--1986:1:main Welcome to Valgrind version 3.22.0 debug logging
--1986:1:main Checking current stack is plausible
--1986:1:main Checking initial stack was noted
--1986:1:main Starting the address space manager
--1986:2: aspacem   sp_at_startup = 0x00bed6eb60 (supplied)
--1986:2: aspacem minAddr = 0x000400 (computed)
--1986:2: aspacem maxAddr = 0x00bed6dfff (computed)
--1986:2: aspacem  cStart = 0x000400 (computed)
--1986:2: aspacem  vStart = 0x00616b7000 (computed)
--1986:2: aspacem   suggested_clstack_end = 0x00bdd6efff (computed)
--1986:2: aspacem   <<< SHOW_SEGMENTS: Initial layout (5 segments)
--1986:2: aspacem   0 segment names in 0 slots
--1986:2: aspacem   freelist is empty
--1986:2: aspacem 0: RSVN 00-0003ff 64m - SmFixed
--1986:2: aspacem 1:  000400-00616b6fff   1494m
--1986:2: aspacem 2: RSVN 00616b7000-00616b7fff4096 - SmFixed
--1986:2: aspacem 3:  00616b8000-00bed6dfff   1494m
--1986:2: aspacem 4: RSVN 00bed6e000-00   1042m - SmFixed
--1986:2: aspacem   >>>
--1986:2: aspacem   Reading /proc/self/maps
--1986:2: aspacem   <<< SHOW_SEGMENTS: With contents of /proc/self/maps (13
segments)
--1986:2: aspacem   1 segment names in 1 slots
--1986:2: aspacem   freelist is empty
--1986:2: aspacem   (0,4,3) /tmp/valgrind/libexec/valgrind/memcheck-arm-linux
--1986:2: aspacem 0: RSVN 00-0003ff 64m - SmFixed
--1986:2: aspacem 1:  000400-0057ff   1344m
--1986:2: aspacem 2: FILE 005800-0058232fff 2306048 r-x-- d=0x001
i=47517   o=0   (0,4)
--1986:2: aspacem 3:  0058233000-005823afff   32768
--1986:2: aspacem 4: FILE 005823b000-005823cfff8192 rw--- d=0x001
i=47517   o=2306048 (0,4)
--1986:2: aspacem 5: ANON 005823d000-0058bacfff 9895936 rw---
--1986:2: aspacem 6:  0058bad000-00616b6fff139m
--1986:2: aspacem 7: RSVN 00616b7000-00616b7fff4096 - SmFixed
--1986:2: aspacem 8:  00616b8000-00bed4dfff   1494m
--1986:2: aspacem 9: ANON 00bed4e000-00bed6efff  135168 rw---
--1986:2: aspacem10: RSVN 00bed6f000-00fffe   1042m - SmFixed
--1986:2: aspacem11: anon 00-000fff4096 r-x--
--1986:2: aspacem12: RSVN 001000-00   61440 - SmFixed
--1986:2: aspacem   >>>
--1986:1:main Address space manager is running
--1986:1:main Starting the dynamic memory manager
--1986:1:mallocfr newSuperblock at 0x616B8000 (pszB 4194288)  owner
VALGRIND/core
--1986:1:mallocfr deferred_reclaimSuperblock at 0x616B8000 (pszB 4194288) 
(prev 0x0) owner VALGRIND/core
--1986:1:main Dynamic memory manager is running
--1986:1:main Initialise m_debuginfo
--1986:1:main VG_(libdir) = /tmp/valgrind/libexec/valgrind
--1986:1:main Getting launcher's name ...
--1986:1:main ... /tmp/valgrind/bin/valgrind
--1986:1:main Get hardware capabilities ...
--1986:1: machine ARMv7 VFP 1 VFP2 1 VFP3 1 NEON 1
--1986:1:   cache Could not autodetect cache info
--1986:1:main ... arch = ARM, hwcaps = ARMv7-neon-vfp
--1986:1:main Getting the working directory at startup
--1986:1:main ... /root
--1986:1:main Split up command line
--1986:1:main (early_) Process Valgrind's command line options
--1986:1:main Create initial image
--1986:1: initimg Loading client
--1986:1: initimg Setup client env
--1986:2: initimg   preload_string:
--1986:2: initimg

[kwin] [Bug 481460] With fractional scale factors on Wayland, Zoom window enlarges continuously without user interaction

[bugzilla_noreply]

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

fanzhuyi...@gmail.com changed:

   What|Removed |Added

 CC||fanzhuyi...@gmail.com

--- Comment #9 from fanzhuyi...@gmail.com ---
FWIW I can reproduce with 125% scale, 2560x1600 screen. Qt 6.7, arch linux,
wayland, zoom 5.17.10-1.

The 125% scale seems quite important, since I can't reproduce if I use 115%,
120%, 130%, or 135% scale.

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

[kwin] [Bug 483538] [Wayland] VRAM leak when repeatedly switching between window icons

[Michał Lubas]

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

Michał Lubas  changed:

   What|Removed |Added

 CC||lubaso...@hotmail.com

--- Comment #4 from Michał Lubas  ---
FWIW, I have two GPUs - RX570 (amdgpu) and 12900k integrated (i915), with one
monitor connected to each gpu. When I start switching between konsole windows
when both are present on the monitor connected to the amd gpu, the VRAM is not
rising. But when I move both konsole windows to the monitor connected to the
Intel gpu and start swithing windows then VRAM (on the *amdgpu* and also system
RAM/GTT after a while) is rising rapidly. Disabling thumbnails indeed fixes the
issue, thank you for the workaround.

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

[kate] [Bug 484024] Kate crashes when colored brackets plugin enabled

[bugzilla_noreply]

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

--- Comment #4 from nat...@upchur.ch ---
(In reply to nathan from comment #3)
> Created attachment 167491 [details]
> The file in question
> 
> Absolutely; attached.

Okay, this is strange: I just opened the file by double clicking it, and no
crash occurred. What I had been doing before was opening a session that
contained the file; when I did so, this file opened by default. When I turned
on the plugin after opening the session, Kate crashed  every time. Now that I
have opened the file by double clicking it (rather than it opening by default
when I resume a session), I can turn on the plugin and Kate does not crash when
displaying the file, even when opened via a session.

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

[kate] [Bug 484024] Kate crashes when colored brackets plugin enabled

[bugzilla_noreply]

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

--- Comment #3 from nat...@upchur.ch ---
Created attachment 167491
  --> https://bugs.kde.org/attachment.cgi?id=167491=edit
The file in question

Absolutely; attached.

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

[kwin] [Bug 483957] Add the option to Overview effect to turn Add/Remove Virtual Desktop Buttons on or off

[tracyanne]

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

--- Comment #1 from tracyanne  ---
While C++ is not one of my strengths, All of my QML development has been done
using Python, I would happily take this one on if I could understand how or
where in the code the checkboxes in KCMs ui are parsed, and the values stored.
Additionally if I could understand how or where the parms are passed from the
C++ code to the QML.

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

[Bluedevil] [Bug 482783] “Restore previous status” doesn't enable Bluetooth at boot.

[`{third : ;]

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

--- Comment #4 from `{third: "Beedell", first: "Roke"}`{.JSON5} 
<4wy78...@rokejulianlockhart.addy.io> ---
Created attachment 167490
  --> https://bugs.kde.org/attachment.cgi?id=167490=edit
Plasmoid GUI if forcefully enabled at boot regardless of previous boot's
configuration.

Noteworthily, after updating to https://kde.org/info/plasma-6.0.1/, I've a
useful demonstration — should I instruct it to enable it at boot regardless of
the preference recorded during previous OS deinitialization, it enables as
expected, but the GUI does not appear to indicate this. See the attachment — it
certainly shouldn't be able to list available devices if disabled.

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

[Powerdevil] [Bug 484031] After waking from suspend with four-monitor setup, one or two monitors don't wake up

[Zamundaaa]

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

Zamundaaa  changed:

   What|Removed |Added

 CC||m...@ratijas.tk,
   ||natalie_clar...@yahoo.de,
   ||xaver.h...@gmail.com
Product|kwin|Powerdevil
  Component|multi-screen|general
   Assignee|kwin-bugs-n...@kde.org  |plasma-b...@kde.org

--- Comment #1 from Zamundaaa  ---
KWin on x11 isn't involved in power management of screens

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

[plasmashell] [Bug 483596] Panels set to opaque remain translucent

[bugzilla_noreply]

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

fanzhuyi...@gmail.com changed:

   What|Removed |Added

 Resolution|--- |DOWNSTREAM
 CC||fanzhuyi...@gmail.com
 Status|REPORTED|RESOLVED

--- Comment #3 from fanzhuyi...@gmail.com ---
You would need to report issues with 3rd party themes to the developers of
these themes.

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

[konsole] [Bug 483951] konsole crashes when text selection contains emoji

[bugzilla_noreply]

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

fanzhuyi...@gmail.com changed:

   What|Removed |Added

  Latest Commit||https://invent.kde.org/util
   ||ities/konsole/-/commit/d590
   ||3c4795962c29fb8d9fbe2aafeed
   ||a0fb4b7b6
 Resolution|--- |FIXED
 Status|REPORTED|RESOLVED
 CC||fanzhuyi...@gmail.com

--- Comment #3 from fanzhuyi...@gmail.com ---
Cannot reproduce on git build, so let's call this fixed.

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

[kcolorchooser] [Bug 479406] The "Pick Screen Color" button is missing on Wayland session

[Andrew]

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

Andrew  changed:

   What|Removed |Added

 CC||andrewnguyen...@gmail.com

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

[kwin] [Bug 483789] While holding down shortcut to open or close an effect such as Overview, Grid, etc. the effect constantly open and closes manically

[bugzilla_noreply]

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

--- Comment #7 from fanzhuyi...@gmail.com ---
(In reply to postix from comment #6)
> May I open another more general issue for it? I mean it doesn't need to be
> resolved immediately but it could be on the radar and implemented later ...

This introduces inconsistencies in how shortcuts are handled, complicates the
UX, and adds more code complexity for little benefit.

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

[plasmashell] [Bug 482469] Plasmashell does not remember desktop icon size or programs in the panel

[Randall Winkhart]

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

--- Comment #19 from Randall Winkhart  ---
(In reply to rdbladefan91 from comment #18)
> I had the same problem in regards to plasmashell not remembering  programs
> in the panel after a reset. A workaround for me was to switch to a Plasma 6
> X11 Session and then pin the applications to the taskbar and then switch
> back to the wayland session.

Setting up my task manager icons in X11 then switching back to Wayland worked
for me, as well.

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

[Powerdevil] [Bug 483490] No longer possible to set DDC/CI compatible external monitor to 0% brightness using system tray screen brightness slider (limited to 1%)

[NW]

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

--- Comment #6 from NW  ---
Alternative: https://bugs.kde.org/show_bug.cgi?id=484033

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

[systemsettings] [Bug 484032] Bring back feature to change icons size for Qt apps

[medin]

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

medin  changed:

   What|Removed |Added

Summary|Bring back feature to   |Bring back feature to
   |change icons size   |change icons size for Qt
   ||apps

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

[Powerdevil] [Bug 484033] New: Screen brightness system tray icon mouse scroll wheel 0% adjustment

[NW]

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

Bug ID: 484033
   Summary: Screen brightness system tray icon mouse scroll wheel
0% adjustment
Classification: Plasma
   Product: Powerdevil
   Version: 6.0.2
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: nw9165-jjnfov5...@yahoo.com
CC: m...@ratijas.tk, natalie_clar...@yahoo.de
  Target Milestone: ---

According to https://bugs.kde.org/show_bug.cgi?id=483490 , the minimum value of
the system tray screen brightness slider was intentionally limited to 1% (so
that it can no longer be set to 0%) for KDE Plasma 6.

However:

When hovering the mouse cursor over the system tray screen brightness icon
(without clicking it) and then using the mouse scroll wheel to reduce the
screen brightness (by scrolling down), the screen brightness can still be set
to 0%.

Is this also intentional?

Getting the system tray icon mouse scroll wheel adjustment method also limited
to 1% is not necessarily the purpose of this bug report. Because the system
tray icon mouse scroll wheel adjustment method allows KDE Plasma users to
retain full control over the screen brightness. The bug report's purpose is
merely to clarify if it is intentionally working.

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

[konsole] [Bug 482481] Konsole forces full hinting (hintfull) despite both fontconfig and KDE settings

[bugzilla_noreply]

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

ninj...@gmail.com changed:

   What|Removed |Added

 CC||ninj...@gmail.com

--- Comment #2 from ninj...@gmail.com ---
This was done because Qt6 removed QFont::ForceIntegerMetrics, which was what
previous konsole versions used to force glyphs to conform to the character cell
grid of a terminal.

Now, on Qt6, we enable full hinting for the same reason, see
https://invent.kde.org/utilities/konsole/-/merge_requests/911

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

[systemsettings] [Bug 484032] New: Bring back feature to change icons size

[medin]

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

Bug ID: 484032
   Summary: Bring back feature to change icons size
Classification: Applications
   Product: systemsettings
   Version: 6.0.2
  Platform: Manjaro
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: kcm_icons
  Assignee: plasma-b...@kde.org
  Reporter: med.medin.2...@gmail.com
  Target Milestone: ---

Created attachment 167489
  --> https://bugs.kde.org/attachment.cgi?id=167489=edit
Big toolbar icons

After upgrading to Plasma 6.0.2, all my toolbars icons' size got reset and they
appear incorrectly bigger on my small 15.6" screen, even if I set my font to
9pt, it's truly frustrating to change icon size for each Qt app but it's
bearable, the real problem is that some apps/tools don't have any way to change
their icons size like spectacle, open/save dialogs...

The feature was removed under the pretext that it doesn't work globally for non
Qt apps, but who care for them, we simply need it to change icons size for Qt
apps, especially on Plasma desktop where users use mostly Qt apps and few GTK
ones. Even GNOME don't give any attention to Qt apps and simply locked their
ugly Adwaita apps into our face, so why should KDE remove a useful feature for
its Qt apps to appease those parties.

For now, scaling down my display is not working and every possible scale value
results in a blurry interface including icons, fonts and widgets. And even if
scaling down is fixed, I don't think it will correctly pick small (16px) as my
default toolbar icons size, so it will always appear inconsistent.

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

[konsole] [Bug 483951] konsole crashes when text selection contains emoji

[bugzilla_noreply]

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

ninj...@gmail.com changed:

   What|Removed |Added

 CC||ninj...@gmail.com

--- Comment #2 from ninj...@gmail.com ---
This looks like one of the cases fixed by
https://invent.kde.org/utilities/konsole/-/merge_requests/958

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

[kwin] [Bug 484031] New: After waking from suspend with four-monitor setup, one or two monitors don't wake up

[bugzilla_noreply]

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

Bug ID: 484031
   Summary: After waking from suspend with four-monitor setup, one
or two monitors don't wake up
Classification: Plasma
   Product: kwin
   Version: 6.0.2
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: multi-screen
  Assignee: kwin-bugs-n...@kde.org
  Reporter: g...@section9.follonica.org
  Target Milestone: ---

Created attachment 167488
  --> https://bugs.kde.org/attachment.cgi?id=167488=edit
qdbus org.kde.KWin /KWin supportInformation

SUMMARY
I have a four-monitor setup. All monitors have different resolutions and are
connected to an AMD RX580.
Sometimes, after waking up the system after a suspend event, one or two
monitors don't wake up. This issue never happened to me before upgradeing to
Plasma 6.0.0. I'm running on X11.

STEPS TO REPRODUCE
1. Suspend the system via systemctl suspend or by clicking "sleep" in kickoff
2. wait some time
3. wake up the system

OBSERVED RESULT
One or two monitors, approximatly 50% of the time, don't wake up. The monitors
that don't wake up are always the same, one connected via an HDMI-DVI adapter
and the other via an HDMI one. The other two monitors, hooked up via HDMI and
DP always wake up without issues.

EXPECTED RESULT
All monitors wake up.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Fedora Linux 39
KDE Plasma Version:  6.0.2
KDE Frameworks Version:  6.0.0
Qt Version: 6.6.2

ADDITIONAL INFORMATION

xrandr output after waking up and one monitor off (HDMI-A-1):
Screen 0: minimum 320 x 200, current 4480 x 2284, maximum 16384 x 16384
DisplayPort-0 connected primary 2560x1440+1920+844 (normal left inverted right
x axis y axis) 597mm x 336mm
2560x1440 59.95*+  74.9772.0060.0250.0148.00
1920x1200 59.95
1920x1080 74.9760.0050.0059.94
1600x1200 59.95
1280x1440 59.91
1680x1050 59.95
1280x1024 75.0260.02
1440x900  59.89
1280x960  60.00
1280x800  59.95
1280x720  60.0050.0059.94
1024x768  75.0370.0760.00
832x624   74.55
800x600   72.1975.0060.3256.25
720x576   50.00
720x480   60.0059.94
640x480   75.0072.8166.6760.0059.94
720x400   70.08
DisplayPort-1 disconnected (normal left inverted right x axis y axis)
HDMI-A-0 connected 1280x1024+640+0 inverted (normal left inverted right x axis
y axis) 338mm x 270mm
1280x1024 60.02*+  75.02
1280x800  60.02
1152x864  75.00
1280x720  60.02
1024x768  75.0370.0760.00
832x624   74.55
800x600   72.1975.0060.3256.25
640x480   75.0072.8166.6759.94
720x400   70.08
HDMI-A-1 connected (normal left inverted right x axis y axis)
1920x1080 60.00 +  50.0050.0059.94
1680x1050 59.88
1600x900  60.00
1280x1024 60.02
1440x900  59.90
1280x800  59.91
1280x720  60.0050.0059.94
1024x768  60.00
800x600   60.32
720x576   50.00
720x480   60.0059.94
640x480   60.0059.94
DVI-D-0 connected 1920x1080+0+1024 (normal left inverted right x axis y axis)
510mm x 290mm
1920x1080 60.00*+
1680x1050 59.88
1280x1024 60.02
1440x900  60.00
1280x960  60.00
1280x800  60.00
1152x864  59.97
1280x720  60.00
1024x768  60.00
800x600   60.32
640x480   59.94

Have to wake up the monitor via "xrandr --output HDMI-A-1 --auto" and
subsequently rearrange the disposition with kscreen kcm.

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

[yakuake] [Bug 385882] Yakuake Wayland: when launching Yakuake the second time it appears in the middle of the screen

[Nicolas Fella]

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

Nicolas Fella  changed:

   What|Removed |Added

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

--- Comment #19 from Nicolas Fella  ---
I cannot directly reproduce the problem.

Yakuake uses the plasma-shell Wayland protocol for positioning on Wayland.
Based on the symptoms I suspect that is going wrong.

When I comment out
https://invent.kde.org/utilities/yakuake/-/blob/master/app/mainwindow.cpp?ref_type=heads#L168
so that m_plasmaShell is never initialized Yakuake indeed appears in the middle
of the screen (which is an artifact of the default 'Centered' window placement
policy)

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

[plasmashell] [Bug 484030] New: Black screen on Plasma 6 login after changing theme

[bugzilla_noreply]

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

Bug ID: 484030
   Summary: Black screen on Plasma 6 login after changing theme
Classification: Plasma
   Product: plasmashell
   Version: 6.0.2
  Platform: unspecified
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: generic-crash
  Assignee: plasma-b...@kde.org
  Reporter: bsnapc...@gmail.com
  Target Milestone: 1.0

Application: plasmashell (6.0.2)

Qt Version: 6.6.2
Frameworks Version: 6.0.0
Operating System: Linux 6.7.6-201.fsync.fc39.x86_64 x86_64
Windowing System: Wayland
Distribution: Nobara Linux 39 (KDE Plasma)
DrKonqi: 6.0.2 [CoredumpBackend]

-- Information about the crash:
I wasn't doing anything noteworthy, just downloading and trying theme's via the
built in "get new" function for downloading themes.   I tried going back to the
original Breeze Dark theme, and it did not apply correctly.   I figured this
could be remedied by restarting the machine, but after logging in to my user
account,  I was greeted with a black screen and a "Plasmashell - Crash Handler"
message.   I can open programs via terminal, but I have no desktop background
picture, and no taskbar.   If I hover my mouse over where the taskbar would be,
and get about 10 or more Plasmashell crash handler messages.   I've tried to
updates, and while I can update fine, it doesn't fix the issue.   I'm using
Nobara 39.

The reporter is unsure if this crash is reproducible.

-- Backtrace:
Application: plasmashell (plasmashell), signal: Segmentation fault


This GDB supports auto-downloading debuginfo from the following URLs:
  
Enable debuginfod for this session? (y or [n]) [answered N; input not from
terminal]
Debuginfod has been disabled.
To make this setting permanent, add 'set debuginfod enabled off' to .gdbinit.
[New LWP 50247]
[New LWP 50072]
[New LWP 50122]
[New LWP 50121]
[New LWP 49985]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
Core was generated by `/usr/bin/plasmashell --no-respawn'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x7fe6fa8ae834 in __pthread_kill_implementation () from
/lib64/libc.so.6
[Current thread is 1 (Thread 0x7fe6e52006c0 (LWP 50247))]
Cannot QML trace cores :(
[Current thread is 1 (Thread 0x7fe6e52006c0 (LWP 50247))]

Thread 5 (Thread 0x7fe6f5d54b00 (LWP 49985)):
#0  0x7fe6fa8a9169 in __futex_abstimed_wait_common () at /lib64/libc.so.6
#1  0x7fe6fa8abb09 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libc.so.6
#2  0x7fe6fb158d7b in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at
/lib64/libQt6Core.so.6
#3  0x7fe6fc4fbeed in
QQmlThread::internalCallMethodInThread(QQmlThread::Message*) () at
/lib64/libQt6Qml.so.6
#4  0x7fe6fc64ff42 in QQmlTypeLoader::load(QQmlDataBlob*,
QQmlTypeLoader::Mode) () at /lib64/libQt6Qml.so.6
#5  0x7fe6fc650628 in QQmlTypeLoader::getType(QUrl const&,
QQmlTypeLoader::Mode) () at /lib64/libQt6Qml.so.6
#6  0x7fe6fc52c625 in QQmlComponentPrivate::loadUrl(QUrl const&,
QQmlComponent::CompilationMode) () at /lib64/libQt6Qml.so.6
#7  0x7fe6fdf4976c in PlasmaQuick::SharedQmlEngine::setSource(QUrl const&)
() at /lib64/libPlasmaQuick.so.6
#8  0x7fe6fdf616a9 in ContainmentItem::loadWallpaper() () at
/lib64/libPlasmaQuick.so.6
#9  0x7fe6fdf61fa7 in ContainmentItem::itemChange(QQuickItem::ItemChange,
QQuickItem::ItemChangeData const&) () at /lib64/libPlasmaQuick.so.6
#10 0x7fe6fca3ee5b in QQuickItemPrivate::refWindow(QQuickWindow*) () at
/lib64/libQt6Quick.so.6
#11 0x7fe6fca3f29d in QQuickItem::setParentItem(QQuickItem*) () at
/lib64/libQt6Quick.so.6
#12 0x7fe6fdf4426a in
PlasmaQuick::ContainmentViewPrivate::setContainment(Plasma::Containment*) () at
/lib64/libPlasmaQuick.so.6
#13 0x5594fe1b6d36 in ShellCorona::addOutput(QScreen*) ()
#14 0x5594fe1ba6df in ShellCorona::loadDefaultLayout() ()
#15 0x7fe6fda91c05 in Plasma::Corona::loadLayout(QString const&) () at
/lib64/libPlasma.so.6
#16 0x5594fe1bb932 in ShellCorona::load() ()
#17 0x7fe6fb001951 in void doActivate(QObject*, int, void**) () at
/lib64/libQt6Core.so.6
#18 0x7fe6fd982313 in
KActivities::Consumer::serviceStatusChanged(KActivities::Consumer::ServiceStatus)
() at /lib64/libPlasmaActivities.so.6
#19 0x7fe6fb001951 in void doActivate(QObject*, int, void**) () at
/lib64/libQt6Core.so.6
#20 0x7fe6fd98fee3 in
KActivities::ActivitiesCache::setAllActivities(QList const&) ()
at /lib64/libPlasmaActivities.so.6
#21 0x7fe6fd993454 in
KActivities::ActivitiesCache::qt_static_metacall(QObject*, QMetaObject::Call,
int, void**) () at /lib64/libPlasmaActivities.so.6
#22 0x7fe6fb001ed8 in void doActivate(QObject*, int, void**) () at
/lib64/libQt6Core.so.6
#23 0x7fe6fc0191b1 in

[kwin] [Bug 483605] Pop-up Windows Resizing Themselves Automatically

[Ryan Ronnander]

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

--- Comment #2 from Ryan Ronnander  ---
(In reply to David Edmundson from comment #1)
> Can you share what scale factor you use?

Sure thing, I am using 250% scale factor and "legacy applications apply scaling
themselves".

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

[KScreen] [Bug 483993] Display Configuration OSD / Screen Layout - adjusting settings doesn't work under X11

[Nicolas Fella]

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

Nicolas Fella  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
 CC||nicolas.fe...@gmx.de
 Resolution|--- |DUPLICATE

--- Comment #1 from Nicolas Fella  ---


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

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

[KScreen] [Bug 482642] On X11, cannot change multi-screen settings via OSD

[Nicolas Fella]

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

Nicolas Fella  changed:

   What|Removed |Added

 CC||wladys...@outlook.com

--- Comment #15 from Nicolas Fella  ---
*** Bug 483993 has been marked as a duplicate of this bug. ***

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

[plasmashell] [Bug 482811] On X11, After upgrading from Plasma 5, panel always moves moved from one screen to another one after screen unlock

[Samuel]

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

--- Comment #10 from Samuel  ---
(In reply to Nate Graham from comment #8)
> Oh I have one more question, if you don't mind:
> 
> When this happens, can you make the issue go away by restarting plasmashell
> with `systemctl restart --user plasma-plasmashell.service` (assuming you're
> using the systemd boot; if not, try `plasmashell --replace`)?

Got back and test it, used systemctl restart --user plasma-plasmashell.service
when it happened, and totally worked, also, when the bug appeared again,
entering in edit mode got the taskbar back too.

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

[okular] [Bug 482904] Okular segfaults when changing languages for voice

[Albert Astals Cid]

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

Albert Astals Cid  changed:

   What|Removed |Added

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

--- Comment #1 from Albert Astals Cid  ---
Could perfectly be an issue in qt yes.

Can you try giving valgrind a go to see if it gives you some more interesting
information?

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

[bugzilla_noreply]

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

fanzhuyi...@gmail.com changed:

   What|Removed |Added

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

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

[plasmashell] [Bug 483962] The widget search overlaps items

[bugzilla_noreply]

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

fanzhuyi...@gmail.com changed:

   What|Removed |Added

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

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

[valgrind] [Bug 484002] Add suppression for invalid read in glibc's __wcpncpy_avx2() via wcsxfrm()

[Sam James]

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

Sam James  changed:

   What|Removed |Added

   See Also||https://sourceware.org/bugz
   ||illa/show_bug.cgi?id=31509
 CC||s...@gentoo.org

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

[krita] [Bug 484029] New: The display of the krita.org sitemap in the browser is just a list of text

[bugzilla_noreply]

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

Bug ID: 484029
   Summary: The display of the krita.org sitemap in the browser is
just a list of text
Classification: Applications
   Product: krita
   Version: git master (please specify the git hash!)
  Platform: Microsoft Windows
OS: Microsoft Windows
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: * Unknown
  Assignee: krita-bugs-n...@kde.org
  Reporter: suzihi...@ruru.be
  Target Milestone: ---

SUMMARY
I'm not an English speaker, so forgive me if there are some strange
expressions.
If you view the following URL in your browser, you will see a string of text
instead of the website you expect to see.
Without a sitemap it is impossible to navigate to pages that do not have links
on the page.
https://krita.org/en/sitemap.xml

STEPS TO REPRODUCE
1. Go to https://krita.org
2. Click on the Sitemap link at the bottom of the page

OBSERVED RESULT
It takes me to a page that looks like a text log.

EXPECTED RESULT
A page with links to various pages is displayed.

SOFTWARE/OS VERSIONS
Windows: 10 Pro 22H2

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

[okular] [Bug 484017] Yellow highlight and pop-up note color is (subjectively) too intense, should use a muted color similar to Plasma's sticky note yellow

[Albert Astals Cid]

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

Albert Astals Cid  changed:

   What|Removed |Added

 CC||aa...@kde.org

--- Comment #1 from Albert Astals Cid  ---
We have had these colors for decades. I don't see the need to change them given
that they are configurable, if someone doesn't like them, they can be changed.

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

[plasmashell] [Bug 483272] Panel widgets overlap with each other at login

[bugzilla_noreply]

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

fanzhuyi...@gmail.com changed:

   What|Removed |Added

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

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

[plasmashell] [Bug 477317] Non-floating Panel with "Fit Content" does not take the correct width on plasmashell start if Digital Clock is present, but resizes to correct width if "Edit Mode" is activa

[bugzilla_noreply]

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

fanzhuyi...@gmail.com changed:

   What|Removed |Added

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

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

[plasma-systemmonitor] [Bug 483978] Overview - System Monitor - Disk Icon displays 'total space'

[bugzilla_noreply]

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

teadrinkingprogram...@proton.me changed:

   What|Removed |Added

 CC||ahiems...@heimr.nl,
   ||plasma-b...@kde.org,
   ||teadrinkingprogrammer@proto
   ||n.me
  Component|general |general
Version|unspecified |6.0.2
Product|kde |plasma-systemmonitor
   Platform|Other   |Neon
   Assignee|unassigned-b...@kde.org |ksysguard-b...@kde.org

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

[plasmashell] [Bug 483962] The widget search overlaps items

[bugzilla_noreply]

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

teadrinkingprogram...@proton.me changed:

   What|Removed |Added

   Assignee|unassigned-b...@kde.org |plasma-b...@kde.org
   Target Milestone|--- |1.0
   Platform|Other   |Neon
  Component|general |Widget Explorer
Version|unspecified |6.0.2
Product|kde |plasmashell

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

[plasmashell] [Bug 482469] Plasmashell does not remember desktop icon size or programs in the panel

[bugzilla_noreply]

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

rdbladefa...@gmail.com changed:

   What|Removed |Added

 CC||rdbladefa...@gmail.com

--- Comment #18 from rdbladefa...@gmail.com ---
I had the same problem in regards to plasmashell not remembering  programs in
the panel after a reset. A workaround for me was to switch to a Plasma 6 X11
Session and then pin the applications to the taskbar and then switch back to
the wayland session.

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

[partitionmanager] [Bug 441916] Partition Manager crashed while shrinking ntfs partition (Crash in PartWidget::paintEvent)

[Andrius Štikonas]

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

Andrius Štikonas  changed:

   What|Removed |Added

 CC||lee.head.5...@gmail.com

--- Comment #17 from Andrius Štikonas  ---
*** Bug 484028 has been marked as a duplicate of this bug. ***

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

[partitionmanager] [Bug 484028] kde partition manager crash

[Andrius Štikonas]

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

Andrius Štikonas  changed:

   What|Removed |Added

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

--- Comment #1 from Andrius Štikonas  ---


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

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

[plasmashell] [Bug 483961] Application Menu Launcher not wrapping around when using keypresses

[bugzilla_noreply]

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

teadrinkingprogram...@proton.me changed:

   What|Removed |Added

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

--- Comment #2 from teadrinkingprogram...@proton.me ---
-

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

[yakuake] [Bug 477908] Yakuake not working correctly after KWin Wayland crash

[Louis Moureaux]

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

--- Comment #5 from Louis Moureaux  ---
> Yakuake uses the KWayland library to do Wayland things. It doesn't handle 
> compositor restarts properly, likely causing this bug.

Sounds like something I could look at if you have a more precise pointer (no
promise though, especially on a timeline).

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

[plasmashell] [Bug 483961] Application Menu Launcher not wrapping around when using keypresses

[bugzilla_noreply]

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

--- Comment #1 from teadrinkingprogram...@proton.me ---
Hi there! Thank you for reporting this bug.
Could you please fill in the bugreport template? This helps the bug report get
to the right people. Could you also fill in the correct version number in the
bugreport metadata? I already prefilled the correct product and component for
you.

Thanks!

Here is the template:

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

[plasmashell] [Bug 483961] Application Menu Launcher not wrapping around when using keypresses

[bugzilla_noreply]

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

teadrinkingprogram...@proton.me changed:

   What|Removed |Added

  Component|general |Application Launcher
   ||(Kickoff)
   Assignee|unassigned-b...@kde.org |plasma-b...@kde.org
Product|kde |plasmashell
Version|unspecified |6.0.1
   Target Milestone|--- |1.0
 CC||mikel5...@gmail.com,
   ||noaha...@gmail.com,
   ||teadrinkingprogrammer@proto
   ||n.me

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

[partitionmanager] [Bug 481117] PartitionManager crash when shrinking ext4, session firefox open and move two windows of Partition Manager

[bugzilla_noreply]

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

lee.head.5...@gmail.com changed:

   What|Removed |Added

 CC||lee.head.5...@gmail.com

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

[yakuake] [Bug 477908] Yakuake not working correctly after KWin Wayland crash

[Nicolas Fella]

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

--- Comment #4 from Nicolas Fella  ---
(In reply to Louis Moureaux from comment #3)
> Related to https://bugs.kde.org/show_bug.cgi?id=385882 ?

Yakuake uses the KWayland library to do Wayland things. It doesn't handle
compositor restarts properly, likely causing this bug.

A similar problem could also explain
https://bugs.kde.org/show_bug.cgi?id=385882

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

[kwin] [Bug 483243] kwin_wayland segfault every morning while turning monitors on and unlocking

[andy]

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

--- Comment #6 from andy  ---
I wrapped my screenshot operations around checking `dbus-send --session
--dest=org.freedesktop.ScreenSaver --type=method_call --print-reply
/org/freedesktop/ScreenSaver org.freedesktop.ScreenSaver.GetActive`. It seems
to have done the trick, no crash this morning.

Maybe this is still relevant to fix for the sake of kwin shouldn't be able to
get segfaulted by a screenshot program.

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

[kate] [Bug 484024] Kate crashes when colored brackets plugin enabled

[Waqar Ahmed]

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

Waqar Ahmed  changed:

   What|Removed |Added

 CC||waqar@gmail.com

--- Comment #2 from Waqar Ahmed  ---
The backtrace says otherwise.

Would it be possible for you to share the file which causes the crash?

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

[partitionmanager] [Bug 484028] New: kde partition manager crash

[bugzilla_noreply]

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

Bug ID: 484028
   Summary: kde partition manager crash
Classification: Applications
   Product: partitionmanager
   Version: 23.08.5
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: andr...@stikonas.eu
  Reporter: lee.head.5...@gmail.com
  Target Milestone: ---

Application: partitionmanager (23.08.5)

Qt Version: 5.15.12
Frameworks Version: 5.115.0
Operating System: Linux 6.7.9-200.fc39.x86_64 x86_64
Windowing System: Wayland
Distribution: "Fedora Linux 39 (KDE Plasma)"
DrKonqi: 5.27.11 [KCrashBackend]

-- Information about the crash:
Working with USB storage, I had just deleted 3 partitions and applied changes.
Then I created a single new partition and applied changes. I left the program
running while I looked up a thing or two in my browser. When I returned, I saw
the crash notice and bug report request.

The reporter is unsure if this crash is reproducible.

-- Backtrace:
Application: KDE Partition Manager (partitionmanager), signal: Segmentation
fault

[KCrash Handler]
#4  0x7f64c54aa4ff in PartWidget::paintEvent(QPaintEvent*) () at
/lib64/libkpmcore.so.12
#5  0x7f64c47f36b8 in QWidget::event(QEvent*) () at
/lib64/libQt5Widgets.so.5
#6  0x7f64c47aeb95 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /lib64/libQt5Widgets.so.5
#7  0x7f64c3ab4e78 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at /lib64/libQt5Core.so.5
#8  0x7f64c47eb3ce in QWidgetPrivate::sendPaintEvent(QRegion const&) () at
/lib64/libQt5Widgets.so.5
#9  0x7f64c47ec22d in QWidgetPrivate::drawWidget(QPaintDevice*, QRegion
const&, QPoint const&, QFlags, QPainter*,
QWidgetRepaintManager*) () at /lib64/libQt5Widgets.so.5
#10 0x7f64c47ed1dd in QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*,
QList const&, int, QRegion const&, QPoint const&,
QFlags, QPainter*, QWidgetRepaintManager*) ()
at /lib64/libQt5Widgets.so.5
#11 0x7f64c47eb6d3 in QWidgetPrivate::drawWidget(QPaintDevice*, QRegion
const&, QPoint const&, QFlags, QPainter*,
QWidgetRepaintManager*) () at /lib64/libQt5Widgets.so.5
#12 0x7f64c47ed1dd in QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*,
QList const&, int, QRegion const&, QPoint const&,
QFlags, QPainter*, QWidgetRepaintManager*) ()
at /lib64/libQt5Widgets.so.5
#13 0x7f64c47ed030 in QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*,
QList const&, int, QRegion const&, QPoint const&,
QFlags, QPainter*, QWidgetRepaintManager*) ()
at /lib64/libQt5Widgets.so.5
#14 0x7f64c47eb6d3 in QWidgetPrivate::drawWidget(QPaintDevice*, QRegion
const&, QPoint const&, QFlags, QPainter*,
QWidgetRepaintManager*) () at /lib64/libQt5Widgets.so.5
#15 0x7f64c47ed1dd in QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*,
QList const&, int, QRegion const&, QPoint const&,
QFlags, QPainter*, QWidgetRepaintManager*) ()
at /lib64/libQt5Widgets.so.5
#16 0x7f64c47ed030 in QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*,
QList const&, int, QRegion const&, QPoint const&,
QFlags, QPainter*, QWidgetRepaintManager*) ()
at /lib64/libQt5Widgets.so.5
#17 0x7f64c47ed030 in QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*,
QList const&, int, QRegion const&, QPoint const&,
QFlags, QPainter*, QWidgetRepaintManager*) ()
at /lib64/libQt5Widgets.so.5
#18 0x7f64c47ed030 in QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*,
QList const&, int, QRegion const&, QPoint const&,
QFlags, QPainter*, QWidgetRepaintManager*) ()
at /lib64/libQt5Widgets.so.5
#19 0x7f64c47ed030 in QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*,
QList const&, int, QRegion const&, QPoint const&,
QFlags, QPainter*, QWidgetRepaintManager*) ()
at /lib64/libQt5Widgets.so.5
#20 0x7f64c47ed030 in QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*,
QList const&, int, QRegion const&, QPoint const&,
QFlags, QPainter*, QWidgetRepaintManager*) ()
at /lib64/libQt5Widgets.so.5
#21 0x7f64c47ed030 in QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*,
QList const&, int, QRegion const&, QPoint const&,
QFlags, QPainter*, QWidgetRepaintManager*) ()
at /lib64/libQt5Widgets.so.5
#22 0x7f64c47ed030 in QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*,
QList const&, int, QRegion const&, QPoint const&,
QFlags, QPainter*, QWidgetRepaintManager*) ()
at /lib64/libQt5Widgets.so.5
#23 0x7f64c47ed030 in QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*,
QList const&, int, QRegion const&, QPoint const&,
QFlags, QPainter*, QWidgetRepaintManager*) ()
at /lib64/libQt5Widgets.so.5
#24 0x7f64c47eb6d3 in QWidgetPrivate::drawWidget(QPaintDevice*, QRegion
const&, QPoint const&, QFlags, QPainter*,
QWidgetRepaintManager*) () at /lib64/libQt5Widgets.so.5
#25 0x7f64c47c0901 in QWidgetRepaintManager::paintAndFlush() () at
/lib64/libQt5Widgets.so.5

[yakuake] [Bug 385882] Yakuake Wayland: when launching Yakuake the second time it appears in the middle of the screen

[Louis Moureaux]

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

Louis Moureaux  changed:

   What|Removed |Added

 CC||m_loui...@yahoo.com

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

[kde] [Bug 483955] Task Manager odd default settings

[bugzilla_noreply]

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

teadrinkingprogram...@proton.me changed:

   What|Removed |Added

   Platform|Other   |Neon

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

[yakuake] [Bug 477908] Yakuake not working correctly after KWin Wayland crash

[Louis Moureaux]

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

Louis Moureaux  changed:

   What|Removed |Added

 CC||m_loui...@yahoo.com

--- Comment #3 from Louis Moureaux  ---
Related to https://bugs.kde.org/show_bug.cgi?id=385882 ?

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

[kde] [Bug 483953] KDE neon: Taskbar edit mode, deleting items is unnecessarily frustrating

[bugzilla_noreply]

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

teadrinkingprogram...@proton.me changed:

   What|Removed |Added

   Platform|Other   |Neon

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

[plasmashell] [Bug 484022] Libreoffice icon don't respect their pin position

[bugzilla_noreply]

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

teadrinkingprogram...@proton.me changed:

   What|Removed |Added

   Platform|Other   |Arch Linux

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

[cantor] [Bug 484027] New: Shortcut keys not indicated in menus (missing underlines)

[simon]

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

Bug ID: 484027
   Summary: Shortcut keys not indicated in menus (missing
underlines)
Classification: Applications
   Product: cantor
   Version: 24.02.0
  Platform: openSUSE
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: cantor-b...@kde.org
  Reporter: si...@i2cchip.com
  Target Milestone: ---

SUMMARY
I was going to report that there are not keyboard shortcuts in menus, but it
appears that there are.
The letter shortcut keys are not underlined as expected, so one does not know
what they are or that they even exist.

STEPS TO REPRODUCE
1. Press "alt-W   T"  A new text entry appears, so "T" shortcut exists 
2. In menu item "Insert Text Entry" , "T" is not underlined as it should be


OBSERVED RESULT
No letters are underlined in menu items

EXPECTED RESULT
Every menu item should have an underlined shortcut

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.

[neon] [Bug 483980] Neon Arm64 ISO file needed, thanks

[bugzilla_noreply]

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

teadrinkingprogram...@proton.me changed:

   What|Removed |Added

 OS|Other   |Linux
   Platform|Other   |Neon

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

[neon] [Bug 483956] neon-ubuntu-advantage-tools : Breaks: ubuntu-advantage-tools but 31.2~22.04 is to be installed

[bugzilla_noreply]

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

teadrinkingprogram...@proton.me changed:

   What|Removed |Added

   Platform|Other   |Neon

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

[kwin] [Bug 483240] VRR below 30-ish FPS turns off completely

[fililip]

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

--- Comment #4 from fililip  ---
One note I'll add: after resuming from suspend, even when using the HW cursor,
VRR still breaks below 30 FPS and requires a restart of KWin. Is this just
random behavior or a bug?

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

[kde] [Bug 483861] Need help with rearranging desktop icons issue. needs a fix.

[Nicolas Fella]

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

Nicolas Fella  changed:

   What|Removed |Added

 CC||nicolas.fe...@gmx.de
 Resolution|WAITINGFORINFO  |NOT A BUG
 Status|NEEDSINFO   |RESOLVED
   Severity|critical|normal

--- Comment #2 from Nicolas Fella  ---
This is not a suitable place to ask for support. Please use your distribution's
support channels or https://discuss.kde.org/

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