[kwin] [Bug 465790] Resizing an Aurorae-decorated window leads to malformed decorations
https://bugs.kde.org/show_bug.cgi?id=465790 --- Comment #32 from punk.salt6...@fastmail.com --- Non-qt apps like Firefox also can get it, but it happens rarely.(In reply to Michał Dybczak from comment #31) > To add more details to me previous comment: > > Maybe all apps became immune, because I couldn't trigger it anymore. > Non-qt apps like Firefox also can get it, but it happens rarely. This is the opposite of what I'm experiencing. Once the memory has been corrupted, new windows of the same app starts out as normal but easily becomes corrupted after a few minimize and move / resize events. Also for me what's inside the windows doesn't seem to matter. Firefox, kitty, obs studio, everything can get bugged. I think this just means it's very random. Random memory gets corrupted and that's why we experience different results. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 466696] Dolphin "Open With -> Other Application..." does not work.
https://bugs.kde.org/show_bug.cgi?id=466696 Petr Bartos changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG --- Comment #1 from Petr Bartos --- Problem was on my side (or Fedora packaging side). Based on this https://invent.kde.org/plasma/plasma-integration/-/merge_requests/73 i have found i am missing "xdg-desktop-portal-kde". -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 466926] New: Crash when importing faulty WireGuard config
https://bugs.kde.org/show_bug.cgi?id=466926
Bug ID: 466926
Summary: Crash when importing faulty WireGuard config
Classification: Applications
Product: systemsettings
Version: 5.27.2
Platform: Archlinux
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: general
Assignee: plasma-b...@kde.org
Reporter: dan...@naegele.dev
Target Milestone: ---
Application: systemsettings (5.27.2)
Qt Version: 5.15.8
Frameworks Version: 5.103.0
Operating System: Linux 6.2.2-arch1-1 x86_64
Windowing System: X11
Distribution: "Arch Linux"
DrKonqi: 5.27.2 [KCrashBackend]
-- Information about the crash:
Tried to import a wireguard config, which had not working keys, see here:
https://www.hardill.me.uk/wordpress/2021/04/20/setting-up-wireguard-ipv6/
[Interface]
Address = 10.9.0.2/32, 2001:8b0:2c1:xxx::2/128
PrivateKey = UFIJGgtKsor6xxxbWeKmw+Bb5ODpyNblEA=
DNS = 8.8.8.8
[Peer]
PublicKey = jMB2oMu+YTKigGxxSYcTde/7HT+QlQoZFm0=
AllowedIPs = 0.0.0.0/0, ::0/0
Endpoint = hardill.me.uk:53145
The crash can be reproduced every time.
-- Backtrace:
Application: Systemeinstellungen (systemsettings), signal: Segmentation fault
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = }
[KCrash Handler]
#6 0x7f03b2de7b97 in OpenVpnUiPlugin::importConnectionSettings(QString
const&) (this=, fileName=...) at
/usr/src/debug/plasma-nm/plasma-nm-5.27.2/vpn/openvpn/openvpn.cpp:187
#7 0x7f03c5fe3f7f in KCMNetworkmanagement::importVpn()
(this=0x55777f7c79f0) at
/usr/src/debug/plasma-nm/plasma-nm-5.27.2/kcm/kcm.cpp:569
#8 KCMNetworkmanagement::onRequestCreateConnection(int, QString const&,
QString const&, bool) (this=0x55777f7c79f0, connectionType=,
vpnType=, specificType=, shared=)
at /usr/src/debug/plasma-nm/plasma-nm-5.27.2/kcm/kcm.cpp:279
#9 0x7f03e70bec20 in doActivate(QObject*, int, void**)
(sender=0x55777ffa5150, signal_index=31, argv=0x7ffc85c914c0) at
kernel/qobject.cpp:3935
#10 0x7f03e4e3209c in QQmlVMEMetaObject::metaCall(QObject*,
QMetaObject::Call, int, void**) (this=0x55777f9d0440, o=,
c=QMetaObject::InvokeMetaMethod, _id=48, a=0x7ffc85c914c0) at
/usr/src/debug/qt5-declarative/qtdeclarative/src/qml/qml/qqmlvmemetaobject.cpp:969
#11 0x7f03e4e76544 in QQmlObjectOrGadget::metacall(QMetaObject::Call, int,
void**) const (this=0x7ffc85c91760, type=QMetaObject::InvokeMetaMethod,
index=, argv=) at
/usr/src/debug/qt5-declarative/qtdeclarative/src/qml/qml/qqmlobjectorgadget.cpp:51
#12 0x7f03e4d77671 in CallMethod (callType=,
callArgs=, engine=, argTypes=,
argCount=, returnType=, index=,
object=) at /usr/include/qt/QtCore/qvarlengtharray.h:189
#13 CallPrecise(QQmlObjectOrGadget const&, QQmlPropertyData const&,
QV4::ExecutionEngine*, QV4::CallData*, QMetaObject::Call) (object=, data=, engine=, callArgs=,
callType=) at
/usr/src/debug/qt5-declarative/qtdeclarative/src/qml/jsruntime/qv4qobjectwrapper.cpp:1553
#14 0x7f03e4d7cde2 in QV4::QObjectMethod::callInternal(QV4::Value const*,
QV4::Value const*, int) const (this=, thisObject=, argv=0x7f03b33c06d8, argc=) at
/usr/src/debug/qt5-declarative/qtdeclarative/src/qml/jsruntime/qv4qobjectwrapper.cpp:2115
#15 0x7f03e4d8eda3 in QV4::Moth::VME::interpret(QV4::CppStackFrame*,
QV4::ExecutionEngine*, char const*) (frame=0x7ffc85c91b70,
engine=0x55777f9b4350, code=0x7f03b33c06c0 "\300\311\377\262\003\177") at
/usr/src/debug/qt5-declarative/qtdeclarative/src/qml/jsruntime/qv4vme_moth.cpp:757
#16 0x7f03e4d94804 in QV4::Moth::VME::exec(QV4::CppStackFrame*,
QV4::ExecutionEngine*) (frame=, engine=) at
/usr/src/debug/qt5-declarative/qtdeclarative/src/qml/jsruntime/qv4vme_moth.cpp:466
#17 0x7f03e4d36c36 in QV4::Function::call(QV4::Value const*, QV4::Value
const*, int, QV4::ExecutionContext const*) (this=,
thisObject=, argv=, argc=,
context=) at
/usr/src/debug/qt5-declarative/qtdeclarative/src/qml/jsruntime/qv4function.cpp:69
#18 0x7f03e4e971ad in QQmlJavaScriptExpression::evaluate(QV4::CallData*,
bool*) (this=0x55777fb73290, callData=0x7f03b33c0618, isUndefined=0x0) at
/usr/src/debug/qt5-declarative/qtdeclarative/src/qml/qml/qqmljavascriptexpression.cpp:212
#19 0x7f03e4e537f1 in QQmlBoundSignalExpression::evaluate(void**)
(this=this@entry=0x55777fb73290, a=a@entry=0x7ffc85c93a60) at
/usr/src/debug/qt5-declarative/qtdeclarative/src/qml/qml/qqmlboundsignal.cpp:224
#20 0x7f03e4e5476c in QQmlBoundSignal_callback(QQmlNotifierEndpoint*,
void**) (a=0x7ffc85c93a60, e=0x55777fb733b0) at
../../include/QtQml/5.15.8/QtQml/private/../../../../../../qtdeclarative/src/qml/qml/qqmlboundsignalexpressionpointer_p.h:69
#21 QQmlBoundSignal_callback(QQmlNotifierEndpoint*, void**) (e=0x55777fb733b0,
a=0x7ffc85c93a60) at
/usr/src/debug/qt5-declarative/qtdeclarative/src/qml/qml/qqmlboundsignal.cpp:341
#22 0x7f03e4e7647f in QQmlNotifier::emitNotify(QQmlNotifierEndpoint*,
void**)
[digikam] [Bug 466893] Hidden elements in the Pick Label and Color Label locations
https://bugs.kde.org/show_bug.cgi?id=466893 --- Comment #5 from Maik Qualmann --- I wouldn't change the color and pick labels widgets in the Description tab at this time. In the Filter tab you need to be able to select multiple color and pick labels, so all of them are visible. In the Description tab I can only assign one of them to an image. Also, the visibility of which color or pick label is worse only through the shadow of the tool button. The color and pick labels are also accessible via key shortcuts. Maik -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 457859] Powerdevil does not respect sleep inhibitors created with systemd-inhibit by unprivileged users
https://bugs.kde.org/show_bug.cgi?id=457859 bugs.kde.org-...@meurisse.org changed: What|Removed |Added CC||bugs.kde.org-c69@meurisse.o ||rg -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 462307] File icons are drawn at wrong position if desktop scaling is active
https://bugs.kde.org/show_bug.cgi?id=462307 --- Comment #18 from Evgeny Brazgin --- PR: https://invent.kde.org/utilities/krusader/-/merge_requests/118 -- You are receiving this mail because: You are watching all bug changes.
[qca] [Bug 466854] 2.3.5: test suite is failing in `Hashing` unit
https://bugs.kde.org/show_bug.cgi?id=466854 --- Comment #3 from Brad Hards --- I'm sorry if you misinterpreted my comments. Please understand that you aren't really describing your situation, configuration or test environment in detail, and we need to understand those in order to work out if there is a problem, and if so, what the problem is. I really do want to know what providers (the backend implementations that QCA uses, and is testing in that test) you are using / have compiled. The capabilities of QCA depend on the functionality in the library that is wrapped by the provider. Please tell me what library is. It looks like this is some redhat variant - I'm not familiar with the crypto policies on any of those. Is it possible that your libraries (say OpenSSL) are built without any support for the failing hash algorithms? Can you test if those specific algorithms work with the libraries independent of QCA (e.g. using openssl command line tools)? -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 462307] File icons are drawn at wrong position if desktop scaling is active
https://bugs.kde.org/show_bug.cgi?id=462307
Evgeny Brazgin changed:
What|Removed |Added
CC||k...@xapienz.ru
--- Comment #17 from Evgeny Brazgin ---
Thanks Benjamin for finding the cause!
I found a shorter workaround — just wrap a pixmap into QIcon.
diff --git a/app/Panel/PanelView/listmodel.cpp
b/app/Panel/PanelView/listmodel.cpp
index d6ad6c5f..7731e895 100644
--- a/app/Panel/PanelView/listmodel.cpp
+++ b/app/Panel/PanelView/listmodel.cpp
@@ -177,7 +177,7 @@ QVariant ListModel::data(const QModelIndex& index, int
role) const
if (properties()->displayIcons) {
if (_justForSizeHint)
return QPixmap(_view->fileIconSize(),
_view->fileIconSize());
-return _view->getIcon(fileitem);
+return QIcon(_view->getIcon(fileitem));
}
break;
}
It might be more efficient to change all the inner calls of it to directly
return QIcon (because this is what the things inside operate with), however
that would be a lot more complicated solution.
--
You are receiving this mail because:
You are watching all bug changes.
[calligrasheets] [Bug 466925] clicking cell border color wheel freezes the application
https://bugs.kde.org/show_bug.cgi?id=466925 --- Comment #1 from Roberto Rodríguez --- On step 3, I mean to click the color red in the triangle -- You are receiving this mail because: You are watching all bug changes.
[calligrasheets] [Bug 466925] New: clicking cell border color wheel freezes the application
https://bugs.kde.org/show_bug.cgi?id=466925 Bug ID: 466925 Summary: clicking cell border color wheel freezes the application Classification: Applications Product: calligrasheets Version: 3.2.1 Platform: Slackware OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: calligra-sheets-bugs-n...@kde.org Reporter: robertorodrig...@wp.pl Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Select a range of cells 2. Add a border to the cells 3. Click the red color on the color wheel OBSERVED RESULT A spinner cursor is displayed and the application doesn't respond anymore. EXPECTED RESULT The cell border(s) turn red SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Debian 11.6 and Slackware 15.0 (available in About System) KDE Plasma Version: 5.23.5 KDE Frameworks Version: 5.90.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION If you select the color BEFORE applying a border, it works fine. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 459373] Maximized XWayland apps leave pixel gaps when using a fractional scaling factor
https://bugs.kde.org/show_bug.cgi?id=459373 --- Comment #28 from hexchain --- I have a panel on the left screen edge. When an XWayland window is already maximized, changing the panel width or changing the scale factor a little bit (e.g. 175 to 170 or 180 and vice versa) makes gaps disappear. But they come back after re-maximizing the window. -- You are receiving this mail because: You are watching all bug changes.
[NeoChat] [Bug 462732] Two Low Priority sections after first start and login
https://bugs.kde.org/show_bug.cgi?id=462732 Justin Zobel changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #4 from Justin Zobel --- I haven't seen this for a long time, resolving it. Will open a new one if it happens again. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466924] New: Improve UX of Emoji Selector with additional settings
https://bugs.kde.org/show_bug.cgi?id=466924 Bug ID: 466924 Summary: Improve UX of Emoji Selector with additional settings Classification: Plasma Product: plasmashell Version: master Platform: unspecified OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: Emoji Selector Assignee: plasma-b...@kde.org Reporter: calm.song3...@dmu.gg Target Milestone: 1.0 Emojis should be quick and easy to add to text. I'd like to recommend a couple of changes that would help make the Emoji Selector faster and more efficient to use: 1. Introduce a settings area to customise the behaviour. 2. Add a dropdown setting to change the behaviour when selecting an emoji with the following options: Insert (default), Insert & Copy, Copy. 3. Add a boolean setting to automatically close the Emoji Selector window after selecting an emoji. This feature would close Bug 434932 and would bring the Emoji Selector UX to be on-par with other popular solutions. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 466923] XWayland Crash on Wake
https://bugs.kde.org/show_bug.cgi?id=466923 --- Comment #2 from Jason Playne --- xwayland installed version is 2:22.1.1-1ubuntu0.5 -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 466923] XWayland Crash on Wake
https://bugs.kde.org/show_bug.cgi?id=466923 --- Comment #1 from Jason Playne --- The first entry in systemd's coredump list for /usr/bin/Xwayland is from Fri 2022-12-09 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 433854] A lot of times copy-paste does not work.
https://bugs.kde.org/show_bug.cgi?id=433854 --- Comment #24 from tomtomtomreportin...@gmail.com --- Er, I might have posted in the wrong issue then. The issue I have been having is relatively recent and I only realized now that this report is from 2021. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 466923] New: XWayland Crash on Wake
https://bugs.kde.org/show_bug.cgi?id=466923 Bug ID: 466923 Summary: XWayland Crash on Wake Classification: I don't know Product: kde Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: ja...@jasonplayne.com Target Milestone: --- Created attachment 157029 --> https://bugs.kde.org/attachment.cgi?id=157029=edit The the back traces in systemd after resume 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 a wayland session 2. open an xwayland app (for example, discord) 3. push system to sleep 4. wake system OBSERVED RESULT No XWayland apps are running EXPECTED RESULT The software I started before putting the machine to sleep is there when I wake it up SOFTWARE/OS VERSIONS Operating System: KDE neon 5.27 KDE Plasma Version: 5.27.2 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 6.2.2-x64v3-xanmod1 (64-bit) Graphics Platform: Wayland Processors: 24 × AMD Ryzen 9 7900X 12-Core Processor Memory: 30.5 GiB of RAM Graphics Processor: AMD Radeon RX 7900 XT Manufacturer: Gigabyte Technology Co., Ltd. Product Name: B650 AORUS ELITE AX ADDITIONAL INFORMATION this happens every time i put the computer to sleep and wake it again. It has been happening for a while now (sometime during the 5.26 release cycle) -- You are receiving this mail because: You are watching all bug changes.
[kmenuedit] [Bug 466164] kmenueditor crashes after saving and reediting the item.
https://bugs.kde.org/show_bug.cgi?id=466164 --- Comment #3 from Matias Barletta --- Created attachment 157028 --> https://bugs.kde.org/attachment.cgi?id=157028=edit New crash information added by DrKonqi kmenuedit (5.27.2) using Qt 5.15.8 Editing Menu, selecting the offending menu item, then crash -- Backtrace (Reduced): #4 0x7f1d1c0c4324 in QWidgetLineControl::internalSetText(QString const&, int, bool) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 [...] #9 0x7f1d1c268b32 in QTreeWidget::currentItemChanged(QTreeWidgetItem*, QTreeWidgetItem*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 [...] #11 0x7f1d1b2656c7 in QItemSelectionModel::currentChanged(QModelIndex const&, QModelIndex const&) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #12 0x7f1d1b26917d in QItemSelectionModel::setCurrentIndex(QModelIndex const&, QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #13 0x7f1d1c1eb14e in QAbstractItemView::mousePressEvent(QMouseEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 465531] Dolphin Crashes Out of the Blue
https://bugs.kde.org/show_bug.cgi?id=465531 --- 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.
[kmymoney] [Bug 461288] Next scheduled loan due date changes to wrong date
https://bugs.kde.org/show_bug.cgi?id=461288 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- 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.
[NeoChat] [Bug 456865] Long event changes overlap with other events
https://bugs.kde.org/show_bug.cgi?id=456865 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- 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-pa] [Bug 465590] Audio Volume Device name text extends outside of widget on hover if it's too long
https://bugs.kde.org/show_bug.cgi?id=465590 --- Comment #5 from doncb...@gmail.com --- (In reply to Nate Graham from comment #4) > In this case the problem is that we show the full string on hover, and > *that* string overflows. So we have the standard set of options for how to > handle a string that doesn't fit in its current space: > 1. Elide it and add a tooltip to see the whole text. Downsides: still can't > see the rest of it when not hovering. > 2. Wrap it. Downsides: can re-arrange the layout awkwardly. > 3. Expand the space to make it always fit. Downsides: isn't always feasible, > and can produce bad results for really long strings. > > In this case 3 is not feasible and 2 would be undesirable because we don't > want the layout to re-arrange on hover. So that leaves #1. You're absolutely right Nate, I completely forgot to consider how unusual it would be for the interface to rapidly rearrange itself as you scrolled through it. Very long text (the broken variety) that was wrapped would not make it fully unusable, but I would definitely prefer the safer single line elided if such a breakage were to occur. I think there is a 4th option which would make text scrollable and use a fade instead of an elide, but that really just seems like a pain in general. Most OSes use the elide + tooltip and that seems to be the safest way to handle unexpected values, so it gets my vote as well. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 466899] Don't require that input time's time format match the local time zone's time format
https://bugs.kde.org/show_bug.cgi?id=466899 Bug Janitor Service changed: What|Removed |Added Status|REPORTED|ASSIGNED Ever confirmed|0 |1 --- Comment #4 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/plasma/kdeplasma-addons/-/merge_requests/354 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 466359] since upgrade to KDE Framework 5.103, kstart5 does not return after starting application
https://bugs.kde.org/show_bug.cgi?id=466359 thenujan changed: What|Removed |Added Assignee|kio-bugs-n...@kde.org |sthenujan2...@gmail.com CC||sthenujan2...@gmail.com -- 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
https://bugs.kde.org/show_bug.cgi?id=466742 Aleix Pol changed: What|Removed |Added Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas |ma/discover/commit/08ed9e8c |ma/discover/commit/5a19ba27 |125aca3628c31b9abd624cd171f |d1a836b35e0e33a11803e53ada2 |ffb49 |32a7a --- Comment #3 from Aleix Pol --- Git commit 5a19ba27d1a836b35e0e33a11803e53ada232a7a by Aleix Pol. Committed on 06/03/2023 at 01:51. Pushed by apol into branch 'master'. pk: Finish porting away from runservices The code is gone but this remained... (cherry picked from commit 08ed9e8c125aca3628c31b9abd624cd171fffb49) M +16 -6 libdiscover/backends/PackageKitBackend/PackageKitSourcesBackend.cpp https://invent.kde.org/plasma/discover/commit/5a19ba27d1a836b35e0e33a11803e53ada232a7a -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466691] Icons-only Task Manager - Sort Manual - Order of windows lost after x11vnc remote connection
https://bugs.kde.org/show_bug.cgi?id=466691 --- Comment #3 from Michael --- Only locked the screen. Step 5 is more "unlock the physical terminal rather than use a remotely grabbed tmux session of the same user account that has credentials to grab screenbuffer data via X11 mechanisms." -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 466919] DrKonqi crashed while submitting
https://bugs.kde.org/show_bug.cgi?id=466919 Bug Janitor Service changed: What|Removed |Added Severity|normal |crash -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466920] plasmashell crashes in mouse action config
https://bugs.kde.org/show_bug.cgi?id=466920 Bug Janitor Service changed: What|Removed |Added Severity|normal |crash -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 447010] Documents created from templates unexpectedly reuse template's metadata such as total editing time, created/modified date, revision number
https://bugs.kde.org/show_bug.cgi?id=447010 --- Comment #4 from z...@zeragamba.ca --- Still an issue in 5.1.0 :( Any chance this can be looked at, or at least some pointers as to where to look to see if I can patch it myself? My idea on patching this issue was the following: - On open file - if was opened as template, - reset created and modified dates to current timestamp - reset revision number to 0 - reset editing time to 0 - ensure recording folder is updated to new timestamp -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466922] New: Primary screen reverts to default when switching TTYs
https://bugs.kde.org/show_bug.cgi?id=466922 Bug ID: 466922 Summary: Primary screen reverts to default when switching TTYs Classification: Plasma Product: kwin Version: 5.27.2 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: multi-screen Assignee: kwin-bugs-n...@kde.org Reporter: theoc...@gmail.com Target Milestone: --- SUMMARY When switching to a different TTY (e.g. TTY3 via `ctrl`+`alt`+`F3`), the primary monitor changes to the default monitor. STEPS TO REPRODUCE 1. Change primary monitor to a different monitor 2. Switch to tty3 or above `ctrl`+`alt`+`F3` to `F6` 3. Switch back to tty2 or tty7 (depends on whether you're using Wayland or Xorg) OBSERVED RESULT The primary monitor switches to the default (usually smaller) monitor. EXPECTED RESULT The primary monitor stays the same. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux (kernel 6.1.12-zen1-1-zen) KDE Plasma Version: 5.27.2-1 KDE Frameworks Version: 5.103.0-1 Qt Version: 5.15.8+kde+r181-1 ADDITIONAL INFORMATION Using NVIDIA GTX 960 with Intel Xeon E5-1650 32GB RAM Wayland display server -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466921] New: Garbled text when searching in history.
https://bugs.kde.org/show_bug.cgi?id=466921 Bug ID: 466921 Summary: Garbled text when searching in history. Classification: Plasma Product: plasmashell Version: 5.27.2 Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Clipboard Assignee: plasma-b...@kde.org Reporter: rokejulianlockh...@outlook.com Target Milestone: 1.0 Created attachment 157027 --> https://bugs.kde.org/attachment.cgi?id=157027=edit Depiction of this problem. STEPS TO REPRODUCE 1. Search for something in the clipboard. That's all. OBSERVED RESULT Provided by the attachment. EXPECTED RESULT The text should not be as depicted, obviously. SOFTWARE/OS VERSIONS Windows: Inapplicable. macOS: Inapplicable. Linux/KDE Plasma: Yes. 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.
[Discover] [Bug 466742] Show an error in the UI when the external "Software Sources" app can't be launched
https://bugs.kde.org/show_bug.cgi?id=466742 Luigi Toscano changed: What|Removed |Added Latest Commit||https://invent.kde.org/plas ||ma/discover/commit/08ed9e8c ||125aca3628c31b9abd624cd171f ||ffb49 Status|ASSIGNED|RESOLVED Resolution|--- |FIXED --- Comment #2 from Luigi Toscano --- Git commit 08ed9e8c125aca3628c31b9abd624cd171fffb49 by Luigi Toscano, on behalf of Aleix Pol. Committed on 06/03/2023 at 00:49. Pushed by ltoscano into branch 'Plasma/5.27'. pk: Finish porting away from runservices The code is gone but this remained... M +16 -6 libdiscover/backends/PackageKitBackend/PackageKitSourcesBackend.cpp https://invent.kde.org/plasma/discover/commit/08ed9e8c125aca3628c31b9abd624cd171fffb49 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466920] New: plasmashell crashes in mouse action config
https://bugs.kde.org/show_bug.cgi?id=466920 Bug ID: 466920 Summary: plasmashell crashes in mouse action config Classification: Plasma Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: nicolas.fe...@gmx.de CC: k...@davidedmundson.co.uk Target Milestone: 1.0 STEPS TO REPRODUCE 1. Right-click on desktop, configure wallpaper 2. Go to "Mouse actions" 3. Click on information icon for a mouse action 4. Press Esc OBSERVED RESULT Boom EXPECTED RESULT No boom Plasma master #0 __pthread_kill_implementation (threadid=, signo=signo@entry=11, no_tid=no_tid@entry=0) at pthread_kill.c:44 #1 0x7f5ef58afec3 in __pthread_kill_internal (signo=11, threadid=) at pthread_kill.c:78 #2 0x7f5ef585fa76 in __GI_raise (sig=11) at ../sysdeps/posix/raise.c:26 #3 0x7f5ef93216ba in KCrash::defaultCrashHandler(int) (sig=11) at /home/nico/kde6/src/kcrash/src/kcrash.cpp:597 #4 0x7f5ef585fb20 in () at /lib64/libc.so.6 #5 QQmlPropertyCache::propertyCount() const (this=0x0) at /usr/src/debug/qt6-qtdeclarative-6.4.2-1.fc37.x86_64/redhat-linux-build/include/QtQml/6.4.2/QtQml/private/../../../../../../src/qml/qml/qqmlpropertycache_p.h:437 #6 QQmlPropertyCache::property(int) const (index=10, this=0x0) at /usr/src/debug/qt6-qtdeclarative-6.4.2-1.fc37.x86_64/redhat-linux-build/include/QtQml/6.4.2/QtQml/private/../../../../../../src/qml/qml/qqmlpropertycache_p.h:335 #7 QQmlInterceptorMetaObject::doIntercept(QMetaObject::Call, int, void**) (this=0x51916d0, c=QMetaObject::WriteProperty, id=10, a=0x7ffe7d459ad0) at /usr/src/debug/qt6-qtdeclarative-6.4.2-1.fc37.x86_64/src/qml/qml/qqmlvmemetaobject.cpp:279 #8 0x7f5ef761d6e2 in QQmlInterceptorMetaObject::intercept(QMetaObject::Call, int, void**) (a=0x7ffe7d459ad0, id=10, c=QMetaObject::WriteProperty, this=0x51916d0) at /usr/src/debug/qt6-qtdeclarative-6.4.2-1.fc37.x86_64/src/qml/qml/qqmlvmemetaobject_p.h:104 #9 QQmlVMEMetaObject::metaCall(QObject*, QMetaObject::Call, int, void**) (this=0x51916d0, o=, c=QMetaObject::WriteProperty, _id=10, a=0x7ffe7d459ad0) at /usr/src/debug/qt6-qtdeclarative-6.4.2-1.fc37.x86_64/src/qml/qml/qqmlvmemetaobject.cpp:651 #10 0x7f5ef74e64ca in QQmlPropertyData::doMetacall<(QMetaObject::Call)2>(QObject*, int, void**) const (this=0x4e6ddf8, argv=0x7ffe7d459ad0, idx=, object=0x7f5e7d6367df ) at /usr/src/debug/qt6-qtdeclarative-6.4.2-1.fc37.x86_64/redhat-linux-build/include/QtQml/6.4.2/QtQml/private/../../../../../../src/qml/qml/qqmlpropertydata_p.h:320 #11 QQmlPropertyData::writeProperty(QObject*, void*, QFlags) const (this=this@entry=0x4e6ddf8, target=target@entry=0x7f5ed401e860, value=, flags=..., flags@entry=...) at /usr/src/debug/qt6-qtdeclarative-6.4.2-1.fc37.x86_64/redhat-linux-build/include/QtQml/6.4.2/QtQml/private/../../../../../../src/qml/qml/qqmlpropertydata_p.h:340 #12 0x7f5ef7596ebc in QQmlPropertyPrivate::write(QObject*, QQmlPropertyData const&, QVariant const&, QQmlRefPointer const&, QFlags) (object=0x7f5ed401e860, property=..., value=..., context=..., flags=...) at /usr/src/debug/qt6-qtdeclarative-6.4.2-1.fc37.x86_64/src/qml/qml/qqmlproperty.cpp:1381 #13 0x7f5ef7598ea2 in QQmlPropertyPrivate::writeValueProperty(QObject*, QQmlPropertyData const&, QQmlPropertyData const&, QVariant const&, QQmlRefPointer const&, QFlags) (object=, core=, valueTypeData=, value=..., context=..., flags=..., flags@entry=...) at /usr/src/debug/qt6-qtdeclarative-6.4.2-1.fc37.x86_64/src/qml/qml/qqmlproperty.cpp:1293 #14 0x7f5ef7598f11 in QQmlPropertyPrivate::writeValueProperty(QVariant const&, QFlags) (this=0x4e6ddc0, value=..., flags=...) at /usr/src/debug/qt6-qtdeclarative-6.4.2-1.fc37.x86_64/src/qml/qml/qqmlproperty.cpp:1259 #15 0x7f5ef7598fe1 in QQmlPropertyPrivate::write(QQmlProperty const&, QVariant const&, QFlags) (that=..., value=..., flags=..., flags@entry=...) at /usr/src/debug/qt6-qtdeclarative-6.4.2-1.fc37.x86_64/src/qml/qml/qqmlproperty.cpp:1668 #16 0x7f5ef7598ffb in QQmlProperty::write(QVariant const&) const (this=this@entry=0x7ffe7d459ce0, value=...) at /usr/include/qt6/QtCore/qflags.h:73 #17 0x7f5ef7599039 in QQmlProperty::write(QObject*, QString const&, QVariant const&) (object=, name=..., value=...) at /usr/src/debug/qt6-qtdeclarative-6.4.2-1.fc37.x86_64/src/qml/qml/qqmlproperty.cpp:1601 #18 0x7f5ee47558f0 in QQuickPopupPrivate::hideOverlay() (this=0x4fe8870) at /usr/src/debug/qt6-qtdeclarative-6.4.2-1.fc37.x86_64/src/quicktemplates2/qquickpopup.cpp:816 #19 QQuickPopupPrivate::hideOverlay() (this=0x4fe8870) at /usr/src/debug/qt6-qtdeclarative-6.4.2-1.fc37.x86_64/src/quicktemplates2/qquickpopup.cpp:812 #20 0x7f5ee47555f0 in QQuickPopupPrivate::prepareExitTransition() (this=0x4fe8870) at
[drkonqi] [Bug 466919] New: DrKonqi crashed while submitting
https://bugs.kde.org/show_bug.cgi?id=466919
Bug ID: 466919
Summary: DrKonqi crashed while submitting
Classification: Applications
Product: drkonqi
Version: master
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: plasma-b...@kde.org
Reporter: nicolas.fe...@gmx.de
Target Milestone: ---
Halfway through the submission process, I think on the duplicates page, DrKonqi
crashed
Application: Die KDE-Absturzbehandlung (drkonqi), signal: Segmentation fault
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = 0x0}
[KCrash Handler]
#5 0x7f4f288c3d8a in ?? ()
#6 0x7f496afca3c0 in pcre2_match_data_create_16 () from
/lib64/libpcre2-16.so.0
#7 0x7f496bf3aa9c in
QRegularExpressionPrivate::doMatch(QRegularExpressionMatchPrivate*, long long,
QRegularExpressionPrivate::CheckSubjectStringOption,
QRegularExpressionMatchPrivate const*) const () from /lib64/libQt6Core.so.6
#8 0x7f496bf3b355 in QRegularExpression::match(QString const&, long long,
QRegularExpression::MatchType, QFlags) const
() from /lib64/libQt6Core.so.6
#9 0x004781be in BacktraceLineGdb::parse (this=0x7f48f3ffe7d0) at
/home/nico/kde6/src/drkonqi/src/parser/backtraceparsergdb.cpp:64
#10 0x00478e16 in BacktraceLineGdb::BacktraceLineGdb
(this=0x7f48f3ffe7d0, lineStr=...) at
/home/nico/kde6/src/drkonqi/src/parser/backtraceparsergdb.cpp:22
#11 0x00478f1c in BacktraceParserGdb::parseLine (this=,
lineStr=...) at
/home/nico/kde6/src/drkonqi/src/parser/backtraceparsergdb.cpp:200
#12 0x00479509 in BacktraceParserGdb::newLine (this=0x467d230,
lineStr=...) at
/home/nico/kde6/src/drkonqi/src/parser/backtraceparsergdb.cpp:191
#13 0x7f496bdc7f8f in void doActivate(QObject*, int, void**) () from
/lib64/libQt6Core.so.6
#14 0x00426ae3 in ParseBugBacktraces::newLine
(this=this@entry=0x7f48f3ffea50, _t1=...) at
/home/nico/kde6/build/drkonqi/src/DrKonqiInternal_autogen/W72SJHHTCE/moc_parsebugbacktraces.cpp:166
#15 0x00471773 in ParseBugBacktraces::parse (this=0x7f48f3ffea50,
comment=...) at
/home/nico/kde6/src/drkonqi/src/bugzillaintegration/parsebugbacktraces.cpp:126
#16 0x00471966 in ParseBugBacktraces::parse
(this=this@entry=0x7f48f3ffea50) at
/home/nico/kde6/src/drkonqi/src/bugzillaintegration/parsebugbacktraces.cpp:113
#17 0x0046b24c in operator() (__closure=0x7f48f3ffea20) at
/home/nico/kde6/src/drkonqi/src/bugzillaintegration/duplicatefinderjob.cpp:108
#18 std::__invoke_impl
>&, QObject*)::&> (__f=...) at /usr/include/c++/12/bits/invoke.h:61
#19 std::__invoke >&, QObject*)::&> (__fn=...) at
/usr/include/c++/12/bits/invoke.h:96
#20 std::invoke >&, QObject*)::&> (__fn=...) at
/usr/include/c++/12/functional:110
#21 operator() (function=..., __closure=) at
/usr/include/qt6/QtConcurrent/qtconcurrentstoredfunctioncall.h:116
#22 std::__invoke_impl >&, QObject*)::
>::runFunctor():: >&, QObject*):: >)>&,
DuplicateFinderJob::slotCommentsFetched(const QList
>&, QObject*):: > (__f=...) at
/usr/include/c++/12/bits/invoke.h:61
#23 std::__invoke >&, QObject*)::
>::runFunctor():: >&, QObject*):: >)>&,
DuplicateFinderJob::slotCommentsFetched(const QList
>&, QObject*):: > (__fn=...) at
/usr/include/c++/12/bits/invoke.h:96
#24 std::__apply_impl >&, QObject*)::
>::runFunctor():: >&, QObject*):: >)>&,
std::tuple >&, QObject*):: >, 0> (__t=...,
__f=...) at /usr/include/c++/12/tuple:1852
#25 std::apply >&, QObject*)::
>::runFunctor():: >&, QObject*):: >)>&,
std::tuple >&, QObject*):: > > (__t=...,
__f=...) at /usr/include/c++/12/tuple:1863
#26
QtConcurrent::StoredFunctionCall >&, QObject*):: >::runFunctor(void)
(this=0x447da80) at
/usr/include/qt6/QtConcurrent/qtconcurrentstoredfunctioncall.h:122
#27 0x0046be52 in
QtConcurrent::RunFunctionTaskBase::run
(this=0x447da80) at /usr/include/qt6/QtConcurrent/qtconcurrentrunbase.h:83
#28 0x7f496bf0dd33 in QThreadPoolThread::run() () from
/lib64/libQt6Core.so.6
#29 0x7f496bf08ce8 in QThreadPrivate::start(void*) () from
/lib64/libQt6Core.so.6
#30 0x7f496b6ae12d in start_thread () from /lib64/libc.so.6
#31 0x7f496b72fbc0 in clone3 () from /lib64/libc.so.6
Thread 22 (Thread 0x7f490897c6c0 (LWP 250962) "Thread (pooled)"):
#1 0x7f496b6ad804 in pthread_cond_timedwait@@GLIBC_2.3.2 () from
/lib64/libc.so.6
#2 0x7f496bf114a9 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from
/lib64/libQt6Core.so.6
#3 0x7f496bf0e081 in QThreadPoolThread::run() () from
/lib64/libQt6Core.so.6
#4 0x7f496bf08ce8 in QThreadPrivate::start(void*) () from
/lib64/libQt6Core.so.6
#5 0x7f496b6ae12d in start_thread () from /lib64/libc.so.6
#6 0x7f496b72fbc0 in clone3 () from /lib64/libc.so.6
Thread 21 (Thread 0x7f490917d6c0 (LWP 250961) "Thread (pooled)"):
#1 0x7f496b6ad804 in pthread_cond_timedwait@@GLIBC_2.3.2 () from
/lib64/libc.so.6
#2
[kinfocenter] [Bug 466707] About this System: "Show More Information" button in System Settings representation doesn't actually show more information when clicked
https://bugs.kde.org/show_bug.cgi?id=466707 Nate Graham changed: What|Removed |Added Latest Commit||https://invent.kde.org/plas ||ma/kinfocenter/commit/20f62 ||bdc56be09f69f5d580af3d6e3c5 ||20b3c062 Resolution|--- |FIXED Version Fixed In||6.0 Status|ASSIGNED|RESOLVED --- Comment #3 from Nate Graham --- Git commit 20f62bdc56be09f69f5d580af3d6e3c520b3c062 by Nate Graham. Committed on 05/03/2023 at 23:15. Pushed by ngraham into branch 'master'. Rename "Show More Information" button to "Launch Info Center" It actually doesn't show you more information--at least not immediately. This is because it launches Info Center, which displays the very same page you came from by default. Let's rename the button to set user expectations accordingly. FIXED-IN: 6.0 M +1-1Modules/about-distro/src/package/contents/ui/main.qml https://invent.kde.org/plasma/kinfocenter/commit/20f62bdc56be09f69f5d580af3d6e3c520b3c062 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466918] plasmashell does not automatically start when when logging into the Wayland session
https://bugs.kde.org/show_bug.cgi?id=466918 alphabitserial changed: What|Removed |Added CC||alphabitser...@pm.me -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466918] New: plasmashell does not automatically start when when logging into the Wayland session
https://bugs.kde.org/show_bug.cgi?id=466918 Bug ID: 466918 Summary: plasmashell does not automatically start when when logging into the Wayland session Classification: Plasma Product: plasmashell Version: 5.27.2 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: alphabitser...@pm.me CC: k...@davidedmundson.co.uk Target Milestone: 1.0 SUMMARY plasmashell does not automatically start when when logging into the Wayland session. STEPS TO REPRODUCE 1. Log into Plasma (Wayland) from SDDM OBSERVED RESULT plasmashell does not automatically start. It starts fine if I open KRunner and enter `kstart5 plasmashell` EXPECTED RESULT plasmashell should automatically start. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux KDE Plasma Version: 5.27.2 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION I am using an NVIDIA RTX 3050 with driver version 525.89.02 The issue is consistent, not intermittent. This may or may not be related, but when I experience this issue, KWallet doesn't automatically unlock, either. I'm not using automatic login with SDDM, where that behavior would be expected. Please let me know of any additional information I could provide that may be of assistance with debugging. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 466674] Wayland: various apps crash in DpmsManager::addScreen() when display enters sleep
https://bugs.kde.org/show_bug.cgi?id=466674 Bug Janitor Service changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|ASSIGNED --- Comment #8 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/plasma/libkscreen/-/merge_requests/115 -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 348529] When screen is locked, turn off screen with a shorter timeout
https://bugs.kde.org/show_bug.cgi?id=348529 --- Comment #54 from jonathan haney --- Sadly the short answer is no. TBH I didn't think anyone that would want "Switch off after" disabled but "Switch off while locked" enabled. Allowing "Switch off after" to be set to 0 would be trivial and would allow for this behavior but I haven't traced its usage fully so I'm not super confident in it not causing new issues atm. However, now that I think about it I'm pretty certain they'll ask me to move the code out of dpms and make a special home for it elsewhere. If so it might be a few weeks before I can resubmit due to health issues but you'll probably end up getting that behavior sooner than 8 years. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 466674] Wayland: various apps crash in DpmsManager::addScreen() when display enters sleep
https://bugs.kde.org/show_bug.cgi?id=466674 --- Comment #7 from Aleix Pol --- So here's a fix in Qt, I'll add a workaround until we can rely on this... https://codereview.qt-project.org/c/qt/qtwayland/+/464669 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466288] Bluetooth media sessions don't appear in Media Player when using mpris-proxy
https://bugs.kde.org/show_bug.cgi?id=466288 Fushan Wen changed: What|Removed |Added Version Fixed In||5.27.3 Status|ASSIGNED|RESOLVED Resolution|--- |FIXED Latest Commit||https://invent.kde.org/plas ||ma/plasma-workspace/commit/ ||177cf79ba2e1a055823677a7103 ||99b63bb55efb5 --- Comment #4 from Fushan Wen --- Git commit 177cf79ba2e1a055823677a710399b63bb55efb5 by Fushan Wen. Committed on 05/03/2023 at 16:57. Pushed by fusionfuture into branch 'Plasma/5.27'. dataengines/mpris2: tolerate non-standards compliant players like mpris-proxy BlueZ mpris-proxy doesn't provide "SupportedUriSchemes" or "SupportedMimeTypes". Since the two properties are not directly used in the media controller widget, show a debug message instead of rejecting the player. FIXED-IN: 5.27.3 M +6-2dataengines/mpris2/mpris2engine.cpp https://invent.kde.org/plasma/plasma-workspace/commit/177cf79ba2e1a055823677a710399b63bb55efb5 -- You are receiving this mail because: You are watching all bug changes.
[NeoChat] [Bug 466407] Neochat often hangs at QMetaObjectPrivate::disconnect
https://bugs.kde.org/show_bug.cgi?id=466407 Fushan Wen changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #2 from Fushan Wen --- I have downgraded to 22.12.2 and haven't seen the issue, so can't really reproduce now. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 446235] The item "Clear recent files list" doesn't work.
https://bugs.kde.org/show_bug.cgi?id=446235 Nate Graham changed: What|Removed |Added Product|frameworks-kio |plasmashell CC||k...@davidedmundson.co.uk, ||n...@kde.org Target Milestone|--- |1.0 Assignee|kio-bugs-n...@kde.org |plasma-b...@kde.org Version|5.88.0 |5.27.2 Component|general |general --- Comment #5 from Nate Graham --- Can you reproduce the files *never* being cleared, or the files only being cleared after navigating elsewhere and then back (or restarting plasmashell). I can reproduce the latter. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466917] New: CPU Temperature in Fahrenheit
https://bugs.kde.org/show_bug.cgi?id=466917 Bug ID: 466917 Summary: CPU Temperature in Fahrenheit Classification: Plasma Product: plasmashell Version: master Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: System Monitor Assignee: plasma-b...@kde.org Reporter: bren...@bdwy.app CC: ahiems...@heimr.nl, notm...@gmail.com Target Milestone: 1.0 Would love it if I had the option to display the CPU temperature in Fahrenheit instead of Celsius in the "Total CPU Use" widget. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 348529] When screen is locked, turn off screen with a shorter timeout
https://bugs.kde.org/show_bug.cgi?id=348529 Jeff changed: What|Removed |Added CC||jeffclay+...@gmail.com --- Comment #53 from Jeff --- (In reply to jonathan haney from comment #51) > Created attachment 156995 [details] > Bug fix sample > > Looks like the last attempt got shot down by the maintainers. > So out of curiosity I spent a few hours and have a local fix with some > changes around dpms.cpp/h dpmsconfig.cpp/h > I adding an extra timer and the GUI controls seen in the attachment above. > I think I spent more time figuring out how to test this and handling > dependencies vs actually writing code :P > If people think the interface is good I'll go jump some hoops to figure out > how to put in the merge request. Thank you for this! Out of curiosity, will you be able to only enable screen power off when locked without enabling it for a logged in session. Session Locked -> power save after X minutes. Session ! Locked -> power save never. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 463134] The Discover panel applet says "System up to date," even if there are available updates.
https://bugs.kde.org/show_bug.cgi?id=463134 Shmerl changed: What|Removed |Added Version|5.26.90 |5.27.2 --- Comment #4 from Shmerl --- Still happens in 5.27.2. -- You are receiving this mail because: You are watching all bug changes.
[NeoChat] [Bug 462732] Two Low Priority sections after first start and login
https://bugs.kde.org/show_bug.cgi?id=462732 Tobias Fella changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #3 from Tobias Fella --- Did you ever see this again? I'm a bit confused, since the rooms have the same section and are right next to each other, they should be shown as one section, which makes this look like a qt bug. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 466916] baloo_file_extractor crashes and the coredump take too much space
https://bugs.kde.org/show_bug.cgi?id=466916 tagwer...@innerjoin.org changed: What|Removed |Added CC||tagwer...@innerjoin.org --- Comment #1 from tagwer...@innerjoin.org --- Looks similar to Bug 466760 ... ... and there might be a connection to Bug 465801 that affects baloo on Wayland. Try logging in with X11 and see if the same happens. -- You are receiving this mail because: You are watching all bug changes.
[NeoChat] [Bug 466381] Clicking on image with touch opens context menu
https://bugs.kde.org/show_bug.cgi?id=466381 Tobias Fella changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://invent.kde.org/netw ||ork/neochat/commit/e954fc20 ||4f84c9a1fd42b999a1bbfd5fb9f ||201c8 Status|CONFIRMED |RESOLVED --- Comment #1 from Tobias Fella --- Git commit e954fc204f84c9a1fd42b999a1bbfd5fb9f201c8 by Tobias Fella. Committed on 05/03/2023 at 23:19. Pushed by tfella into branch 'master'. Don't open context menu when tapping on an image M +1-0src/qml/Component/Timeline/TimelineContainer.qml https://invent.kde.org/network/neochat/commit/e954fc204f84c9a1fd42b999a1bbfd5fb9f201c8 -- You are receiving this mail because: You are watching all bug changes.
[NeoChat] [Bug 466478] Copy image to clipboard
https://bugs.kde.org/show_bug.cgi?id=466478 Tobias Fella changed: What|Removed |Added Latest Commit||https://invent.kde.org/netw ||ork/neochat/commit/d1f7e709 ||1e53d8c7e275032e0e3eb97e233 ||6d8fb Resolution|--- |FIXED Status|ASSIGNED|RESOLVED --- Comment #2 from Tobias Fella --- Git commit d1f7e7091e53d8c7e275032e0e3eb97e2336d8fb by Tobias Fella, on behalf of Alessio Mattiazzi. Committed on 05/03/2023 at 23:19. Pushed by tfella into branch 'master'. Copy image to the clipboard Add a context menu option to save an image in the timeline to the clipboard M +12 -0src/clipboard.cpp M +1-0src/clipboard.h M +14 -0src/qml/Menu/Timeline/FileDelegateContextMenu.qml https://invent.kde.org/network/neochat/commit/d1f7e7091e53d8c7e275032e0e3eb97e2336d8fb -- You are receiving this mail because: You are watching all bug changes.
[kinfocenter] [Bug 466707] About this System: "Show More Information" button in System Settings representation doesn't actually show more information when clicked
https://bugs.kde.org/show_bug.cgi?id=466707 Bug Janitor Service changed: What|Removed |Added Status|CONFIRMED |ASSIGNED --- Comment #2 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/plasma/kinfocenter/-/merge_requests/134 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 466679] Discover can't handle UEFI Secure Boot firmware updates
https://bugs.kde.org/show_bug.cgi?id=466679 --- Comment #3 from ternoma...@gmail.com --- This bug also affects me. It seems that it was reported recently in many places, e.g.: https://askubuntu.com/questions/1453959/getting-the-input-is-not-of-cabinet-format-on-discover https://forums.fedoraforum.org/showthread.php?329903-Error-upgrading-Dell-laptop-firmware https://www.kubuntuforums.net/forum/currently-supported-releases/kubuntu-22-04-jammy-jellyfish/software-support-be/668585-lenovo-system-firmware-update-will-not-install My configuration: Kubuntu 22.10 KDE 5.27.2 -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 466899] Don't require that input time's time format match the local time zone's time format
https://bugs.kde.org/show_bug.cgi?id=466899 Natalie Clarius changed: What|Removed |Added Assignee|plasma-b...@kde.org |natalie_clar...@yahoo.de -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 466679] Discover can't handle UEFI Secure Boot firmware updates
https://bugs.kde.org/show_bug.cgi?id=466679 ternoma...@gmail.com changed: What|Removed |Added CC||ternoma...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 466899] Don't require that input time's time format match the local time zone's time format
https://bugs.kde.org/show_bug.cgi?id=466899 --- Comment #3 from Natalie Clarius --- It would become a nested loop, though it may well be that it's still not noticeable. I'll play around with it. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 466591] File Associations do not survive a reboot
https://bugs.kde.org/show_bug.cgi?id=466591 Evert Vorster changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #2 from Evert Vorster --- This problem is now completely gone. Since this is a rolling update system, there was probably an update that fixed it, but I would not know which one. Thanks, everybody, for looking -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466662] Application-Specific settings do not survive a reboot.
https://bugs.kde.org/show_bug.cgi?id=42 Evert Vorster changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #3 from Evert Vorster --- This problem is now completely gone. Since this is a rolling update system, there was probably an update that fixed it, but I would not know which one. Thanks, everybody, for looking -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 466899] Don't require that input time's time format match the local time zone's time format
https://bugs.kde.org/show_bug.cgi?id=466899 --- Comment #2 from Nate Graham --- Depending on how poor the performance of iterating through all locales is, it might not even be noticeable. If that's the case, I think it could be the winning solution. -- You are receiving this mail because: You are watching all bug changes.
[NeoChat] [Bug 466381] Clicking on image with touch opens context menu
https://bugs.kde.org/show_bug.cgi?id=466381 Tobias Fella changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 453314] When changing display resolutions, desktop icons should try to keep the same position as much as possible
https://bugs.kde.org/show_bug.cgi?id=453314 --- Comment #1 from tomash...@gmail.com --- This heuristic is apparently (as per resolution to https://bugs.kde.org/show_bug.cgi?id=453141 ) already implemented for widgets, so implementing it for icons should not be as hard as there would be something to build on. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 453141] When changing display resolutions, desktop Widgets should try to keep the same position as much as possible
https://bugs.kde.org/show_bug.cgi?id=453141 --- Comment #9 from tomash...@gmail.com --- Ok, though if this functionality had been there all along, this should never have been accepted as a bug:-). -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 466899] Don't require that input time's time format match the local time zone's time format
https://bugs.kde.org/show_bug.cgi?id=466899 --- Comment #1 from Natalie Clarius --- I had the same thought, but haven't found a satisfactory solution. This is all the valid short time formats (ignoring dates) across locales: > 'Kl'. H.mm > AP 'ga' h:mm > AP h.mm > AP h:mm > APh:mm > B H:mm > H.mm > H:m > H:mm > H:mm 'hodź'. > H:mm 'ч'. > HH 'h' mm > HH.mm > HH:mm > HH:mm:ss > h:mm AP > hh:mm AP > ཆུ་ཚོད་ h སྐར་མ་ mm AP Note that these don't uniquely map to the possible strings, e.g. "h" means with or without leading zero and "AP" is the A.M./P.M. affix to be spelled out. See https://doc.qt.io/qt-6/qtime.html#toString. Initially I tried with a regex, but that became monstrous rather quickly and only introduces bugs like we already had in the night color KCM so I don't think that's a viable alternative. Iterating through all locales would be possible but costly performance-wise, and would introduce problems with multiple valid interpretations of dates (d/m/y vs m/d/y format). We could settle on a few selected formats, like C, en_US and the system locale, and hope that that covers most use cases. -- You are receiving this mail because: You are watching all bug changes.
[NeoChat] [Bug 466382] Share image from image view
https://bugs.kde.org/show_bug.cgi?id=466382 Tobias Fella changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[NeoChat] [Bug 466330] NeoChat Crashes at launch
https://bugs.kde.org/show_bug.cgi?id=466330 Tobias Fella changed: What|Removed |Added Resolution|--- |LATER Status|REPORTED|RESOLVED --- Comment #1 from Tobias Fella --- This will go away with https://invent.kde.org/network/neochat/-/merge_requests/808 -- You are receiving this mail because: You are watching all bug changes.
[NeoChat] [Bug 466407] Neochat often hangs at QMetaObjectPrivate::disconnect
https://bugs.kde.org/show_bug.cgi?id=466407 Tobias Fella changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #1 from Tobias Fella --- I'm going to need a more precise info than "at QMetaObjectPrivate::disconnect", what's the call stack? -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 259917] the simulate option cannot be selected and the 'remove image' option is greyed out
https://bugs.kde.org/show_bug.cgi?id=259917 North changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #11 from North --- Reported, reported, reported. I no longer have a cd reader. Go away. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 447280] Cut/paste under wayland is hit and miss
https://bugs.kde.org/show_bug.cgi?id=447280 Nate Graham changed: What|Removed |Added CC||n...@kde.org --- Comment #2 from Nate Graham --- Do you have your clipboard history size set up 1 by any chance? If so this is Bug 466041 which was just fixed for Plasma 5.27.3. If not, please change the status to REPORTED if you can still reproduce the issue in Plasma 5.27.2 or later. Thanks a lot! -- You are receiving this mail because: You are watching all bug changes.
[NeoChat] [Bug 466895] Direct messages show information that is not applicable
https://bugs.kde.org/show_bug.cgi?id=466895 --- Comment #3 from Tobias Fella --- Git commit e6a060c1927219ece41a13fe5ebe3d648f502274 by Tobias Fella. Committed on 05/03/2023 at 16:21. Pushed by tfella into branch 'master'. Don't show highlights in DMs It's a DM, the messages are all meant for us anyway M +1-1src/models/messageeventmodel.cpp https://invent.kde.org/network/neochat/commit/e6a060c1927219ece41a13fe5ebe3d648f502274 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466041] Data must be copied twice before being pasted on Wayland when history size is set to 1 entry
https://bugs.kde.org/show_bug.cgi?id=466041 Nate Graham changed: What|Removed |Added CC||a.g...@libero.it --- Comment #11 from Nate Graham --- *** Bug 433854 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 433854] A lot of times copy-paste does not work.
https://bugs.kde.org/show_bug.cgi?id=433854 Nate Graham changed: What|Removed |Added Resolution|--- |DUPLICATE Status|CONFIRMED |RESOLVED --- Comment #23 from Nate Graham --- Aha, that makes this Bug 466041, which was just fixed. *** This bug has been marked as a duplicate of bug 466041 *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 433854] A lot of times copy-paste does not work.
https://bugs.kde.org/show_bug.cgi?id=433854 tomtomtomreportin...@gmail.com changed: What|Removed |Added CC||tomtomtomreportingin@gmail. ||com --- Comment #22 from tomtomtomreportin...@gmail.com --- I finally realized the issue only occurs if history size is set to 1. Happens regardless of Wayland or X11. Can anyone else confirm if setting the history size to greater than 1 resolves the issue? -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 466884] Missing writev uninit padding suppression for _XSend
https://bugs.kde.org/show_bug.cgi?id=466884
--- Comment #3 from Matthew Fennell
---
(In reply to Paul Floyd from comment #1)
> Can you find the source in xcb that is causing this?
I'll do my best :) To be honest - I'm not at all familiar with how these
libraries interact, so forgive me if this description is not very good. But,
here goes:
I made a more minimal example that does not require openscenegraph. Here is the
backtrace of the bug:
#0 __GI___writev (fd=3, iov=0x7fffdbf0, iovcnt=3) at
../sysdeps/unix/sysv/linux/writev.c:26
#1 0x77c38fb9 in write_vec (count=0x7fffdb8c,
vector=0x7fffdb90, c=0xc430) at ../../src/xcb_conn.c:277
#2 _xcb_conn_wait (c=c@entry=0xc430, cond=cond@entry=0xd560,
vector=vector@entry=0x7fffdb90, count=count@entry=0x7fffdb8c) at
../../src/xcb_conn.c:523
#3 0x77c39381 in _xcb_out_send (count=,
vector=, c=0xc430) at ../../src/xcb_out.c:464
#4 xcb_writev (c=c@entry=0xc430, vector=vector@entry=0x7fffdbf0,
count=-9332, count@entry=3, requests=requests@entry=8) at
../../src/xcb_out.c:412
#5 0x77ea3eae in _XSend (dpy=0x9d80, data=0x7fffdc20
"8\004", data@entry=0x0, size=size@entry=0) at ../../src/xcb_io.c:578
#6 0x77ea447c in _XReply (dpy=dpy@entry=0x9d80,
rep=rep@entry=0x7fffdcf0, extra=extra@entry=0, discard=discard@entry=1) at
../../src/xcb_io.c:670
#7 0x77e8eac4 in XInternAtom (dpy=0x9d80, name=0x603f
"_MOTIF_WM_HINTS", onlyIfExists=0) at ../../src/IntAtom.c:182
#8 0x55cb in main () at
/home/matthew/Documents/libre-racing/dependencies/bug-reports/x11-uninitialised-variable-usage/example.cpp:70
Frame 8:
The bug is triggered by a call to XInternAtom(display, "_MOTIF_WM_HINTS", 0);
This call on its own does not cause any reports - it relies on the previous
lines.
Frame 7 (libX11):
libX11 has a Display struct which contains a char * dpy->buffer. It also has
another char * dpy->bufptr, which starts set to the same position as
dpy->buffer, but expands and shrinks throughout the lifetime of the program.
In the call to XInternAtom, libX11 passes dpy to xcb.
Frame 5 (xcb):
xcb creates the struct iovec * like so:
vec[0].iov_base = dpy->buffer
vec[0].iov_len = dpy->bufptr - dpy->buffer
There is also vec[1], and vec[2], but they both have iov_len values of 0.
At this point:
dpy->buffer: "\001\030\f"
dpy->bufptr: ""
dpy->bufptr - dpy->buffer = 296
Frames #4-0:
This iovec * is passed down to the writev call without modification.
Then, on the writev call, valgrind reports:
==21464== Syscall param writev(vector[...]) points to uninitialised byte(s)
==21464==at 0x4AD770D: __writev (writev.c:26)
==21464==by 0x4AD770D: writev (writev.c:24)
==21464==by 0x4BC6FB8: write_vec (xcb_conn.c:277)
==21464==by 0x4BC6FB8: _xcb_conn_wait (xcb_conn.c:523)
==21464==by 0x4BC7380: _xcb_out_send (xcb_out.c:464)
==21464==by 0x4BC7380: xcb_writev (xcb_out.c:412)
==21464==by 0x48B1EAD: _XSend (xcb_io.c:578)
==21464==by 0x48B247B: _XReply (xcb_io.c:670)
==21464==by 0x489CAC3: XInternAtom (IntAtom.c:182)
==21464==by 0x1095CA: main (example.cpp:70)
==21464== Address 0x4ee5738 is 264 bytes inside a block of size 16,384 alloc'd
==21464==at 0x483AB65: calloc (vg_replace_malloc.c:760)
==21464==by 0x48A1D79: XOpenDisplay (OpenDis.c:240)
==21464==by 0x10920B: main (example.cpp:5)
==21464== Uninitialised value was created by a stack allocation
==21464==at 0x109207: main (example.cpp:5)
==21464==
{
Memcheck:Param
writev(vector[...])
fun:__writev
fun:writev
fun:write_vec
fun:_xcb_conn_wait
fun:_xcb_out_send
fun:xcb_writev
fun:_XSend
fun:_XReply
fun:XInternAtom
fun:main
}
I believe the error is ultimately caused by 296 (iov_len = dpy->bufptr -
dpy->buffer) > 264 (amount of initialised memory in dpy->buffer).
However, unfortunately, I don't know enough about X11 to understand why this is
happening, or if it's expected. Nevertheless, I hope this helps a little.
Let me know if you'd like me to do more research or there's some other info
that would help. I initially reported here since I noticed the almost identical
suppressions, but I'm certainly open to the suggestion that this is a real bug
in X. I just don't know enough to know how to tell for sure :)
--
You are receiving this mail because:
You are watching all bug changes.
[valgrind] [Bug 466884] Missing writev uninit padding suppression for _XSend
https://bugs.kde.org/show_bug.cgi?id=466884 --- Comment #2 from Matthew Fennell --- Created attachment 157026 --> https://bugs.kde.org/attachment.cgi?id=157026=edit Minimal example without openscenegraph dependency -- You are receiving this mail because: You are watching all bug changes.
[audiotube] [Bug 466901] UI isn't drawn properly on GNOME
https://bugs.kde.org/show_bug.cgi?id=466901 --- Comment #3 from Maksym Hazevych --- The PR you linked is more about Fedora's RPM I believe. But this problem is in the Flatpak build. A good fix would be to put the proper QML theme inside the KDE's Flatpak runtime. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 453141] When changing display resolutions, desktop Widgets should try to keep the same position as much as possible
https://bugs.kde.org/show_bug.cgi?id=453141 Nate Graham changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |FIXED --- Comment #8 from Nate Graham --- Please don't re-open bug reports based on conjecture. If you're experiencing an issue, please submit a new bug report. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 453141] When changing display resolutions, desktop Widgets should try to keep the same position as much as possible
https://bugs.kde.org/show_bug.cgi?id=453141 Nate Graham changed: What|Removed |Added Status|RESOLVED|CLOSED -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 433859] Add mismatched detection to C++ 17 aligned new/delete
https://bugs.kde.org/show_bug.cgi?id=433859 --- Comment #3 from Paul Floyd --- For libstdc++ look in ibstdc++-v3/libsupc++/new_opa.cc -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 466913] Feature request: select only some calendars in collection
https://bugs.kde.org/show_bug.cgi?id=466913 Bug Janitor Service changed: What|Removed |Added Severity|normal |wishlist -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 466914] Kded5 crash when switchin between monitor and tv
https://bugs.kde.org/show_bug.cgi?id=466914 Bug Janitor Service changed: What|Removed |Added Severity|normal |crash -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 466916] New: baloo_file_extractor crashes and the coredump take too much space
https://bugs.kde.org/show_bug.cgi?id=466916 Bug ID: 466916 Summary: baloo_file_extractor crashes and the coredump take too much space Classification: Frameworks and Libraries Product: frameworks-baloo Version: 5.103.0 Platform: Archlinux OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: Baloo File Daemon Assignee: baloo-bugs-n...@kde.org Reporter: bachirg...@gmail.com Target Milestone: --- Created attachment 157025 --> https://bugs.kde.org/attachment.cgi?id=157025=edit Backtraces generated by gdb and drkonqi-coredump-gui 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 *** baloo_file_extractor crashes and the coredump take too much space (in /var/lib/systemd/coredump), I attached some backtraces generated by drkonqi and gdb, but feel free to ask for more details STEPS TO REPRODUCE 1. Use Baloo 2. It crashes and ends up producing several Gb of coredumps after some time OBSERVED RESULT The program crashes and generates too much coredumps EXPECTED RESULT The program doesn't crash or at least generates a limited amount of dumps SOFTWARE/OS VERSIONS Linux/KDE Plasma: 6.2.1-arch1-1 (64-bit) (available in About System) KDE Plasma Version: 5.27.2 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 466915] New: Disable Ctrl+Alt+MouseWheel keybind
https://bugs.kde.org/show_bug.cgi?id=466915 Bug ID: 466915 Summary: Disable Ctrl+Alt+MouseWheel keybind Classification: Applications Product: systemsettings Version: 5.27.2 Platform: Archlinux OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: kcm_workspace Assignee: plasma-b...@kde.org Reporter: mrtng...@gmail.com Target Milestone: --- Disable Ctrl+Alt+MouseWheel keybind It changes Virtual Desktops by default. I can't seem to find an option to configure it in the Plasma menu -- You are receiving this mail because: You are watching all bug changes.
[audiotube] [Bug 466901] UI isn't drawn properly on GNOME
https://bugs.kde.org/show_bug.cgi?id=466901 --- Comment #2 from Jonah Brüchert --- Yeah... this will happen with pretty much any QML app. What you are seeing is the "Default" style, which is really really basic. I've added some code to fall back to a better style, but I think https://github.com/FedoraQt/QGnomePlatform/pull/130 is the more proper fix. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 466914] New: Kded5 crash when switchin between monitor and tv
https://bugs.kde.org/show_bug.cgi?id=466914 Bug ID: 466914 Summary: Kded5 crash when switchin between monitor and tv Classification: Plasma Product: KScreen Version: 5.27.2 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: common Assignee: kscreen-bugs-n...@kde.org Reporter: bucior3...@gmail.com Target Milestone: --- Created attachment 157024 --> https://bugs.kde.org/attachment.cgi?id=157024=edit kded5 crash I have one monitor connected via DP and tv connected via HDMI, only one is used at the same time, when i switch to tv as main display and then try to switch back to monitor osd (super + p) is not working 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: Wayland Processors: 16 × AMD Ryzen 7 5800X 8-Core Processor Memory: 31.2 GiB of RAM Graphics Processor: AMD Radeon RX 6800 XT Manufacturer: Gigabyte Technology Co., Ltd. Product Name: X570S AORUS ELITE AX System Version: -CF -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 466864] Krusader crashes on launch with fresh install of krusader-git-2.9.0.dev.r6611.g07f7d051-1
https://bugs.kde.org/show_bug.cgi?id=466864 Davide Gianforte changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO CC||dav...@gengisdave.org --- Comment #1 from Davide Gianforte --- Hi, can you provide a backtrace of the crash? Thanks -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 466913] New: Feature request: select only some calendars in collection
https://bugs.kde.org/show_bug.cgi?id=466913 Bug ID: 466913 Summary: Feature request: select only some calendars in collection Classification: Frameworks and Libraries Product: Akonadi Version: 5.21.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: DAV Resource Assignee: kdepim-b...@kde.org Reporter: bugs.kde@e3q.eu Target Milestone: --- Caldav collections can have multiple calendars. Sometimes one does not wish to synchronize all of them. (I have one which very often causes the resource to get stuck…) It would be convenient to have the possibility to only synchronize a selected subset of the available calendars. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 450738] [wish] Automatic layout management.
https://bugs.kde.org/show_bug.cgi?id=450738 postix changed: What|Removed |Added CC||pos...@posteo.eu -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 433859] Add mismatched detection to C++ 17 aligned new/delete
https://bugs.kde.org/show_bug.cgi?id=433859 --- Comment #2 from Paul Floyd --- For the C++ aligned allocators libc++ bumps up the allocation size if it is less than sizeof(void*) and then uses posix_memalign libstdc++ does a popcnt (!!!) to check for power of 2 then calls aligned_alloc (actually it looks like a feature check for aligned_alloc _aligned_malloc (Windows) posix_memalign and then memalign), It will also bump up size to be an integer multiple of I need to look at the standard to see what size triggers use of aligned allocators. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 466884] Missing writev uninit padding suppression for _XSend
https://bugs.kde.org/show_bug.cgi?id=466884 Paul Floyd changed: What|Removed |Added CC||pjfl...@wanadoo.fr --- Comment #1 from Paul Floyd --- Can you find the source in xcb that is causing this? -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 466912] New: Breeze dark folder icon turns to almost-noise under dark themes
https://bugs.kde.org/show_bug.cgi?id=466912 Bug ID: 466912 Summary: Breeze dark folder icon turns to almost-noise under dark themes Classification: Plasma Product: Breeze Version: 5.27.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Icons Assignee: visual-des...@kde.org Reporter: david.cortes.riv...@gmail.com CC: kain...@gmail.com, m...@nueljl.in Target Milestone: --- SUMMARY After the latest updates to the breeze theme, now the "breeze dark" icon for folders follows the accent color of either theme or wallpaper. This might look reasonable if one selects the default breeze colors, but if one selects a dark theme, the folder icons become too dark to the point that they are hard to see (and look quite ugly too). STEPS TO REPRODUCE 1. Go to Settings -> Appearance -> Icons -> select "Breeze Dark". 2. Go to Settings -> Appearance -> Colors -> Use accent color -> select "From current color scheme". 3. Install some good color themes for dark settings, such as "Obsidian Coast" or "Dark Obsidian" (from the button "Get New Color Schemes" in this same section). 4. Apply said theme. For worst results, use "Dark Obsidian" in combination with the "breeze" application style and "breeze dark" icons. OBSERVED RESULT Icons for folders are hard to distinguish, and look bad. EXPECTED RESULT Icons for folders should not adapt their color based on themes. Or, at the very least, if they do, then the "breeze dark" icons sould play along with dark themes. SOFTWARE/OS VERSIONS Operating System: Debian GNU/Linux 12 KDE Plasma Version: 5.27.2 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 6.1.0-5-amd64 (64-bit) Graphics Platform: X11 Processors: 20 × 12th Gen Intel® Core™ i7-12700H Memory: 62.6 GiB of RAM Graphics Processor: Mesa Intel® Graphics Manufacturer: SLIMBOOK Product Name: Executive ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 466911] New: Default logout option setting disappeared after update
https://bugs.kde.org/show_bug.cgi?id=466911 Bug ID: 466911 Summary: Default logout option setting disappeared after update Classification: Applications Product: systemsettings Version: 5.27.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: david.cortes.riv...@gmail.com Target Milestone: --- SUMMARY After the last KDE updates, the section to select the default logout option (the one that is pre-selected when pressing Ctrl+Alt+Del, like "restart" or "shutdown") disappeared from the system settings. STEPS TO REPRODUCE 1. Go to system settings. 2. Try to find the setting for the default logout option. Try using the search bar if needed. OBSERVED RESULT It's not there. Also no direct shortcut to trigger the dialog with a pre-selected option of choice without adding an extra widget. EXPECTED RESULT Should have the option to change the default logout option in the same place where it used to be in the system settings. SOFTWARE/OS VERSIONS Operating System: Debian GNU/Linux 12 KDE Plasma Version: 5.27.2 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 6.1.0-5-amd64 (64-bit) Graphics Platform: X11 Processors: 20 × 12th Gen Intel® Core™ i7-12700H Memory: 62.6 GiB of RAM Graphics Processor: Mesa Intel® Graphics Manufacturer: SLIMBOOK Product Name: Executive ADDITIONAL INFORMATION -- 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
https://bugs.kde.org/show_bug.cgi?id=463538 --- Comment #7 from Tobias Fella --- Yes, sorry, I've reset the status so the bug won't be closed -- 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
https://bugs.kde.org/show_bug.cgi?id=463538 --- Comment #6 from 318...@gmail.com --- I provided the requested info. -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 466910] New: System monitor doesn't show detailed process information like KSysGuard did
https://bugs.kde.org/show_bug.cgi?id=466910 Bug ID: 466910 Summary: System monitor doesn't show detailed process information like KSysGuard did Classification: Plasma Product: plasma-systemmonitor Version: 5.27.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: david.cortes.riv...@gmail.com CC: ahiems...@heimr.nl, plasma-b...@kde.org Target Milestone: --- SUMMARY In KSysGuard, if I right-click a process, there's an option "Detailed Information" which is very helpful when one wants to get more info out of a process. This is however not available in the new system monitor that is meant to replace KSysGuard - the closest thing it has is a pop-up with info about the columns that were configured, but this pop-up is not copy-pastable. STEPS TO REPRODUCE 1. Launch KSysGuard. 2. Right-click some process. 3. Select "Detailed Information" and make a note of all the info that it has (e.g. TTY, command that launched it, location, etc.). 4. Launch the new system monitor. 5. Try to extract all the information above in a way that could be copied to a text editor, for some entry under "applications" or "processes". OBSERVED RESULT Not possible to get detailed info and copy it to a text editor. EXPECTED RESULT Should be as helpful as KSysGuard. SOFTWARE/OS VERSIONS Operating System: Debian GNU/Linux 12 KDE Plasma Version: 5.27.2 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 6.1.0-5-amd64 (64-bit) Graphics Platform: X11 Processors: 20 × 12th Gen Intel® Core™ i7-12700H Memory: 62.6 GiB of RAM Graphics Processor: Mesa Intel® Graphics Manufacturer: SLIMBOOK Product Name: Executive ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 466909] New: System monitor edit mode and column ticker is very un-intuitive
https://bugs.kde.org/show_bug.cgi?id=466909 Bug ID: 466909 Summary: System monitor edit mode and column ticker is very un-intuitive Classification: Plasma Product: plasma-systemmonitor Version: 5.27.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: david.cortes.riv...@gmail.com CC: ahiems...@heimr.nl, plasma-b...@kde.org Target Milestone: --- SUMMARY The way that the system monitor means to get user configuration is very un-intuitive. If I have a custom configuration for which columns to show on a page in the system monitor and I then accidentally enter "edit mode" and click "discard changes" before I am able to do anything harmful in that page, it will reset all the custom columns that I selected to the default, even though they were not changed inside the "edit mode". STEPS TO REPRODUCE 1. Launch system monitor. 2. Go to some section like "processes" in the left panel. 3. Click the three dots menu and select "Configure columns...". 4. Enable extra columns of your choice there. 5. Click the three dots menu again, but this time select "Edit Page". 6. Don't do anything there, but click "Discard Changes". OBSERVED RESULT The custom columns configuration is lost. EXPECTED RESULT The custom column configuration should be preserved, since it was configured inside a different menu. SOFTWARE/OS VERSIONS Operating System: Debian GNU/Linux 12 KDE Plasma Version: 5.27.2 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 6.1.0-5-amd64 (64-bit) Graphics Platform: X11 Processors: 20 × 12th Gen Intel® Core™ i7-12700H Memory: 62.6 GiB of RAM Graphics Processor: Mesa Intel® Graphics Manufacturer: SLIMBOOK Product Name: Executive ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 466908] New: Automatically System Process Stop
https://bugs.kde.org/show_bug.cgi?id=466908 Bug ID: 466908 Summary: Automatically System Process Stop Classification: Applications Product: systemsettings Version: 5.27.2 Platform: unspecified OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: i.am.rathorea...@gmail.com Target Milestone: --- Application: systemsettings (5.27.2) Qt Version: 5.15.8 Frameworks Version: 5.103.0 Operating System: Linux 6.1.15-060115-generic x86_64 Windowing System: X11 Distribution: KDE neon 5.27 DrKonqi: 5.27.2 [KCrashBackend] -- Information about the crash: I had change my system font. Suddenly system crash dialog appears and system become choppy. The crash can be reproduced sometimes. -- Backtrace: Application: System Settings (systemsettings), signal: Aborted [KCrash Handler] #4 __pthread_kill_implementation (no_tid=0, signo=6, threadid=140628505163264) at ./nptl/pthread_kill.c:44 #5 __pthread_kill_internal (signo=6, threadid=140628505163264) at ./nptl/pthread_kill.c:78 #6 __GI___pthread_kill (threadid=140628505163264, signo=signo@entry=6) at ./nptl/pthread_kill.c:89 #7 0x7fe6a4442476 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #8 0x7fe6a44287f3 in __GI_abort () at ./stdlib/abort.c:79 #9 0x7fe6a4c91ba3 in QMessageLogger::fatal(char const*, ...) const () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7fe6a2c80b8e in QQmlData::destroyed(QObject*) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #11 0x7fe6a4ef1e2b in QObject::~QObject() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #12 0x7fe6881e2062 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/qml/QtQuick/Templates.2/libqtquicktemplates2plugin.so #13 0x7fe6a4ee711e in QObjectPrivate::deleteChildren() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #14 0x7fe6a4ef21a6 in QObject::~QObject() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #15 0x7fe6a33ef159 in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #16 0x7fe6a4ee711e in QObjectPrivate::deleteChildren() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #17 0x7fe6a4ef21a6 in QObject::~QObject() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #18 0x7fe688244225 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/qml/QtQuick/Layouts/libqquicklayoutsplugin.so #19 0x7fe6a4ee711e in QObjectPrivate::deleteChildren() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #20 0x7fe6a4ef21a6 in QObject::~QObject() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #21 0x7fe6881e1609 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/qml/QtQuick/Templates.2/libqtquicktemplates2plugin.so #22 0x7fe6a374d4ba in KDeclarative::QmlObject::~QmlObject() () from /lib/x86_64-linux-gnu/libKF5Declarative.so.5 #23 0x7fe6a374e22d in KDeclarative::QmlObjectSharedEngine::~QmlObjectSharedEngine() () from /lib/x86_64-linux-gnu/libKF5Declarative.so.5 #24 0x7fe6a37629b2 in KQuickAddons::ConfigModule::~ConfigModule() () from /lib/x86_64-linux-gnu/libKF5QuickAddons.so.5 #25 0x7fe6815974cb in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/plasma/kcms/systemsettings/kcm_fonts.so #26 0x7fe6a5b5b5c7 in ?? () from /lib/x86_64-linux-gnu/libKF5KCMUtils.so.5 #27 0x7fe6a5b5b5ed in ?? () from /lib/x86_64-linux-gnu/libKF5KCMUtils.so.5 #28 0x7fe6a5b60998 in KCModuleProxy::deleteClient() () from /lib/x86_64-linux-gnu/libKF5KCMUtils.so.5 #29 0x7fe6a5b61353 in KCModuleProxy::~KCModuleProxy() () from /lib/x86_64-linux-gnu/libKF5KCMUtils.so.5 #30 0x7fe6a5b6152d in KCModuleProxy::~KCModuleProxy() () from /lib/x86_64-linux-gnu/libKF5KCMUtils.so.5 #31 0x7fe6a4ee711e in QObjectPrivate::deleteChildren() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #32 0x7fe6a5dab056 in QWidget::~QWidget() () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #33 0x7fe6a5dab3ad in QWidget::~QWidget() () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #34 0x7fe6a4ee711e in QObjectPrivate::deleteChildren() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #35 0x7fe6a5dab056 in QWidget::~QWidget() () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #36 0x7fe6a5f126ad in QScrollArea::~QScrollArea() () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #37 0x7fe6a64f9eb8 in KPageWidgetItem::~KPageWidgetItem() () from /lib/x86_64-linux-gnu/libKF5WidgetsAddons.so.5 #38 0x7fe6a64fbae9 in ?? () from /lib/x86_64-linux-gnu/libKF5WidgetsAddons.so.5 #39 0x7fe6a64fef81 in KPageWidgetModel::removePage(KPageWidgetItem*) () from /lib/x86_64-linux-gnu/libKF5WidgetsAddons.so.5 #40 0x7fe6a69cf945 in ModuleView::closeModules() () from /lib/x86_64-linux-gnu/libsystemsettingsview.so.3 #41 0x7fe69426ced6 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/systemsettingsview/systemsettings_sidebar_mode.so #42 0x7fe69426df9e in ?? () from
[plasma-systemmonitor] [Bug 466907] New: System monitor settings pop-up cannot be dragged
https://bugs.kde.org/show_bug.cgi?id=466907 Bug ID: 466907 Summary: System monitor settings pop-up cannot be dragged Classification: Plasma Product: plasma-systemmonitor Version: 5.27.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: david.cortes.riv...@gmail.com CC: ahiems...@heimr.nl, plasma-b...@kde.org Target Milestone: --- SUMMARY If I try to change the settings of something in the system monitor, the pop-up window that it opens is not clickable, which is detrimental to usability as then I cannot have a clear view of what I have currently configured to show in the UI as I need to make changes. STEPS TO REPRODUCE 1. Launch system monitor. 2. Go to some section like "Processes" in the left panel. 3. Click the three dots menu, select "Configure columns...". 4. Try to drag the pop-up that opens from its header section where there should be a titlebar. OBSERVED RESULT Cannot drag the pop-up subwindow. EXPECTED RESULT Should let me drag the pop-up subwindow so that then I can see my current view before as I change the settings. SOFTWARE/OS VERSIONS Operating System: Debian GNU/Linux 12 KDE Plasma Version: 5.27.2 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 6.1.0-5-amd64 (64-bit) Graphics Platform: X11 Processors: 20 × 12th Gen Intel® Core™ i7-12700H Memory: 62.6 GiB of RAM Graphics Processor: Mesa Intel® Graphics Manufacturer: SLIMBOOK Product Name: Executive ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 466906] New: Cannot drag columns in system monitor pages
https://bugs.kde.org/show_bug.cgi?id=466906 Bug ID: 466906 Summary: Cannot drag columns in system monitor pages Classification: Plasma Product: plasma-systemmonitor Version: 5.27.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: david.cortes.riv...@gmail.com CC: ahiems...@heimr.nl, plasma-b...@kde.org Target Milestone: --- SUMMARY I cannot drag columns in a system monitor page to re-arrange them in the order I want them. STEPS TO REPRODUCE 1. Launch system monitor. 2. Go to some section like "Processes" in the left panel. 3. Pick a column like "Name" or "CPU" and try to drag it further to the right with the mouse. OBSERVED RESULT Doesn't move. EXPECTED RESULT Should let me place the columns in the order that I want them. SOFTWARE/OS VERSIONS Operating System: Debian GNU/Linux 12 KDE Plasma Version: 5.27.2 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 6.1.0-5-amd64 (64-bit) Graphics Platform: X11 Processors: 20 × 12th Gen Intel® Core™ i7-12700H Memory: 62.6 GiB of RAM Graphics Processor: Mesa Intel® Graphics Manufacturer: SLIMBOOK Product Name: Executive ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465790] Resizing an Aurorae-decorated window leads to malformed decorations
https://bugs.kde.org/show_bug.cgi?id=465790 --- Comment #31 from Michał Dybczak --- To add more details to me previous comment: No scaling (100%) Aurorae: WhiteSur Dark The issue happens more likely on Qt apps, like Konsole. You need to adjust the width of a window to trigger it. This time, I got even a new effect: the titlebar was expanding down, and the graphics was expanding along the way, which is looked as if it was melting Quite trippy... Once I closed the Konsole from the dock (I couldn't interact with the enormously extended buttons) and launched it again, it was immune to that glitch. Maybe all apps became immune, because I couldn't trigger it anymore. Non-qt apps like Firefox also can get it, but it happens rarely. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 464340] Rendu crashed
https://bugs.kde.org/show_bug.cgi?id=464340 --- Comment #7 from emohr --- It seems you have some issues on clips in the timeline. Your first MP3 clip has an issue. Then on an MPG4 clip on minute 4 and minute 43/44 is an issue. Please convert these clips in the project bin with right click “Transcode to Edit Friendly Format” and exchange the clips in the trimline. Then try rendering again. Il semble que vous ayez des problèmes avec les clips dans la timeline. Votre premier clip MP3 a un problème. Ensuite, sur un clip MPG4 à la minute 4 et aux minutes 43/44, il y a un problème. Veuillez convertir ces clips dans la corbeille du projet avec un clic droit "Transcode to Edit Friendly Format" et échanger les clips dans la ligne de coupe. Essayez ensuite de refaire le rendu. -- You are receiving this mail because: You are watching all bug changes.
[ktextaddons] [Bug 466894] AutoCorrectionLanguage widget shows entries in lowercase
https://bugs.kde.org/show_bug.cgi?id=466894 --- Comment #4 from Raphael Kubo da Costa --- Doesn't that also apply to lowercasing everything like it's currently done, in which case it might be better to just provide a mix of capitalized and non-capitalized entries as returned by QLocale? -- You are receiving this mail because: You are watching all bug changes.
