[kmymoney] [Bug 439865] kf5.kio.core: couldn't create slave: "Meldung von klauncher: Unbekanntes Protokoll „g“.\n"
https://bugs.kde.org/show_bug.cgi?id=439865 --- Comment #1 from Ralf Habacker --- >kf5.kio.core: couldn't create slave: "Meldung von klauncher: Unbekanntes > Protokoll „g“.\n" The term „g“ is the first character from the installation path "g:\..." on Windows, which probably indicates a problem in kio parsing a windows path url. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 439865] kf5.kio.core: couldn't create slave: "Meldung von klauncher: Unbekanntes Protokoll „g“.\n"
https://bugs.kde.org/show_bug.cgi?id=439865 Ralf Habacker changed: What|Removed |Added CC||kdelibs-b...@kde.org Component|general |general Product|kmymoney|frameworks-kio Assignee|kmymoney-de...@kde.org |kio-bugs-n...@kde.org Version|5.1.2 |5.83.0 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 420939] Baloo purge not completing
https://bugs.kde.org/show_bug.cgi?id=420939 --- Comment #29 from tagwer...@innerjoin.org --- (In reply to Scott from comment #27) > Created attachment 140064 [details] > Screen1 Interesting screenshot... I'd agree, strange that there's nothing shown after "Terms:" beyond the mimetype... In this instance, I'd find a completely different MP3, look at that and compare. I've just discovered that "exiftool", something I'd only considered as looking at metadata in image files, can also list the metadata for audio/video. Well, worked for me for a small sample of files. Try exiftool ...yourfile... -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 439869] New: pen pressure not working
https://bugs.kde.org/show_bug.cgi?id=439869 Bug ID: 439869 Summary: pen pressure not working Product: krita Version: 4.4.5 Platform: Other OS: Microsoft Windows Status: REPORTED Severity: major Priority: NOR Component: * Unknown Assignee: krita-bugs-n...@kde.org Reporter: skyelf102...@gmail.com Target Milestone: --- SUMMARY tried updating to the latest version, but still doesn't work, tried going into settings and manually adding pen pressure but still doesn't work. I know it's not my tablet because it works fine on other programs. I'm not sure what to do, krita is my preferred drawing program.. STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 405423] Can't change default search engine
https://bugs.kde.org/show_bug.cgi?id=405423 --- Comment #8 from Raphael Rosch --- The way I worked around it was to edit it in the source code and compile. If memory serves me right, I offered to look into it, fix it, and contribute the code (among other fixes for bugs that were affecting me -- like tab width size), but I never heard back from David. I eventually ended up no longer using falkon. It's a neat project with lots of potential, though, and am grateful it was available as an option when I needed an alternative. -- You are receiving this mail because: You are watching all bug changes.
[kfind] [Bug 439870] New: Use files index does not work for disks in /media
https://bugs.kde.org/show_bug.cgi?id=439870 Bug ID: 439870 Summary: Use files index does not work for disks in /media Product: kfind Version: 21.04.3 Platform: Neon Packages OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: francois072@e.email Target Milestone: --- SUMMARY When enabling use files index and I selected my other HDD no results are shown. STEPS TO REPRODUCE 1. Configure baloo to index disk in /media 2. Open Kfind and select the disk indexed in step 1. 3. Check "Use files index" box. 4. Click on "Find" button. OBSERVED RESULT No results are presented. EXPECTED RESULT Results should be instantly presented. Operating System: KDE neon 5.22 KDE Plasma Version: 5.22.3 KDE Frameworks Version: 5.84.0 Qt Version: 5.15.3 Kernel Version: 5.8.0-59-generic (64-bit) Graphics Platform: X11 ADDITIONAL INFORMATION Having "Use files index" box unchecked does present results for disk in /media. Having "Use files index" box checked does present results for user's home directory. /home/francois/.config/baloofilerc: [General] dbVersion=2 exclude filters=*~,*.part,*.o,*.la,*.lo,*.loT,*.moc,moc_*.cpp,qrc_*.cpp,ui_*.h,cmake_install.cmake,CMakeCache.txt,CTestTestfile.cmake,libtool,config.status,confdefs.h,autom4te,conftest,confstat,Makefile.am,*.gcode,.ninja_deps,.ninja_log,build.ninja,*.csproj,*.m4,*.rej,*.gmo,*.pc,*.omf,*.aux,*.tmp,*.po,*.vm*,*.nvram,*.rcore,*.swp,*.swap,lzo,litmain.sh,*.orig,.histfile.*,.xsession-errors*,*.map,*.so,*.a,*.db,*.qrc,*.ini,*.init,*.img,*.vdi,*.vbox*,vbox.log,*.qcow2,*.vmdk,*.vhd,*.vhdx,*.sql,*.sql.gz,*.ytdl,*.class,*.pyc,*.pyo,*.elc,*.qmlc,*.jsc,*.fastq,*.fq,*.gb,*.fasta,*.fna,*.gbff,*.faa,po,CVS,.svn,.git,_darcs,.bzr,.hg,CMakeFiles,CMakeTmp,CMakeTmpQmake,.moc,.obj,.pch,.uic,.npm,.yarn,.yarn-cache,__pycache__,node_modules,node_packages,nbproject,core-dumps,lost+found exclude filters version=8 folders[$e]=$HOME/,/media/francois/Storage/ index hidden folders=true only basic indexing=true -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 439269] Opening the settings dialog closes the applet even if it's pinned open
https://bugs.kde.org/show_bug.cgi?id=439269 --- Comment #7 from popov895 --- > Looks like it's fixed in Plasma 5.22.2. I was wrong. It's reproducible on KDE neon Unstable Edition (Plasma 5.22.80, Frameworks 5.85.0) -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 439871] New: Konsole segfaults
https://bugs.kde.org/show_bug.cgi?id=439871 Bug ID: 439871 Summary: Konsole segfaults Product: konsole Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: rgawe...@gmail.com Target Milestone: --- Application: konsole (21.07.80) Qt Version: 5.15.3 Frameworks Version: 5.85.0 Operating System: Linux 5.8.0-59-generic x86_64 Windowing System: X11 Drkonqi Version: 5.22.3 Distribution: KDE neon Testing Edition -- Information about the crash: - What I was doing when the application crashed: Trying to open konsole - System info Up to date KDE neon Testing Edition distribution KDE Plasma 5.22.3 Linux kernel 5.8.0.59-generic 64 bit The crash can be reproduced every time. -- Backtrace: Application: Konsole (konsole), signal: Segmentation fault [New LWP 77662] [New LWP 77663] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". 0x7fdea635aaff in __GI___poll (fds=0x7ffe2df5c8f8, nfds=1, timeout=1000) at ../sysdeps/unix/sysv/linux/poll.c:29 [Current thread is 1 (Thread 0x7fdea14489c0 (LWP 77661))] Thread 3 (Thread 0x7fde9f10f700 (LWP 77663)): #0 __GI___libc_read (nbytes=16, buf=0x7fde9f10e9a0, fd=7) at ../sysdeps/unix/sysv/linux/read.c:26 #1 __GI___libc_read (fd=7, buf=0x7fde9f10e9a0, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:24 #2 0x7fdea4909b2f in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fdea48c0ebe in g_main_context_check () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fdea48c1312 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7fdea48c14a3 in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7fdea6927fcb in QEventDispatcherGlib::processEvents (this=0x7fde9b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #7 0x7fdea68cc25b in QEventLoop::exec (this=this@entry=0x7fde9f10ebb0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:141 #8 0x7fdea66e5c22 in QThread::exec (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #9 0x7fdea576bf4b in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #10 0x7fdea66e6dbc in QThreadPrivate::start (arg=0x7fdea57efd80) at thread/qthread_unix.cpp:329 #11 0x7fdea5282609 in start_thread (arg=) at pthread_create.c:477 #12 0x7fdea6367293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7fdea03d8700 (LWP 77662)): #0 0x7fdea635aaff in __GI___poll (fds=0x7fdea03d7ae8, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7fdea44bbc1a in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7fdea44bd90a in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7fdea0b15e58 in QXcbEventQueue::run (this=0x557ba4568720) at qxcbeventqueue.cpp:228 #4 0x7fdea66e6dbc in QThreadPrivate::start (arg=0x557ba4568720) at thread/qthread_unix.cpp:329 #5 0x7fdea5282609 in start_thread (arg=) at pthread_create.c:477 #6 0x7fdea6367293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 1 (Thread 0x7fdea14489c0 (LWP 77661)): [KCrash Handler] #4 0x7fdea6d757d5 in qGetPtrHelper > const> (ptr=...) at ../../include/QtCore/../../src/corelib/global/qglobal.h:1143 #5 QWindow::d_func (this=0x0) at ../../include/QtGui/../../src/gui/kernel/qwindow.h:98 #6 QWindow::winId (this=this@entry=0x0) at kernel/qwindow.cpp:663 #7 0x7fdea5fd0943 in KWindowEffects::enableBlurBehind (window=0x0, enable=, region=...) at ./src/kwindoweffects.cpp:45 #8 0x7fdea7ce54d3 in Konsole::MainWindow::setBlur (blur=true, this=0x557ba47a8e40) at ./src/MainWindow.cpp:892 #9 Konsole::MainWindow::setBlur (this=0x557ba47a8e40, blur=) at ./src/MainWindow.cpp:876 #10 0x7fdea7ce8c52 in Konsole::MainWindow::activeViewChanged (controller=0x557ba471f850, this=0x557ba47a8e40) at /usr/include/c++/9/bits/atomic_base.h:413 #11 Konsole::MainWindow::activeViewChanged (this=0x557ba47a8e40, controller=0x557ba471f850) at ./src/MainWindow.cpp:243 #12 0x7fdea690477e in QtPrivate::QSlotObjectBase::call (a=0x7ffe2df5d820, r=0x557ba47a8e40, this=0x557ba4822590) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #13 doActivate (sender=0x557ba47f6d70, signal_index=5, argv=0x7ffe2df5d820) at kernel/qobject.cpp:3886 #14 0x7fdea7b78216 in Konsole::ViewManager::activeViewChanged(Konsole::SessionController*) () from /usr/lib/x86_64-linux-gnu/libkonsoleprivate.so.21 #15 0x7fdea7ba838b in Konsole::ViewManager::controllerChanged(Konsole::SessionController*) () from /usr/lib/x86_64-linux-gnu/libkonsoleprivate.so.21 #16 0x7fdea7ba8717 in Konsole::ViewManager::createController(Konsol
[kwin] [Bug 391322] Meta key randomly stops opening Plasma launcher menu
https://bugs.kde.org/show_bug.cgi?id=391322 Bryan Pedini changed: What|Removed |Added CC||b.ped...@bjphoster.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 436999] New calendar renders too many dots for months and years view
https://bugs.kde.org/show_bug.cgi?id=436999 popov895 changed: What|Removed |Added CC||popov...@ukr.net --- Comment #4 from popov895 --- Created attachment 140069 --> https://bugs.kde.org/attachment.cgi?id=140069&action=edit Multiple dots in the Calendar applet I observe something like this, so I didn't file a new bug, but reopened this one. STEPS TO REPRODUCE 1. Open Digital Clock applet 2. Check "Keep Open" button in the top right corner 3. Open Settings dialog (clicking "Configure Digital Clock..." button or menuitem with the same name in the context menu) and close it 4. Repeat step 3 several times SOFTWARE/OS VERSIONS Operating System: KDE neon Unstable Edition KDE Plasma Version: 5.22.80 KDE Frameworks Version: 5.85.0 Qt Version: 5.15.3 Graphics Platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 436999] New calendar renders too many dots for months and years view
https://bugs.kde.org/show_bug.cgi?id=436999 --- Comment #5 from popov895 --- Created attachment 140070 --> https://bugs.kde.org/attachment.cgi?id=140070&action=edit Multiple dots in month view Same on month view, but not in years view. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 439871] Konsole segfaults
https://bugs.kde.org/show_bug.cgi?id=439871 --- Comment #1 from netizen --- I can open it from an xterm as root, gathering more info now... -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 439872] New: plasma-systemmonitor crashes at launch
https://bugs.kde.org/show_bug.cgi?id=439872 Bug ID: 439872 Summary: plasma-systemmonitor crashes at launch Product: plasma-systemmonitor Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: qydwhotm...@gmail.com CC: ahiems...@heimr.nl, plasma-b...@kde.org Target Milestone: --- Created attachment 140071 --> https://bugs.kde.org/attachment.cgi?id=140071&action=edit Backtrace SUMMARY Cannot open systemmonitor because it constantly crashes. STEPS TO REPRODUCE 1. Open plasma-systemmonitor form Kickoff OBSERVED RESULT plasma-systemmonitor crashes. EXPECTED RESULT plasma-systemmonitor launches. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20210712 KDE Plasma Version: 5.22.80 KDE Frameworks Version: 5.85.0 Qt Version: 5.15.2 Kernel Version: 5.13.0-1-default (64-bit) Graphics Platform: X11 Processors: 8 × AMD Ryzen 7 4700U with Radeon Graphics Memory: 15.0 GiB of RAM Graphics Processor: AMD RENOIR ADDITIONAL INFORMATION Backtrace log in attachment # zypper info plasma5-systemmonitor Loading repository data... Reading installed packages... Information for package plasma5-systemmonitor: -- Repository : unstable-kde-frameworks Name : plasma5-systemmonitor Version: 5.22.80git.20210712T145851~2aa482c-ku.21.1 Arch : x86_64 Vendor : obs://build.opensuse.org/KDE:Unstable Installed Size : 676.1 KiB Installed : Yes (automatically) Status : up-to-date Source package : plasma5-systemmonitor-5.22.80git.20210712T145851~2aa482c-ku.21.1.src Summary: An application for monitoring system resources Description: plasma-systemmonitor provides an interface for monitoring system sensors, process information and other system resources. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 439873] New: Switching users isn't working
https://bugs.kde.org/show_bug.cgi?id=439873 Bug ID: 439873 Summary: Switching users isn't working Product: plasmashell Version: master Platform: Neon Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: techxga...@outlook.com CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY Switching users causes the screen to go black. Had to do a hard reboot. STEPS TO REPRODUCE 1. Open Application Launcher 2. Select Switch User OBSERVED RESULT Screen goes black and freezes. EXPECTED RESULT Should be able to switch users normally SOFTWARE/OS VERSIONS Operating System: KDE neon Unstable Edition KDE Plasma Version: 5.22.80 KDE Frameworks Version: 5.85.0 Qt Version: 5.15.3 Kernel Version: 5.8.0-59-generic (64-bit) Graphics Platform: Wayland Processors: 4 × Intel® Core™ i7-4510U CPU @ 2.00GHz Memory: 15.5 GiB of RAM Graphics Processor: Mesa DRI Intel® HD Graphics 4400 ADDITIONAL INFORMATION Not sure if being Wayland has anything to do with it. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 439869] pen pressure not working
https://bugs.kde.org/show_bug.cgi?id=439869 Halla Rempt changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED Severity|major |normal CC||ha...@valdyas.org Component|* Unknown |Tablets (tablet issues are ||only very rarely bugs in ||Krita!) Platform|Other |Microsoft Windows --- Comment #1 from Halla Rempt --- Sorry, problems with pressure support are never bugs in Krita, and always issues with your setup. There is plenty of information on investigating those setup issues in the documentation and on krita-artists.org. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 439856] Pen pressure isn't working, working fine up until now, nothing is different and the pressure works with other apps,
https://bugs.kde.org/show_bug.cgi?id=439856 Halla Rempt changed: What|Removed |Added Platform|Other |Microsoft Windows Component|* Unknown |Tablets (tablet issues are ||only very rarely bugs in ||Krita!) CC||ha...@valdyas.org Severity|major |normal Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Halla Rempt --- It's useless to report something that isn't a bug in the first place, while not gfiving any useful information, twice. This isn't a place to get user support: go to krita-artists.org for that. *** This bug has been marked as a duplicate of bug 439869 *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 439869] pen pressure not working
https://bugs.kde.org/show_bug.cgi?id=439869 --- Comment #2 from Halla Rempt --- *** Bug 439856 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 439862] cosmetic artifacts on canvas 5.0.0-prealpha (git c75e336)
https://bugs.kde.org/show_bug.cgi?id=439862 Halla Rempt changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO CC||ha...@valdyas.org --- Comment #2 from Halla Rempt --- Are you really using the CPU canvas? Or are you using the OpenGL canvas -- i.e. canvas acceleration is enabled? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 439863] Problem with Downloads
https://bugs.kde.org/show_bug.cgi?id=439863 Halla Rempt changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED CC||ha...@valdyas.org --- Comment #1 from Halla Rempt --- Sorry, this isn't a bug in Krita. If you have trouble downloading, your location might be served with a mirror that's broken. Please go to download.kde.org/stable/krita/4.4.5, click on the details link and choose a different mirror. -- You are receiving this mail because: You are watching all bug changes.
[libalkimia] [Bug 439874] New: Add support to handle http status code 410
https://bugs.kde.org/show_bug.cgi?id=439874 Bug ID: 439874 Summary: Add support to handle http status code 410 Product: libalkimia Version: 8.1.0 Platform: Other OS: All Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: kmymoney-de...@kde.org Reporter: ralf.habac...@freenet.de Target Milestone: --- SUMMARY On access to http://finanztreff.de/kurse_einzelkurs_detail.htn?u=100&i=ORCL the response code is [11436] kf5.kio.kio_http: Received Status Response: [11436] kf5.kio.kio_http: "HTTP/1.1 410 Gone" [11436] kf5.kio.kio_http: QUrl("http://finanztreff.de/kurse_einzelkurs_detail.htn?u=100&i=ORCL";) response code: 410 previous response code: 0 indicating that the service isn't available anymore. This should be handled by alkimia on fetching online quotes, e.g. by informing the user about that state. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 439875] New: Plasma crash when exiting latte dock "panel settings" mode after removing a plasmoid
https://bugs.kde.org/show_bug.cgi?id=439875 Bug ID: 439875 Summary: Plasma crash when exiting latte dock "panel settings" mode after removing a plasmoid Product: plasmashell Version: 5.22.3 Platform: Archlinux Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: kde-b...@growse.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.22.3) Qt Version: 5.15.2 Frameworks Version: 5.84.0 Operating System: Linux 5.12.15-arch1-1 x86_64 Windowing System: Wayland Drkonqi Version: 5.22.3 Distribution: Arch Linux -- Information about the crash: - What I was doing when the application crashed: On Arch linux, using latte-dock 0.9.12, I had added a plasmoid to a panel, but wanted to remove it. With the "Add Widgets" screen open, I put latte dock into "panel settings" mode to remove the widget, and then when focussing on the "Add Widgets" window again, plasma crashed. The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault [KCrash Handler] #4 0x7fa560276813 in QQuickWindowPrivate::sendFilteredPointerEventImpl(QQuickPointerEvent*, QQuickItem*, QQuickItem*) () from /usr/lib/libQt5Quick.so.5 #5 0x7fa560276727 in QQuickWindowPrivate::sendFilteredPointerEventImpl(QQuickPointerEvent*, QQuickItem*, QQuickItem*) () from /usr/lib/libQt5Quick.so.5 #6 0x7fa560276727 in QQuickWindowPrivate::sendFilteredPointerEventImpl(QQuickPointerEvent*, QQuickItem*, QQuickItem*) () from /usr/lib/libQt5Quick.so.5 #7 0x7fa560276727 in QQuickWindowPrivate::sendFilteredPointerEventImpl(QQuickPointerEvent*, QQuickItem*, QQuickItem*) () from /usr/lib/libQt5Quick.so.5 #8 0x7fa56027d973 in QQuickWindowPrivate::deliverMouseEvent(QQuickPointerMouseEvent*) () from /usr/lib/libQt5Quick.so.5 #9 0x7fa56027f2fc in QQuickWindowPrivate::deliverPointerEvent(QQuickPointerEvent*) () from /usr/lib/libQt5Quick.so.5 #10 0x7fa55ec0a635 in QWindow::event(QEvent*) () from /usr/lib/libQt5Gui.so.5 #11 0x7fa55f4fdd62 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5 #12 0x7fa55e8253aa in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/libQt5Core.so.5 #13 0x7fa55ebfe210 in QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) () from /usr/lib/libQt5Gui.so.5 #14 0x7fa55ebd37e5 in QWindowSystemInterface::sendWindowSystemEvents(QFlags) () from /usr/lib/libQt5Gui.so.5 #15 0x7fa55c3d3101 in ?? () from /usr/lib/libQt5WaylandClient.so.5 #16 0x7fa55cb2210c in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #17 0x7fa55cb75b99 in ?? () from /usr/lib/libglib-2.0.so.0 #18 0x7fa55cb1f871 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #19 0x7fa55e87dfd6 in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #20 0x7fa55e823d1c in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #21 0x7fa55e82c284 in QCoreApplication::exec() () from /usr/lib/libQt5Core.so.5 #22 0x55593966521a in ?? () #23 0x7fa55e1afb25 in __libc_start_main () from /usr/lib/libc.so.6 #24 0x55593966534e in ?? () [Inferior 1 (process 1592) detached] Possible duplicates by query: bug 439716, bug 439100, bug 436640, bug 435261, bug 434868. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 420939] Baloo purge not completing
https://bugs.kde.org/show_bug.cgi?id=420939 --- Comment #30 from Scott --- Seems we had a mid-air collision and my last post was lost as it was submitted at the same time you submitted your last post, anyway to briefly recap. Firstly, just to confirm, what is the correct config setting/syntax to enable content indexing: 1/ Remove the line, only basic indexing=true, or, 2/ Include the line, only basic indexing=false Baloo is part,n parcel of Kubuntu and should work straight out-of-the-box, just like my monitor or speakers. There should be no need to install programs for baloo to work. Following your instructions I have demonstrated that the expected indexing does not occur. So we can confirm that this preceding step, to the issues you identified in an earlier post, is a problem. It is clear that baloo should index duration (the play time of a music piece) as is evidenced by the selectable field in Dolphin, Audi>Duration. As you are likely aware, issues surrounding the usability of baloo have been around for many years, I have been trying to use it for 7 years without success. This bug was originally about purging and now it throws up issues with initial indexing, which is also mentioned early on in the dialogue of the bug. I think though that someone needs to decide what baloo is supposed to do, is it supposed to collect audio/visual file metadata? If yes, it fails and that is the first bug as is amply demonstrated by the numerous bug reports about baloo and metadata information not appearing. If no, then Dolphin needs to be amended so these metadata fields are not accessible. If I have to install extra software so baloo might work I am not really interested, I can do what I have done and install other software that gives me durations which are also visible from remote computers which baloo cannot do. >From the information in this post it is clear that multiple people have an issue with baloo not indexing correctly. Is it possible to just fix that issue first and then revisit the other downstream issues? Better yet, why don't we use a file manager that can read metadata and give baloo the heave-ho. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 437626] Krita crashes on save when documents are too large, and contain procedural layers
https://bugs.kde.org/show_bug.cgi?id=437626 Halla Rempt changed: What|Removed |Added Version|4.4.3 |4.4.2 --- Comment #23 from Halla Rempt --- Could you please update to 4.4.5 and check whether that still happens? I see a lot of asserts in the log, and that's rather scary. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 439876] New: When setting Okular as default PDF viewer, issue when I double click file.
https://bugs.kde.org/show_bug.cgi?id=439876 Bug ID: 439876 Summary: When setting Okular as default PDF viewer, issue when I double click file. Product: okular Version: 20.12.2 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: PDF backend Assignee: okular-de...@kde.org Reporter: markbaber1...@live.co.uk Target Milestone: --- Created attachment 140072 --> https://bugs.kde.org/attachment.cgi?id=140072&action=edit Okular issue Windows 10 SUMMARY Whenever I set Okular as my default PDF viewer and open a file, there seems to be a saved 'session' from the last PDF file I opened. This looks like it has cached a screenshot or something and I have added an attachment. I have tried to delete Okular and reinstall it, but noticed the issue keeps happening - I can get around this by opening Okular and opening the PDF file via the File-Open. STEPS TO REPRODUCE 1. Set Okular as default PDF viewer on Windows 2. Double click a PDF file 3. Check if this looks like my attachment OBSERVED RESULT Have a snippet of the last PDF file which was opened, along with the first page of the new PDF file i've opened. EXPECTED RESULT Open the PDF file which was clicked to open. SOFTWARE/OS VERSIONS Windows: 10 - 21H1 - 19043.1110 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.
[dolphin] [Bug 439877] New: Dolphin crashes when right-clicking on file oro folder to summon the contextual menu
https://bugs.kde.org/show_bug.cgi?id=439877 Bug ID: 439877 Summary: Dolphin crashes when right-clicking on file oro folder to summon the contextual menu Product: dolphin Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: paul.br...@kde.org CC: kfm-de...@kde.org Target Milestone: --- Application: dolphin (21.11.70) Qt Version: 5.15.3 Frameworks Version: 5.85.0 Operating System: Linux 5.8.0-59-generic x86_64 Windowing System: X11 Distribution: KDE neon Unstable Edition DrKonqi: 5.22.80 [CoredumpBackend] -- Information about the crash: - What I was doing when the application crashed: Open Dolphin, right click on a file to summon the contextual menu. After a second or less, Dolphin crahses evert time. The crash can be reproduced every time. -- Backtrace: Application: Dolphin (dolphin), signal: Segmentation fault [New LWP 1547] [New LWP 1404] [New LWP 1409] [New LWP 1410] [New LWP 1411] [New LWP 1412] [New LWP 1401] [New LWP 1413] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Core was generated by `/usr/bin/dolphin'. Program terminated with signal SIGSEGV, Segmentation fault. #0 __GI_raise (sig=) at ../sysdeps/unix/sysv/linux/raise.c:50 [Current thread is 1 (Thread 0x7f979fbc3700 (LWP 1547))] [Current thread is 1 (Thread 0x7f979fbc3700 (LWP 1547))] Thread 8 (Thread 0x7fd7c4856700 (LWP 1413)): #0 0x7fd7dfc23aff in __GI___poll (fds=0x7fd7a4005240, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7fd7ddbf836e in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fd7ddbf84a3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fd7e01f0fb2 in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fd7e019525b in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fd7dffaec22 in QThread::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fd7dffafdbc in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fd7de676609 in start_thread (arg=) at pthread_create.c:477 #8 0x7fd7dfc30293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 7 (Thread 0x7fd7db1ed600 (LWP 1401)): #0 syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 #1 0x7fd7dffb2061 in QSemaphore::acquire(int) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7fd7e01cd6e2 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7fd7e01c6c03 in QObject::destroyed(QObject*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fd7e01cb9d5 in QObject::~QObject() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fd7e2184ede in KBookmarkManager::~KBookmarkManager() () from /lib/x86_64-linux-gnu/libKF5Bookmarks.so.5 #6 0x7fd7e218501d in KBookmarkManager::~KBookmarkManager() () from /lib/x86_64-linux-gnu/libKF5Bookmarks.so.5 #7 0x7fd7e218482e in ?? () from /lib/x86_64-linux-gnu/libKF5Bookmarks.so.5 #8 0x7fd7dfb57a27 in __run_exit_handlers (status=1, listp=0x7fd7dfcf9718 <__exit_funcs>, run_list_atexit=run_list_atexit@entry=true, run_dtors=run_dtors@entry=true) at exit.c:108 #9 0x7fd7dfb57be0 in __GI_exit (status=) at exit.c:139 #10 0x7fd7da892d97 in ?? () from /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #11 0x7fd7da8c5e77 in ?? () from /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #12 0x7fd7ddbf817d in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #13 0x7fd7ddbf8400 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #14 0x7fd7ddbf84a3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #15 0x7fd7e01f0fb2 in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #16 0x7fd7e019525b in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #17 0x7fd7e0dfea88 in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #18 0x7fd7e0dfebb3 in QMenu::exec(QPoint const&, QAction*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #19 0x55a96c9b4af9 in DolphinContextMenu::openItemContextMenu (this=this@entry=0x55a96e9c30f0) at ./src/dolphincontextmenu.cpp:298 #20 0x55a96c9b5148 in DolphinContextMenu::open (this=this@entry=0x55a96e9c30f0) at ./src/dolphincontextmenu.cpp:112 #21 0x55a96c9aa67d in DolphinMainWindow::openContextMenu (this=0x55a96d969de0, pos=..., item=..., url=..., customActions=...) at /usr/include/c++/9/bits/atomic_base.h:413 #22 0x7fd7e01cd77e in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #23 0x7fd7e2315488 in DolphinView::requestContextMenu (this=this@entry=0x55a96e2f47d0, _t1=..., _t2=..
[plasma-systemmonitor] [Bug 438318] Some AMD gpu (lm-sensors-based?) sensors no longer available
https://bugs.kde.org/show_bug.cgi?id=438318 David Redondo changed: What|Removed |Added CC||k...@david-redondo.de --- Comment #6 from David Redondo --- The cause of the problem is, that in the new sensors plugin coretemp, k10temp and amdgpu are intentionally excluded to not expose duplicated sensors because these are already handles by the CPU and GPU plugins. However those do not expose all of the available sensors. For the amd gpu case it's possible to map gpu to sensors using the PCI address, so they can belong to GPU in the ui which makes more sense than in the hardware sensors dumping ground. For coretemp, do you have a specific use case for monitoring the package temperature instead of for example core temps? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 439878] New: Breeze GTK theme is messing with Pamac
https://bugs.kde.org/show_bug.cgi?id=439878 Bug ID: 439878 Summary: Breeze GTK theme is messing with Pamac Product: plasmashell Version: 5.22.3 Platform: Other OS: Linux Status: REPORTED Severity: major Priority: NOR Component: Theme - Breeze Assignee: visual-des...@kde.org Reporter: med.medin.2...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 140073 --> https://bugs.kde.org/attachment.cgi?id=140073&action=edit Breeze GTK theme is messing with Pamac This bug is creating high tension on Manjaro forum after latest Pamac update 13/07, it seems the real problem is that Breeze theme for GTK apps is not updated. See attached image for comparison between Breeze and Adwaita themes. Operating System: Manjaro Linux KDE Plasma Version: 5.22.3 KDE Frameworks Version: 5.84.0 Qt Version: 5.15.2 Kernel Version: 5.4.131-1-MANJARO (64-bit) Graphics Platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 439879] New: White corners
https://bugs.kde.org/show_bug.cgi?id=439879 Bug ID: 439879 Summary: White corners Product: plasmashell Version: 5.22.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: med.medin.2...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 140074 --> https://bugs.kde.org/attachment.cgi?id=140074&action=edit White corners It seems 5.22 update broke Breeze theme. See attached image for more info. -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 438318] Some AMD gpu (lm-sensors-based?) sensors no longer available
https://bugs.kde.org/show_bug.cgi?id=438318 --- Comment #7 from Artem --- Well, I would like to have the correct information about the CPU temperature. The "sensors" command shows that the temperatures of the processor in general and specific cores in particular may differ, so using the temperature of a specific core is not a correct solution to the problem. The output of the temperature of all the cores in one chart will look very bulky and inconvenient for perception. System Monitor already has a group of sensors "CPUs -> All", where there are sensors of the total CPU load. But why do they exist, if you can use the load of a specific core? (irony) In my opinion, it would be quite consistent to add the value of the package temperature to the "CPUs -> All" group. -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 438318] Some AMD gpu (lm-sensors-based?) sensors no longer available
https://bugs.kde.org/show_bug.cgi?id=438318 --- Comment #8 from Matthias Mueller --- My usecase is/was monitoring the GPU-Power - i guess the mentioned mapping of PCI-adresses is nothing that can be done in userspace but has to be patched in? Or am i missing something? -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 438318] Some AMD gpu (lm-sensors-based?) sensors no longer available
https://bugs.kde.org/show_bug.cgi?id=438318 --- Comment #9 from David Redondo --- Thanks Artem, that's a good idea. > PCI-adresses is nothing that can be done in userspace but has to be patched > in? Or am i missing something? Yes it has to be done in the code. I mentioned it because I am currently working on it. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 439880] New: Shadow corners are more darker
https://bugs.kde.org/show_bug.cgi?id=439880 Bug ID: 439880 Summary: Shadow corners are more darker Product: plasmashell Version: 5.22.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Theme - Breeze Assignee: visual-des...@kde.org Reporter: med.medin.2...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 140075 --> https://bugs.kde.org/attachment.cgi?id=140075&action=edit Shadow corners are more darker See attached image for more info. Operating System: Manjaro Linux KDE Plasma Version: 5.22.3 KDE Frameworks Version: 5.84.0 Qt Version: 5.15.2 Kernel Version: 5.4.131-1-MANJARO (64-bit) Graphics Platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 439565] In the Reports export there is no more option to save as html or csv
https://bugs.kde.org/show_bug.cgi?id=439565 Dawid Wróbel changed: What|Removed |Added Status|REPORTED|RESOLVED Latest Commit||https://invent.kde.org/pack ||aging/craft-blueprints-kde/ ||commit/3af80a6b818477622776 ||e300b6d85a60444329e9 Resolution|--- |FIXED --- Comment #2 from Dawid Wróbel --- Git commit 3af80a6b818477622776e300b6d85a60444329e9 by Dawid Wróbel. Committed on 15/07/2021 at 10:17. Pushed by wrobelda into branch 'master'. kmymoney: do not blacklist MIME info M +0-1extragear/kmymoney/blacklist.txt https://invent.kde.org/packaging/craft-blueprints-kde/commit/3af80a6b818477622776e300b6d85a60444329e9 -- You are receiving this mail because: You are watching all bug changes.
[Craft] [Bug 429511] QMimeDatabase: Error loading internal MIME data
https://bugs.kde.org/show_bug.cgi?id=429511 Dawid Wróbel changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=439565 CC||m...@dawidwrobel.com -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 439565] In the Reports export there is no more option to save as html or csv
https://bugs.kde.org/show_bug.cgi?id=439565 Dawid Wróbel changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=429511 -- You are receiving this mail because: You are watching all bug changes.
[Craft] [Bug 429511] QMimeDatabase: Error loading internal MIME data
https://bugs.kde.org/show_bug.cgi?id=429511 Dawid Wróbel changed: What|Removed |Added See Also|https://bugs.kde.org/show_b | |ug.cgi?id=439565| -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 439565] In the Reports export there is no more option to save as html or csv
https://bugs.kde.org/show_bug.cgi?id=439565 Dawid Wróbel changed: What|Removed |Added See Also|https://bugs.kde.org/show_b | |ug.cgi?id=429511| -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 439868] QMimeDatabase: Error loading internal MIME data
https://bugs.kde.org/show_bug.cgi?id=439868 Dawid Wróbel changed: What|Removed |Added CC||m...@dawidwrobel.com See Also||https://bugs.kde.org/show_b ||ug.cgi?id=439565 -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 439565] In the Reports export there is no more option to save as html or csv
https://bugs.kde.org/show_bug.cgi?id=439565 Dawid Wróbel changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=439868 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 439881] New: Calendar weird look
https://bugs.kde.org/show_bug.cgi?id=439881 Bug ID: 439881 Summary: Calendar weird look Product: plasmashell Version: 5.22.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Calendar Assignee: plasma-b...@kde.org Reporter: med.medin.2...@gmail.com Target Milestone: 1.0 Created attachment 140076 --> https://bugs.kde.org/attachment.cgi?id=140076&action=edit Calendar weird look The year, month, and day tabs sometimes show short horizontal bar that grow after moving mouse, and events area has weird horizontal scrollbar. See attached video for more info. Operating System: Manjaro Linux KDE Plasma Version: 5.22.3 KDE Frameworks Version: 5.84.0 Qt Version: 5.15.2 Kernel Version: 5.4.131-1-MANJARO (64-bit) Graphics Platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 439867] error: Cannot load library ...\bin\kmymoney\woob.dll
https://bugs.kde.org/show_bug.cgi?id=439867 Dawid Wróbel changed: What|Removed |Added CC||m...@dawidwrobel.com Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #1 from Dawid Wróbel --- *** This bug has been marked as a duplicate of bug 438977 *** -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 426400] Fix KF5 issues on Windows
https://bugs.kde.org/show_bug.cgi?id=426400 Bug 426400 depends on bug 439867, which changed state. Bug 439867 Summary: error: Cannot load library ...\bin\kmymoney\woob.dll https://bugs.kde.org/show_bug.cgi?id=439867 What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 438977] AppImage doesn't start
https://bugs.kde.org/show_bug.cgi?id=438977 Dawid Wróbel changed: What|Removed |Added CC||ralf.habac...@freenet.de --- Comment #3 from Dawid Wróbel --- *** Bug 439867 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kfind] [Bug 439870] Use files index does not work for disks in /media
https://bugs.kde.org/show_bug.cgi?id=439870 tagwer...@innerjoin.org changed: What|Removed |Added CC||tagwer...@innerjoin.org --- Comment #1 from tagwer...@innerjoin.org --- (In reply to francois072 from comment #0) > 1. Configure baloo to index disk in /media That means you should be able to change directory in Dolphin to /media/francois/Storage/ and start typing a filename for baloo to find. The Dolphin search dialog should look like: https://bugsfiles.kde.org/attachment.cgi?id=137169 (Taken from in Bug 435119) which means Dolphin is using baloo You can also do: baloosearch ...fileinyourmediafolders... and see if it finds the file... > 2. Open Kfind and select the disk indexed in step 1. Here you've switched to using a different search tool... > 3. Check "Use files index" box. The "Use files index" means "You've created a file index with the 'updatedb' program, look through this to find the files you want..." > 4. Click on "Find" button. > Having "Use files index" box unchecked does present results for disk in > /media. In this case KFind looks though your /media directory structure "there and then" and lists the matches. > Having "Use files index" box checked does present results for user's home > directory. That implies (I think) that mlocate and updatedb are installed, just that updatedb isn't indexing your /media folders. -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 438318] Some AMD gpu (lm-sensors-based?) sensors no longer available
https://bugs.kde.org/show_bug.cgi?id=438318 --- Comment #10 from Artem --- David Redondo, that is, can we expect that this will be fixed after some time? Should I start a separate issue on GitLab, or is it enough just to observe the current development? I doubt that I will be able to implement such a change on my own, so I can only hope for you. -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 438318] Some AMD gpu (lm-sensors-based?) sensors no longer available
https://bugs.kde.org/show_bug.cgi?id=438318 --- Comment #11 from David Redondo --- This bug report is sufficient to track the issue -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 439477] Clicking on links in Qt/KDE apps causes the website to be cached, rather than the link being forwarded to the browser
https://bugs.kde.org/show_bug.cgi?id=439477 --- Comment #11 from Manuel Geißer --- Yeah, I'll do that. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 439518] Deleting an active sieve script leaves sieve unfunctional (using Dovecot)
https://bugs.kde.org/show_bug.cgi?id=439518 Laurent Montel changed: What|Removed |Added CC||mon...@kde.org --- Comment #1 from Laurent Montel --- I need to make a big change in libksieve for doing it. It's on my todo list 21.12 -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 439872] plasma-systemmonitor crashes at launch
https://bugs.kde.org/show_bug.cgi?id=439872 qydwhotm...@gmail.com changed: What|Removed |Added Keywords||drkonqi -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 439518] Deleting an active sieve script leaves sieve unfunctional (using Dovecot)
https://bugs.kde.org/show_bug.cgi?id=439518 Tobias Leupold changed: What|Removed |Added CC||t...@l3u.de --- Comment #2 from Tobias Leupold --- Nice if this is on the to do list :-) I also asked the Dovecot mailing list about this problem. The final statement was that handling this correctly is up to the managesieve client. Thanks in advance for addressing this! -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 439877] Dolphin crashes when right-clicking on file or folder to summon the contextual menu
https://bugs.kde.org/show_bug.cgi?id=439877 Paul Brown changed: What|Removed |Added Summary|Dolphin crashes when|Dolphin crashes when |right-clicking on file oro |right-clicking on file or |folder to summon the|folder to summon the |contextual menu |contextual menu -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 439876] When setting Okular as default PDF viewer, issue when I double click file.
https://bugs.kde.org/show_bug.cgi?id=439876 David Hurka changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #1 from David Hurka --- Looks strange, no idea what could cause this. Have you verified that it is actually a part of the last PDF file you opened? I. e. have you tried to open different PDF files in series, and the first “page” looks different depending on the last file? Can you look what File -> Properties says? Does it report one page too much for the current document? Can you look whether the wrong “page” also appears in File -> Print Preview? > Component: PDF backend Have you tried it with different file types? Okular can also open e. g. .txt and .ps and so on. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 439882] New: Account retrieval error
https://bugs.kde.org/show_bug.cgi?id=439882 Bug ID: 439882 Summary: Account retrieval error Product: kmymoney Version: 5.1.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: onlinebanking Assignee: kmymoney-de...@kde.org Reporter: bugzi...@lubich.com Target Milestone: --- Since version 5.1.2 it happens again and again that my PIN is incorrect. "+9050::Die Nachricht enthält Fehler.+9800::Dialog abgebrochen+9340::Auftrag abgelehnt." This has already occurred three times this month and is incomprehensible to me because I work with KeePassXC (and I selected the bank correctly). If I had this error message every two or three months before, I could understand that I had selected the wrong bank. But the frequency this month (and with this version) is amazing. I would like to exclude KeePassXC (Version 2.6.6 since June 17th) for the time being. Greetings Udo SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.18.6 KDE Frameworks Version: 5.71.0 Qt Version: 5.12.7 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 420939] Baloo purge not completing
https://bugs.kde.org/show_bug.cgi?id=420939 --- Comment #31 from tagwer...@innerjoin.org --- (In reply to Scott from comment #30) > ... just to confirm, what is the correct config setting/syntax to > enable content indexing: > 1/ Remove the line, only basic indexing=true, or, > 2/ Include the line, only basic indexing=false Yes. Or go through "System Settings > Search > File Search" and you'll see an "Also index file content" checkbox. > It is clear that baloo should index duration (the play time of a music > piece) as is evidenced by the selectable field in Dolphin, Audio>Duration. The question is, where has the "duration" information got lost. >From your screenshot (with balooshow), baloo hasn't extracted it. On to the next step... If you run 'exiftool' on the file, you should see if the information is there in the file. If it is, then there's a bug in the extractor. If exiftool does not show the info, then maybe there's an issue with the file. A useful comparative test is to download and try a different MP3 file... In general I see the "Duration" listed for the MP3's I've checked (in Dolphin and listed by "balooshow -x" and exiftool). I don't see much info for videos (a little and maybe not sufficient) even with exiftool. I think yes, it's good that baloo tries to extract embedded metadata from the files. However, it's clearly a horrible, messy job to have to do. As far as I remember I installed exiftool on Neon with: sudo apt install libimage-exiftool-perl It is handy, solid and straightforward -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 433107] Wayland: iGPU/AMDGPU multi-monitor keeps displaying the SDDM screen if iGPU-DisplayPort is connected
https://bugs.kde.org/show_bug.cgi?id=433107 --- Comment #26 from Zamundaaa --- Git commit afcef2a6f822c46d3167f4b49bb8a3b13696c8c8 by Xaver Hugl. Committed on 15/07/2021 at 11:42. Pushed by zamundaaa into branch 'master'. platforms/drm: fix crash with secondary GPUs and buffer age M +2-1src/plugins/platforms/drm/abstract_egl_drm_backend.h M +24 -12 src/plugins/platforms/drm/egl_gbm_backend.cpp M +4-3src/plugins/platforms/drm/egl_gbm_backend.h M +1-1src/plugins/platforms/drm/egl_stream_backend.cpp https://invent.kde.org/plasma/kwin/commit/afcef2a6f822c46d3167f4b49bb8a3b13696c8c8 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 433107] Wayland: iGPU/AMDGPU multi-monitor keeps displaying the SDDM screen if iGPU-DisplayPort is connected
https://bugs.kde.org/show_bug.cgi?id=433107 --- Comment #27 from Zamundaaa --- crash should be fixed (at least it works with vkms) -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 432405] Photo Meta Data such as "Data Photographed" Not Showing Up
https://bugs.kde.org/show_bug.cgi?id=432405 tagwer...@innerjoin.org changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #3 from tagwer...@innerjoin.org --- Ping :-) -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 439883] New: onlinequoteeditor5 not included in kmymoney binaries generated by KDE CI
https://bugs.kde.org/show_bug.cgi?id=439883 Bug ID: 439883 Summary: onlinequoteeditor5 not included in kmymoney binaries generated by KDE CI Product: kmymoney Version: 5.1.2 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: packaging Assignee: kmymoney-de...@kde.org Reporter: ralf.habac...@freenet.de Target Milestone: --- onlinequoteeditor is provided by the alkimia package, which is included in binary builds for kmymoney, but the mentioned executable is excluded by packaging. STEPS TO REPRODUCE 1. download kmymoney binary build from https://binary-factory.kde.org/job/KMyMoney_Nightly_win64/ 2. unpack the archive and inspect the bin folder OBSERVED RESULT There is no file named onlinequoteeditor5.exe EXPECTED RESULT That file should be present ADDITIONAL INFORMATION The online quotes editor provides advanced features for editing and testing online quotes sources and can be a useful addition to kmymoney. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 439884] New: KPIM crashed while deleting mail from KMAIL folder. Unable to restart AKONADI without rebooting.
https://bugs.kde.org/show_bug.cgi?id=439884 Bug ID: 439884 Summary: KPIM crashed while deleting mail from KMAIL folder. Unable to restart AKONADI without rebooting. Product: kmail2 Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: folders Assignee: kdepim-b...@kde.org Reporter: jcmc...@verizon.net Target Milestone: --- Created attachment 140077 --> https://bugs.kde.org/attachment.cgi?id=140077&action=edit status post crash SUMMARY STEPS TO REPRODUCE 1. 2. 3. john@cml06:~> sudo akonadictl stop [sudo] password for root: QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root' D-Bus session bus is not available! KCrash: Application 'akonadictl' crashing... KCrash: Attempting to start /usr/lib64/libexec/drkonqi qt.qpa.xcb: could not connect to display qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found. error: XDG_RUNTIME_DIR not set in the environment. Failed to create wl_display (No such file or directory) qt.qpa.plugin: Could not load the Qt platform plugin "wayland" in "" even though it was found. This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem. Available platform plugins are: wayland-org.kde.kwin.qpa, eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, wayland-egl, wayland, wayland-xcomposite-egl, wayland-xcomposite-glx, xcb. Unable to start Dr. Konqi Re-raising signal for core dump handling. Aborted john@cml06:~> sudo akonadictl restart QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root' D-Bus session bus is not available! KCrash: Application 'akonadictl' crashing... KCrash: Attempting to start /usr/lib64/libexec/drkonqi qt.qpa.xcb: could not connect to display qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found. error: XDG_RUNTIME_DIR not set in the environment. Failed to create wl_display (No such file or directory) qt.qpa.plugin: Could not load the Qt platform plugin "wayland" in "" even though it was found. This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem. Available platform plugins are: wayland-org.kde.kwin.qpa, eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, wayland-egl, wayland, wayland-xcomposite-egl, wayland-xcomposite-glx, xcb. Unable to start Dr. Konqi Re-raising signal for core dump handling. Aborted john@cml06:~> OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 439885] New: KMAIL crashed
https://bugs.kde.org/show_bug.cgi?id=439885 Bug ID: 439885 Summary: KMAIL crashed Product: kmail2 Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: plasmagee...@gmail.com Target Milestone: --- Application: kmail (5.17.2 (21.04.2)) Qt Version: 5.15.3 Frameworks Version: 5.83.0 Operating System: Linux 5.8.0-59-generic x86_64 Windowing System: X11 Drkonqi Version: 5.22.3 Distribution: KDE neon User Edition 5.22 -- Information about the crash: - What I was doing when the application crashed: - I was responding to an email, the kmail crashed when I clicked Send The crash can be reproduced every time. -- Backtrace: Application: KMail (kmail), signal: Segmentation fault [New LWP 118447] [New LWP 118448] [New LWP 118449] [New LWP 118450] [New LWP 118451] [New LWP 118452] [New LWP 118453] [New LWP 118454] [New LWP 118455] [New LWP 118460] [New LWP 118479] [New LWP 118481] [New LWP 118487] [New LWP 118488] [New LWP 118489] [New LWP 118490] [New LWP 118491] [New LWP 118492] [New LWP 118511] [New LWP 118520] [New LWP 118531] [New LWP 118630] [New LWP 119121] [New LWP 132748] [New LWP 144794] [New LWP 145797] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". 0x7fb9f56e2aff in __GI___poll (fds=0x7ffcd6fc4b78, nfds=1, timeout=1000) at ../sysdeps/unix/sysv/linux/poll.c:29 [Current thread is 1 (Thread 0x7fb9e65a4200 (LWP 118445))] Thread 27 (Thread 0x7fb9350a5700 (LWP 145797)): #0 futex_abstimed_wait_cancelable (private=, abstime=0x7fb9350a40b0, clockid=, expected=0, futex_word=0x7fb9350a4288) at ../sysdeps/nptl/futex-internal.h:320 #1 __pthread_cond_wait_common (abstime=0x7fb9350a40b0, clockid=, mutex=0x7fb9350a4238, cond=0x7fb9350a4260) at pthread_cond_wait.c:520 #2 __pthread_cond_timedwait (cond=0x7fb9350a4260, mutex=0x7fb9350a4238, abstime=0x7fb9350a40b0) at pthread_cond_wait.c:656 #3 0x7fb9f9f2f20a in ?? () from /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x0001ef58 in ?? () #5 0x3636ba8c in ?? () #6 0x0001ef37 in ?? () #7 0x3636ba8c in ?? () #8 0x7fb954001568 in ?? () #9 0x7c6fd7a01c04d000 in ?? () #10 0x in ?? () Thread 26 (Thread 0x7fb93cd22700 (LWP 144794)): #0 0x7fb9f56e2aff in __GI___poll (fds=0x7fb988003790, nfds=3, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7fb9e7c0d1d6 in ?? () from /lib/x86_64-linux-gnu/libpulse.so.0 #2 0x7fb9e7bfe841 in pa_mainloop_poll () from /lib/x86_64-linux-gnu/libpulse.so.0 #3 0x7fb9e7bfeec3 in pa_mainloop_iterate () from /lib/x86_64-linux-gnu/libpulse.so.0 #4 0x7fb9e7bfef70 in pa_mainloop_run () from /lib/x86_64-linux-gnu/libpulse.so.0 #5 0x7fb9e7c0d11d in ?? () from /lib/x86_64-linux-gnu/libpulse.so.0 #6 0x7fb9e705f72c in ?? () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-13.99.so #7 0x7fb9f2543609 in start_thread (arg=) at pthread_create.c:477 #8 0x7fb9f56ef293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 25 (Thread 0x7fb937fff700 (LWP 132748)): #0 0x7fb9f56e2aff in __GI___poll (fds=0x7fb958003be0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7fb9ef03d36e in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fb9ef03d4a3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fb9f5cb1fcb in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fb9f5c5625b in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fb9f5a6fc22 in QThread::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fb9f5a70dbc in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fb9f2543609 in start_thread (arg=) at pthread_create.c:477 #8 0x7fb9f56ef293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 24 (Thread 0x7fb9368a8700 (LWP 119121)): #0 0x7fb9f5cb18ae in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #1 0x7fb9f5cb012d in QTimerInfoList::updateCurrentTime() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7fb9f5cb0709 in QTimerInfoList::timerWait(timespec&) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7fb9f5cb1d26 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fb9ef03c8ef in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7fb9ef03d29b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7fb9ef03d4a3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #7 0x7fb9f5cb1fcb in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fb9f5c5625b in QEven
[frameworks-kio] [Bug 439886] New: Remove `~/.cache/kioexec/krun/` and use regular temporary files instead
https://bugs.kde.org/show_bug.cgi?id=439886 Bug ID: 439886 Summary: Remove `~/.cache/kioexec/krun/` and use regular temporary files instead Product: frameworks-kio Version: 5.84.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kio-bugs-n...@kde.org Reporter: geisse...@gmail.com CC: kdelibs-b...@kde.org Target Milestone: --- SUMMARY KIO places downloaded files in the permanent cache directory `~/.cache/kioexec/krun/`, which persists across different sessions and is never cleaned up by the system. Users have reported this directory to grow enormously over time, unless manual measures are taken. A persistent cache seems inappropriate for KIO downloads. Instead, regular temporary files should be used, placed in the system's dedicated temporary directory (QStandardPaths::TempLocation, https://doc.qt.io/qt-5/qstandardpaths.html). Temporary files have the advantage that they are cleaned up automatically on reboot. Therefore, I would suggest to remove `~/.cache/kioexec/krun/` entirely and modify all components that currently rely on this directory to use temporary files instead. STEPS TO REPRODUCE Invoke a KIO download. OBSERVED RESULT The file will get placed in `~/.cache/kioexec/krun/`. EXPECTED RESULT The file should be placed in the temporary directory of the operating system. SOFTWARE/OS VERSIONS Operating System: KDE neon 5.22 KDE Plasma Version: 5.22.3 KDE Frameworks Version: 5.84.0 Qt Version: 5.15.3 Kernel Version: 5.8.0-59-generic (64-bit) Graphics Platform: Wayland ADDITIONAL INFORMATION See also https://bugs.kde.org/show_bug.cgi?id=439477 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 439477] Clicking on links in Qt/KDE apps causes the website to be cached, rather than the link being forwarded to the browser
https://bugs.kde.org/show_bug.cgi?id=439477 --- Comment #12 from Manuel Geißer --- https://bugs.kde.org/show_bug.cgi?id=439886 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 439886] Remove `~/.cache/kioexec/krun/` and use regular temporary files instead
https://bugs.kde.org/show_bug.cgi?id=439886 Manuel Geißer changed: What|Removed |Added Platform|Other |Neon Packages CC||geisse...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 439887] New: Support storing data back to opened file in a SMB directory
https://bugs.kde.org/show_bug.cgi?id=439887 Bug ID: 439887 Summary: Support storing data back to opened file in a SMB directory Product: umbrello Version: 2.32.1 (KDE releases 20.08.1) Platform: Debian testing OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: umbrello-de...@kde.org Reporter: markus.elfr...@web.de Target Milestone: --- I would like to store a few changes in a file which was opened from a SMB directory in a session of “Knoppix 9.1”. Unfortunately, I stumbled on the following error message. knoppix@Microknoppix:~$ LANG=C umbrello5 smb://….xmi … umbrello: could not upload file "/tmp/umbrello.FKzECM" to QUrl("smb://….xmi") umbrello: Modified file= "Unbenannt" -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 433028] Header for QWidgets KCMs not aligned with sidebar header
https://bugs.kde.org/show_bug.cgi?id=433028 medin changed: What|Removed |Added Ever confirmed|0 |1 Resolution|FIXED |--- Status|RESOLVED|REOPENED --- Comment #17 from medin --- The problem is still present on 5.22.3 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 439865] kf5.kio.core: couldn't create slave: "Meldung von klauncher: Unbekanntes Protokoll „g“.\n"
https://bugs.kde.org/show_bug.cgi?id=439865 Thomas Baumgart changed: What|Removed |Added CC||tbaumg...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 439888] New: Clock in panel has not enough top padding
https://bugs.kde.org/show_bug.cgi?id=439888 Bug ID: 439888 Summary: Clock in panel has not enough top padding Product: plasmashell Version: 5.22.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Digital Clock Assignee: plasma-b...@kde.org Reporter: med.medin.2...@gmail.com Target Milestone: 1.0 Created attachment 140078 --> https://bugs.kde.org/attachment.cgi?id=140078&action=edit Clock in panel has not enough top padding See attached image. Operating System: Manjaro Linux KDE Plasma Version: 5.22.3 KDE Frameworks Version: 5.84.0 Qt Version: 5.15.2 Kernel Version: 5.4.131-1-MANJARO (64-bit) Graphics Platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 438318] Some AMD gpu (lm-sensors-based?) sensors no longer available
https://bugs.kde.org/show_bug.cgi?id=438318 --- Comment #12 from Maciej Stanczew --- My usecases for all of the filtered drivers: coretemp: Similarly to what Artem mentioned, I'm interested in package temperature, not per-core temperatures. k10temp: Ryzen CPUs have a peculiar way of reporting Tctl (search "Ryzen sawtooth"), and because of that I'd like to also monitor Tccd1 (which behaves much more reasonably). (Also, k10temp only provides package temperatures, so it's a bit unintuitive when the CPU plugin splits it per-core, with all cores reporting the same temperature.) amdgpu: This I think is the most clear, we're missing edge/junction/memory temperatures, fan speed, power, and voltage, and they are not available in any other way. > The cause of the problem is, that in the new sensors plugin coretemp, k10temp > and amdgpu are intentionally excluded to not expose duplicated sensors > because these are already handles by the CPU and GPU plugins. Is there any harm in having those sensors duplicated? Personally I think that CPU/GPU plugins could expose a vendor-neutral, standardized set of sensors, while Hardware Sensors could still expose raw, driver-specific sensor data. That way users could use sensors from CPU/GPU plugins for basic temperature/frequency/usage monitoring, while more demanding users could get all the data that the drivers provide. -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 439872] plasma-systemmonitor crashes at launch
https://bugs.kde.org/show_bug.cgi?id=439872 David Edmundson changed: What|Removed |Added CC||k...@davidedmundson.co.uk Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #1 from David Edmundson --- *** This bug has been marked as a duplicate of bug 418148 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 418148] Plasma crashing at boot in QQmlPropertyCacheCreator::propertyCacheForObject() on X11/Wayland/FullWayland
https://bugs.kde.org/show_bug.cgi?id=418148 David Edmundson changed: What|Removed |Added CC||qydwhotm...@gmail.com --- Comment #5 from David Edmundson --- *** Bug 439872 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 405402] Input device problems under Wayland
https://bugs.kde.org/show_bug.cgi?id=405402 David Edmundson changed: What|Removed |Added CC||k...@davidedmundson.co.uk Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #2 from David Edmundson --- *** This bug has been marked as a duplicate of bug 418148 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 418148] Plasma crashing at boot in QQmlPropertyCacheCreator::propertyCacheForObject() on X11/Wayland/FullWayland
https://bugs.kde.org/show_bug.cgi?id=418148 David Edmundson changed: What|Removed |Added CC||johnathan.raymond@knightswh ||osaynil.com --- Comment #6 from David Edmundson --- *** Bug 405402 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 425944] Crash on open
https://bugs.kde.org/show_bug.cgi?id=425944 David Edmundson changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED CC||k...@davidedmundson.co.uk --- Comment #1 from David Edmundson --- *** This bug has been marked as a duplicate of bug 418148 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 418148] Plasma crashing at boot in QQmlPropertyCacheCreator::propertyCacheForObject() on X11/Wayland/FullWayland
https://bugs.kde.org/show_bug.cgi?id=418148 David Edmundson changed: What|Removed |Added CC||herzensch...@gmail.com --- Comment #7 from David Edmundson --- *** Bug 425944 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 439872] plasma-systemmonitor crashes at launch
https://bugs.kde.org/show_bug.cgi?id=439872 --- Comment #2 from David Edmundson --- Can you confirm clearing ~/.cache/plasma-systemmonitor/qmlcache fixes it? Ideally can you take a backup of that folder first? -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 439872] plasma-systemmonitor crashes at launch
https://bugs.kde.org/show_bug.cgi?id=439872 --- Comment #3 from qydwhotm...@gmail.com --- (In reply to David Edmundson from comment #2) > Can you confirm clearing ~/.cache/plasma-systemmonitor/qmlcache fixes it? > > Ideally can you take a backup of that folder first? Yes, it is fixed. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 439729] In-stack preview with "Copy" blending mode breaks background rendering
https://bugs.kde.org/show_bug.cgi?id=439729 Dmitry Kazakov changed: What|Removed |Added Status|REPORTED|RESOLVED Latest Commit||https://invent.kde.org/grap ||hics/krita/commit/87d9c1bf2 ||da0848557baf7b80aaceb1330f8 ||8ecd Resolution|--- |FIXED --- Comment #5 from Dmitry Kazakov --- Git commit 87d9c1bf2da0848557baf7b80aaceb1330f88ecd by Dmitry Kazakov. Committed on 15/07/2021 at 07:57. Pushed by dkazakov into branch 'master'. Fix transform tool to transform layer in COPY mode M +2-1libs/image/kis_layer.cc M +3-1 plugins/tools/tool_transform2/strokes/inplace_transform_stroke_strategy.cpp M +3-1 plugins/tools/tool_transform2/strokes/transform_stroke_strategy.cpp https://invent.kde.org/graphics/krita/commit/87d9c1bf2da0848557baf7b80aaceb1330f88ecd -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 427545] Dual DisplayPort monitors (tiled, MST, e.g. 5k) are not supported by KWin
https://bugs.kde.org/show_bug.cgi?id=427545 Nate Graham changed: What|Removed |Added CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 439844] accessing kubuntu with tightvnc
https://bugs.kde.org/show_bug.cgi?id=439844 Harald Sitter changed: What|Removed |Added CC||sit...@kde.org Status|REPORTED|RESOLVED Resolution|--- |DOWNSTREAM --- Comment #4 from Harald Sitter --- Please file this with ubuntu. Those are all ubuntu crash reports we can't do anything with. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 439886] Remove `~/.cache/kioexec/krun/` and use regular temporary files instead
https://bugs.kde.org/show_bug.cgi?id=439886 Nate Graham changed: What|Removed |Added Ever confirmed|0 |1 CC||a.samir...@gmail.com, ||n...@kde.org Severity|normal |wishlist Status|REPORTED|CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 439886] Remove `~/.cache/kioexec/krun/` and use regular temporary files instead
https://bugs.kde.org/show_bug.cgi?id=439886 Nate Graham changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=439477 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 439477] Clicking on links in Qt/KDE apps causes the website to be cached, rather than the link being forwarded to the browser
https://bugs.kde.org/show_bug.cgi?id=439477 Nate Graham changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=439886 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 439889] New: The bottom progress bar is inconsistent with the progress bar on the Colorize Mask layer.
https://bugs.kde.org/show_bug.cgi?id=439889 Bug ID: 439889 Summary: The bottom progress bar is inconsistent with the progress bar on the Colorize Mask layer. Product: krita Version: 4.4.5 Platform: Other OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: Tools/Colorize Assignee: krita-bugs-n...@kde.org Reporter: 1012468...@qq.com Target Milestone: --- Created attachment 140079 --> https://bugs.kde.org/attachment.cgi?id=140079&action=edit The bottom progress bar is inconsistent with the progress bar on the Colorize Mask layer. SUMMARY The bottom progress bar is inconsistent with the progress bar on the Colorize Mask layer. Sometimes the progress bar at the bottom will disappear, but the progress bar of the Colorize Mask layer is still there. STEPS TO REPRODUCE 1. Use the Colorize Mask tool to assign colors to the line draft. 2. Update. 3. Observe the progress bar at the bottom and the progress bar on the Colorize Mask layer. OBSERVED RESULT The bottom progress bar is inconsistent with the progress bar on the Colorize Mask layer. EXPECTED RESULT The bottom progress bar is synchronized with the progress bar on the Colorize Mask layer. Krita Version: 4.4.5 Languages: en_US, en, en_US, en, en_US, en, en_US, en, en_US, en, en_US, en, en_US, en, en_US, en, zh_CN, zh, en_US, en Hidpi: true Qt Version (compiled): 5.12.9 Version (loaded): 5.12.9 OS Information Build ABI: x86_64-little_endian-llp64 Build CPU: x86_64 CPU: x86_64 Kernel Type: winnt Kernel Version: 10.0.19042 Pretty Productname: Windows 10 (10.0) Product Type: windows Product Version: 10 OpenGL Info Vendor: "Google Inc." Renderer: "ANGLE (NVIDIA GeForce GTX 970 Direct3D11 vs_5_0 ps_5_0)" Version: "OpenGL ES 3.0 (ANGLE 2.1.0.57ea533f79a7)" Shading language: "OpenGL ES GLSL ES 3.00 (ANGLE 2.1.0.57ea533f79a7)" Requested format: QSurfaceFormat(version 3.0, options QFlags(DeprecatedFunctions), depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::DoubleBuffer, swapInterval 0, colorSpace QSurfaceFormat::DefaultColorSpace, profile QSurfaceFormat::CompatibilityProfile) Current format:QSurfaceFormat(version 3.0, options QFlags(), depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, stencilBufferSize 8, samples 0, swapBehavior QSurfaceFormat::DefaultSwapBehavior, swapInterval 0, colorSpace QSurfaceFormat::DefaultColorSpace, profile QSurfaceFormat::NoProfile) Version: 3.0 Supports deprecated functions false is OpenGL ES: true QPA OpenGL Detection Info supportsDesktopGL: true supportsAngleD3D11: true isQtPreferAngle: true Hardware Information GPU Acceleration: auto Memory: 32693 Mb Number of Cores: 16 Swap Location: C:/Users/xi/AppData/Local/Temp Current Settings Current Swap Location: C:/Users/xi/AppData/Local/Temp Current Swap Location writable: true Undo Enabled: true Undo Stack Limit: 30 Use OpenGL: true Use OpenGL Texture Buffer: true Use AMD Vectorization Workaround: false Canvas State: OPENGL_SUCCESS Autosave Interval: 900 Use Backup Files: true Number of Backups Kept: 1 Backup File Suffix: ~ Backup Location: Same Folder as the File Backup Location writable: false Use Win8 Pointer Input: false Use RightMiddleTabletButton Workaround: false Levels of Detail Enabled: false Use Zip64: false Display Information Number of screens: 2 Screen: 0 Name: \\.\DISPLAY1 Depth: 32 Scale: 1 Resolution in pixels: 2560x1440 Manufacturer: Model: Refresh Rate: 59 Screen: 1 Name: \\.\DISPLAY2 Depth: 32 Scale: 1 Resolution in pixels: 1920x1080 Manufacturer: Model: Refresh Rate: 60 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 439880] Shadow corners are more darker
https://bugs.kde.org/show_bug.cgi?id=439880 Nate Graham changed: What|Removed |Added CC||n...@kde.org Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #1 from Nate Graham --- Did you by any chance happen to try out the Wayland session and then switch back to X11? If so, this is Bug 429057. Does it happen with Breeze Light? -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 439615] ksystemstats keeps crashing on every login
https://bugs.kde.org/show_bug.cgi?id=439615 David Redondo changed: What|Removed |Added Resolution|--- |FIXED Version Fixed In||5.22.4 Latest Commit||https://invent.kde.org/plas ||ma/ksystemstats/commit/7055 ||0a94e1752a8adad577574ab3b05 ||1088f5a61 Status|ASSIGNED|RESOLVED --- Comment #15 from David Redondo --- Git commit 70550a94e1752a8adad577574ab3b051088f5a61 by David Redondo. Committed on 09/07/2021 at 12:36. Pushed by davidre into branch 'master'. Don't crash if there's no input subfeature Apaprently not all sensors have an "input" subfeature for example some can only have an "average" subfeature. FIXED-IN:5.22.4 M +4-0plugins/lmsensors/SensorsFeatureSensor.cpp https://invent.kde.org/plasma/ksystemstats/commit/70550a94e1752a8adad577574ab3b051088f5a61 -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 439878] Breeze GTK theme is messing with Pamac
https://bugs.kde.org/show_bug.cgi?id=439878 Nate Graham changed: What|Removed |Added Target Milestone|1.0 |--- CC||n...@kde.org Product|plasmashell |Breeze Component|Theme - Breeze |gtk theme Assignee|visual-des...@kde.org |uhh...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 439615] ksystemstats keeps crashing on every login
https://bugs.kde.org/show_bug.cgi?id=439615 David Redondo changed: What|Removed |Added Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas |ma/ksystemstats/commit/7055 |ma/ksystemstats/commit/782d |0a94e1752a8adad577574ab3b05 |be81acaa3d364d12c1e42e44fc9 |1088f5a61 |0c447df22 --- Comment #16 from David Redondo --- Git commit 782dbe81acaa3d364d12c1e42e44fc90c447df22 by David Redondo. Committed on 15/07/2021 at 13:45. Pushed by davidre into branch 'Plasma/5.22'. Don't crash if there's no input subfeature Apaprently not all sensors have an "input" subfeature for example some can only have an "average" subfeature. FIXED-IN:5.22.4 (cherry picked from commit 70550a94e1752a8adad577574ab3b051088f5a61) M +4-0plugins/lmsensors/SensorsFeatureSensor.cpp https://invent.kde.org/plasma/ksystemstats/commit/782dbe81acaa3d364d12c1e42e44fc90c447df22 -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 417078] Unhelpful "Aborted due to failure" error message sometimes appears when updating Flatpak apps
https://bugs.kde.org/show_bug.cgi?id=417078 --- Comment #20 from Jonathan Riddell --- flatpak in neon is now at 1.10.2 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 433107] Wayland: iGPU/AMDGPU multi-monitor keeps displaying the SDDM screen if iGPU-DisplayPort is connected
https://bugs.kde.org/show_bug.cgi?id=433107 --- Comment #28 from Andrew Ammerlaan --- Created attachment 140080 --> https://bugs.kde.org/attachment.cgi?id=140080&action=edit wayland-session-log (In reply to Zamundaaa from comment #27) > crash should be fixed (at least it works with vkms) Yes the crash is fixed now, Thanks. After applying the patch from your Merge Request I get a proper display on one of the monitors connected to the iGPU, the other two continue to display the SDDM screen. The monitor connected to the AMDGPU (DVI-D-1) turns black. I can move my mouse onto those monitors, and they are properly shown in Display Settings (correct configuration and correct resolution etc). I see some "Invalid argument" in the logs, so perhaps that is the cause. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 344588] 'Regional Setting - Formats - Region' setting behaves unexpected
https://bugs.kde.org/show_bug.cgi?id=344588 Juha Tuomala changed: What|Removed |Added CC||t...@iki.fi --- Comment #13 from Juha Tuomala --- (In reply to Dennis Schridde from comment #9) > I have the exact same issue. > > I wouldn't mind having my datestrings in German, but what really bothers me > is that I select the "language" to be English and the "formats" to be > German, but I end up getting German output on the console. > > The reasons for this unexpected behaviour is that `.config/plasma-localerc` > sets LANG when I choose a format: > ``` > [Formats] > LANG=de_DE.UTF-8 > > [Translations] > LANGUAGE=en_GB:en_US:de > ``` > > This results in the following `.config/plasma-locale-settings.sh` being > generated: > ``` > # Generated script, do not edit > # Exports language-format specific env vars from startkde. > # This script has been generated from kcmshell5 formats. > # It will automatically be overwritten from there. > export LANG=de_DE.UTF-8 > export LANGUAGE=en_GB:en_US:de > ``` > > I would expect System Settings > Regional Settings > Translations to set > LC_MESSAGES, LANG and LANGUAGE, while ... > Formats should set all other > LC_*. That should be correct according to the specs - any misbehaving > application would mean a bug in that application that KDE developers should > not worry about. This bug is going strong, years go by and nobody fixes this. I've seen major bugs here live well over 10 years and nothing happens. These days I don't report anything new, just whine in comments. This is just a big joke. -- You are receiving this mail because: You are watching all bug changes.
[kfind] [Bug 439870] Use files index does not work for disks in /media
https://bugs.kde.org/show_bug.cgi?id=439870 --- Comment #2 from francois072@e.email --- I see. I thought that Kfind also uses baloo. I did not realize that Kfind used mlocate for the database. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 439165] Kontact crashed while in background
https://bugs.kde.org/show_bug.cgi?id=439165 --- Comment #3 from Bob Mattes --- Created attachment 140081 --> https://bugs.kde.org/attachment.cgi?id=140081&action=edit New crash information added by DrKonqi kontact (5.17.3 (21.04.3)) using Qt 5.15.2 - What I was doing when the application crashed: I was reading a document in Ocular when Kontact crashed in the background. Kontact reliably crashes every time a few minutes after running it. Seems to work correctly before the crash. This behavior has been consistent for several weeks. -- Backtrace (Reduced): #6 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:49 #7 0x7f9dae082864 in __GI_abort () at abort.c:79 #8 0x7f9dae2d49b6 in __gnu_cxx::__verbose_terminate_handler () at ../../../../libstdc++-v3/libsupc++/vterminate.cc:95 #9 0x7f9dae2e019c in __cxxabiv1::__terminate (handler=) at ../../../../libstdc++-v3/libsupc++/eh_terminate.cc:48 #10 0x7f9dae2e0207 in std::terminate () at ../../../../libstdc++-v3/libsupc++/eh_terminate.cc:58 -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 437617] Temperature icon?
https://bugs.kde.org/show_bug.cgi?id=437617 manuelj...@pm.me changed: What|Removed |Added CC||manuelj...@pm.me Status|ASSIGNED|RESOLVED Resolution|--- |FIXED --- Comment #2 from manuelj...@pm.me --- Fixed on the previous MR. Need to figure out why it didn't automatically set to resolved. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 439269] Opening the settings dialog closes the applet even if it's pinned open
https://bugs.kde.org/show_bug.cgi?id=439269 --- Comment #8 from Felipe Kinoshita --- It's working for me now -- You are receiving this mail because: You are watching all bug changes.
[kfind] [Bug 439870] Use files index does not work for disks in /media
https://bugs.kde.org/show_bug.cgi?id=439870 francois072@e.email changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[xdg-desktop-portal-kde] [Bug 439607] Can't share screen on a Wayland session with Firefox
https://bugs.kde.org/show_bug.cgi?id=439607 --- Comment #26 from benaventeadr...@gmail.com --- (In reply to Jan Grulich from comment #25) > Can you run "dbus-monitor --session" from a terminal and keep it running. > Then from a different terminal (tab) start Chrome with > "PIPEWIRE_DEBUG=5:connection chrome". Try to share a screen and post here > both logs. ### FROM `dbus-monitor` ### string "toggle-type" variant string "checkmark" ) dict entry( string "visible" variant boolean true ) ] array [ ] } variant struct { int32 605 array [ dict entry( string "type" variant string "separator" ) dict entry( string "visible" variant boolean true ) ] array [ ] } variant struct { int32 606 array [ dict entry( string "enabled" variant boolean true ) dict entry( string "icon-name" variant string "object-unlocked" ) dict entry( string "label" variant string "Solo lectura" ) dict entry( string "toggle-state" variant int32 0 ) dict entry( string "toggle-type" variant string "checkmark" ) dict entry( string "visible" variant boolean true ) ] array [ ] } variant struct { int32 607 array [ dict entry( string "type" variant string "separator" ) dict entry( string "visible" variant boolean true ) ] array [ ] } variant struct { int32 608 array [ dict entry( string "enabled" variant boolean true ) dict entry( string "icon-name" variant string "format-font-size-more" ) dict entry( string "label" variant string "Agrandar la letra" ) dict entry( string "shortcut" variant array [ array [ string "Control" string "plus" ] ] ) dict entry( string "visible" variant boolean true ) ] array [ ] } variant struct { int32 609 array [ dict entry( string "enabled" variant boolean true ) dict entry( string "label" variant string "Reiniciar el tamaño del tipo de letra" ) dict entry( string "shortcut" variant array [ array [ string "Control" string "Alt" string "0" ] ] ) dict entry( string "visible" variant boolean true ) ] array [ ] } variant struct {
[dolphin] [Bug 439747] Dolphin is unable to access passwordless windows 10 shares.
https://bugs.kde.org/show_bug.cgi?id=439747 Harald Sitter changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |UPSTREAM --- Comment #14 from Harald Sitter --- https://bugzilla.samba.org/show_bug.cgi?id=14761 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 429338] Context menus shown in wrong locations on Wayland
https://bugs.kde.org/show_bug.cgi?id=429338 caulier.gil...@gmail.com changed: What|Removed |Added Version Fixed In||7.4.0 Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #7 from caulier.gil...@gmail.com --- Ok i mark this file as fixed... Reopen if necessary Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 429338] Context menus shown in wrong locations on Wayland
https://bugs.kde.org/show_bug.cgi?id=429338 caulier.gil...@gmail.com changed: What|Removed |Added Component|Usability-i18n |Usability-Menus -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 439845] Ctrl+Arrow stop at random places in the middle of words
https://bugs.kde.org/show_bug.cgi?id=439845 --- Comment #2 from php4...@gmail.com --- What exactly is the feature?? How is jumping to the middle of an all-upper-case word related to camel case? Can you give an example of the usecase it is supposed to address? -- You are receiving this mail because: You are watching all bug changes.