[frameworks-kimageformats] [Bug 493466] New: Endianness bug in PCX reader’s peekHeader() method on big endian architectures
https://bugs.kde.org/show_bug.cgi?id=493466 Bug ID: 493466 Summary: Endianness bug in PCX reader’s peekHeader() method on big endian architectures Classification: Frameworks and Libraries Product: frameworks-kimageformats Version: 6.6.0 Platform: Debian unstable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: alex.me...@kde.org Reporter: couc...@debian.org CC: aa...@kde.org, kdelibs-b...@kde.org Target Milestone: --- When reading from a sequential device, the peekHeader() method in the PCX readers reads the header from its defined little endian endianness into the arch-specific endianness of the current architecture for multibyte types. Being a "peek" method, it then tries to push back the bytes into the device after reading for its next use, but it doesn’t convert multibyte types correctly from arch-specifice endianness back into the initial little endian format. Subsequent reading of the data from the device will thus lead to incorrect values for multibyte types on the next use, where quint16 types in the header have their bytes swapped. I’ve proposed an MR here with a fix : https://invent.kde.org/frameworks/kimageformats/-/merge_requests/258 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwidgetsaddons] [Bug 493060] Konsole crash when trying to change font
https://bugs.kde.org/show_bug.cgi?id=493060 --- Comment #2 from Aurélien COUDERC --- Reverting https://invent.kde.org/frameworks/kwidgetsaddons/-/commit/810903365c3dd25d1e6b859a9b853df298ed23a5 fixes the crash. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwidgetsaddons] [Bug 493060] Konsole crash when trying to change font
https://bugs.kde.org/show_bug.cgi?id=493060 Aurélien COUDERC changed: What|Removed |Added Assignee|konsole-de...@kde.org |cf...@kde.org Product|konsole |frameworks-kwidgetsaddons Component|font|general CC||kdelibs-b...@kde.org Version|24.08.0 |6.6.0 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 493060] Konsole crash when trying to change font
https://bugs.kde.org/show_bug.cgi?id=493060
--- Comment #1 from Aurélien COUDERC ---
I’m having the same issue with systemsettings so this bug report should
probably be moved to frameworks' kwidgetsaddons.
Thread 1 "systemsettings" received signal SIGSEGV, Segmentation fault.
KFontChooserPrivate::init (this=0x5897abd0) at
/usr/include/c++/14/bits/unique_ptr.h:193
193 pointer_M_ptr() const noexcept { return std::get<0>(_M_t); }
(gdb) bt
#0 KFontChooserPrivate::init (this=0x5897abd0) at
/usr/include/c++/14/bits/unique_ptr.h:193
#1 0x774f4934 in KFontChooser::KFontChooser
(this=this@entry=0x59348260, flags=..., parent=parent@entry=0x7fffdc0034b0)
at ./src/kfontchooser.cpp:145
#2 0x774f92e0 in KFontChooserDialog::KFontChooserDialog
(this=0x7fffdc0034b0, flags=..., parent=)
at ./src/kfontchooserdialog.cpp:26
#3 0x774f9895 in KFontChooserDialog::getFont (theFont=..., flags=...,
parent=parent@entry=0x0) at ./src/kfontchooserdialog.cpp:92
#4 0x7fffa4667189 in KFonts::adjustFont (this=0x5937ccd0,
font=, category=...) at ./kcms/fonts/fonts.cpp:162
#5 0x7fffa4664da8 in KFonts::qt_metacall (this=0x5937ccd0,
_c=QMetaObject::InvokeMetaMethod, _id=8, _a=0x7fff99e8)
at
./obj-x86_64-linux-gnu/kcms/fonts/kcm_fonts_autogen/EWIEGA46WW/moc_fonts.cpp:351
#6 0x7611e7b3 in ??? () at /lib/x86_64-linux-gnu/libQt6Qml.so.6
#7 0x75ff90dd in ??? () at /lib/x86_64-linux-gnu/libQt6Qml.so.6
#8 0x760015b1 in QV4::QObjectMethod::callInternal(QV4::Value const*,
QV4::Value const*, int) const ()
at /lib/x86_64-linux-gnu/libQt6Qml.so.6
#9 0x7604514a in ??? () at /lib/x86_64-linux-gnu/libQt6Qml.so.6
#10 0x76048623 in ??? () at /lib/x86_64-linux-gnu/libQt6Qml.so.6
#11 0x75fba2ae in ??? () at /lib/x86_64-linux-gnu/libQt6Qml.so.6
#12 0x75fbd155 in QV4::Function::call(QObject*, void**, QMetaType
const*, int, QV4::ExecutionContext*) ()
at /lib/x86_64-linux-gnu/libQt6Qml.so.6
#13 0x760f2579 in QQmlJavaScriptExpression::evaluate(void**, QMetaType
const*, int) () at /lib/x86_64-linux-gnu/libQt6Qml.so.6
#14 0x7608d09b in QQmlBoundSignalExpression::evaluate(void**) () at
/lib/x86_64-linux-gnu/libQt6Qml.so.6
#15 0x7609222b in ??? () at /lib/x86_64-linux-gnu/libQt6Qml.so.6
#16 0x76111c67 in QQmlNotifier::emitNotify(QQmlNotifierEndpoint*,
void**) () at /lib/x86_64-linux-gnu/libQt6Qml.so.6
#17 0x751d10b8 in ??? () at /lib/x86_64-linux-gnu/libQt6Core.so.6
#18 0x7fffed8e492a in QQuickAbstractButtonPrivate::handleRelease(QPointF
const&, unsigned long) ()
at /lib/x86_64-linux-gnu/libQt6QuickTemplates2.so.6
#19 0x7fffed8fcafd in QQuickControl::mouseReleaseEvent(QMouseEvent*) () at
/lib/x86_64-linux-gnu/libQt6QuickTemplates2.so.6
#20 0x7660bde3 in QQuickItem::event(QEvent*) () at
/lib/x86_64-linux-gnu/libQt6Quick.so.6
#21 0x76dafae2 in QApplicationPrivate::notify_helper (this=, receiver=0x593c9be0, e=0x7fffc990)
at ./src/widgets/kernel/qapplication.cpp:3296
#22 0x751801c8 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at /lib/x86_64-linux-gnu/libQt6Core.so.6
--Type for more, q to quit, c to continue without paging--
#23 0x7675f3ab in
QQuickDeliveryAgentPrivate::deliverMatchingPointsToItem(QQuickItem*, bool,
QPointerEvent*, bool) ()
at /lib/x86_64-linux-gnu/libQt6Quick.so.6
#24 0x767611c6 in
QQuickDeliveryAgentPrivate::deliverUpdatedPoints(QPointerEvent*) () at
/lib/x86_64-linux-gnu/libQt6Quick.so.6
#25 0x76762a23 in
QQuickDeliveryAgentPrivate::deliverPointerEvent(QPointerEvent*) () at
/lib/x86_64-linux-gnu/libQt6Quick.so.6
#26 0x76763b34 in
QQuickDeliveryAgentPrivate::handleMouseEvent(QMouseEvent*) () at
/lib/x86_64-linux-gnu/libQt6Quick.so.6
#27 0x76759ce8 in QQuickDeliveryAgent::event(QEvent*) () at
/lib/x86_64-linux-gnu/libQt6Quick.so.6
#28 0x7669e02c in QQuickWindow::event(QEvent*) () at
/lib/x86_64-linux-gnu/libQt6Quick.so.6
#29 0x76dafae2 in QApplicationPrivate::notify_helper (this=, receiver=0x5932b740, e=0x7fffc990)
at ./src/widgets/kernel/qapplication.cpp:3296
#30 0x751801c8 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at /lib/x86_64-linux-gnu/libQt6Core.so.6
#31 0x777d8f8d in QQuickWidget::mouseReleaseEvent(QMouseEvent*) () at
/lib/x86_64-linux-gnu/libQt6QuickWidgets.so.6
#32 0x76dfa8b3 in QWidget::event (this=0x5932b710,
event=0x7fffcf40) at ./src/widgets/kernel/qwidget.cpp:8959
#33 0x76dafae2 in QApplicationPrivate::notify_helper
(this=this@entry=0x555e5340, receiver=receiver@entry=0x5932b710,
e=e@entry=0x7fffcf40)
at ./src/widgets/kernel/qapplication.cpp:3296
#34 0x76db4540 in QApplication::notify (this=,
receiver=, e=0x7fffcf40)
at ./src/widgets/kernel/qapplication.cpp:2782
#35 0x751801c8 in QCoreApp
[konsole] [Bug 493061] New: When selecting an Emoji font, it doesn’t scale with the zoom level
https://bugs.kde.org/show_bug.cgi?id=493061
Bug ID: 493061
Summary: When selecting an Emoji font, it doesn’t scale with
the zoom level
Classification: Applications
Product: konsole
Version: 24.08.0
Platform: Debian unstable
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: font
Assignee: konsole-de...@kde.org
Reporter: couc...@debian.org
Target Milestone: ---
SUMMARY
When selecting an Emoji font different from the default in Konsole, the font
stays at a fixed size.
Once selected it won’t react to the zoom level (Ctrl++ / Ctrl+- / Ctrl+mouse
wheel), so even if you zoom a lot the emojis stay very small.
STEPS TO REPRODUCE
1. Open profile configuration
2. Go to the Appearance section and the Complex Text Layout tab
3. Select an emoji font / size different from the default and save
OBSERVED RESULT
Once the custom emoji font has been selected, the emoji size becomes constant
and doesnt react to the zoom level in konsole.
EXPECTED RESULT
The emoji size reacts to the zoom level, the same way that the text font does.
WORKAROUND
Setting the font size to -1 in ~/.local/share/konsole/${profile}.profile makes
the emoji font size behave correctly.
SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Debian unstable/linux 6.11-rc5
KDE Plasma Version: 6.1.5
KDE Frameworks Version: 6.6.0
Qt Version: 6.6.2
--
You are receiving this mail because:
You are watching all bug changes.
[konsole] [Bug 493060] Konsole crash when trying to change font
https://bugs.kde.org/show_bug.cgi?id=493060 Aurélien COUDERC changed: What|Removed |Added Platform|Other |Debian unstable -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 493060] New: Konsole crash when trying to change font
https://bugs.kde.org/show_bug.cgi?id=493060
Bug ID: 493060
Summary: Konsole crash when trying to change font
Classification: Applications
Product: konsole
Version: 24.08.0
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: font
Assignee: konsole-de...@kde.org
Reporter: couc...@debian.org
Target Milestone: ---
SUMMARY
Konsole crashes when trying to select a font.
Either for the main font or the emoji font.
STEPS TO REPRODUCE
1. Launch Konsole
2. Open profile configuration page
3. In the Appearance section click the « Choose » button to select a font.
OBSERVED RESULT
SIGSEGV
EXPECTED RESULT
Font selection dialog
SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Debian unstable/linux 6.11-rc5
KDE Plasma Version: 6.1.5
KDE Frameworks Version: 6.6.0
Qt Version: 6.6.2
ADDITIONAL INFORMATION
Thread 1 "konsole" received signal SIGSEGV, Segmentation fault.
KFontChooserPrivate::init (this=0x56794190) at
/usr/include/c++/14/bits/unique_ptr.h:193
193 pointer_M_ptr() const noexcept { return std::get<0>(_M_t); }
(gdb) bt
#0 KFontChooserPrivate::init (this=0x56794190) at
/usr/include/c++/14/bits/unique_ptr.h:193
#1 0x758f4934 in KFontChooser::KFontChooser
(this=this@entry=0x56783ad0, flags=...,
flags@entry=..., parent=parent@entry=0x56794560) at
./src/kfontchooser.cpp:145
#2 0x77ca1990 in Konsole::FontDialog::FontDialog
(this=this@entry=0x56794560, parent=parent@entry=0x563bea70,
emoji=emoji@entry=false, font=...)
at /usr/include/x86_64-linux-gnu/qt6/QtCore/qflags.h:74
#3 0x77d0fd2d in Konsole::EditProfileDialog::showFontDialog
(this=0x563bea70) at ./src/widgets/EditProfileDialog.cpp:1253
#4 0x763d12d1 in ??? () at /lib/x86_64-linux-gnu/libQt6Core.so.6
#5 0x774bf196 in QAbstractButton::clicked (this=,
_t1=)
at
./obj-x86_64-linux-gnu/src/widgets/Widgets_autogen/include/moc_qabstractbutton.cpp:408
#6 0x774b6c6e in QAbstractButtonPrivate::emitClicked
(this=0x56558ee0) at ./src/widgets/widgets/qabstractbutton.cpp:379
#7 0x774b6f4d in QAbstractButtonPrivate::click (this=0x56558ee0)
at ./src/widgets/widgets/qabstractbutton.cpp:372
#8 0x774c5009 in QAbstractButton::mouseReleaseEvent
(this=0x56558e50, e=0x7fffcfb0)
at ./src/widgets/widgets/qabstractbutton.cpp:974
#9 0x773fa8b3 in QWidget::event (this=0x56558e50,
event=0x7fffcfb0) at ./src/widgets/kernel/qwidget.cpp:8959
#10 0x773afae2 in QApplicationPrivate::notify_helper
(this=this@entry=0x55588340, receiver=receiver@entry=0x56558e50,
e=e@entry=0x7fffcfb0)
at ./src/widgets/kernel/qapplication.cpp:3296
#11 0x773b4540 in QApplication::notify (this=,
receiver=, e=0x7fffcfb0)
at ./src/widgets/kernel/qapplication.cpp:2782
#12 0x763801c8 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at /lib/x86_64-linux-gnu/libQt6Core.so.6
#13 0x773a927e in QApplicationPrivate::sendMouseEvent
(receiver=0x56558e50, event=0x7fffcfb0, alienWidget=, nativeWidget=0x563bea70, buttonDown=,
lastMouseReceiver=..., spontaneous=true, onlyDispatchEnterLeave=false) at
./src/widgets/kernel/qapplication.cpp:2366
#14 0x7740e448 in QWidgetWindow::handleMouseEvent (this=0x56714820,
event=0x7fffd3c0)
at ./src/widgets/kernel/qwidgetwindow.cpp:653
#15 0x77409f38 in QWidgetWindow::event (this=0x56714820,
event=0x7fffd3c0) at ./src/widgets/kernel/qwidgetwindow.cpp:267
#16 0x773afae2 in QApplicationPrivate::notify_helper (this=, receiver=0x56714820, e=0x7fffd3c0)
at ./src/widgets/kernel/qapplication.cpp:3296
#17 0x763801c8 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at /lib/x86_64-linux-gnu/libQt6Core.so.6
--Type for more, q to quit, c to continue without paging--
#18 0x76bc4f9b in QGuiApplicationPrivate::processMouseEvent
(e=0x7fffe0002a90) at ./src/gui/kernel/qguiapplication.cpp:2325
#19 0x76c1db7c in QWindowSystemInterface::sendWindowSystemEvents
(flags=...) at ./src/gui/kernel/qwindowsysteminterface.cpp:1109
#20 0x76f51d54 in userEventSourceDispatch (source=) at
./src/gui/platform/unix/qeventdispatcher_glib.cpp:38
#21 0x736bf7df in g_main_dispatch
(context=context@entry=0x7fffe8000f00) at ../../../glib/gmain.c:3357
#22 0x736c1a17 in g_main_context_dispatch_unlocked
(context=0x7fffe8000f00) at ../../../glib/gmain.c:4208
#23 g_main_context_iterate_unlocked
(context=context@entry=0x7fffe8000f00, block=block@entry=1,
dispatch=dispatch@entry=1, self=)
at ../../../glib/gmain.c:4273
#24 0x736c2180 in g_main_context_iteration (context=0x7fffe8000f00,
may_block=1) at ../../../glib/gmain.c:4338
#25 0x7657a1b3 in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib/
[neon] [Bug 480681] Installer crashes when selecting French BEPO, AFNOR keyboard layout
https://bugs.kde.org/show_bug.cgi?id=480681 --- Comment #2 from Aurélien COUDERC --- Created attachment 165438 --> https://bugs.kde.org/attachment.cgi?id=165438&action=edit French BEPO AFNOR layout preview The French (BEPO, AFNOR) layout seems to have some very funky UTF-8 emojis which I’m sure are not part of the norm. https://bepo.fr/wiki/Accueil -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 480681] Installer crashes when selecting French BEPO, AFNOR keyboard layout
https://bugs.kde.org/show_bug.cgi?id=480681 --- Comment #1 from Aurélien COUDERC --- > STEPS TO REPRODUCE > 1. Boot the live image (tested on Neon Unstable image from 28/01/24) > 2. Launch the installer > 3. Select Français (French) language > 4. Click Next for the timezone This is missing step 5. which triggers the crash. :-) 5. Select the « French (BEPO, AFNOR) » layout -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 480681] New: Installer crashes when selecting French BEPO, AFNOR keyboard layout
https://bugs.kde.org/show_bug.cgi?id=480681 Bug ID: 480681 Summary: Installer crashes when selecting French BEPO, AFNOR keyboard layout Classification: KDE Neon Product: neon Version: unspecified Platform: Neon OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: Live/Install images Assignee: neon-b...@kde.org Reporter: couc...@debian.org CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Boot the live image (tested on Neon Unstable image from 28/01/24) 2. Launch the installer 3. Select Français (French) language 4. Click Next for the timezone OBSERVED RESULT Installer crash. See stack trace at the bottom. EXPECTED RESULT Installer not crashing. SOFTWARE/OS VERSIONS Linux/KDE Plasma: linux 6.5.0-15-generic / KDE Neon Unstable from 28/01/24 KDE Plasma Version: 6.0.80 KDE Frameworks Version: 5.249.0 Qt Version: 6.6.1 ADDITIONAL INFORMATION Choosing the same keyboard layout from in the system settings from the live image works fine, so it seems to be a installer specific bug. Application: Calamares (_neon), signal: Aborted [KCrash Handler] #4 __pthread_kill_implementation (no_tid=0, signo=6, threadid=140528670030208) at ./nptl/pthread_kill.c:44 #5 __pthread_kill_internal (signo=6, threadid=140528670030208) at ./nptl/pthread_kill.c:78 #6 __GI___pthread_kill (threadid=140528670030208, signo=signo@entry=6) at ./nptl/pthread_kill.c:89 #7 0x7fcf65525476 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #8 0x7fcf6550b7f3 in __GI_abort () at ./stdlib/abort.c:79 #9 0x7fcf65e326f3 in qAbort () at ./src/corelib/global/qglobal.cpp:161 #10 0x7fcf65e2e055 in qt_message_fatal (message=..., context=...) at ./src/corelib/global/qlogging.cpp:2003 #11 qt_message(QtMsgType, const QMessageLogContext &, const char *, typedef __va_list_tag __va_list_tag *) (msgType=msgType@entry=QtFatalMsg, context=..., msg=, ap=ap@entry=0x7fffdb6c9d10) at ./src/corelib/global/qlogging.cpp:378 #12 0x7fcf65e3309f in QMessageLogger::fatal (this=, msg=) at ./src/corelib/global/qlogging.cpp:901 #13 0x7fcf65e03261 in qt_assert (assertion=, file=, line=) at ./src/corelib/global/qassert.cpp:68 #14 0x7fcf41825c11 in KeyBoardPreview::fromUnicodeString(QString) () from /usr/lib/x86_64-linux-gnu/calamares/modules/keyboard/libcalamares_viewmodule_keyboard.so #15 0x7fcf4182c3aa in KeyBoardPreview::loadCodes() () from /usr/lib/x86_64-linux-gnu/calamares/modules/keyboard/libcalamares_viewmodule_keyboard.so #16 0x7fcf4182c761 in KeyBoardPreview::setVariant(QString) () from /usr/lib/x86_64-linux-gnu/calamares/modules/keyboard/libcalamares_viewmodule_keyboard.so #17 0x7fcf41814632 in ?? () from /usr/lib/x86_64-linux-gnu/calamares/modules/keyboard/libcalamares_viewmodule_keyboard.so #18 0x7fcf65d827ae in QtPrivate::QSlotObjectBase::call (a=, r=, this=, this=, r=, a=) at ./src/corelib/kernel/qobjectdefs_impl.h:433 #19 doActivate (sender=0x55e9e510d2e0, signal_index=26, argv=0x7fffdb6ca210) at ./src/corelib/kernel/qobject.cpp:4021 #20 0x7fcf418009c2 in XKBListModel::currentIndexChanged(int) () from /usr/lib/x86_64-linux-gnu/calamares/modules/keyboard/libcalamares_viewmodule_keyboard.so #21 0x7fcf4180cdf7 in XKBListModel::setCurrentIndex(int) () from /usr/lib/x86_64-linux-gnu/calamares/modules/keyboard/libcalamares_viewmodule_keyboard.so #22 0x7fcf418144a1 in ?? () from /usr/lib/x86_64-linux-gnu/calamares/modules/keyboard/libcalamares_viewmodule_keyboard.so #23 0x7fcf65d827ae in QtPrivate::QSlotObjectBase::call (a=, r=, this=, this=, r=, a=) at ./src/corelib/kernel/qobjectdefs_impl.h:433 #24 doActivate (sender=0x55e9e5159940, signal_index=4, argv=0x7fffdb6ca330) at ./src/corelib/kernel/qobject.cpp:4021 #25 0x7fcf65c3c00e in QItemSelectionModel::currentChanged (this=this@entry=0x55e9e5159940, _t1=..., _t2=...) at ./obj-x86_64-linux-gnu/src/corelib/Core_autogen/include/moc_qitemselectionmodel.cpp:667 #26 0x7fcf65c3fbbc in QItemSelectionModel::setCurrentIndex (this=0x55e9e5159940, index=..., command=...) at ./src/corelib/itemmodels/qitemselectionmodel.cpp:1403 #27 0x7fcf66e055ad in QAbstractItemView::mousePressEvent (this=0x55e9e513d110, event=) at ./src/widgets/itemviews/qabstractitemview.cpp:1829 #28 0x7fcf66fcd233 in QWidget::event (this=0x55e9e513d110, event=0x7fffdb6caa40) at ./src/widgets/kernel/qwidget.cpp:8979 #29 0x7fcf66f07fa6 in QFrame::event (this=0x55e9e513d110, e=0x7fffdb6caa40) at ./src/widgets/widgets/qframe.cpp:515 #30 0x7fcf65db7448 in QCoreApplicationPrivate::sendThroughObjectEventFilters (receiver=receiver@e
[krita] [Bug 468566] Cannot enter characters with `ALT GR` modifier key while renaming layers (keys combination is captured by shortcuts)
https://bugs.kde.org/show_bug.cgi?id=468566 --- Comment #12 from Aurélien Da Campo --- Hi Dmitry! Here is the shot - I even managed to reproduce it with the Windows On-Screen Keyboard: https://www.swisstransfer.com/d/1cb99891-2ca7-4d59-a8d7-1b979c050635 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 468566] Cannot enter characters with `ALT GR` modifier key while renaming layers (keys combination is captured by shortcuts)
https://bugs.kde.org/show_bug.cgi?id=468566 --- Comment #10 from Aurélien Da Campo --- I just tested the provided build (5.2.0-prealpha (git a92c1c6)) and the issue is still present with the same symptoms. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 468566] Cannot enter characters with `ALT GR` modifier key while renaming layers (keys combination is captured by shortcuts)
https://bugs.kde.org/show_bug.cgi?id=468566 --- Comment #2 from Aurélien Da Campo --- (In reply to Halla Rempt from comment #1) > Hi! > > Can you add those characters > > * when the layerbox is undocked? > * the search field in the brush presets docker? Hi, Thanks for taking the time to investigate this issue :) Here are few answers to your questions: 1) The behavior is the same when the layer box is docked or undocked 2) The behavior is the same when in the brush presets search box I noticed something new, I can enter few of the characters on Vector Layers. This really seems to be linked to the capture of shortcuts by the current context. When being in the context of a Paint Layer, the character input is captured by the shortcuts of the painting tool. For example, if I try to enter the character `[` with the shortcut `ALTGR` + `[` I see callout showing that the Brush Size has been reduced but no characters are entered in the input field. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 468566] New: Cannot enter characters with `ALT GR` modifier key while renaming layers (keys combination is captured by shortcuts)
https://bugs.kde.org/show_bug.cgi?id=468566
Bug ID: 468566
Summary: Cannot enter characters with `ALT GR` modifier key
while renaming layers (keys combination is captured by
shortcuts)
Classification: Applications
Product: krita
Version: 5.1.4
Platform: Other
OS: Microsoft Windows
Status: REPORTED
Severity: normal
Priority: NOR
Component: Shortcuts and Canvas Input Settings
Assignee: krita-bugs-n...@kde.org
Reporter: aurelien.daca...@gmail.com
Target Milestone: ---
SUMMARY
Entering special characters (3rd character alternative) through `ALT GR`
modifier key while renaming a layer is not possible or complicated via
copy/pasting them.
STEPS TO REPRODUCE
1. Start renaming a layer
2. Try to type a special character using ALT GR modifier key
OBSERVED RESULT
The keyboard combination is captured by a shortcut and therefore no characters
are added to the text field.
EXPECTED RESULT
All Krita specific shortcuts should be disabled while entering text.
WORKAROUND
Copy the character from an outside text editor and paste it in Krita
ADDITIONAL INFORMATION
I have a Swiss French keyboard layout (QWERTZ), the characters I cannot
directly enter are: ¦@#°§¬|¢´~[]{}\
--
You are receiving this mail because:
You are watching all bug changes.
[Welcome Center] [Bug 466698] Welcome Center Page 1 shows incorrect description of Debian
https://bugs.kde.org/show_bug.cgi?id=466698 --- Comment #4 from Aurélien COUDERC --- 5.27.2 migrated to testing/bookworm so the bug should be fixed for everyone now. -- You are receiving this mail because: You are watching all bug changes.
[Welcome Center] [Bug 466698] Welcome Center Page 1 shows incorrect description of Debian
https://bugs.kde.org/show_bug.cgi?id=466698 Aurélien COUDERC changed: What|Removed |Added CC||couc...@debian.org --- Comment #2 from Aurélien COUDERC --- Ah, yes my fault, sorry for that. :-( I was trying to make some additional customization to plasma-welcome and some experiments went into the package by mistake. Version 5.27.2 in unstable is already fixed, and I’ll try to get it migrating to testing/bookworm asap. Sorry for the breakage. -- You are receiving this mail because: You are watching all bug changes.
[libkdegames] [Bug 465195] konqi-modern card deck is under a non-free software license
https://bugs.kde.org/show_bug.cgi?id=465195 Aurélien COUDERC changed: What|Removed |Added Summary|konqi-modern card deck is |konqi-modern card deck is |under a non-free software |under a non-free software |licens |license -- You are receiving this mail because: You are watching all bug changes.
[libkdegames] [Bug 465195] New: konqi-modern card deck is under a non-free software licens
https://bugs.kde.org/show_bug.cgi?id=465195 Bug ID: 465195 Summary: konqi-modern card deck is under a non-free software licens Classification: Frameworks and Libraries Product: libkdegames Version: unspecified Platform: Debian unstable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kde-games-b...@kde.org Reporter: couc...@debian.org Target Milestone: --- The license of the konqi-modern carddeck found in ./src/carddecks/svg-konqi-modern/COPYRIGHT is an MIT-like license, unfortunately modified with the following condition : « Permission is hereby granted, free of charge, to any member of the KDE project (the "K Desktop Environment" http://www.kde.org) obtaining a copy of this "Konqi SDK" package and associated documentation files (the "Package"), to deal in the Package without restriction […] » The « to any member of the KDE project » makes it non FOSS, since FOSS requires that the software be usable by anyone for any purpose. For example, the Debian Free Software Guidelines [1] item 5. states : « 5. No Discrimination Against Persons or Groups The license must not discriminate against any person or group of persons. » The card deck should either be re-licensed if the original authors agree, or dropped from libkdegames. [1] https://www.debian.org/social_contract.en.html#guidelines -- You are receiving this mail because: You are watching all bug changes.
[ktouch] [Bug 422088] Can't type in Wayland
https://bugs.kde.org/show_bug.cgi?id=422088 Aurélien COUDERC changed: What|Removed |Added CC||couc...@debian.org -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kguiaddons] [Bug 464571] Symbols from libwayland-server are published in the library’s ABI
https://bugs.kde.org/show_bug.cgi?id=464571 Aurélien COUDERC changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG --- Comment #2 from Aurélien COUDERC --- I understand this is the expected way to go for interacting with the Wayland compositor so closing. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kguiaddons] [Bug 464571] Symbols from libwayland-server are published in the library’s ABI
https://bugs.kde.org/show_bug.cgi?id=464571 --- Comment #1 from Aurélien COUDERC --- The wayland symbols appear after this commit : https://invent.kde.org/frameworks/kguiaddons/-/commit/3984732e007e71632a525d89227fdfe94fa037ad -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kguiaddons] [Bug 464571] New: Symbols from libwayland-server are published in the library’s ABI
https://bugs.kde.org/show_bug.cgi?id=464571 Bug ID: 464571 Summary: Symbols from libwayland-server are published in the library’s ABI Classification: Frameworks and Libraries Product: frameworks-kguiaddons Version: 5.102.0 Platform: Debian unstable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdelibs-b...@kde.org Reporter: couc...@debian.org Target Milestone: --- Dear upstream, while packaging kguiaddons 5.102 for Debian I noticed the following new symbols : wl_buffer_interface@Base 5.102.0 wl_callback_interface@Base 5.102.0 wl_compositor_interface@Base 5.102.0 wl_data_device_interface@Base 5.102.0 wl_data_device_manager_interface@Base 5.102.0 wl_data_offer_interface@Base 5.102.0 wl_data_source_interface@Base 5.102.0 wl_display_interface@Base 5.102.0 wl_keyboard_interface@Base 5.102.0 wl_output_interface@Base 5.102.0 wl_pointer_interface@Base 5.102.0 wl_region_interface@Base 5.102.0 wl_registry_interface@Base 5.102.0 wl_seat_interface@Base 5.102.0 wl_shell_interface@Base 5.102.0 wl_shell_surface_interface@Base 5.102.0 wl_shm_interface@Base 5.102.0 wl_shm_pool_interface@Base 5.102.0 wl_subcompositor_interface@Base 5.102.0 wl_subsurface_interface@Base 5.102.0 wl_surface_interface@Base 5.102.0 wl_touch_interface@Base 5.102.0 These symbols are also part of libwayland-server0 so I doubt they should be part of kguiaddons library. Am I missing something ? Is there a way to remove them ? Full build log here : https://people.debian.org/~coucouf/kguiaddons_5.102.0.build.log Thanks for your help -- You are receiving this mail because: You are watching all bug changes.
[dragonplayer] [Bug 464137] New: No more recent files list since the UI overhaul
https://bugs.kde.org/show_bug.cgi?id=464137 Bug ID: 464137 Summary: No more recent files list since the UI overhaul Classification: Applications Product: dragonplayer Version: unspecified Platform: Debian unstable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: couc...@debian.org CC: myr...@kde.org, sit...@kde.org Target Milestone: --- SUMMARY Since the UI overhaul, dragon has lost the list of recent files that it used to have on its welcome screen. I think that was a nice feature and would be worth keeping. Kate/Kwrite welcome screens come to mind as nice rewrites that implement this functionality. STEPS TO REPRODUCE 1. Launch dragonplayer 2. Play a file 3. Quit dragonplayer 4. Launch dragonplayer again OBSERVED RESULT No list of recent files in the UI. EXPECTED RESULT When starting dragonplayer the second time (step 4.), I’d expect to have a quick way to reopen the file played at step 2. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Plasma Version: 5.26.5 KDE Frameworks Version: 5.101.0 Qt Version: 5.15.7 ADDITIONAL INFORMATION Running the HEAD of the master branch as of 2022-01-08, commit cb45215c. -- You are receiving this mail because: You are watching all bug changes.
[filelight] [Bug 464067] filelight looses piechart depth levels when navigating back or up
https://bugs.kde.org/show_bug.cgi?id=464067 Aurélien COUDERC changed: What|Removed |Added Version|unspecified |22.12.1 -- You are receiving this mail because: You are watching all bug changes.
[filelight] [Bug 464070] filelight doesn’t register navigation down the tree for Back/Forward navigation
https://bugs.kde.org/show_bug.cgi?id=464070 Aurélien COUDERC changed: What|Removed |Added Version|unspecified |22.12.1 -- You are receiving this mail because: You are watching all bug changes.
[filelight] [Bug 464070] filelight doesn’t register navigation down the tree for Back/Forward navigation
https://bugs.kde.org/show_bug.cgi?id=464070 --- Comment #2 from Aurélien COUDERC --- Also reproducible in 22.04.3. -- You are receiving this mail because: You are watching all bug changes.
[filelight] [Bug 464067] filelight looses piechart depth levels when navigating back or up
https://bugs.kde.org/show_bug.cgi?id=464067 --- Comment #2 from Aurélien COUDERC --- Not reproducible in 22.04.3. -- You are receiving this mail because: You are watching all bug changes.
[filelight] [Bug 464070] filelight doesn’t register navigation down the tree for Back/Forward navigation
https://bugs.kde.org/show_bug.cgi?id=464070 --- Comment #1 from Aurélien COUDERC --- Also reproducible in 22.12.1. -- You are receiving this mail because: You are watching all bug changes.
[filelight] [Bug 464067] filelight looses piechart depth levels when navigating back or up
https://bugs.kde.org/show_bug.cgi?id=464067 --- Comment #1 from Aurélien COUDERC --- Also reproducible in 22.12.1. -- You are receiving this mail because: You are watching all bug changes.
[filelight] [Bug 464070] New: filelight doesn’t register navigation down the tree for Back/Forward navigation
https://bugs.kde.org/show_bug.cgi?id=464070 Bug ID: 464070 Summary: filelight doesn’t register navigation down the tree for Back/Forward navigation Classification: Applications Product: filelight Version: unspecified Platform: Debian unstable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: couc...@debian.org CC: martin.sandsm...@kde.org Target Milestone: --- SUMMARY When navigating down the tree of an analysed folder by clicking the pie chart elements or the folder names on the left panel, the action is not registered for the « Back » navigation and the Back button stays greyed. STEPS TO REPRODUCE 1. Start filelight and analyse your home folder. 2. Click any of the pie chart elements, or folders in the left pane. OBSERVED RESULT The Back button stays greyed and cannot be used. EXPECTED RESULT The Back button should be active and lead back to the previous location in the tree. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Plasma Version: 5.25.5 KDE Frameworks Version: 5.101.0 Qt Version: 5.15.7 ADDITIONAL INFORMATION Running the HEAD of the master branch as of 2023-01-07, commit 902a954. Other actions like « Up » or « Go to Overview » do register and activate Back/Forward navigation. -- You are receiving this mail because: You are watching all bug changes.
[filelight] [Bug 464067] New: filelight looses piechart depth levels when navigating back or up
https://bugs.kde.org/show_bug.cgi?id=464067 Bug ID: 464067 Summary: filelight looses piechart depth levels when navigating back or up Classification: Applications Product: filelight Version: unspecified Platform: Debian unstable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: couc...@debian.org CC: martin.sandsm...@kde.org Target Milestone: --- SUMMARY When doing an initial analysis of a folder, filelight will display a 5-level depth analysis of the space use in the pie-chart view. However if clicking on one of the outer ring elements and navigating back with the « Up » button, you never get the 5-level depth. STEPS TO REPRODUCE 1. Start filelight and analyze your home folder 2. Click one of the elements in the outer/5th level ring to dive in 3. Click the « Up » button 5 times OBSERVED RESULT Single ring / single depth pie chart analysis of the home folder. EXPECTED RESULT 5-level deep analysis of the home folder, same as after the initial analysis. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Plasma Version: 5.26.5 KDE Frameworks Version: 5.101.1 Qt Version: 5.15.7 ADDITIONAL INFORMATION Running the HEAD of the master branch as of 2023-01-07, commit 902a954. I have a big home with > 600k files and > 600 GiB, it’s not reproducible on a second smaller user home on this machine. The issue happens even when analysing as smaller folder down the tree in the big user’s home. -- You are receiving this mail because: You are watching all bug changes.
[filelight] [Bug 463409] Cannot close the context menu opened with right-click without choosing one of the actions
https://bugs.kde.org/show_bug.cgi?id=463409 --- Comment #2 from Aurélien COUDERC --- Any chance to get that fixed in the 22.12 branch we plan to ship for the next Debian release ? -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 463034] "Battery low" notification persists even if battery fully charged
https://bugs.kde.org/show_bug.cgi?id=463034 --- Comment #5 from Aurélien COUDERC --- I just had another weird behaviour : - My battery discharged to 10% and I got the notification. - I plugged my AC and the notification disappeared. - I unplugged it, while still at 10%. - The battery continued discharging below 10% and I didn’t get the notification again (I ended up plugging the AC anyway at 7%). There seem to be an issue with the interaction between the AC plugging / unplugging and being exactly at 10% or not. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 463034] "Battery low" notification persists even if battery fully charged
https://bugs.kde.org/show_bug.cgi?id=463034 Aurélien COUDERC changed: What|Removed |Added CC||couc...@debian.org --- Comment #4 from Aurélien COUDERC --- Yes, I can confirm the bug on Debian unstable with the same software versions as the reporter. -- You are receiving this mail because: You are watching all bug changes.
[filelight] [Bug 463409] Cannot close the context menu opened with right-click without choosing one of the actions
https://bugs.kde.org/show_bug.cgi?id=463409 Aurélien COUDERC changed: What|Removed |Added CC||couc...@debian.org -- You are receiving this mail because: You are watching all bug changes.
[filelight] [Bug 463409] New: Cannot close the context menu opened with right-click without choosing one of the actions
https://bugs.kde.org/show_bug.cgi?id=463409 Bug ID: 463409 Summary: Cannot close the context menu opened with right-click without choosing one of the actions Classification: Applications Product: filelight Version: 22.12.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: couc...@debian.org CC: martin.sandsm...@kde.org Target Milestone: --- SUMMARY Cannot close the context menu opened with right-click without choosing one of the actions. STEPS TO REPRODUCE 1. Open Filelight, analyze a folder. 2. Right click on any of the pie chart areas. 3. Click (left or right) anywhere in the UI outside of the context menu. OBSERVED RESULT The context menu stays open. EXPECTED RESULT The context menu should close. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Debian unstable KDE Plasma Version: 5.26.4 KDE Frameworks Version: 5.101.0 Qt Version: 5.15.7 Graphics Platform: Wayland ADDITIONAL INFORMATION The Esc key does correctly close the menu. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 462928] Copying a file after another copies the first file again
https://bugs.kde.org/show_bug.cgi?id=462928 Aurélien COUDERC changed: What|Removed |Added CC||couc...@debian.org --- Comment #4 from Aurélien COUDERC --- The same bug was reported on Debian unstable since the 22.12.0 upload : https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025943 -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 461299] elisa: irrtating stutters when playing audio
https://bugs.kde.org/show_bug.cgi?id=461299 --- Comment #10 from Aurélien COUDERC --- For reference there’s an upstream bug referencing the FLAC stuttering issue in VLC/libvlc here : https://code.videolan.org/videolan/vlc/-/issues/27454 And a fix : https://code.videolan.org/videolan/vlc/-/merge_requests/2918/diffs That we’ve applied to the Debian sources on top of 3.0.18 with a minor fix here : https://salsa.debian.org/multimedia-team/vlc/-/commit/c5289e84e17421c1e40ef9f0953b6c0f96a20cb2 -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 461299] elisa: irrtating stutters when playing audio
https://bugs.kde.org/show_bug.cgi?id=461299 --- Comment #5 from Aurélien COUDERC --- After more testing it seems to be limited to some files and the stuttering is reproducible for the same file and timestamp with all VLC-based apps. Mplayer doesn’t choke on the same files. I will do more testing and report but I guess from an Elisa standpoint you can close the bug. Thanks ! -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 461299] elisa: irrtating stutters when playing audio
https://bugs.kde.org/show_bug.cgi?id=461299 Aurélien COUDERC changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- CC||couc...@debian.org Ever confirmed|0 |1 --- Comment #3 from Aurélien COUDERC --- I’ve added the patch to the Debian package on top of 22.08.3 but it doesn’t solve the issue. It makes it less frequent but I still have occasional sound cuts on an otherwise idle modern machine. I’ve not looked at the code but if the stutter is due to the playback directly waiting for the data to load from the disk, the correct solution is not to make the buffer bigger, it’s only going to make it less frequent. Also loading complete files in memory is not the solution either. I have a couple of albums that are a single FLAC file of a couple hundres of MBs and it seems overkill to load these entirely into memory. If the issue is really the playback buffer becoming empty, the real fix would be to ensure the prefetch is done in the background so the playback never ends up waiting for the data to be there. Thanks for looking into this ! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 457340] New: Cyclic dependency between QML modules in notifications package
https://bugs.kde.org/show_bug.cgi?id=457340 Bug ID: 457340 Summary: Cyclic dependency between QML modules in notifications package Product: plasmashell Version: 5.25.3 Platform: Other OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: Notifications Assignee: plasma-b...@kde.org Reporter: couc...@debian.org CC: k...@privat.broulik.de Target Milestone: 1.0 The following can be found in system logs: plasmashell[PID]: Cyclic dependency detected between "file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/global/Globals.qml" and "file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/ThumbnailStrip.qml" This must be due to applets/notifications/package/contents/ui/NotificationHeader.qml:21 import "global" and applets/notifications/package/contents/ui/global/Globals.qml:23 import ".." -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kjs] [Bug 457338] New: Migrate from obsolete pcre1 to pcre2.
https://bugs.kde.org/show_bug.cgi?id=457338 Bug ID: 457338 Summary: Migrate from obsolete pcre1 to pcre2. Product: frameworks-kjs Version: 5.96.0 Platform: Debian unstable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: b.buschin...@googlemail.com Reporter: couc...@debian.org CC: kdelibs-b...@kde.org Target Milestone: --- Dear upstream, kjs uses the obsolete and now unsupported pcre library and it would be better to switch to the pcre2 implementation that is actively maintained and has been around for some years now. Debian has started the process of retiring the old pcre implementation (libpcre3-dev package) and ideally we would like to remove it from the next Debian stable release. The Debian bug report can be found here: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000112 Thanks, -- Aurélien -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 454161] Brightness stuck at 30%
https://bugs.kde.org/show_bug.cgi?id=454161 --- Comment #23 from Aurélien COUDERC --- (In reply to Nate Graham from comment #19) > Can affected folks test that patch? ^^ Works for me on top of the Debian package on an XPS 7390. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 454161] Brightness stuck at 30%
https://bugs.kde.org/show_bug.cgi?id=454161 --- Comment #9 from Aurélien COUDERC --- (In reply to Nate Graham from comment #6) > Are you using the slider in the Battery & Brightness applet? Does it work if > you click on a position in the track rather than dragging the handle? I’ve reverted the commits for some time now, but as far as I remember both the slider and the keys had the same effect. It was not only blocking at ~20 % but the brightness was also flickering between steps until it reached that level. So it would do something like 6%, 8%, 2%, 12%, 1%, 16%, 3%, 18% (not precisely these numbers but you get the idea). -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 454161] Brightness stuck at 30%
https://bugs.kde.org/show_bug.cgi?id=454161 Aurélien COUDERC changed: What|Removed |Added Keywords||regression -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 454853] New: When in present windows mode, if the computer goes in standby mode, the computer stays unlocked
https://bugs.kde.org/show_bug.cgi?id=454853 Bug ID: 454853 Summary: When in present windows mode, if the computer goes in standby mode, the computer stays unlocked Product: kwin Version: 5.24.5 Platform: Other OS: Linux Status: REPORTED Severity: major Priority: NOR Component: effects-present-windows Assignee: kwin-bugs-n...@kde.org Reporter: aurelien.castei...@gmail.com Target Milestone: --- SUMMARY When in present windows mode, if the computer goes in standby mode, the computer stays unlocked STEPS TO REPRODUCE 1. Enter in the present windows mode (by reaching a hot corner or pressing Ctrl+F10) 2. Do not click on a window or the background. 3. Enter in standby mode (for example by closing the lid if it's a laptop) 4. Leave the standby mode (by reopening the laptop's lid) OBSERVED RESULT The computer stays in the present windows mode, without asking for a password. If the user clicks on a window or the background, he can continue using the computer without any kind of authentication. EXPECTED RESULT The computer should ask for a password, before continuing in the present windows mode. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.18.1-zen1-1-zen (available in About System) KDE Plasma Version: 5.24.5 KDE Frameworks Version: 5.94.0 Qt Version: 5.15.4 ADDITIONAL INFORMATION Distribution: Garuda Linux (Dr460nized edition) (Arch-based) Display server: X11 -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 454161] Brightness stuck at 30%
https://bugs.kde.org/show_bug.cgi?id=454161 Aurélien COUDERC changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #4 from Aurélien COUDERC --- Quick note to say that for me it’s a serious bug. The brightness I get with the bug is more around 20% and makes it barely usable during daytime. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 454161] Brightness stuck at 30%
https://bugs.kde.org/show_bug.cgi?id=454161 Aurélien COUDERC changed: What|Removed |Added CC||couc...@debian.org --- Comment #3 from Aurélien COUDERC --- Same issue on Debian unstable working on packaging 5.25 beta. Others (at least from Kubuntu) don’t have the issue so not sure if the hardware or kernel is involved. My kernel is 5.17.6, and the laptop an XPS 13 7390. The issue is linked to the following commit : Write brightness to all raw devices https://invent.kde.org/plasma/powerdevil/-/commit/761fc8a4bf4bd70bcd9aca63fc67382c94ecf884 Reverting it and its followup : Fix Commit 761fc8a4 https://invent.kde.org/plasma/powerdevil/-/commit/94f8186804d8a67459a11673b602c55e34db25ad fixes the issue for me. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 448957] New: Symbols disappeared between 5.23.5 and 5.23.90 without soname bump
https://bugs.kde.org/show_bug.cgi?id=448957 Bug ID: 448957 Summary: Symbols disappeared between 5.23.5 and 5.23.90 without soname bump Product: KScreen Version: 5.23.90 Platform: Debian unstable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: libkscreen Assignee: kscreen-bugs-n...@kde.org Reporter: couc...@debian.org Target Milestone: --- Dear upstream, while packaging Plasma 5.24 beta for Debian I noticed the following symbols disappeared from KScreen. +#MISSING: 4:5.23.90-1# _ZN7KScreen6Output14setLogicalSizeERK6QSizeF@Base 4:5.18.3 +#MISSING: 4:5.23.90-1# _ZN7KScreen6Output18logicalSizeChangedEv@Base 4:5.18.3 +#MISSING: 4:5.23.90-1# _ZNK7KScreen6Output11logicalSizeEv@Base 4:5.18.3 Wouldn’t that deserve a soname bump ? Thanks, -- Aurélien -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 437451] Adding a directory containing over 199 files adds x-199 files
https://bugs.kde.org/show_bug.cgi?id=437451 Aurélien Oudelet (auroud85_fr) changed: What|Removed |Added CC||aoude...@outlook.com --- Comment #2 from Aurélien Oudelet (auroud85_fr) --- (In reply to Albert Astals Cid from comment #1) > Update to 21.04.0 Thanks pointing this. Reported malfunctioning version = 20.12.0 Current latest available release version = 21.04.1 As Mageia is a fixed release, we are investigating to migrate some packages to latest release. But, is there an interesting commit for k3b to solve the main issue of this report? I could then argue to upgrade all KFramework/Plasma/KDE Gear stuff for Mageia 8. Regards, auroud85 from Mageia Devs. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 397825] [Wayland] Message viewer displays only a black rectangle
https://bugs.kde.org/show_bug.cgi?id=397825 --- Comment #38 from Aurélien --- @ian : I just upgraded to kf5 5.82.0 and the bug is still here! Note that KMail version is still 20.12.2 (Please remove my email address from your quote ;) -- 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
https://bugs.kde.org/show_bug.cgi?id=385882 Aurélien changed: What|Removed |Added CC||k...@ap2c.org --- Comment #16 from Aurélien --- Same problem here under Fedora 34: - yakuake 20.12.2 - plasma 5.21.5 - kde framework 5.81.0 This is *really* annoying.. we can't work with it.. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 397825] [Wayland] Message viewer displays only a black rectangle
https://bugs.kde.org/show_bug.cgi?id=397825 Aurélien changed: What|Removed |Added CC||k...@ap2c.org --- Comment #36 from Aurélien --- I still encounter the problem with kf 5.81 and kmail 20.12.2 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 432145] Global menu doesn't appear for windows on secondary monitor
https://bugs.kde.org/show_bug.cgi?id=432145 Aurélien Oudelet (auroud85_fr) changed: What|Removed |Added Status|REPORTED|CONFIRMED CC||aoude...@outlook.com Ever confirmed|0 |1 --- Comment #2 from Aurélien Oudelet (auroud85_fr) --- I confirm the issue. Using Global Menu on Primary screen, dragging for example a Dolphin window to second monitor: booh, there is no Global Menu anymore for Dolphin when that window is in focus. Operating System: Mageia Cauldron KDE Plasma Version: 5.21.5 KDE Frameworks Version: 5.82.0 Qt Version: 5.15.2 Kernel Version: 5.12.4-desktop-1.mga9 OS Type: 64-bit Processors: 4 × Intel® Core™ i5-6600K CPU @ 3.50GHz Memory: 15.6 Gio of RAM -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kinit] [Bug 436538] kdeinit5: Qt: Session management error: networkIdsList argument is NULL
https://bugs.kde.org/show_bug.cgi?id=436538 Aurélien Oudelet (auroud85_fr) changed: What|Removed |Added URL||https://bugs.mageia.org/sho ||w_bug.cgi?id=27958 --- Comment #1 from Aurélien Oudelet (auroud85_fr) --- Added downstream bug report: https://bugs.mageia.org/show_bug.cgi?id=27958 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kinit] [Bug 436538] New: kdeinit5: Qt: Session management error: networkIdsList argument is NULL
https://bugs.kde.org/show_bug.cgi?id=436538 Bug ID: 436538 Summary: kdeinit5: Qt: Session management error: networkIdsList argument is NULL Product: frameworks-kinit Version: 5.81.0 Platform: Mageia RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: fa...@kde.org Reporter: aoude...@outlook.com CC: kdelibs-b...@kde.org Target Milestone: --- SUMMARY On Mageia systems, when opening Dolphin, Kate or Spectacle (among others), in system journal, there is this complain: kdeinit5[1577]: Qt: Session management error: networkIdsList argument is NULL STEPS TO REPRODUCE 1. Open a session. 2. Open Konsole, type "sudo journalctl -f" to see system journal 3. Open Dolphin from Kickoff or even from a Konsole session. OBSERVED RESULT kdeinit5[1577]: Qt: Session management error: networkIdsList argument is NULL EXPECTED RESULT No error. Operating System: Mageia 9 KDE Plasma Version: 5.21.4 KDE Frameworks Version: 5.81.0 Qt Version: 5.15.2 Kernel Version: 5.12.1-desktop-1.mga9 OS Type: 64-bit Graphics Platform: X11 Processors: 4 × Intel® Core™ i5-6600K CPU @ 3.50GHz Memory: 3.8 Gio of RAM Graphics Processor: SVGA3D; build: RELEASE; LLVM; This is reported against latest version we build (Cauldron, our Mageia devel version). It is also present in our stable distribution Mageia 8 (KF5.76). -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 430855] Dolphin 20.12.0 spurious error logging when opening Dolphin
https://bugs.kde.org/show_bug.cgi?id=430855 Aurélien Oudelet (auroud85_fr) changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #5 from Aurélien Oudelet (auroud85_fr) --- Fixed for kf.kio.core -- You are receiving this mail because: You are watching all bug changes.
[kmplayer] [Bug 383176] kmplayer crashed when opening settings
https://bugs.kde.org/show_bug.cgi?id=383176 Aurélien Oudelet (auroud85_fr) changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED CC||aoude...@outlook.com --- Comment #3 from Aurélien Oudelet (auroud85_fr) --- The segfault KMplayer -> Settings -> Configure KMplayer is fixed in latest git snapshot. Tested in Mageia 8 system today with this version: kmplayer-0.12.0b-9.git20210126.1.mga8 This should be closed fixed. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 432862] dolphin crashes when starting
https://bugs.kde.org/show_bug.cgi?id=432862 --- Comment #3 from Aurélien Oudelet (auroud85_fr) --- (In reply to Nate Graham from comment #2) > It's an option in Dolphin settings Window > Startup; you can disable it and > see what text is added to ~/.config/dolphinrc, and then ship a dolphinrc > file that includes that by default. For this, better is to trigger a file remove upon quit our installer. So, basically, users will have the functionality and no segfault. The option in the above file is: [General] RememberOpenedTabs=false But, on my file, there are other settings I don't know well the meaning. ;) > However we should really just fix the bug. I think there's a chance it's > already fixed in the upcoming 21.04 release because I added some logic to > handle invalid paths on launch. Could you check? Yeah, this should be done ASAP, but, for now we are in release and version freeze for Mageia 8. ASAP Cauldron reopen, I do think our maintainers will see this. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 432862] dolphin crashes when starting
https://bugs.kde.org/show_bug.cgi?id=432862 Aurélien Oudelet (auroud85_fr) changed: What|Removed |Added CC||aoude...@outlook.com Component|search |general URL||https://bugs.mageia.org/sho ||w_bug.cgi?id=28324 Platform|Other |Mageia RPMs --- Comment #1 from Aurélien Oudelet (auroud85_fr) --- After many tries, we, at Mageia, conclude this is due to the Saved Session management. In facts, the "Live" user session and datas are carried over in the newly installed system on harddrive to the first user which will have a new Unix name based on user info and will have a user ID of 1000. As reported by our KDE maintainers at Mageia at Comment 0, launching Dolphin in Live env. is OK but not in newly installed system. It segfaults badly. But, trying to know why, I created a totally new user "test" with totally empty /home/test directory. And noow, Dolphin DOES NOT segfault. I conclued that: there are strange bits of datas written somewhere in Live environment that are carried over the newly system and present in the first user home directory. Investigating: The culprit is session management added to Dolphin in Dolphin 20.08 I think. This is the option in Dolphin's preferences: Startup => Show on startup "Folders, tabs, and window state from last time". This wants to open /home/live/ with several name "live" somewhere... and it crashed because it no longer exists although there is a symlink "Live" that points to /home/aurelien (where "aurelien" is the name of the first user created after installation on my test system). But, the GUI option is not user accessible as Dolphin crashes as soon as it launches. After many tries, there are several files to delete to workaround this on already installed systems: First: ~/.config/session/dolphin_dolphin_dolphin ~/.config/dolphinrc Remove everything in them. => No segfault after. My request also is to know which CLI command can we type to deactivate the option to restore the previous Dolphin's state. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 416497] No shadows on GTK menus
https://bugs.kde.org/show_bug.cgi?id=416497 Aurélien Oudelet (auroud85_fr) changed: What|Removed |Added CC||aoude...@outlook.com --- Comment #8 from Aurélien Oudelet (auroud85_fr) --- Still valid in Operating System: Mageia 8 KDE Plasma Version: 5.20.4 KDE Frameworks Version: 5.76.0 Qt Version: 5.15.2 Kernel Version: 5.10.14-desktop-1.mga8 OS Type: 64-bit Processors: 4 × Intel® Core™ i5-6600K CPU @ 3.50GHz Memory: 15.6 Gio of RAM Graphics Processor: GeForce GTX 1660 Ti/PCIe/SSE2 As soon as we set "Breeze" in Systemsettings5 => Application Style => Configure GNOME/GTK Application Style... there is no shadow in GTK right-click and GTK menus. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 279614] The Dolphin shell panel (opened by F4) does not source .bashrc when opened by session restore
https://bugs.kde.org/show_bug.cgi?id=279614 Aurélien Oudelet (auroud85_fr) changed: What|Removed |Added Version|2.1 |20.12.2 CC||aoude...@outlook.com --- Comment #38 from Aurélien Oudelet (auroud85_fr) --- I don't know if this is related but: Dolphin 20.12.1 has an option to Show on startup: "Folders, tabs, window state of last time"(A) or a user's selected directory (B), in Startup pane of Dolphin's preferences. When the above (A) option is selected and a Terminal pane was previously opened, a new instance of Dolphin has this Terminal pane without colors outputs. But, if (B) option is selected, the same Terminal pane has colors outputs... It seems the (A) option relies on a Restore Session functionality... If you consider that this is not related, I shall open a new BR. (This was previously reported in Mageia's Bugzilla at: https://bugs.mageia.org/show_bug.cgi?id=28309 Aurelien O. Mageia Bugsquad Team. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 432586] Dead zone in the top left corner - cannot activate kickoff
https://bugs.kde.org/show_bug.cgi?id=432586 Aurélien COUDERC changed: What|Removed |Added CC||couc...@debian.org --- Comment #1 from Aurélien COUDERC --- In fact it depends on various factors like the scaling and the exact size of the panel. For example I’m using 125% and it’s broken when the panel height is in [30px,40px] but neither below or above. And for 100% it is broken in [44px, 54px]. What seems to happen is that: - the K menu icon is not scaled continuously but by by notches, I guess to use only available bitmap sizes and have it always crisp - when the panel is made taller than the immediately smaller icon size that can fit, padding is added around the icon - the padding is not clickable (neither on the left nor on the top side in fact) -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 422177] New Users kcm doesn't set user avatar as expected
https://bugs.kde.org/show_bug.cgi?id=422177 --- Comment #40 from Aurélien Oudelet (auroud85_fr) --- Following my comment 39, To workaround this, 1) Choose and copy a png avatar like ones found under /usr/share/kpackage/kcms/kcm_users/contents/img/ 2) Copy/paste chosen PNG file as "~/.face" 3) Make a symlink as: $ ln -s ./.face ./.face.icon 4) set ACL like this: $ setfacl -m u:sddm:r ~/.face.icon $ setfacl -m u:sddm:x ~/ This permits sddm to see your avatar as ".face.icon" in your user root home directory. Why makin a symlink? For simply change your avatar by only change the ~/.face file. AccountsService and QML KCM_users are totally broken as is for now. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 425079] Some Plasma and Qt apps on X11 logs warnings in journal (qt.qpa.xcb)
https://bugs.kde.org/show_bug.cgi?id=425079 Aurélien Oudelet (auroud85_fr) changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REPORTED|RESOLVED --- Comment #2 from Aurélien Oudelet (auroud85_fr) --- With WORKAROUND in Comment 1 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 425008] plasmashell : kf5.kio.gui: Failed to register new cgroup
https://bugs.kde.org/show_bug.cgi?id=425008 --- Comment #5 from Aurélien Oudelet (auroud85_fr) --- (In reply to David Edmundson from comment #4) > This was merged. Please reopen if this is still an issue Many thanks, can you give me the link to commit please? Best regards, -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 432080] Each notification is displayed, a warning occurs: "QML QQuickItem: Binding loop detected for property "height""
https://bugs.kde.org/show_bug.cgi?id=432080 --- Comment #2 from Aurélien Oudelet (auroud85_fr) --- (In reply to Nate Graham from comment #1) > You already reported this as Bug 431080. :) > > *** This bug has been marked as a duplicate of bug 431080 *** Oh sorry. Mistake. I was importing this BR in our Bugzilla. ;) Thanks you so much. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 432083] New: /usr/share/kpackage/genericqml/org.kde.systemsettings.sidebar/contents/ui/introPage.qml:109:27: QML IntroIcon (parent or ancestor of QQuickLayoutAttached): Binding l
https://bugs.kde.org/show_bug.cgi?id=432083 Bug ID: 432083 Summary: /usr/share/kpackage/genericqml/org.kde.systemsettings. sidebar/contents/ui/introPage.qml:109:27: QML IntroIcon (parent or ancestor of QQuickLayoutAttached): Binding loop detected for property "minimumHeight" Product: systemsettings Version: 5.20.4 Platform: Mageia RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: aoude...@outlook.com Target Milestone: --- SUMMARY Launching systemsettings5 produces warnings in system logs: STEPS TO REPRODUCE 1. Launch systemsettings5 to main page. 2. See in system logs below warnings. OBSERVED RESULT QQmlEngine::setContextForObject(): Object already has a QQmlContext systemsettings5[28547]: file:///usr/share/kpackage/genericqml/org.kde.systemsettings.sidebar/contents/ui/introPage.qml:109:27: QML IntroIcon (parent or ancestor of QQuickLayoutAttached): Binding loop detected for property "minimumHeight" Above warning repeated 3 times. EXPECTED RESULT No warnings. SOFTWARE/OS VERSIONS Operating System: Mageia 8 KDE Plasma Version: 5.20.4 KDE Frameworks Version: 5.76.0 Qt Version: 5.15.2 Kernel Version: 5.10.9-desktop-3.mga8 OS Type: 64-bit Processors: 4 × Intel® Core™ i5-6600K CPU @ 3.50GHz Memory: 15.6 Gio of RAM Graphics Processor: GeForce GTX 1660 Ti/PCIe/SSE2 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 432082] New: /usr/share/plasma/plasmoids/org.kde.plasma.taskmanager/contents/ui/Task.qml:379: Unable to assign [undefined] to QString
https://bugs.kde.org/show_bug.cgi?id=432082 Bug ID: 432082 Summary: /usr/share/plasma/plasmoids/org.kde.plasma.taskmanager /contents/ui/Task.qml:379: Unable to assign [undefined] to QString Product: plasmashell Version: 5.20.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Task Manager and Icons-Only Task Manager Assignee: h...@kde.org Reporter: aoude...@outlook.com CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY Each time we launch systemsettings5 from a pinned shortcut in Icon-only taskbar, we can see in system log: /usr/share/plasma/plasmoids/org.kde.plasma.taskmanager/contents/ui/Task.qml:379: Unable to assign [undefined] to QString STEPS TO REPRODUCE 1. Pin systemsettings5 in Icons-only taskmanager 2. Click once to launch 3. See in system log above warning repeated 2 times. OBSERVED RESULT plasmashell[2430]: file:///usr/share/plasma/plasmoids/org.kde.plasma.taskmanager/contents/ui/Task.qml:379: Unable to assign [undefined] to QString plasmashell[2430]: file:///usr/share/plasma/plasmoids/org.kde.plasma.taskmanager/contents/ui/Task.qml:379: Unable to assign [undefined] to QString systemd[2224]: Started Configuration du système - Configuration du système. EXPECTED RESULT No warning. SOFTWARE/OS VERSIONS Operating System: Mageia 8 KDE Plasma Version: 5.20.4 KDE Frameworks Version: 5.76.0 Qt Version: 5.15.2 Kernel Version: 5.10.9-desktop-3.mga8 OS Type: 64-bit Processors: 4 × Intel® Core™ i5-6600K CPU @ 3.50GHz Memory: 15.6 Gio of RAM Graphics Processor: GeForce GTX 1660 Ti/PCIe/SSE2 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 432081] New: /usr/share/plasma/plasmoids/org.kde.plasma.taskmanager/contents/ui/main.qml:460: TypeError: Cannot read property 'length' of undefined
https://bugs.kde.org/show_bug.cgi?id=432081 Bug ID: 432081 Summary: /usr/share/plasma/plasmoids/org.kde.plasma.taskmanager /contents/ui/main.qml:460: TypeError: Cannot read property 'length' of undefined Product: plasmashell Version: 5.20.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Task Manager and Icons-Only Task Manager Assignee: h...@kde.org Reporter: aoude...@outlook.com CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY Each time a pinned application is launched, you can see in system log: plasmashell[2430]: file:///usr/share/plasma/plasmoids/org.kde.plasma.taskmanager/contents/ui/main.qml:460: TypeError: Cannot read property 'length' of undefined STEPS TO REPRODUCE 1. Pin an application in icon-only task manager 2. Click to open this pinned application. 3. See in system log such warning: plasmashell[2430]: file:///usr/share/plasma/plasmoids/org.kde.plasma.taskmanager/contents/ui/main.qml:460: TypeError: Cannot read property 'length' of undefined Repeated 2 times. This writes unnecessary warning to system log. EXPECTED RESULT SOFTWARE/OS VERSIONS Operating System: Mageia 8 KDE Plasma Version: 5.20.4 KDE Frameworks Version: 5.76.0 Qt Version: 5.15.2 Kernel Version: 5.10.9-desktop-3.mga8 OS Type: 64-bit Processors: 4 × Intel® Core™ i5-6600K CPU @ 3.50GHz Memory: 15.6 Gio of RAM Graphics Processor: GeForce GTX 1660 Ti/PCIe/SSE2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 432080] Each notification is displayed, a warning occurs: "QML QQuickItem: Binding loop detected for property "height""
https://bugs.kde.org/show_bug.cgi?id=432080 Aurélien Oudelet (auroud85_fr) changed: What|Removed |Added Summary|Each notification is|Each notification is |displayed, a QML|displayed, a warning |QQuickItem: Binding loop|occurs: "QML QQuickItem: |detected for property |Binding loop detected for |"height"|property "height"" -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 432080] New: Each notification is displayed, a QML QQuickItem: Binding loop detected for property "height"
https://bugs.kde.org/show_bug.cgi?id=432080 Bug ID: 432080 Summary: Each notification is displayed, a QML QQuickItem: Binding loop detected for property "height" Product: plasmashell Version: 5.20.4 Platform: Mageia RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Notifications Assignee: k...@privat.broulik.de Reporter: aoude...@outlook.com CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY Each new notification is received, we can see in system log: plasmashell[2430]: file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/NotificationPopup.qml:116:15: QML QQuickItem: Binding loop detected for property "height" each time we get a notification (new mail, new IM message, new device connected) This is annoynning. STEPS TO REPRODUCE 1. Open Konsole and type "journalctl -f" to see there the system log. 2. Have KMail/whatever mail reader set to receive mail. 3. Send to you a mail. 4. See when receiving mail, a notification. 5. See in system log the above warning. OBSERVED RESULT plasmashell[2430]: file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/NotificationPopup.qml:116:15: QML QQuickItem: Binding loop detected for property "height" EXPECTED RESULT No warning. SOFTWARE/OS VERSIONS Operating System: Mageia 8 KDE Plasma Version: 5.20.4 KDE Frameworks Version: 5.76.0 Qt Version: 5.15.2 Kernel Version: 5.10.9-desktop-3.mga8 OS Type: 64-bit Processors: 4 × Intel® Core™ i5-6600K CPU @ 3.50GHz Memory: 15.6 Gio of RAM Graphics Processor: GeForce GTX 1660 Ti/PCIe/SSE2 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 298133] The Properties dialog considers non-files like 'proc' for the size calculation, causing an apparent root directory size of 128 TiB
https://bugs.kde.org/show_bug.cgi?id=298133 --- Comment #6 from Aurélien Oudelet (auroud85_fr) --- Operating System: Mageia 8 KDE Plasma Version: 5.20.4 KDE Frameworks Version: 5.76.0 Qt Version: 5.15.2 Kernel Version: 5.10.8-desktop-2.mga8 OS Type: 64-bit Processors: 4 × Intel® Core™ i5-6600K CPU @ 3.50GHz Memory: 15.6 Gio of RAM Graphics Processor: GeForce GTX 1660 Ti/PCIe/SSE2 Reproduced also. Here is our bugreport: https://bugs.mageia.org/show_bug.cgi?id=28098 And right, duplicate bugs should refer to the oldest. Best regards, For Mageia Bugsquad Team -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 298133] The Properties dialog considers non-files like 'proc' for the size calculation, causing an apparent root directory size of 128 TiB
https://bugs.kde.org/show_bug.cgi?id=298133 Aurélien Oudelet (auroud85_fr) changed: What|Removed |Added CC||ads.bistr...@gmail.com --- Comment #5 from Aurélien Oudelet (auroud85_fr) --- *** Bug 423057 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 423057] Dolphin incorrectly displays the partition size
https://bugs.kde.org/show_bug.cgi?id=423057 Aurélien Oudelet (auroud85_fr) changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #7 from Aurélien Oudelet (auroud85_fr) --- Assigning here. Duplicate. *** This bug has been marked as a duplicate of bug 298133 *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 298133] The Properties dialog considers non-files like 'proc' for the size calculation, causing an apparent root directory size of 128 TiB
https://bugs.kde.org/show_bug.cgi?id=298133 Aurélien Oudelet (auroud85_fr) changed: What|Removed |Added CC||boz...@abv.bg --- Comment #4 from Aurélien Oudelet (auroud85_fr) --- *** Bug 353391 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 353391] wrong calculated size of direcories
https://bugs.kde.org/show_bug.cgi?id=353391 --- Comment #10 from Aurélien Oudelet (auroud85_fr) --- (In reply to Claudius Ellsel from comment #9) > Hm, usually I'd expect the oldest bug to be the original one (in this case > it seems https://bugs.kde.org/show_bug.cgi?id=298133 is the one) and then > all newer bugs to be marked as duplicates of that one. Is there a reason not > to handle it this way here? Right. *** This bug has been marked as a duplicate of bug 298133 *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 298133] The Properties dialog considers non-files like 'proc' for the size calculation, causing an apparent root directory size of 128 TiB
https://bugs.kde.org/show_bug.cgi?id=298133 Aurélien Oudelet (auroud85_fr) changed: What|Removed |Added Resolution|DUPLICATE |--- Status|RESOLVED|REOPENED Keywords||usability Assignee|kdelibs-b...@kde.org|fa...@kde.org Version|4.7 |5.76.0 CC||kdelibs-b...@kde.org Component|general |Properties dialog Product|kdelibs |frameworks-kio Platform|Ubuntu Packages |unspecified -- You are receiving this mail because: You are watching all bug changes.
[kdelibs] [Bug 298133] The Properties dialog considers non-files like 'proc' for the size calculation, causing an apparent root directory size of 128 TiB
https://bugs.kde.org/show_bug.cgi?id=298133 Aurélien Oudelet (auroud85_fr) changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |DUPLICATE CC||aoude...@outlook.com --- Comment #3 from Aurélien Oudelet (auroud85_fr) --- Duplicate. Found this via Google. *** This bug has been marked as a duplicate of bug 423057 *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 423057] Dolphin incorrectly displays the partition size
https://bugs.kde.org/show_bug.cgi?id=423057 Aurélien Oudelet (auroud85_fr) changed: What|Removed |Added CC||aram.grigoryan.mail@gmail.c ||om --- Comment #6 from Aurélien Oudelet (auroud85_fr) --- *** Bug 298133 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 423057] Dolphin incorrectly displays the partition size
https://bugs.kde.org/show_bug.cgi?id=423057 Aurélien Oudelet (auroud85_fr) changed: What|Removed |Added CC||boz...@abv.bg --- Comment #5 from Aurélien Oudelet (auroud85_fr) --- *** Bug 353391 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 353391] wrong calculated size of direcories
https://bugs.kde.org/show_bug.cgi?id=353391 Aurélien Oudelet (auroud85_fr) changed: What|Removed |Added CC||aoude...@outlook.com Resolution|--- |DUPLICATE Status|CONFIRMED |RESOLVED --- Comment #8 from Aurélien Oudelet (auroud85_fr) --- Duplicate, really. Annoying. *** This bug has been marked as a duplicate of bug 423057 *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 423057] Dolphin incorrectly displays the partition size
https://bugs.kde.org/show_bug.cgi?id=423057 Aurélien Oudelet (auroud85_fr) changed: What|Removed |Added CC||aoude...@outlook.com --- Comment #4 from Aurélien Oudelet (auroud85_fr) --- Operating System: Mageia 8 KDE Plasma Version: 5.20.4 KDE Frameworks Version: 5.76.0 Qt Version: 5.15.2 Kernel Version: 5.10.8-desktop-2.mga8 OS Type: 64-bit Processors: 4 × Intel® Core™ i5-6600K CPU @ 3.50GHz Memory: 15.6 Gio of RAM Graphics Processor: GeForce GTX 1660 Ti/PCIe/SSE2 Same. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 422177] New Users kcm doesn't set user avatar as expected
https://bugs.kde.org/show_bug.cgi?id=422177 Aurélien Oudelet (auroud85_fr) changed: What|Removed |Added Version|5.19.90 |5.20.4 CC||aoude...@outlook.com --- Comment #39 from Aurélien Oudelet (auroud85_fr) --- Accountsservice daemon + Plasma 5.20.4 I can reproduce the bug. Operating System: Mageia 8 KDE Plasma Version: 5.20.4 KDE Frameworks Version: 5.76.0 Qt Version: 5.15.2 Kernel Version: 5.10.7-desktop-1.mga8 OS Type: 64-bit Processors: 4 × Intel® Core™ i5-6600K CPU @ 3.50GHz Memory: 15.6 Gio of RAM Graphics Processor: GeForce GTX 1660 Ti/PCIe/SSE2 -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 430857] Errors in Breeze SDDM theme reported by sddm-greeter
https://bugs.kde.org/show_bug.cgi?id=430857 Aurélien Oudelet (auroud85_fr) changed: What|Removed |Added Status|NEEDSINFO |CONFIRMED Resolution|WAITINGFORINFO |--- Ever confirmed|0 |1 --- Comment #4 from Aurélien Oudelet (auroud85_fr) --- (In reply to Aurélien Oudelet (auroud85_fr) from comment #2) > Created attachment 134359 [details] > sddm-greeter output at login time with Breeze theme > > So sorry. > Really attaching a the log output. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 431405] Add a GUI option to turn on Numlock
https://bugs.kde.org/show_bug.cgi?id=431405 --- Comment #1 from Aurélien Oudelet (auroud85_fr) --- Nevermind. I didn't see the "sync settings" option... I do think this should be more explicit than a sync button and a pretty obscure text where numlock is mentioned. In French, it is mentioned at the 5th place between Plasma theme and cursors... -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 431405] Add a GUI option to turn on Numlock
https://bugs.kde.org/show_bug.cgi?id=431405 Aurélien Oudelet (auroud85_fr) changed: What|Removed |Added Platform|Other |Mageia RPMs -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 368063] NumLock not turned on
https://bugs.kde.org/show_bug.cgi?id=368063 Aurélien Oudelet (auroud85_fr) changed: What|Removed |Added CC||pr...@ww.ee --- Comment #26 from Aurélien Oudelet (auroud85_fr) --- *** Bug 414207 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 414207] NumLock on Plasma Startup => "Turn On" has no effect / does not work.
https://bugs.kde.org/show_bug.cgi?id=414207 Aurélien Oudelet (auroud85_fr) changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED CC||aoude...@outlook.com --- Comment #1 from Aurélien Oudelet (auroud85_fr) --- *** This bug has been marked as a duplicate of bug 368063 *** -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 431405] New: Add a GUI option to turn on Numlock
https://bugs.kde.org/show_bug.cgi?id=431405 Bug ID: 431405 Summary: Add a GUI option to turn on Numlock Product: systemsettings Version: 5.20.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_sddm Assignee: k...@davidedmundson.co.uk Reporter: aoude...@outlook.com CC: plasma-b...@kde.org Target Milestone: --- Flags: Usability+ SUMMARY There is no option in sddm-kcm to activate Numlock feature in sddm-kcm. OBSERVED RESULT Actually, users must add "Numlock=On" in /etc/sddm.conf or add a dropping-file 10.Numlock.conf (in /etc/sddm.conf.d/) with this content: [General] Numlock=On EXPECTED RESULT A toggle in sddm-KCM to activate it. Operating System: Mageia 8 KDE Plasma Version: 5.20.4 KDE Frameworks Version: 5.76.0 Qt Version: 5.15.2 Kernel Version: 5.10.6-desktop-1.mga8 OS Type: 64-bit Processors: 4 × Intel® Core™ i5-6600K CPU @ 3.50GHz Memory: 15.6 Gio of RAM Graphics Processor: GeForce GTX 1660 Ti/PCIe/SSE2 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 425079] Some Plasma and Qt apps on X11 logs warnings in journal (qt.qpa.xcb)
https://bugs.kde.org/show_bug.cgi?id=425079 --- Comment #1 from Aurélien Oudelet (auroud85_fr) --- Such logging errors can be silenced by adding a file like this in /etc/xdg/QtProject/qtlogging.ini [Rules] qt.qpa.xcb.warning=false qt.qml.connections.warning=false -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 430860] With Breeze SDDM theme, typing a wrong password is not told to user.
https://bugs.kde.org/show_bug.cgi?id=430860 Aurélien Oudelet (auroud85_fr) changed: What|Removed |Added Ever confirmed|0 |1 Status|NEEDSINFO |CONFIRMED Resolution|WAITINGFORINFO |--- --- Comment #3 from Aurélien Oudelet (auroud85_fr) --- Here are videos of the behaviour: 1) With Users list: https://youtu.be/u0EI9FRIG1c 2) With no user list, user must enter his Unix name: https://youtu.be/BDrQ2wbpEog -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 430860] With Breeze SDDM theme, typing a wrong password is not told to user.
https://bugs.kde.org/show_bug.cgi?id=430860 --- Comment #2 from Aurélien Oudelet (auroud85_fr) --- (In reply to Nate Graham from comment #1) > Works for me in English, and I see in the code that there's supposed to be a > message there. Does it happen again for you if you temporarily switch the > language to English? In facts, if SDDM displays a list of users, even in English locale or in French, there is no wrong password feedback. BUT if user must enter his user name and his password, the "Failed login" message is displayed. I upload to my youtube account a video of this behaviour. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 430584] Strange kernel outputs when ejecting a usb key
https://bugs.kde.org/show_bug.cgi?id=430584 Aurélien Oudelet (auroud85_fr) changed: What|Removed |Added Resolution|WAITINGFORINFO |UPSTREAM Status|NEEDSINFO |RESOLVED --- Comment #5 from Aurélien Oudelet (auroud85_fr) --- (In reply to David Edmundson from comment #4) > >The issue is really when clicking on Plasma UI, > > What do you think the issue our side is? No, after many strace, the issue is in kernel 5.10, not in Plasma API. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 431080] New: QML error Binding Loop detected with org.kde.plasma.notifications
https://bugs.kde.org/show_bug.cgi?id=431080 Bug ID: 431080 Summary: QML error Binding Loop detected with org.kde.plasma.notifications Product: plasmashell Version: 5.20.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Notifications Assignee: k...@privat.broulik.de Reporter: aoude...@outlook.com CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY Each time a notification appears in systray (from receiving a mail in KMail or other application that generates one), in system journal we can see: janv. 02 18:16:13 mageia.local plasmashell[2438]: file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/SelectableLabel.qml:59:9: QML QQuickTextEdit: Binding loop detected for property "width" janv. 02 18:16:13 mageia.local plasmashell[2438]: file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/NotificationPopup.qml:116:15: QML QQuickItem: Binding loop detected for property "height" janv. 02 18:16:13 mageia.local plasmashell[2438]: file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/SelectableLabel.qml:59:9: QML QQuickTextEdit: Binding loop detected for property "width" janv. 02 18:16:13 mageia.local plasmashell[2438]: file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/NotificationPopup.qml:116:15: QML QQuickItem: Binding loop detected for property "height" janv. 02 18:21:27 mageia.local plasmashell[2438]: file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/NotificationPopup.qml:116:15: QML QQuickItem: Binding loop detected for property "height" janv. 02 18:27:17 mageia.local plasmashell[2438]: file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/NotificationPopup.qml:116:15: QML QQuickItem: Binding loop detected for property "height" janv. 02 18:28:07 mageia.local plasmashell[2438]: file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/NotificationPopup.qml:116:15: QML QQuickItem: Binding loop detected for property "height" janv. 02 18:33:51 mageia.local plasmashell[2438]: file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/NotificationPopup.qml:116:15: QML QQuickItem: Binding loop detected for property "height" janv. 02 18:34:51 mageia.local plasmashell[2438]: file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/NotificationPopup.qml:116:15: QML QQuickItem: Binding loop detected for property "height" janv. 02 18:39:05 mageia.local plasmashell[2438]: file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/CompactRepresentation.qml:146: ReferenceError: jobProgressItem is not defined janv. 02 18:39:05 mageia.local plasmashell[2438]: file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/CompactRepresentation.qml:145:13: QML PropertyChanges: Cannot assign to non-existent property "visible" janv. 02 18:39:06 mageia.local plasmashell[2438]: file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/NotificationPopup.qml:116:15: QML QQuickItem: Binding loop detected for property "height" janv. 02 18:43:17 mageia.local plasmashell[2438]: file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/NotificationPopup.qml:116:15: QML QQuickItem: Binding loop detected for property "height" janv. 02 18:45:22 mageia.local plasmashell[2438]: file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/NotificationPopup.qml:116:15: QML QQuickItem: Binding loop detected for property "height" janv. 02 18:45:54 mageia.local plasmashell[2438]: file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/NotificationPopup.qml:116:15: QML QQuickItem: Binding loop detected for property "height" janv. 02 18:56:47 mageia.local plasmashell[2438]: file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/NotificationPopup.qml:116:15: QML QQuickItem: Binding loop detected for property "height" janv. 02 18:59:08 mageia.local plasmashell[2438]: file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/NotificationPopup.qml:116:15: QML QQuickItem: Binding loop detected for property "height" janv. 02 19:00:48 mageia.local plasmashell[2438]: file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/NotificationPopup.qml:116:15: QML QQuickItem: Binding loop detected for property "height" janv. 02 19:03:26 mageia.local plasmashell[2438]: file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/NotificationPopup.qml:116:15: QML QQuickItem: Binding loop detected for property "height" janv. 02 19:03:48 mageia.local plasmashell[2438]: file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/NotificationPopup.qml:116:15: QML QQuickItem: Binding loop d
[plasmashell] [Bug 430584] Strange kernel outputs when ejecting a usb key
https://bugs.kde.org/show_bug.cgi?id=430584 Aurélien Oudelet (auroud85_fr) changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|UPSTREAM|--- Ever confirmed|0 |1 --- Comment #3 from Aurélien Oudelet (auroud85_fr) --- No, after some try, https://github.com/storaged-project/udisks/issues/827 The issue is really when clicking on Plasma UI, when I want to remove the device, when clicking on "Remove device safely". -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 401547] kdeconnect spams journald with debug-like messages
https://bugs.kde.org/show_bug.cgi?id=401547 Aurélien Oudelet (auroud85_fr) changed: What|Removed |Added Platform|Neon Packages |Mageia RPMs Status|CONFIRMED |RESOLVED Resolution|--- |WORKSFORME Version|1.3.3 |1.10 Component|common |plasmoid --- Comment #3 from Aurélien Oudelet (auroud85_fr) --- I never see this while using kdeconnect. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 429196] kf.plasma.core: findInCache with a lastModified timestamp of 0 is deprecated message makes system lags.
https://bugs.kde.org/show_bug.cgi?id=429196 Aurélien Oudelet (auroud85_fr) changed: What|Removed |Added Version|5.20.3 |5.20.4 Platform|Other |Mageia RPMs -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 429196] kf.plasma.core: findInCache with a lastModified timestamp of 0 is deprecated message makes system lags.
https://bugs.kde.org/show_bug.cgi?id=429196 --- Comment #1 from Aurélien Oudelet (auroud85_fr) --- In facts, removing KDE/Plasma related contents inside ~/.cache, ~/.config, ~/.kde resolve the issue here. I really don't know where exactly as I used great means... Leaving this opened, as long as our Mageia users don't have migrated from Mageia 7 (Plasma 5.15) to Mageia 8 (Plasma 5.20.4). -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 430857] Errors in Breeze SDDM theme reported by sddm-greeter
https://bugs.kde.org/show_bug.cgi?id=430857 --- Comment #2 from Aurélien Oudelet (auroud85_fr) --- Created attachment 134359 --> https://bugs.kde.org/attachment.cgi?id=134359&action=edit sddm-greeter output at login time with Breeze theme So sorry. Really attaching a the log output. -- You are receiving this mail because: You are watching all bug changes.
