[frameworks-kio] [Bug 423031] [Wayland] Modifier keys to move (shift), copy (ctrl) and create a link (ctrl+shift) don't work if pressed after I start to drag the file/folder
https://bugs.kde.org/show_bug.cgi?id=423031 --- Comment #25 from Max --- > It does seem like kde people have given feedback, and its mostly qt we are > waiting on. ... I got confused, David Edmundson has not reviewed it yet, maybe it has fallen between the cracks.. Maybe this bug should be reopened since it needs action from kde people still.. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kiconthemes] [Bug 484639] Fallback to Breeze ignored by KIconLoader because of wrong global initialization order
https://bugs.kde.org/show_bug.cgi?id=484639 Max changed: What|Removed |Added CC||thesource...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 484216] Plasmoid popups close immediately after open when using non-default keyboard layout switching policies
https://bugs.kde.org/show_bug.cgi?id=484216 --- Comment #15 from Max --- I just noticed something: when this problem happens (i.e. I click on a tray icon and popup disappears), keyboard layout tray icon also plays animation like it was also clicked though it was not, layout is not changed though. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 484216] Plasmoid popups close immediately after open
https://bugs.kde.org/show_bug.cgi?id=484216 --- Comment #12 from Max --- I can partially confirm that it seems to be somehow connected to policy, but for me it's inconsistent. Sometimes after I switch policy (to application or window) tray popups start to work properly on any layout but other time this bug manifests. Maybe something happens during switching/initialization of a policy? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 485771] Desktop shortcuts disappear after icon update
https://bugs.kde.org/show_bug.cgi?id=485771 Max changed: What|Removed |Added CC||thesource...@gmail.com --- Comment #3 from Max --- For me this happens on any edit of the shortcut not only icon change. The safe method of editing for now is to do it from dolphin (open desktop folder). Operating System: Fedora Linux 40 KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 Kernel Version: 6.8.7-300.fc40.x86_64 (64-bit) Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 484216] Plasmoid popups close immediately after open
https://bugs.kde.org/show_bug.cgi?id=484216 Max changed: What|Removed |Added CC||thesource...@gmail.com --- Comment #7 from Max --- I confirm the same is happening for me. If non-english keyboard layout is selected then I can not open any popup from any tray icon - it's just closed right away. Operating System: Fedora Linux 40 KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 Kernel Version: 6.8.7-300.fc40.x86_64 (64-bit) Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 485440] Data loss error dialog when "Align B and C for 3 input files" preference is checked
https://bugs.kde.org/show_bug.cgi?id=485440 --- Comment #3 from Max Vohlken --- Created attachment 168424 --> https://bugs.kde.org/attachment.cgi?id=168424=edit screen capture of the error dialog -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 485440] Data loss error dialog when "Align B and C for 3 input files" preference is checked
https://bugs.kde.org/show_bug.cgi?id=485440 --- Comment #2 from Max Vohlken --- Created attachment 168423 --> https://bugs.kde.org/attachment.cgi?id=168423=edit input file c -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 485440] Data loss error dialog when "Align B and C for 3 input files" preference is checked
https://bugs.kde.org/show_bug.cgi?id=485440 --- Comment #1 from Max Vohlken --- Created attachment 168422 --> https://bugs.kde.org/attachment.cgi?id=168422=edit input file b -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 485440] New: Data loss error dialog when "Align B and C for 3 input files" preference is checked
https://bugs.kde.org/show_bug.cgi?id=485440 Bug ID: 485440 Summary: Data loss error dialog when "Align B and C for 3 input files" preference is checked Classification: Applications Product: kdiff3 Version: 1.8.4 Platform: RedHat Enterprise Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: application Assignee: reeves...@gmail.com Reporter: max.vohl...@hcl.com Target Milestone: --- Created attachment 168421 --> https://bugs.kde.org/attachment.cgi?id=168421=edit input file a SUMMARY Data loss error dialog is displayed when comparing 3 files and the "Align B and C for 3 input files" preference is checked. STEPS TO REPRODUCE 1. download the 3 input file that are attached. These file will demonstrate the problem. 2. open kdiff3, go into the kdiff3 settings and check the "Align B and C for 3 input files" option in the Diff Settings tab 3. diff the 3 files by running: kdiff3 a b c OBSERVED RESULT a Severe Internal Error dialog will pop-up saying: Data loss error: If it is reproducible please contact the author." My removing line 3 from file c the issue will go away. EXPECTED RESULT I expected kdiff3 to open normally and display the differences between the 3 files SOFTWARE/OS VERSIONS Linux/KDE Plasma: Red Hat Enterprise Linux release 8.9 (Ootpa) KDE Plasma Version: KDE Frameworks Version: 5.96.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION $ dnf info kdiff3 Installed Packages Name : kdiff3 Version : 1.8.4 Release : 1.el8 Architecture : x86_64 Size : 5.8 M Source : kdiff3-1.8.4-1.el8.src.rpm Repository : @System >From repo: epel Summary : Compare + merge 2 or 3 files or directories URL : https://github.com/KDE/kdiff3 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 482409] Unclear how to add printer / button disabled
https://bugs.kde.org/show_bug.cgi?id=482409 Max Harmathy changed: What|Removed |Added CC||harma...@secure.mailbox.org -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 107302] Per-screen virtual desktops
https://bugs.kde.org/show_bug.cgi?id=107302 Max Harmathy changed: What|Removed |Added CC||max.harma...@web.de -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 482817] qdbus org.kde.yakuake /yakuake/sessions org.kde.yakuake.activeSessionId return not correct ID
https://bugs.kde.org/show_bug.cgi?id=482817 --- Comment #3 from Max --- I need to change the profile on the hot key. I get ID: id = $ (qdbus org.kde.yakuake / yakuake / sessions org.kde.yakuake.activeSessionId) The numbering is 0 1 2 3 4 5 ... Then, use it to change the profile: qdbus org.kde.yakuake /Sessions/$id org.kde.konsole.Session.setProfile "Profile 1" The fact is that here /yakuake/sessions ID will be incremental after closing the tabs. And here /Sessions numbers go without considering closed tabs (always 1 2 3 4 5 ...). Until the tabs close, everything works. When several tabs close (those on the right), then here /yakuake/sessions the numbering becomes so 0 4 5 8 ... And it becomes impossible, use of this data here /Sessions/$id -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 482817] qdbus org.kde.yakuake /yakuake/sessions org.kde.yakuake.activeSessionId return not correct ID
https://bugs.kde.org/show_bug.cgi?id=482817 --- Comment #1 from Max --- I need for this id=$(qdbus org.kde.yakuake /yakuake/sessions org.kde.yakuake.activeSessionId) qdbus org.kde.yakuake /Sessions/$id org.kde.konsole.Session.setProfile "Profile 1" -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 482817] New: qdbus org.kde.yakuake /yakuake/sessions org.kde.yakuake.activeSessionId return not correct ID
https://bugs.kde.org/show_bug.cgi?id=482817 Bug ID: 482817 Summary: qdbus org.kde.yakuake /yakuake/sessions org.kde.yakuake.activeSessionId return not correct ID Classification: Applications Product: yakuake Version: 24.02.0 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: h...@kde.org Reporter: max.yego...@mail.ru Target Milestone: --- Create multiple tabs 1 2 3 4 Close the last three so that only the first remains 1 Create more tabs 1 2 3 Now, in tabs 2 and 3, the method begins to return an incorrect ID. If you continue to close tabs except the first and create new ones, then the ID will increase. qdbus org.kde.yakuake /yakuake/sessions org.kde.yakuake.activeSessionId 5 -- You are receiving this mail because: You are watching all bug changes.
[KDE Itinerary] [Bug 481623] New: About page does not show up on Android in landscape mode
https://bugs.kde.org/show_bug.cgi?id=481623 Bug ID: 481623 Summary: About page does not show up on Android in landscape mode Classification: Applications Product: KDE Itinerary Version: unspecified Platform: Android OS: Android 13.x Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: vkra...@kde.org Reporter: max.buchh...@gmx.de Target Milestone: --- SUMMARY When trying to open the KDE Itinerary About page on my phone in landscape mode, the page does not show up. STEPS TO REPRODUCE 1. Open KDE Itinerary 2. Turn your phone into landscape mode 3. Open the menu 4. Click on About OBSERVED RESULT Nothing shows up EXPECTED RESULT About page shows up SOFTWARE/OS VERSIONS KDE-Itinerary: 24.04.70 KDE Frameworks 6.0.0 Qt 6.6.1 ADDITIONAL INFORMATION I have KDE Itinerary installed from the Release repository in F-Droid -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 481208] New: The console closed with an error
https://bugs.kde.org/show_bug.cgi?id=481208 Bug ID: 481208 Summary: The console closed with an error Classification: Applications Product: konsole Version: 23.08.4 Platform: Gentoo Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: macon...@rambler.ru Target Milestone: --- Application: konsole (23.08.4) Qt Version: 5.15.12 Frameworks Version: 5.113.0 Operating System: Linux 5.15.145-calculate x86_64 Windowing System: X11 Distribution: Calculate Linux Desktop 23 KDE DrKonqi: 5.27.10 [KCrashBackend] -- Information about the crash: The mc was running in the console window and an error occurred when closing the window. The second tab was also opened and when closing, I selected "close all". The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Konsole (konsole), signal: Segmentation fault [KCrash Handler] #4 0x7f696889323a in ?? () from /usr/lib64/libkonsoleprivate.so.1 #5 0x7f69688936c5 in ?? () from /usr/lib64/libkonsoleprivate.so.1 #6 0x7f696888f994 in Konsole::Screen::resizeImage(int, int) () from /usr/lib64/libkonsoleprivate.so.1 #7 0x7f696887b807 in Konsole::Emulation::setImageSize(int, int) () from /usr/lib64/libkonsoleprivate.so.1 #8 0x7f69676087e5 in ?? () from /usr/lib64/libQt5Core.so.5 #9 0x7f6968869d78 in Konsole::TerminalDisplay::changedContentSizeSignal(int, int) () from /usr/lib64/libkonsoleprivate.so.1 #10 0x7f69688ef1cd in Konsole::TerminalDisplay::updateImageSize() () from /usr/lib64/libkonsoleprivate.so.1 #11 0x7f69688f6e78 in Konsole::TerminalDisplay::resizeEvent(QResizeEvent*) () from /usr/lib64/libkonsoleprivate.so.1 #12 0x7f696812236a in QWidget::event(QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #13 0x7f69680dfd6e in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #14 0x7f69675d6bb8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib64/libQt5Core.so.5 #15 0x7f6968118ae8 in QWidgetPrivate::setGeometry_sys(int, int, int, int, bool) () from /usr/lib64/libQt5Widgets.so.5 #16 0x7f6968119a5d in QWidget::setGeometry(QRect const&) () from /usr/lib64/libQt5Widgets.so.5 #17 0x7f6968291a06 in ?? () from /usr/lib64/libQt5Widgets.so.5 #18 0x7f6968294116 in ?? () from /usr/lib64/libQt5Widgets.so.5 #19 0x7f696812236a in QWidget::event(QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #20 0x7f69681cd3de in QFrame::event(QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #21 0x7f69680dfd6e in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #22 0x7f69675d6bb8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib64/libQt5Core.so.5 #23 0x7f6968118ae8 in QWidgetPrivate::setGeometry_sys(int, int, int, int, bool) () from /usr/lib64/libQt5Widgets.so.5 #24 0x7f6968119a5d in QWidget::setGeometry(QRect const&) () from /usr/lib64/libQt5Widgets.so.5 #25 0x7f69680ff508 in QLayoutPrivate::doResize() () from /usr/lib64/libQt5Widgets.so.5 #26 0x7f69680dfd53 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #27 0x7f69675d6bb8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib64/libQt5Core.so.5 #28 0x7f6968118ae8 in QWidgetPrivate::setGeometry_sys(int, int, int, int, bool) () from /usr/lib64/libQt5Widgets.so.5 #29 0x7f6968119a5d in QWidget::setGeometry(QRect const&) () from /usr/lib64/libQt5Widgets.so.5 #30 0x7f69682b9752 in QTabWidget::setUpLayout(bool) () from /usr/lib64/libQt5Widgets.so.5 #31 0x7f69682bae16 in ?? () from /usr/lib64/libQt5Widgets.so.5 #32 0x7f69676088ec in ?? () from /usr/lib64/libQt5Core.so.5 #33 0x7f6968295fa1 in QStackedWidget::widgetRemoved(int) () from /usr/lib64/libQt5Widgets.so.5 #34 0x7f69676088ec in ?? () from /usr/lib64/libQt5Core.so.5 #35 0x7f6968105a4e in QStackedLayout::widgetRemoved(int) () from /usr/lib64/libQt5Widgets.so.5 #36 0x7f69681066a6 in QStackedLayout::takeAt(int) () from /usr/lib64/libQt5Widgets.so.5 #37 0x7f696810107e in QLayout::removeWidget(QWidget*) () from /usr/lib64/libQt5Widgets.so.5 #38 0x7f696894561d in Konsole::TabbedViewContainer::viewDestroyed(QObject*) () from /usr/lib64/libkonsoleprivate.so.1 #39 0x7f69676087e5 in ?? () from /usr/lib64/libQt5Core.so.5 #40 0x7f69676028cf in QObject::destroyed(QObject*) () from /usr/lib64/libQt5Core.so.5 #41 0x7f696811d99b in QWidget::~QWidget() () from /usr/lib64/libQt5Widgets.so.5 #42 0x7f6968872d91 in ?? () from /usr/lib64/libkonsoleprivate.so.1 #43 0x7f69676008d5 in QObject::event(QEvent*) () from /usr/lib64/libQt5Core.so.5 #44 0x7f69681cd3de in QFrame::event(QEvent*) () from
[skrooge] [Bug 481005] New: Skrooge failed import files (STA, MT940
https://bugs.kde.org/show_bug.cgi?id=481005 Bug ID: 481005 Summary: Skrooge failed import files (STA, MT940 Classification: Applications Product: skrooge Version: unspecified Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: steph...@mankowski.fr Reporter: mad...@teenspirit.nl Target Milestone: --- SUMMARY When I import a MT940 file, or renamed to STA, I get an error "ERR-5 Import failed" and ERR-1 import is not implemented yet. In Dutch: [ERR-5]: Importeren van bestand met naam 'file:///home/max/documents/bank_202310_MT940231211121025.STA' is mislukt [ERR-1]: Deze importeermodus STA is nog niet geïmplementeerd I have this issue a few months. I expected to be resolved automatically. That happens sometimes if an error is made with a release of an application. But it didn't resolve itself. So what to do? *** 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. File | Import | open file window opens 2. Filter is on All supported formats, but nothing shows. So replace with "*" 3. Click on a MT940 file and error occurs. Happens with any file. OBSERVED RESULT No import. So I have a problem keeping my administration EXPECTED RESULT Import of banking information SOFTWARE/OS VERSIONS Skrooge version 2.31.0 on openSUSE Tumbleweed with latest updates Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 480882] Crash after delete notification about delete default panel
https://bugs.kde.org/show_bug.cgi?id=480882 --- Comment #1 from Max --- Created attachment 165558 --> https://bugs.kde.org/attachment.cgi?id=165558=edit New crash information added by DrKonqi DrKonqi auto-attaching complete backtrace. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 480882] New: Crash after delete notification about delete default panel
https://bugs.kde.org/show_bug.cgi?id=480882 Bug ID: 480882 Summary: Crash after delete notification about delete default panel Classification: Plasma Product: plasmashell Version: 5.27.5 Platform: Debian stable OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: merva.2...@gmail.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 Application: plasmashell (5.27.5) Qt Version: 5.15.8 Frameworks Version: 5.103.0 Operating System: Linux 6.1.0-17-amd64 x86_64 Windowing System: X11 Distribution: Debian GNU/Linux 12 (bookworm) DrKonqi: 5.27.5 [CoredumpBackend] -- Information about the crash: After I removed the panel and after I closed the notification that appeared that the panel had been deleted, a crash occurred The crash can be reproduced every time. -- Backtrace (Reduced): #3 0x7efcdf877c86 in QtQml::qmlExecuteDeferred(QObject*) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #4 0x7efcdfd49059 in QQuickTransition::prepare(QList&, QList&, QQuickTransitionManager*, QObject*) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #5 0x7efcdfd3e997 in QQuickTransitionManager::transition(QList const&, QQuickTransition*, QObject*) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #6 0x7efcde0dd50d in QObject::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7efcdef62fae in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 The reporter indicates this bug may be a duplicate of or related to bug 477559, bug 480164. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 479170] valgrind output
https://bugs.kde.org/show_bug.cgi?id=479170 --- Comment #4 from Tom Max --- On Fri, Feb 2, 2024 at 5:09 PM Arjen Hiemstra wrote: > > https://bugs.kde.org/show_bug.cgi?id=479170 > > --- Comment #3 from Arjen Hiemstra --- > If it's in Qt and already tracked upstream, there isn't much to do here. that Qt bug says the fix is in enabling a compilation flag, it seems Neon is missing it. I reported it here: https://bugs.kde.org/show_bug.cgi?id=479203 > Did you find anything system monitor specific? No, I have a discussion still pending about kconfig, but I have lost 2 times my NEON VM during updates, and that stopped my tests. I'll made my third VM soon -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 443071] Show package changelog
https://bugs.kde.org/show_bug.cgi?id=443071 Max Staff changed: What|Removed |Added CC||bright.joy7...@mstaff.dev -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 479203] New: rebuild QT with -qt-pcre flag
https://bugs.kde.org/show_bug.cgi?id=479203 Bug ID: 479203 Summary: rebuild QT with -qt-pcre flag Classification: KDE Neon Product: neon Version: unspecified Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Packages Unstable Edition Assignee: neon-b...@kde.org Reporter: tmass...@gmail.com CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- SUMMARY *** valgrind reports some memory error running applications of neon unstable. the fix (is not already applied) is well detailed here: https://bugreports.qt.io/browse/QTBUG-116866 *** STEPS TO REPRODUCE 1. run "valgring plasma-systemmonitor" 2. read the output OBSERVED RESULT ==114405== Conditional jump or move depends on uninitialised value(s) ==114405==at 0x486AC39: ??? ==114405==by 0x7A648C7: ??? ==114405== EXPECTED RESULT no valgrind output SOFTWARE/OS VERSIONS KDE Plasma Versione 5.91.90 KDE Frameworks Version: 5.248.0 Qt Version: 6.6.1 Kernel version: 6.2.0-39-generic (64-bit) Graphic Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 479170] valgrind output
https://bugs.kde.org/show_bug.cgi?id=479170 --- Comment #2 from Tom Max --- reproduced also with qt6 on neon unstable. Looking for this bug in Qt's bug system, I found it: https://bugreports.qt.io/browse/QTBUG-116866 but the problem seems to be in NEON, a missing flag building Qt with PCRE. I think I should create a separate bug report for each issue, correct? -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 479170] valgrind output
https://bugs.kde.org/show_bug.cgi?id=479170
--- Comment #1 from Tom Max ---
Probably found from where these strange valgrind notes are coming from, qt
regular expression:
==114405== Conditional jump or move depends on uninitialised value(s)
==114405==at 0x486AC39: ???
==114405==by 0x7A648C7: ???
==114405==
file PageDataObject.cpp, function
QVariant converted(const QVariant , QMetaType::Type type),
this line:
auto match = boolTrueExpression.match(variant.toString());
I have reproduced the problem with this example:
8<===
#include
#include
int main(int argc, char *argv[])
{
const QString qs("section-0");
const QVariant variant (qs);
static const QRegularExpression
boolTrueExpression(QStringLiteral("^[yY][eE][sS]|[tT][rR][uU][eE]$"));
qDebug() << __FILE__ << __LINE__;
auto match = boolTrueExpression.match(variant.toString());
qDebug() << __FILE__ << __LINE__;
if (!match.hasMatch()) {
qDebug() << __FILE__ << __LINE__;
return 0;//QVariant{};
}
}
8<===
running it I can see:
tom1@tom-neon:~/projects/test_regexp/build$ valgrind ./test_regexp
==114405== Memcheck, a memory error detector
==114405== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
==114405== Using Valgrind-3.18.1 and LibVEX; rerun with -h for copyright info
==114405== Command: ./test_regexp
==114405==
/home/tom1/projects/test_regexp/src/main.cpp 10
==114405== Conditional jump or move depends on uninitialised value(s)
==114405==at 0x486AC39: ???
==114405==by 0x7A648C7: ???
==114405==
/home/tom1/projects/test_regexp/src/main.cpp 12
/home/tom1/projects/test_regexp/src/main.cpp 14
==114
NB: I have built the example with qt5, as Kdevelop is not configured for qt6
(or I'm unable to use it) on the neon machine.
Can somebody test this code with qt6 or pass me a link to configure KDevelop
for qt6?
thanks
--
You are receiving this mail because:
You are watching all bug changes.
[plasma-systemmonitor] [Bug 479170] New: valgrind output
https://bugs.kde.org/show_bug.cgi?id=479170 Bug ID: 479170 Summary: valgrind output Classification: Applications Product: plasma-systemmonitor Version: unspecified Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: tmass...@gmail.com CC: ahiems...@heimr.nl, plasma-b...@kde.org Target Milestone: --- Created attachment 164548 --> https://bugs.kde.org/attachment.cgi?id=164548=edit full valgrind output SUMMARY running valgrind on plasma-systemmonitor a lot of trouble are showed. this bug report is to keep trace of them STEPS TO REPRODUCE 1. build plasma-systemmonitor on your machine 2. create this script: $ cat run.sh #!/bin/bash LD_PRELOAD="/home/tom1/kde/build/libksysguard/bin/libFacesPlugin.so /home/tom1/kde/build/libksysguard/bin/libKSysGuardSensorFaces.so /home/tom1/kde/build/kconfig/bin/libKF6ConfigCore.so.6 " valgrind /home/tom1/kde/build/plasma-systemmonitor/bin/plasma-systemmonitor 3. chmod +x && ./run OBSERVED RESULT a lot of issue EXPECTED RESULT no issue SOFTWARE/OS VERSIONS Linux/KDE Plasma neon unstable developer 25-12-2023 KDE Plasma Version 5.91.90 KDE Frameworks Version: 5.248.0 Qt Version: 6.6.1 Kernel version: 6.2.0-39-generic (64-bit) Graphic Platform: Wayland ADDITIONAL INFORMATION full valgring output attached, cannot stay here tom1@tom-neon:~/kde$ ./run.sh ==24605== Memcheck, a memory error detector ==24605== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al. ==24605== Using Valgrind-3.18.1 and LibVEX; rerun with -h for copyright info ==24605== Command: /home/tom1/kde/build/plasma-systemmonitor/bin/plasma-systemmonitor ==24605== *** I suppose Ubuntu ldd problem, not always present ==24605== Invalid read of size 8 ==24605==at 0x40286A8: strncmp (strcmp.S:172) ==24605==by 0x400668D: is_dst (dl-load.c:216) ==24605==by 0x400810E: _dl_dst_count (dl-load.c:253) ==24605==by 0x400810E: expand_dynamic_string_token (dl-load.c:395) ==24605==by 0x40082B7: fillin_rpath.isra.0 (dl-load.c:483) ==24605==by 0x4008602: decompose_rpath (dl-load.c:654) ==24605==by 0x400ABF5: cache_rpath (dl-load.c:696) ==24605==by 0x400ABF5: cache_rpath (dl-load.c:677) ==24605==by 0x400ABF5: _dl_map_object (dl-load.c:2165) ==24605==by 0x4003494: openaux (dl-deps.c:64) ==24605==by 0x6B458A7: _dl_catch_exception (dl-error-skeleton.c:208) ==24605==by 0x4003C7B: _dl_map_object_deps (dl-deps.c:248) ==24605==by 0x400EA0E: dl_open_worker_begin (dl-open.c:592) ==24605==by 0x6B458A7: _dl_catch_exception (dl-error-skeleton.c:208) ==24605==by 0x400DF99: dl_open_worker (dl-open.c:782) ==24605== Address 0xcf5ae19 is 9 bytes inside a block of size 15 alloc'd ==24605==at 0x4848899: malloc (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so) ==24605==by 0x40271DF: malloc (rtld-malloc.h:56) ==24605==by 0x40271DF: strdup (strdup.c:42) ==24605==by 0x4008594: decompose_rpath (dl-load.c:629) ==24605==by 0x400ABF5: cache_rpath (dl-load.c:696) ==24605==by 0x400ABF5: cache_rpath (dl-load.c:677) ==24605==by 0x400ABF5: _dl_map_object (dl-load.c:2165) ==24605==by 0x4003494: openaux (dl-deps.c:64) ==24605==by 0x6B458A7: _dl_catch_exception (dl-error-skeleton.c:208) ==24605==by 0x4003C7B: _dl_map_object_deps (dl-deps.c:248) ==24605==by 0x400EA0E: dl_open_worker_begin (dl-open.c:592) ==24605==by 0x6B458A7: _dl_catch_exception (dl-error-skeleton.c:208) ==24605==by 0x400DF99: dl_open_worker (dl-open.c:782) ==24605==by 0x6B458A7: _dl_catch_exception (dl-error-skeleton.c:208) ==24605==by 0x400E34D: _dl_open (dl-open.c:883) ==24605== ==24605== Invalid read of size 8 ==24605==at 0x40286A8: strncmp (strcmp.S:172) ==24605==by 0x400668D: is_dst (dl-load.c:216) ==24605==by 0x4007F79: _dl_dst_substitute (dl-load.c:295) ==24605==by 0x40082B7: fillin_rpath.isra.0 (dl-load.c:483) ==24605==by 0x4008602: decompose_rpath (dl-load.c:654) ==24605==by 0x400ABF5: cache_rpath (dl-load.c:696) ==24605==by 0x400ABF5: cache_rpath (dl-load.c:677) ==24605==by 0x400ABF5: _dl_map_object (dl-load.c:2165) ==24605==by 0x4003494: openaux (dl-deps.c:64) ==24605==by 0x6B458A7: _dl_catch_exception (dl-error-skeleton.c:208) ==24605==by 0x4003C7B: _dl_map_object_deps (dl-deps.c:248) ==24605==by 0x400EA0E: dl_open_worker_begin (dl-open.c:592) ==24605==by 0x6B458A7: _dl_catch_exception (dl-error-skeleton.c:208) ==24605==by 0x400DF99: dl_open_worker (dl-open.c:782) ==24605== Address 0xcf5ae19 is 9 bytes inside a block of size 15 alloc'd ==24605==at 0x4848899: malloc (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so) ==24605==by 0x40271DF: malloc (rtld-malloc.h:56) ==24605==by 0x40271DF: strdup (strdup.c:42) ==24605==
[plasma-systemmonitor] [Bug 479044] Impossible to sort columns in system monitor
https://bugs.kde.org/show_bug.cgi?id=479044 Tom Max changed: What|Removed |Added CC||tmass...@gmail.com --- Comment #1 from Tom Max --- the problems seems related to this warning: qrc:/qt/qml/org/kde/ksysguard/table/BaseTableView.qml:55:5: QML TableViewHeader: Cannot change current index: TableView.selectionModel.model is not compatible with the model displayed in the view when a different columm is clicked, QML reject the event as the data model is different from the expected model Looking at the cpp code each column has a model which can be different from model used from other column, so probably only the CPU column has the expected data model and for that it works. Probably the QML side needs a review in order to accept each model, can somebody confirm ? -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 477340] Latte Dock doesn't dodge application launcher (KDE Wayland)
https://bugs.kde.org/show_bug.cgi?id=477340 Max changed: What|Removed |Added Assignee|mvourla...@gmail.com|kn...@t-online.de -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 477340] Latte Dock doesn't dodge application launcher (KDE Wayland)
https://bugs.kde.org/show_bug.cgi?id=477340 Max changed: What|Removed |Added CC||kn...@t-online.de -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 466124] kmail preview pane empty on wayland nvidia
https://bugs.kde.org/show_bug.cgi?id=466124 Max Schwarz changed: What|Removed |Added CC||max.schw...@online.de -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 470759] Crash in KWin::CustomTile::setRelativeGeometry using custom script
https://bugs.kde.org/show_bug.cgi?id=470759 Max Nargang changed: What|Removed |Added CC||coffeecod...@outlook.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 476034] Plasma crash when deleting (empty) panel on external monitor
https://bugs.kde.org/show_bug.cgi?id=476034 Max changed: What|Removed |Added Ever confirmed|0 |1 Resolution|BACKTRACE |--- Status|NEEDSINFO |ASSIGNED --- Comment #3 from Max --- Hi Nate, thanks for the info. I attached the output of GDB since that's what I was recommended for openSUSE. If you need it in a different form feel free to reach out. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 476034] Plasma crash when deleting (empty) panel on external monitor
https://bugs.kde.org/show_bug.cgi?id=476034 --- Comment #2 from Max --- Created attachment 162561 --> https://bugs.kde.org/attachment.cgi?id=162561=edit GDB Output Full Backtrace from GDB -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 476034] New: Plasma crash when deleting (empty) panel on external monitor
https://bugs.kde.org/show_bug.cgi?id=476034 Bug ID: 476034 Summary: Plasma crash when deleting (empty) panel on external monitor Classification: Plasma Product: plasmashell Version: 5.27.8 Platform: openSUSE OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: max.sp...@pm.me CC: k...@davidedmundson.co.uk Target Milestone: 1.0 Application: plasmashell (5.27.8) Qt Version: 5.15.11 Frameworks Version: 5.111.0 Operating System: Linux 6.5.6-1-default x86_64 Windowing System: X11 Distribution: openSUSE Tumbleweed DrKonqi: 5.27.8 [CoredumpBackend] -- Information about the crash: When deleting a panel on an external monitor (connected with HDMI) plasma crashes after clicking "delete" immediately The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault PID: 1666 (plasmashell) UID: 1000 (max) GID: 1000 (max) Signal: 11 (SEGV) Timestamp: Tue 2023-10-24 08:14:46 CEST (20s ago) Command Line: /usr/bin/plasmashell --no-respawn Executable: /usr/bin/plasmashell Control Group: /user.slice/user-1000.slice/user@1000.service/session.slice/plasma-plasmashell.service Unit: user@1000.service User Unit: plasma-plasmashell.service Slice: user-1000.slice Owner UID: 1000 (max) Boot ID: be7c0e963d1d4acd9c126ea7c61f4844 Machine ID: 972d0650dbc24f10847539442b8dae25 Hostname: localhost.localdomain Storage: /var/lib/systemd/coredump/core.plasmashell.1000.be7c0e963d1d4acd9c126ea7c61f4844.1666.169812808600.zst (present) Size on Disk: 24.3M Message: Process 1666 (plasmashell) of user 1000 dumped core. Stack trace of thread 1666: #0 0x7fbbd38972a8 pthread_sigmask@GLIBC_2.2.5 (libc.so.6 + 0x972a8) #1 0x7fbbd383f3ad sigprocmask (libc.so.6 + 0x3f3ad) #2 0x7fbbd65398db _ZN6KCrash15setCrashHandlerEPFviE (libKF5Crash.so.5 + 0x58db) #3 0x7fbbd653bd93 _ZN6KCrash19defaultCrashHandlerEi (libKF5Crash.so.5 + 0x7d93) #4 0x7fbbd383f190 __restore_rt (libc.so.6 + 0x3f190) #5 0x7fbbd5a8ade0 _ZN8QQmlData17isSignalConnectedEP24QAbstractDeclarativeDataPK7QObjecti (libQt5Qml.so.5 + 0x28ade0) #6 0x7fbbd4324d0c n/a (libQt5Core.so.5 + 0x324d0c) #7 0x7fbbd428635d _ZN18QAbstractItemModel19modelAboutToBeResetENS_14QPrivateSignalE (libQt5Core.so.5 + 0x28635d) #8 0x56413b72b78c n/a (plasmashell + 0x6f78c) #9 0x56413b6f0d23 n/a (plasmashell + 0x34d23) #10 0x7fbbd5ae1923 n/a (libQt5Qml.so.5 + 0x2e1923) #11 0x7fbbd59be539 n/a (libQt5Qml.so.5 + 0x1be539) #12 0x7fbbd59c01db _ZNK3QV413QObjectMethod12callInternalEPKNS_5ValueES3_i (libQt5Qml.so.5 + 0x1c01db) #13 0x7fbbd59dceaf n/a (libQt5Qml.so.5 + 0x1dceaf) #14 0x7fbbd59e05af n/a (libQt5Qml.so.5 + 0x1e05af) #15 0x7fbbd5972bd2 _ZN3QV48Function4callEPKNS_5ValueES3_iPKNS_16ExecutionContextE (libQt5Qml.so.5 + 0x172bd2) #16 0x7fbbd5afc4dd _ZN24QQmlJavaScriptExpression8evaluateEPN3QV48CallDataEPb (libQt5Qml.so.5 + 0x2fc4dd) #17 0x7fbbd5aad4df _ZN25QQmlBoundSignalExpression8evaluateEPPv (libQt5Qml.so.5 + 0x2ad4df) #18 0x7fbbd5aae6c0 n/a (libQt5Qml.so.5 + 0x2ae6c0) #19 0x7fbbd5ae1405 _ZN12QQmlNotifier10emitNotifyEP20QQmlNotifierEndpointPPv (libQt5Qml.so.5 + 0x2e1405) #20 0x7fbbd4324d2d n/a (libQt5Core.so.5 + 0x324d2d) #21 0x7fbbd4325442 n/a (libQt5Core.so.5 + 0x325442) #22 0x7fbbcd9d7371 _ZN27QQuickAbstractButtonPrivate13handleReleaseERK7QPointF (libQt5QuickTemplates2.so.5 + 0xa4371) #23 0x7fbbcd9f14e5 _ZN13QQuickControl17mouseReleaseEventEP11QMouseEvent (libQt5QuickTemplates2.so.5 + 0xbe4e5) #24 0x7fbbd6089858 _ZN10QQuickItem5eventEP6QEvent (libQt5Quick.so.5 + 0x289858) #25 0x7fbbd51a519e _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt5Widgets.so.5 + 0x1a519e) #26 0x7fbbd42ed198 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Core.so.5 + 0x2ed198) #27 0x7fbbd60a461a _ZN19QQuickWindowPrivate17deliverMouseEventEP23QQuickPointerMouseEvent (libQt5Quick.so.5 + 0x2a461a) #28 0x7fbbd60a5d99 _ZN19QQuickWindowPrivate19deliverPointerEventEP18QQuickPointerEvent (libQt5Quick.so.5 + 0x2a5d99) #29 0x7f
[plasmashell] [Bug 474906] Feature Request: configure default desktop to use when new Monitor is added
https://bugs.kde.org/show_bug.cgi?id=474906 --- Comment #2 from Max Mantel --- What about some kind of Desktop or Control panel Template, that y can define and apply easily? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 474906] Feature Request: configure default desktop to use when new Monitor is added
https://bugs.kde.org/show_bug.cgi?id=474906 Max Mantel changed: What|Removed |Added Keywords||usability CC||mantel@gmx.de -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 474906] New: Feature Request: configure default desktop to use when new Monitor is added
https://bugs.kde.org/show_bug.cgi?id=474906 Bug ID: 474906 Summary: Feature Request: configure default desktop to use when new Monitor is added Classification: Plasma Product: plasmashell Version: master Platform: Ubuntu OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: Desktop Containment Assignee: plasma-b...@kde.org Reporter: mantel@gmx.de CC: notm...@gmail.com Target Milestone: 1.0 SUMMARY When using a Laptop with changing docking stations or adding monitors or projectors, new screens are usually setup with the default background and without widgets/control panels. The user has to configure every new screen manually. It would be much more comfortable if the user could just configure one screen desktop and select that one as default. STEPS TO REPRODUCE 1. configure your laptop desktop 2. connect to an additional monitor OBSERVED RESULT The new monitor has the default desktop background and no control panel. WANTED RESULT The new monitor has the same desktop background and control panel as my main desktop. ALTERNATIVES Alternatively there could be a switch between having multiple desktop configurations or just one for all screens (not mirroring windows, just the desktops and widgets/control panels). SOFTWARE/OS VERSIONS KDE Plasma Version: 5.24.7 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 443082] Offer option to move categories sidebar to other side of main view for better usability and faster access to Favorites
https://bugs.kde.org/show_bug.cgi?id=443082 --- Comment #47 from Max --- (In reply to Forest from comment #46) > Created attachment 161592 [details] > Kickoff with switchable sidebar position (Plasma 5.27 version) > > My solution has been merged into Plasma 6. (Thanks, all!) > Here's a Plasma 5.27 version for those who don't want to wait. That's awesome! Thanks a lot for your dedication and patience. I'm really happy to see this merged in master. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 427214] Add ability to paste Klipper's contents on selection
https://bugs.kde.org/show_bug.cgi?id=427214 --- Comment #23 from Max --- (In reply to David Edmundson from comment #3) > >But I think of a workaround, > > It probably would work some of the time, but that's a massive hack to the > point that I wouldn't accept it in our codebase. After seeing exciting new text input possibilites in David's blog, I really hope this request could finally get resolved in Plasma 6. Even better than I expected, with clipboard text preview on the fly! Can't wait for this to happen. http://blog.davidedmundson.co.uk/blog/new-ideas-using-wayland-input-methods/ -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 443082] Move categories sidebar to other side of main view for better usability (like how SimpleMenu does it)
https://bugs.kde.org/show_bug.cgi?id=443082 --- Comment #35 from Max --- (In reply to Forest from comment #33) > it might help to add a thumbs-up vote on the the merge request's top level > comment/description Thanks for sharing, I upvoted. People who thumbed down probably are not satisfied for the same reason this bug report was created — not having an option toggle in settings. I believe that adding an option is the only way to make everyone happy. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kinit] [Bug 407855] Kdeinit5 unable to write to NFS share
https://bugs.kde.org/show_bug.cgi?id=407855 Max Schettler changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|WORKSFORME |--- -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 420280] Can't add Google account: authentication process gets stuck
https://bugs.kde.org/show_bug.cgi?id=420280 Max changed: What|Removed |Added CC|maximts...@gmail.com| -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 443082] Move categories sidebar to other side of main view for better usability (like how SimpleMenu does it)
https://bugs.kde.org/show_bug.cgi?id=443082
--- Comment #30 from Max ---
(In reply to Forest from comment #29)
> > maybe also make the triangle filter toggleable? As it makes no sense with
> > categories sidebar placed on the right side.
>
> It can be reoriented such that it makes sense on either side, and the
> approach I'm using to put the sidebar on the right takes advantage of that.
I'm not sure if it makes sense, as this filter (per my understanding) was added
specifically to handle mouse movement from bottom left corner to the top right
corner. In case of alternative sidebar placement it probably would only cause
confusion (emotionally descibed by the previous commenter :) ).
I personally against any such sort of mouse filter, as it's directly against
any principles of good UX. When user moves cursor over button, they expect it
to respond by highlight effect, and/or get activated on left click. User may
not know about this whole filter thing and how it works, ending up in situation
when their mouse movement got filtered out — and they just sit there
frustrated, because the button doesn't respond to mouse movement and clicks,
with no visible indication of reason (such as "disabled" greyed out state).
Imagine being a first-time user of KDE Plasma and seeing this ("Linus test", if
you wish) — the first impression would be that the thing is broken and buggy,
that's all...
But anyway, all what I'm suggesting is just an option in settings. I'm totally
okay with "left sidebar + triangle filter" behavior enabled by default — as
long as there's easely discoverable option to change both. But even just an
option for right sidebar placement will already make me much happier.
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 443082] Move categories sidebar to other side of main view for better usability (like how SimpleMenu does it)
https://bugs.kde.org/show_bug.cgi?id=443082 --- Comment #28 from Max --- (In reply to Forest from comment #25) > Created attachment 160376 [details] > draft: Kickoff from Plasma 5.27.5 with configurable sidebar position > > I feel strongly that this should be configurable, so I decided to take on > the work of making it so. > > In case anyone wants to test it, here's a patched version of the Kickoff > plasmoid from Plasma 5.27.5, patched with a new "sidebar position" option. > > To install, create a > $HOME/.local/share/plasma/plasmoids/org.kde.plasma.kickofftest/ directory > and place the contents of this archive in it. This will not interfere with > your existing launcher. This new one is called "Application Launcher > (test)", and you'll have to manually add it to your panel. > > I plan to submit patches for both Plasma 5.27 and Plasma on Gitlab soon. Thanks for your great work. I really hope you'll manage to get this to the patch, and that it won't get rejected by the team – as they appear to be quite protective of the whole left sidebar idea. Also, w hile you're here, maybe also make the triangle filter toggleable? As it makes no sense with categories sidebar placed on the right side. But probably it makes sense to be proposed as another patch in case this one will be accepted. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 472744] New: Inconsistent behaviour between shading / maximizing and restoring windows
https://bugs.kde.org/show_bug.cgi?id=472744 Bug ID: 472744 Summary: Inconsistent behaviour between shading / maximizing and restoring windows Classification: Plasma Product: kwin Version: 5.27.6 Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: m...@dnzm.nl Target Milestone: --- SUMMARY There's some unexpected behaviour when working with window shading and maximizing, and especially, when unshading/unmaximizng them. State/size seems to be lost or not updated at some point. I first encountered this when I maximized a shaded windows and expected it to be unshaded (which it wasn't), but although there's something to be said for keeping a window shaded when maximizing it, but unshading that maximized window should then keep it maximized, and NOT return it to its previous size. Also, at that point, the maximize/restore button is still on "I'm maximized, so click me to restore" mode seems to do nothing. There's actually a few ways in which this seems to go slightly wrong, but at least predictably so. STEPS TO REPRODUCE I'm using a Dolphin window for these steps. 1. Open a window, non-maximized 2. Shade the window 3. Maximize it 4. Unshade it 5. Restore it OBSERVED RESULT At step 4, the window is unshaded, but also un-maximized and moved to the top left of the screen; maximize button is still a restore-button at this point. Also, closing the (Dolphin) window and opening a new one, opens it maximized. At step 5, the window doesn't move or resize, but the button state is now "correct". EXPECTED RESULT At step 4, I'd expect the window to be unshaded but still maximized. Step 5 should restore it to its former size and preferably location. ADDITIONALLY There's another way in which this goes slightly against what you'd expect: 1. Open a non-maximized window 2. Maximize it 3. Shade it 4. Restore it (window is now shaded, but in its previous location and size) 5. Unshade it (window is now unshaded, in the same location, but suddenly resized to maximized-size) SOFTWARE/OS VERSIONS Linux/KDE Plasma: OpenSUSE Tumbleweed, also tried MicroOS, same result. KDE Plasma Version: 5.27.6 KDE Frameworks Version: 5.108.0 Qt Version: 5.15.10 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 471559] Wayland plasma session does not get along with egl-wayland 1.1.12
https://bugs.kde.org/show_bug.cgi?id=471559 Max changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |UPSTREAM --- Comment #3 from Max --- Fixed on the egl-wayland side by recent commits -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kinit] [Bug 407855] Kdeinit5 unable to write to NFS share
https://bugs.kde.org/show_bug.cgi?id=407855 --- Comment #11 from Max Schettler --- Just tested again on Debian 11 with Plasma 5.20. Without the workaround mentioned above the problem persists. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 443082] Move categories sidebar to other side of main view for better usability (like how SimpleMenu does it)
https://bugs.kde.org/show_bug.cgi?id=443082 --- Comment #24 from Max --- I agree with your point that KDE is all about choice, but the choice should not only be about using one start menu or another: the start menu itself should provide the choice and ability to configure it for user's liking, at least the most frequently requested options. You don't have to install whole another taskbar widget in order to get the ability to place it on the right side of your screen, right? Almost every thing in KDE interface has some options and configurations — in fact, there's so much of them, that I keep discovering new options and hidden features even after 6 years of using KDE. And yet, for whatever reason, devs decided to make an exception just for the new Kickoff launcher, implementing quite arguable UX decision and leaving no option to change it, with the argumentation like "get used to it or change the launcher". Just as you mentioned, it feels a lot like macOS, when "big company" forces you to accept their vision on how to use the computer, instead of allowing you to implement your vision. This is not what KDE is all about, in my opinion. Your "solution" about using the Legacy launcher doesn't fit for me, because I quite like the new launcher, I like the grid layout much more that a list one. Also it's the only launcher that will be actively maintained and get new features. But I don't like the left-side sidebar and hover activation — even the legacy launcher had an option to disable hover activation, despite it was less neccessary there. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 471559] New: Wayland plasma session does not get along with egl-wayland 1.1.12
https://bugs.kde.org/show_bug.cgi?id=471559 Bug ID: 471559 Summary: Wayland plasma session does not get along with egl-wayland 1.1.12 Classification: I don't know Product: kde Version: unspecified Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: thesource...@gmail.com Target Milestone: --- SUMMARY After an update of egl-wayland to 1.1.12 native wayland GL applications like glmark2-wayland and glmark2-es2-wayland can not run (using prime render offload, NVIDIA GeForce RTX 3060 laptop, driver 535.54.03), fail with "error 7: importing the supplied dmabufs failed". Reverting back to 1.1.11 solves the issue, but also those apps wotk just fine under gnome wayland session with 1.1.12. I reported this problem on egl-wayland git and they suspect this is a bug of KDE wayland compositor reporting something wrong. Please see this discussion: https://github.com/NVIDIA/egl-wayland/issues/83 STEPS TO REPRODUCE 1. Try to use prime render offload on nvidia card with egl-wayland 1.1.12 with a native wayland GL app 2. 3. OBSERVED RESULT Native wayland GL applications fail with "error 7: importing the supplied dmabufs failed" EXPECTED RESULT Those apps should work SOFTWARE/OS VERSIONS Operating System: Fedora Linux 38 KDE Plasma Version: 5.27.6 KDE Frameworks Version: 5.107.0 Qt Version: 5.15.10 Kernel Version: 6.3.9-200.fc38.x86_64 (64-bit) Graphics Platform: Wayland Processors: 16 × Intel® Core™ i7-10870H CPU @ 2.20GHz Memory: 15.4 ГиБ of RAM Graphics Processor: Mesa Intel® UHD Graphics Manufacturer: Dell Inc. Product Name: Dell G15 5510 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 471443] Low-res Images in Qt Apps when using fractional scaling
https://bugs.kde.org/show_bug.cgi?id=471443 --- Comment #1 from Max Staff --- Telegram Desktop issues: https://github.com/telegramdesktop/tdesktop/issues/26155 https://github.com/telegramdesktop/tdesktop/issues/17173 https://github.com/telegramdesktop/tdesktop/issues/25961 Explanation of the problem (see block below screenshot, item no 4): https://github.com/telegramdesktop/tdesktop/issues/25126 That one also contains links to the respective Qt bugreports, in case they change the text after this bugreport here's a copy: > Icons and emojis are blurry #17173 - exists only in third-party builds, was > reported as https://bugreports.qt.io/browse/QTBUG-95930, > https://bugreports.qt.io/browse/QTBUG-99546 and > https://bugreports.qt.io/browse/QTBUG-110626, Qt tried to fix this, but then > reverted, so apparently they think there's no bug on their side and this > needs a report to KDE as they probably use the wrong API to tell scale factor > to Qt. According to https://doc.qt.io/qt-6/highdpi.html, > QT_SCREEN_SCALE_FACTORS is in line with debug-only environment variables KDE > shouldn't set. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 471443] New: Low-res Images in Qt Apps when using fractional scaling
https://bugs.kde.org/show_bug.cgi?id=471443 Bug ID: 471443 Summary: Low-res Images in Qt Apps when using fractional scaling Classification: I don't know Product: kde Version: unspecified Platform: NixOS OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: bright.joy7...@mstaff.dev Target Milestone: --- Created attachment 159897 --> https://bugs.kde.org/attachment.cgi?id=159897=edit Current pixelated scaling SUMMARY *** Icons in the Telegram Desktop App are blurry or pixelated when setting the global scaling to e.g. 150% in the display settings. *** STEPS TO REPRODUCE 1. Set global scaling to 150% in display settings 2. reboot 3. open Telegram and closely look at any icon OBSERVED RESULT * rounded corners of profile pictures look pixelated * icons and emojis look pixelated EXPECTED RESULT * rounded corners actually round * high-res version of icons and emojis used SOFTWARE/OS VERSIONS NixOS: 23.11 KDE Plasma Version: 5.27.6 KDE Frameworks Version: 5.107.0 Qt Version: 5.15.9 Kernel-Version: 6.3.6 (64-bit) Graphics: X11 ADDITIONAL INFORMATION * Telegram also had display scaling set to 225% by default (in the in-app-settings) after switching to global scaling of 150% * Other users have also reported this to the Telegram Desktop Github issue tracker as well as the Qt issue tracker with both saying that the issue lies with KDE * some users have reported that this happens only on the official version of Telegram for their respective distro, not on snaps * quote from Telegram Desktop issue tracker: "According to https://doc.qt.io/qt-6/highdpi.html, QT_SCREEN_SCALE_FACTORS is in line with debug-only environment variables KDE shouldn't set." -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 471409] New: Plasma crashed after removing widget
https://bugs.kde.org/show_bug.cgi?id=471409 Bug ID: 471409 Summary: Plasma crashed after removing widget Classification: Plasma Product: plasmashell Version: 5.27.5 Platform: Debian stable OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: s.m.smir...@mail.ru CC: k...@davidedmundson.co.uk Target Milestone: 1.0 Application: plasmashell (5.27.5) Qt Version: 5.15.8 Frameworks Version: 5.103.0 Operating System: Linux 6.1.0-9-amd64 x86_64 Windowing System: X11 Distribution: Debian GNU/Linux 12 (bookworm) DrKonqi: 5.27.5 [CoredumpBackend] -- Information about the crash: Plasma crashed after removing thermal widget from main bar The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault PID: 2266 (plasmashell) UID: 1000 (msmirnov) GID: 1000 (msmirnov) Signal: 11 (SEGV) Timestamp: Sat 2023-06-24 14:52:47 MSK (32s ago) Command Line: /usr/bin/plasmashell --no-respawn Executable: /usr/bin/plasmashell Control Group: /user.slice/user-1000.slice/user@1000.service/session.slice/plasma-plasmashell.service Unit: user@1000.service User Unit: plasma-plasmashell.service Slice: user-1000.slice Owner UID: 1000 (msmirnov) Boot ID: 3968481d5785467c8f5343bb5192ba8a Machine ID: a17e1a3bc91045cbaf983b89863b5d49 Hostname: maksbook Storage: /var/lib/systemd/coredump/core.plasmashell.1000.3968481d5785467c8f5343bb5192ba8a.2266.168760756700.zst (present) Size on Disk: 99.9M Message: Process 2266 (plasmashell) of user 1000 dumped core. Module libsystemd.so.0 from deb systemd-252.6-1.amd64 Module libudev.so.1 from deb systemd-252.6-1.amd64 Stack trace of thread 2266: #0 0x7f7372caebb4 pthread_sigmask (libc.so.6 + 0x8fbb4) #1 0x7f7372c5b179 sigprocmask (libc.so.6 + 0x3c179) #2 0x7f737536de9b _ZN6KCrash15setCrashHandlerEPFviE (libKF5Crash.so.5 + 0x4e9b) #3 0x7f737536eb3e _ZN6KCrash19defaultCrashHandlerEi (libKF5Crash.so.5 + 0x5b3e) #4 0x7f7372c5af90 n/a (libc.so.6 + 0x3bf90) #5 0x7f7371dd1e85 n/a (libQt5QmlModels.so.5 + 0x2ce85) #6 0x7f7371dd6dea _ZN13QQmlListModelD1Ev (libQt5QmlModels.so.5 + 0x31dea) #7 0x7f7371dc6b4b n/a (libQt5QmlModels.so.5 + 0x21b4b) #8 0x7f73730db28e _ZN14QObjectPrivate14deleteChildrenEv (libQt5Core.so.5 + 0x2db28e) #9 0x7f73730e7054 _ZN7QObjectD2Ev (libQt5Core.so.5 + 0x2e7054) #10 0x7f7374fd03e5 n/a (libQt5Quick.so.5 + 0x3d03e5) #11 0x7f73730db28e _ZN14QObjectPrivate14deleteChildrenEv (libQt5Core.so.5 + 0x2db28e) #12 0x7f73730e7054 _ZN7QObjectD2Ev (libQt5Core.so.5 + 0x2e7054) #13 0x7f7374fd1125 n/a (libQt5Quick.so.5 + 0x3d1125) #14 0x7f73730db28e _ZN14QObjectPrivate14deleteChildrenEv (libQt5Core.so.5 + 0x2db28e) #15 0x7f73730e7054 _ZN7QObjectD2Ev (libQt5Core.so.5 + 0x2e7054) #16 0x7f7333a75695 n/a (libqtquicktemplates2plugin.so + 0x5a695) #17 0x7f73746ab7e9 _ZN3QV413MemoryManager5sweepEbPFvPKcE (libQt5Qml.so.5 + 0xab7e9) #18 0x7f73746ab935 _ZN3QV413MemoryManagerD1Ev (libQt5Qml.so.5 + 0xab935) #19 0x7f7374725e1c _ZN3QV415ExecutionEngineD2Ev (libQt5Qml.so.5 + 0x125e1c) #20 0x7f737471085d _ZN9QJSEngineD2Ev (libQt5Qml.so.5 + 0x11085d) #21 0x7f7374879cc9 _ZN10QQmlEngineD0Ev (libQt5Qml.so.5 + 0x279cc9) #22 0x7f73730db28e _ZN14QObjectPrivate14deleteChildrenEv (libQt5Core.so.5 + 0x2db28e) #23 0x7f73730e7054 _ZN7QObjectD2Ev (libQt5Core.so.5 + 0x2e7054) #24 0x7f7375807719 _ZN11PlasmaQuick10ConfigViewD0Ev (libKF5PlasmaQuick.so.5 + 0x36719) #25 0x7f73730dd4bf _ZN7QObject5eventEP6QEvent (libQt5Core.so.5 + 0x2dd4bf) #26 0x7f7373f62fae _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt5Widgets.so.5 + 0x162fae) #27 0x7f73730b16f8 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Core.so.5 + 0x2b16f8) #28 0x7f73730b4681 _ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData (libQt5Core.so.5 + 0x2b4681) #29 0x7f737310a153 n/a (libQt5Core.so.5 + 0x30a153) #30 0x7f7371b8b7a9 g_main_context_dispatch (libglib-2.0.so.0 + 0x547a9) #31 0x7f7371b8ba38 n/a (libglib-2.0.so.0 +
[Spectacle] [Bug 469668] New: while using spectacle the color controls are shown below screen.
https://bugs.kde.org/show_bug.cgi?id=469668 Bug ID: 469668 Summary: while using spectacle the color controls are shown below screen. Classification: Applications Product: Spectacle Version: 23.04.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: noaha...@gmail.com Reporter: max.nizamov+manj...@gmail.com CC: k...@david-redondo.de Target Milestone: --- while using spectacle the color controls are shown below screen. i cannot draw an empty rectangle in annotation mode, neither can change color of frame -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 382221] Duplicated panels
https://bugs.kde.org/show_bug.cgi?id=382221 --- Comment #8 from Max Schettler --- Not an answer to your question, but maybe relevant: Without having tried to reproduce this issue I can't remember when I last observed it. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 445512] When switching between app categories, one random app from the last category appears in the next category
https://bugs.kde.org/show_bug.cgi?id=445512 --- Comment #15 from Max --- Still having this problem with the following configuration: Operating System: Fedora Linux 37 KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.8 Kernel Version: 6.2.10-200.fc37.x86_64 (64-bit) Graphics Platform: Wayland Processors: 16 × Intel® Core™ i7-10870H CPU @ 2.20GHz Memory: 15.4 ГиБ of RAM Graphics Processor: Mesa Intel® UHD Graphics Manufacturer: Dell Inc. Product Name: Dell G15 5510 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 420806] Desktop icons moved down based on column number
https://bugs.kde.org/show_bug.cgi?id=420806 --- Comment #7 from Max --- (In reply to Nate Graham from comment #6) > Max, I can't reproduce your originally described issue in Plasma 5.27.4 with > exactly that desktop icon layout. Can you still reproduce it with Plasma > 5.27.4 and a recent Frameworks version (e.g. 5.104 or later)? Hello, I can not reproduce the issue with the following configuration: Operating System: Fedora Linux 37 KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.8 Kernel Version: 6.2.10-200.fc37.x86_64 (64-bit) Graphics Platform: Wayland Processors: 16 × Intel® Core™ i7-10870H CPU @ 2.20GHz Memory: 15.4 ГиБ of RAM Graphics Processor: Mesa Intel® UHD Graphics Manufacturer: Dell Inc. Product Name: Dell G15 5510 -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 464790] Can not end session properly after updating KDE Frameworks from 5.101 to 5.102
https://bugs.kde.org/show_bug.cgi?id=464790 --- Comment #5 from Max --- After some more updates to components like Qt, KDE applications, systemd, the problem is gone, I can now end session properly. Not sure which component was responsible. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 465034] digikam crashes when trying to recognize faces
https://bugs.kde.org/show_bug.cgi?id=465034 --- Comment #5 from Max <1...@mailbox.org> --- (In reply to Maik Qualmann from comment #4) > Again, for the avoidance of doubt: Gilles creates a new AppImage, but it is > not affected since we are still using OpenCV-4.6.0. Here Archlinux would > have to create a new patched version. > > Maik Ah okay, thanks for clarifying! So i'll wait for the patch to the arch opencv package. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 465034] digikam crashes when trying to recognize faces
https://bugs.kde.org/show_bug.cgi?id=465034 --- Comment #3 from Max <1...@mailbox.org> --- (In reply to Maik Qualmann from comment #1) > The cause is a bug in the release version of OpenCV-4.7.0. The problem has > already been fixed in the current master version of OpenCV. We added a > workaround for digiKam-7.10.0 to bypass the bug in OpenCV-4.7.0. > > https://invent.kde.org/graphics/digikam/-/commit/ > f2f86c3c6719e4ea0bc7de95ce1ae33e8c45495e > > Maik Thanks for your quick reply, looking forward to the new build! -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 465034] New: digikam crashes when trying to recognize faces
https://bugs.kde.org/show_bug.cgi?id=465034 Bug ID: 465034 Summary: digikam crashes when trying to recognize faces Classification: Applications Product: digikam Version: 7.9.0 Platform: Archlinux OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: Faces-Workflow Assignee: digikam-bugs-n...@kde.org Reporter: 1...@mailbox.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 *** Whenever digikam tries to update its knowledge about faces, it crashes with the following console output: /usr/include/c++/12.2.0/bits/stl_vector.h:1123: std::vector<_Tp, _Alloc>::reference std::vector<_Tp, _Alloc>::operator[](size_type) [with _Tp = float; _Alloc = std::allocator; reference = float&; size_type = long unsigned int]: Assertion '__n < this->size()' failed. fish: Job 1, 'digikam' terminated by signal SIGABRT (Abort) "Whenever it tries to update its knowledge" comprises the following situations (and maybe more): - I manually label a face in a picture with Ctrl+Mouse. As soon as i hit enter after having typed the name of the person, the program crashes. - I right click on a collection or subcollection and in the context menu, click on "Scan for faces' STEPS TO REPRODUCE 1. Open digikam 2. Right-click any collection or sub-collection from your "Albums" tab. 3. In the context menu, click on "Scan for faces" OBSERVED RESULT The program crashes EXPECTED RESULT It scans for faces without crashing SOFTWARE/OS VERSIONS Arch Linux gcc v12.2.1 Qt Version: 5.15.8 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 464790] Can not end session properly after updating KDE Frameworks from 5.101 to 5.102
https://bugs.kde.org/show_bug.cgi?id=464790 --- Comment #3 from Max --- Created attachment 155657 --> https://bugs.kde.org/attachment.cgi?id=155657=edit Update journal screenshots -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 464790] Can not end session properly after updating KDE Frameworks from 5.101 to 5.102
https://bugs.kde.org/show_bug.cgi?id=464790 --- Comment #2 from Max --- I left my pc and went to bed, in the morning it was still there, so it seems it stays forever until I kill Xorg. I could not find text log of dnfdragora so here are the screenshots of update journal. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 464790] New: Can not end session properly after updating KDE Frameworks from 5.101 to 5.102
https://bugs.kde.org/show_bug.cgi?id=464790 Bug ID: 464790 Summary: Can not end session properly after updating KDE Frameworks from 5.101 to 5.102 Classification: I don't know Product: kde Version: unspecified Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: thesource...@gmail.com Target Milestone: --- SUMMARY After I updated KDE Frameworks packages from 5.101 to 5.102, I can not exit session back to login sceen (sddm). If I press "leave session" in plasma main menu, screen goes black, all apps close, cursor still moves and that's it. The only way I can go back to login screen after that is pressing Ctrl+Alt+Backspace or killing Xorg from another tty. With 5.101 I could return to login screen just fine. STEPS TO REPRODUCE 1. Login to X11 plasma session 2. Try to exit session OBSERVED RESULT Black screen with mouse cursor EXPECTED RESULT Login screen SOFTWARE/OS VERSIONS Operating System: Fedora Linux 37 KDE Plasma Version: 5.26.5 KDE Frameworks Version: 5.102.0 Qt Version: 5.15.8 Kernel Version: 6.1.7-200.fc37.x86_64 (64-bit) Graphics Platform: X11 Processors: 16 × Intel® Core™ i7-10870H CPU @ 2.20GHz Memory: 15.4 ГиБ of RAM Graphics Processor: Mesa Intel® UHD Graphics Manufacturer: Dell Inc. Product Name: Dell G15 5510 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 401347] Unable to connect to KDE with mobile connection
https://bugs.kde.org/show_bug.cgi?id=401347 Max Goodell changed: What|Removed |Added CC||m...@maxgoodell.com --- Comment #4 from Max Goodell --- It would be very useful to be able to connect to a device over a VPN tunnel over mobile data, but it seems like it's only possible using wifi. Maybe it's possible to add an option to select which interfaces the app is allowed to communicate using? -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 463579] New: Wrong files are copied
https://bugs.kde.org/show_bug.cgi?id=463579 Bug ID: 463579 Summary: Wrong files are copied Classification: Applications Product: dolphin Version: 22.12.0 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: thesource...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- SUMMARY *** When I press copy on selected files for the first time I booted into plasma session, all is ok, but when I then select some other files and press copy, first selected files are placed into clipboard instead. This happens only when I try to copy files, not their paths as text. I had to revert to 22.08.2 to avoid that. *** STEPS TO REPRODUCE 1. Start dolphin and press copy over some files. Check that they are properly placed into clipboard. 2. Select something else like text, copy it, see it in clipboard manager. 3. Now select some different files in dolphin and press copy. Check clipboard: it contains the files you selected first, not recently selected and copied. OBSERVED RESULT Dolhin always places the files that were selected first into clipboard EXPECTED RESULT Dolphin should properly copy selected files SOFTWARE/OS VERSIONS Operating System: Fedora Linux 37 KDE Plasma Version: 5.26.4 KDE Frameworks Version: 5.101.0 Qt Version: 5.15.7 Kernel Version: 6.0.15-300.fc37.x86_64 (64-bit) Graphics Platform: X11 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 430210] Font previews do not show up on Wayland
https://bugs.kde.org/show_bug.cgi?id=430210 Max changed: What|Removed |Added CC||maxpat...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 462368] QTAV-library has been removed from unstable
https://bugs.kde.org/show_bug.cgi?id=462368 --- Comment #2 from Max --- (In reply to caulier.gilles from comment #1) > This problem is fixed with next 8.0.0 as QtAv code have been backported to > digiKam core, ported to Qt6, and ported to ffmpeg 5. > > https://invent.kde.org/graphics/digikam/-/tree/master/core/libs/video/qtav > > Gilles Caulier Dear Gilles, that actually good news. :-) Thanks for your immediate reply as well. Max -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 462368] New: QTAV-library has been removed from unstable
https://bugs.kde.org/show_bug.cgi?id=462368 Bug ID: 462368 Summary: QTAV-library has been removed from unstable Classification: Applications Product: digikam Version: 7.7.0 Platform: Debian unstable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: digikam-bugs-n...@kde.org Reporter: mgerstenhoe...@gmx.de Target Milestone: --- digikam uses the qtav-framework. The qtav-libraries have been removed from the unstable repository of debian. Due to less to none reaction by the maintainers as it seems. eg: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971329 The ppa suggested on the qtav-website is not maintained or updated for over 271 days. The question to you digikam-guys is now, do you really want to rely on such a weak maintained and not really settled framework in the future? Is there really no other way feeding ffmpeg properly as that by using qtav? That does not fit to the big news that digikam can now handle videos as well. Thanks for your other works! kind regards, Max -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 94019] Malicious javascriptlet crashes konqueror (FreeBSD)
https://bugs.kde.org/show_bug.cgi?id=94019 --- Comment #12 from Max --- (In reply to Stefano Crocco from comment #11) > (In reply to Max from comment #10) > > It still can be reproduced with Konqueror 22.08.3 and KDE Frameworks 5.99.0 > > Unfortunately, I don't think there's much that Konqueror can do about that, > as javascript code is run by QtWebEngine which, as far as I can tell, > doesn't provide any way for the application to control it. Konqueror crashes only when using KHTML as a web engine. With QtWebEngine, the underlying process runs out of memory without crashing the Konqueror. KHTML: Thread 1 received signal SIGSEGV, Segmentation fault. Invalid permissions for mapped object. 0x0008236c02f4 in KJS::JSObject::mark() () from /usr/local/lib/libKF5JS.so.5 (gdb) QtWebEngine: <--- Last few GCs ---> [80062:0x1e37]79252 ms: Scavenge 3951.1 (3964.3) -> 3950.2 (3965.3) MB, 17.8 / 0.0 ms (average mu = 0.322, current mu = 0.179) allocation failure [80062:0x1e37]82245 ms: Scavenge 3952.1 (3965.3) -> 3951.5 (3967.5) MB, 2984.8 / 0.0 ms (average mu = 0.322, current mu = 0.179) allocation failure [80062:0x1e37]82424 ms: Scavenge 3954.4 (3967.5) -> 3954.3 (3967.5) MB, 165.4 / 0.0 ms (average mu = 0.322, current mu = 0.179) allocation failure <--- JS stacktrace ---> [80062:417406976:1128/121407.732800:FATAL:memory.cc(38)] Out of memory. size=0 [New LWP 193811 of process 80023] [LWP 193811 of process 80023 exited] [LWP 193642 of process 80023 exited] -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 94019] Malicious javascriptlet crashes konqueror (FreeBSD)
https://bugs.kde.org/show_bug.cgi?id=94019 Max changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #10 from Max --- It still can be reproduced with Konqueror 22.08.3 and KDE Frameworks 5.99.0 -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 461821] Audio Capture Stops Working (red button)
https://bugs.kde.org/show_bug.cgi?id=461821 Max Rottersman changed: What|Removed |Added CC||maxrotters...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 461821] New: Audio Capture Stops Working (red button)
https://bugs.kde.org/show_bug.cgi?id=461821 Bug ID: 461821 Summary: Audio Capture Stops Working (red button) Classification: I don't know Product: kde Version: unspecified Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: maxrotters...@gmail.com Target Milestone: --- I can record a first narration just fine. Then it stops working. But will work again in a new project. Maybe it's an image I have with a transform that I was trying to record under? For a while, I was able to record multiple recordings. I've done a lot of deleting old wav files from my computer or timeline. Maybe something got out of whack? I just closed KDenlive and reopened and now that problem has gone away (though I had tried that beofre). So you can throw out this bug report or maybe it substantiates another report that something can disable the audio record. STEPS TO REPRODUCE 1. Create a narration 2. Try to create a second narration SOFTWARE/OS VERSIONS Windows 11. Version 22.08.3. I've tried cleaning project. Deleting temp files. Can't figure it out. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kservice] [Bug 442721] kf.service.services: KApplicationTrader: mimeType "x-scheme-handler/file" not found
https://bugs.kde.org/show_bug.cgi?id=442721 Max changed: What|Removed |Added Status|RESOLVED|REOPENED CC||thesource...@gmail.com Resolution|FIXED |--- --- Comment #16 from Max --- I'm seeing this problem again when trying to open directory from Qt application using QDesktopServices::openUrl. It should invoke dolphin to open directory but instead prints: kf.service.services: KApplicationTrader: mimeType "x-scheme-handler/file" not found Operating System: Fedora Linux 36 KDE Plasma Version: 5.26.0 KDE Frameworks Version: 5.99.0 Qt Version: 5.15.6 Kernel Version: 6.0.5-200.fc36.x86_64 (64-bit) Graphics Platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 460792] plasma-workspace-5.24.6-1.el8.next.x86_64 run krunner can't show anything
https://bugs.kde.org/show_bug.cgi?id=460792 --- Comment #9 from max.23 --- (In reply to Alexander Lohnau from comment #8) > You can run "krunner --replace" on the terminal. That might give you the > path to the RunCommand.qml file. > Otherwise, please attach the log you get. thanks very much. i use find /usr/share to remove theme file. the krunner is work fine i can't image that without yours help, how many time to spent on debugging this problem -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 460792] plasma-workspace-5.24.6-1.el8.next.x86_64 run krunner can't show anything
https://bugs.kde.org/show_bug.cgi?id=460792 --- Comment #7 from max.23 --- how to set krunner begin to show search result when i input only a char? thanks -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 460792] plasma-workspace-5.24.6-1.el8.next.x86_64 run krunner can't show anything
https://bugs.kde.org/show_bug.cgi?id=460792 --- Comment #6 from max.23 --- where is the path of customer runner qml i can remove it by my self -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 460792] plasma-workspace-5.24.6-1.el8.next.x86_64 run krunner can't show anything
https://bugs.kde.org/show_bug.cgi?id=460792 --- Comment #4 from max.23 --- screen record is i press alt+space to launch krunner. but is show a small square area with empty -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 460792] plasma-workspace-5.24.6-1.el8.next.x86_64 run krunner can't show anything
https://bugs.kde.org/show_bug.cgi?id=460792 --- Comment #3 from max.23 --- Created attachment 153077 --> https://bugs.kde.org/attachment.cgi?id=153077=edit this is a screen record -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 460792] plasma-workspace-5.24.6-1.el8.next.x86_64 run krunner can't show anything
https://bugs.kde.org/show_bug.cgi?id=460792 --- Comment #1 from max.23 --- is there a fine version to work in centos 8 stream -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 460792] New: plasma-workspace-5.24.6-1.el8.next.x86_64 run krunner can't show anything
https://bugs.kde.org/show_bug.cgi?id=460792 Bug ID: 460792 Summary: plasma-workspace-5.24.6-1.el8.next.x86_64 run krunner can't show anything Classification: Plasma Product: krunner Version: 5.24.6 Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: windows Assignee: plasma-b...@kde.org Reporter: max...@qq.com CC: alexander.loh...@gmx.de Target Milestone: --- centos 8-stream, install kde, and version is plasma-workspace-5.24.6-1.el8.next.x86_64 run krunner, can't show anything version plasma-workspace-5.23.3-2.el8.x86_64 is work fine -- You are receiving this mail because: You are watching all bug changes.
[kfontview] [Bug 439470] KFontView is unable to open or install a font on Wayland
https://bugs.kde.org/show_bug.cgi?id=439470 Max changed: What|Removed |Added CC||maxpat...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 453445] Scaling setting is no longer honored after some time
https://bugs.kde.org/show_bug.cgi?id=453445 Max changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #4 from Max --- 5.25.4-2 appears to no longer show this behavior. So, this was either addressed and fixed directly or as a side effect (maybe?) of config sync updates. My gratitude goes out to the kwin & plasma teams - thank you people for keeping up the good work! -- You are receiving this mail because: You are watching all bug changes.
[subtitlecomposer] [Bug 459353] Application: Subtitle Composer (subtitlecomposer), signal: Segmentation fault
https://bugs.kde.org/show_bug.cgi?id=459353 Max changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #1 from Max --- Have pushed a possible fix to git master: https://invent.kde.org/multimedia/subtitlecomposer/-/commit/c94e4dc1362b9ac03cddb9def913ea6728875fe2 Can you check if that resolves the crash? If it still crashes: Can you tell me the version of installed libavformat (ffmpeg library) on your system? Do you know if subtitlecomposer was compiled against the same version? -- You are receiving this mail because: You are watching all bug changes.
[kactivitymanagerd] [Bug 398050] Recent documents section is not populated
https://bugs.kde.org/show_bug.cgi?id=398050 --- Comment #16 from Max --- (In reply to Nate Graham from comment #15) > Any chance you could test again with Plasma 5.25? I just checked recent and frequently used entries in 5.25 and it seems they work properly now. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 458598] Kwin crashes in KWin::Workspace::clientArea() after waking from sleep with KDE Snap Assist KWin script active
https://bugs.kde.org/show_bug.cgi?id=458598 Max changed: What|Removed |Added CC||maximts...@gmail.com --- Comment #5 from Max --- (In reply to Nate Graham from comment #1) > This is an issue caused by a bug in the 3rd-party Snap Assist KWin script. > Evidently your system is missing the "pygdbmi" python modue, and this causes > it to crash But this script doesn't depend on "pygdbmi" module, or any other external libraries or modules other than the official KWin Scripting API. The fact that the crash happens only after waking from sleep also makes me suspicious. Is it possible that "clientArea()" method from the API somehow requires "pygdbmi" dependency under the hood? As it seems to be the exact place where the crash happens. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 445129] Provide an ability to emit dbus signals and react to the method calls, so that other programs could interact with a KWin Script
https://bugs.kde.org/show_bug.cgi?id=445129 Max changed: What|Removed |Added CC||maximts...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 457822] New: client.frameGeometry.width doesn't work on Wayland
https://bugs.kde.org/show_bug.cgi?id=457822 Bug ID: 457822 Summary: client.frameGeometry.width doesn't work on Wayland Product: kwin Version: 5.25.4 Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: scripting Assignee: kwin-bugs-n...@kde.org Reporter: maximts...@gmail.com Target Milestone: --- SUMMARY In my KWin script, I use client.frameGeometry API to change window's width like this: client.frameGeometry.width = desiredWidth; While in X11 session this code works just fine, in Wayland window's width doesn't change. At the same time, modifying .x, .y and .height works as expected. SOFTWARE/OS VERSIONS KDE Plasma: 5.25.4 KDE Frameworks: 5.96.0 QT Version: 5.15.5 Kernel: 5.13.0-52-generic (64-bit) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 456959] New: [Request] "Snap assist" feature from Windows
https://bugs.kde.org/show_bug.cgi?id=456959 Bug ID: 456959 Summary: [Request] "Snap assist" feature from Windows Product: kwin Version: unspecified Platform: unspecified OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: maximts...@gmail.com Target Milestone: --- Created attachment 150777 --> https://bugs.kde.org/attachment.cgi?id=150777=edit Gif illustration of "snap assist" feature SUMMARY Windows has a nice feature, which shows thumbnails of other windows when user snaps window to the one of the screen halves. It helps to immediately select next window to be placed near the first one, and it improves productivity a lot for mouse-oriented users. For Gnome, there is Tiling Assistant extension (https://github.com/Leleat/Tiling-Assistant) which provides similar functionality – but there's none for KDE, seemingly because Kwin scripting limitations do not allow to fully recreate such a feature. Therefore, I think it makes sense to request such a feature to be implemented in the system natively – especially in the light of other feature from Windows, "custom snap zones", currently being in the work (https://invent.kde.org/plasma/kwin/-/merge_requests/2560). -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 456922] SVG file that makes Krita use memory infinitely until I kill the process
https://bugs.kde.org/show_bug.cgi?id=456922 Max changed: What|Removed |Added CC||hifi...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 456922] New: SVG file that makes Krita use memory infinitely until I kill the process
https://bugs.kde.org/show_bug.cgi?id=456922 Bug ID: 456922 Summary: SVG file that makes Krita use memory infinitely until I kill the process Product: krita Version: 5.0.6 Platform: Other OS: Microsoft Windows Status: REPORTED Severity: crash Priority: NOR Component: File formats Assignee: krita-bugs-n...@kde.org Reporter: hifi...@gmail.com Target Milestone: --- Created attachment 150742 --> https://bugs.kde.org/attachment.cgi?id=150742=edit bugged file SUMMARY This specific SVG file of an icon puts Krita in a state of infinitely increasing memory used until I have to kill it. For testing purposes I've loaded it into Inkscape and saved it. This worked without any problems. This happened in 4.4.x too but didn't change when I upgraded my installation. STEPS TO REPRODUCE 1. Load the file SOFTWARE/OS VERSIONS Windows: Windows 10 x64 -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 456797] Ark doesn't work with original 7-Zip
https://bugs.kde.org/show_bug.cgi?id=456797 Max changed: What|Removed |Added CC||m...@freebsd.org -- You are receiving this mail because: You are watching all bug changes.
[subtitlecomposer] [Bug 456804] Can't load any video, saying 'option refcounted_frames not found'
https://bugs.kde.org/show_bug.cgi?id=456804 --- Comment #2 from Max --- > Still stucked. So I traced the error log, and wrote a simple patch > attempting to commend some lines in > src/videoplayer/backend/streamdemuxer.cpp > > ``` > 289 //if(avCtx->codec_type == AVMEDIA_TYPE_VIDEO || avCtx->codec_type == > AVMEDIA_TYPE_AUDIO) > 290 // av_dict_set(, "refcounted_frames", "1", 0); > ``` > After recompile and reinstalling, the problem has gone, but I don't know > what the side effect is. There should be no side effects since that option was removed in recent ffmpeg. -- You are receiving this mail because: You are watching all bug changes.
[subtitlecomposer] [Bug 456804] Can't load any video, saying 'option refcounted_frames not found'
https://bugs.kde.org/show_bug.cgi?id=456804 Max changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #1 from Max --- It was already fixed in commit d8f9797 it will be included in next release. You should install subtitlecomposer-git from AUR, or from binary arch linux repo here: https://subtitlecomposer.kde.org/download.html -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 443082] Categories sidebar is located in the wrong place for optimal usability
https://bugs.kde.org/show_bug.cgi?id=443082 --- Comment #14 from Max --- It's not about requesting to change the launcher itself, it's about requesting new options and settings for it. Customizability is one the main principles behind the KDE software, so what's wrong about requesting more of it for a specific widget? I love the new Kickoff widget and it's design, but the sidebar placement causes inconveniences for me – it's not a reason to switch to the old legacy widget like you say, but def. the reason to request a single checkbox in widget settings to eliminate them. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 456657] Option to auto-hide title bar for maximized windows
https://bugs.kde.org/show_bug.cgi?id=456657 --- Comment #3 from Max --- Sorry, I misinterpreted the link you shared – it seems there's indeed an option to automatically hide title bars on maximized windows. But the point 2 still remains, as user can't access the title bar by hovering the top screen edge, he has to manually disable the borderless mode first. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 456657] Option to auto-hide title bar for maximized windows
https://bugs.kde.org/show_bug.cgi?id=456657 --- Comment #2 from Max --- 1) Borderless mode can not be set to trigger automatically on window maximize/unmaximize – it requires using a hotkey or the application menu 2) In currently available borderless mode user can not quickly access window's title bar by hovering the mouse over the top screen edge – the way it is shown on the attached gif -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 443082] Categories sidebar is located in the wrong place for optimal usability
https://bugs.kde.org/show_bug.cgi?id=443082 --- Comment #12 from Max --- Any update on this bug? It seems that Kickoff launcher still doesn't provide an option to place categories on the right side. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 456657] New: Option to auto-hide title bar for maximized windows
https://bugs.kde.org/show_bug.cgi?id=456657 Bug ID: 456657 Summary: Option to auto-hide title bar for maximized windows Product: kwin Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: maximts...@gmail.com Target Milestone: --- Created attachment 150571 --> https://bugs.kde.org/attachment.cgi?id=150571=edit Illustration of described behavior in Mac OS SUMMARY It would be great to have option for auto-hiding window's title bar when it is maximized, and reveal it on hover the top edge of the screen. It will help to maximize used screen space, while allowing to easily bring title bar back when needed to check window's title or drag window around. ADDITIONAL INFORMATION Similar behavior can be observed in Mac OS for maximized windows (demonstrated on attached GIF). -- You are receiving this mail because: You are watching all bug changes.
[libkgapi] [Bug 455383] Build fails on macOS
https://bugs.kde.org/show_bug.cgi?id=455383 Max Leiter changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #2 from Max Leiter --- Fixed in https://invent.kde.org/pim/libkgapi/-/merge_requests/28 -- You are receiving this mail because: You are watching all bug changes.
[libkgapi] [Bug 455383] Build fails on macOS
https://bugs.kde.org/show_bug.cgi?id=455383 --- Comment #1 from Max Leiter --- I've opened a merge request at https://invent.kde.org/pim/libkgapi/-/merge_requests/28 -- You are receiving this mail because: You are watching all bug changes.
