[okular] [Bug 448448] Okular unable to print to LAN printer - status: rendering completed
https://bugs.kde.org/show_bug.cgi?id=448448 Oliver Sander changed: What|Removed |Added CC||oliver.san...@tu-dresden.de --- Comment #1 from Oliver Sander --- I think I have seen this error message as well, but I can't reproduce it now. As a workaround: Does printing work if you enable "force rasterization"? -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 442380] Session restore does not remember which windows were on which virtual desktop on X11
https://bugs.kde.org/show_bug.cgi?id=442380 --- Comment #19 from Attila --- (In reply to Brian Kaye from comment #18) > Problem persists in Fedora 35. System seems to keep older versions of the > application files in .config/session. In my case the folder "config" contains more than 3500 files of "KWrite_..." which were created in a period from December 2019 to December 2021. Usually I have 5 to 15 instances of KWrite running when I logout. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 448553] Icon request: boxplot icon in LabPlot
https://bugs.kde.org/show_bug.cgi?id=448553 --- Comment #2 from Alexander Semke --- (In reply to Nate Graham from comment #1) > Something sort of like this? > https://www.flaticon.com/free-icon/box- > plot_5137068?term=box%20plot=1=43=1=43_id > =5137068=search Yes, something like the first icon here would be great. We're using already view-object-histogram-linear for the histogram and labplot-xy-curve for the xy-curve from Breeze. For boxplots we could create something similar - same two axes as on those two icons just mentioned and then maybe two boxplots, three boxes like on your link is maybe too much for smaller icons... -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 448692] New: Pressing Ctrl+Backspace (Delete Word Left) after single-letter word deletes two words
https://bugs.kde.org/show_bug.cgi?id=448692 Bug ID: 448692 Summary: Pressing Ctrl+Backspace (Delete Word Left) after single-letter word deletes two words Product: kate Version: 21.12.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: part Assignee: kwrite-bugs-n...@kde.org Reporter: nyanpas...@tuta.io Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Open KWrite and type asdf a. Alternatively you can type any number of words, followed by 1 or more spaces, then a single letter, then EOF or a newline. 2. Place the cursor at the end of the line and press Ctrl+Backspace. OBSERVED RESULT The single-letter word and the preceding word are deleted. EXPECTED RESULT Only the single-letter word is deleted. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.23.90 KDE Frameworks Version: 5.90.0 Qt Version: 5.15.2 Kernel Version: 5.16.0-zen1-1-zen (64-bit) Graphics Platform: X11 Processors: 12 × AMD Ryzen 5 5600X 6-Core Processor Memory: 15.6 GiB of RAM Graphics Processor: NVIDIA GeForce GT 730/PCIe/SSE2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Ruqola] [Bug 410021] Various hi-dpi problems
https://bugs.kde.org/show_bug.cgi?id=410021 --- Comment #4 from Laurent Montel --- Can you test against ruqola 1.6.1 ? I know that I made a lot of fix so perhaps there is a fix for you. I can't see where is the problem as we use same font (bold for user name and not bold for text but same font) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 371831] digiKam missing Printer Driver Properties in Image Printing Dialog
https://bugs.kde.org/show_bug.cgi?id=371831 caulier.gil...@gmail.com changed: What|Removed |Added Version Fixed In||7.6.0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 167316] Allow for making pictures bigger when adjusting perspective
https://bugs.kde.org/show_bug.cgi?id=167316 caulier.gil...@gmail.com changed: What|Removed |Added Version Fixed In||7.6.0 CC||caulier.gil...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 148009] perspective control support grid missing
https://bugs.kde.org/show_bug.cgi?id=148009 caulier.gil...@gmail.com changed: What|Removed |Added CC||caulier.gil...@gmail.com Version Fixed In||7.6.0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 138946] Perspective adjustment: orthogonal line guides or grid
https://bugs.kde.org/show_bug.cgi?id=138946 caulier.gil...@gmail.com changed: What|Removed |Added Version Fixed In||7.6.0 Resolution|DUPLICATE |FIXED --- Comment #3 from caulier.gil...@gmail.com --- Fixed with https://bugs.kde.org/show_bug.cgi?id=131170 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 143034] When I print a Colour. JPG in digikam a white diagonal line cuts across the picture
https://bugs.kde.org/show_bug.cgi?id=143034 caulier.gil...@gmail.com changed: What|Removed |Added Summary|When I print a Colour.JPG |When I print a Colour. JPG |in digikam, a white |in digikam a white diagonal |diagonal line cuts across |line cuts across the |the picture, my printer is |picture |a HPDeskjet5150, Set up in | |Yast with added | |HPDeskjet_5150_hpijs PPD| |file| -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 92438] Printing problems digiKam 7.0
https://bugs.kde.org/show_bug.cgi?id=92438 caulier.gil...@gmail.com changed: What|Removed |Added Version Fixed In||7.6.0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 143034] When I print a Colour.JPG in digikam, a white diagonal line cuts across the picture, my printer is a HPDeskjet5150, Set up in Yast with added HPDeskjet_5150_hpijs PPD file
https://bugs.kde.org/show_bug.cgi?id=143034 caulier.gil...@gmail.com changed: What|Removed |Added Version Fixed In||7.6.0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 300399] Image view: right click should offer print option
https://bugs.kde.org/show_bug.cgi?id=300399 caulier.gil...@gmail.com changed: What|Removed |Added Version Fixed In||7.6.0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 221744] printing a photo using canon MP600
https://bugs.kde.org/show_bug.cgi?id=221744 caulier.gil...@gmail.com changed: What|Removed |Added Version Fixed In||7.6.0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 92437] Printing problems digiKam
https://bugs.kde.org/show_bug.cgi?id=92437 caulier.gil...@gmail.com changed: What|Removed |Added Version Fixed In||7.6.0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 92387] Printing problems
https://bugs.kde.org/show_bug.cgi?id=92387 caulier.gil...@gmail.com changed: What|Removed |Added Version Fixed In||7.6.0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 139474] can't print with canon CP 200
https://bugs.kde.org/show_bug.cgi?id=139474 caulier.gil...@gmail.com changed: What|Removed |Added Version Fixed In||7.6.0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 103148] Automatically choose best paper orientation when printing
https://bugs.kde.org/show_bug.cgi?id=103148 caulier.gil...@gmail.com changed: What|Removed |Added Version Fixed In||7.6.0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 91644] High definition photos printing from KDE software : poor quality
https://bugs.kde.org/show_bug.cgi?id=91644 caulier.gil...@gmail.com changed: What|Removed |Added Version Fixed In||7.6.0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 448681] digikam uses abandoned library incompatible with ffmpeg 5.0
https://bugs.kde.org/show_bug.cgi?id=448681 --- Comment #1 from caulier.gil...@gmail.com --- Hi, QtAv is not abandoned at all. I'm in contact with lead developer, and it have been ported to Qt6 recently. Look last PR and commits in the project. We don't plan to change to a new video framework yet in digiKam. ffmpeg backend is the best solution, as i explained in my comment here : https://github.com/wang-bin/QtAV/issues/1294#issuecomment-1007943741 The best way as you already do is to create a report in QtAV with your patch, or better, a merge request from a fork of the repository, which will include all your changes. It will be more easy for the QtAv developers to review changes. Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 395748] Problem with printing
https://bugs.kde.org/show_bug.cgi?id=395748 caulier.gil...@gmail.com changed: What|Removed |Added Summary|Problem with printig|Problem with printing -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 92387] Printing problems
https://bugs.kde.org/show_bug.cgi?id=92387 caulier.gil...@gmail.com changed: What|Removed |Added Summary|Printing problems digikam |Printing problems |7.0 | -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 371831] digiKam missing Printer Driver Properties in Image Printing Dialog
https://bugs.kde.org/show_bug.cgi?id=371831 caulier.gil...@gmail.com changed: What|Removed |Added Summary|Digikam 5 missing Printer |digiKam missing Printer |Driver Properties in Image |Driver Properties in Image |Printing Dialog |Printing Dialog -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 92437] Printing problems digiKam
https://bugs.kde.org/show_bug.cgi?id=92437 caulier.gil...@gmail.com changed: What|Removed |Added Summary|Printing problems Digikam |Printing problems digiKam |7.0 CVS | -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 92387] Printing problems digikam 7.0
https://bugs.kde.org/show_bug.cgi?id=92387 caulier.gil...@gmail.com changed: What|Removed |Added Summary|Printing problems Digikam |Printing problems digikam |7.0 CVS |7.0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 92438] Printing problems digiKam 7.0
https://bugs.kde.org/show_bug.cgi?id=92438 caulier.gil...@gmail.com changed: What|Removed |Added Summary|Printing problems Digikam |Printing problems digiKam |7.0 CVS |7.0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 448593] New generic Flow View plugin for digiKam
https://bugs.kde.org/show_bug.cgi?id=448593 caulier.gil...@gmail.com changed: What|Removed |Added Summary|new view plugin for digikam |New generic Flow View ||plugin for digiKam -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 448593] new view plugin for digikam
https://bugs.kde.org/show_bug.cgi?id=448593 --- Comment #9 from caulier.gil...@gmail.com --- Another important remark : In this function : https://github.com/cathaysia/digikamflowplugin/blob/master/src/PicFlowView.cpp#L169 you access to image directly by a QPixmap() call to later create label in GUI over a loop. This is so far not optimal. 1/ Do not use QPixmap directly. digiKam has a multithread image preview API with a cache mechanism to speed up image data handling with huge album contents. It's accessible from plugins of course. Look use of PreviewLoadThread in Slideshow plugin here : https://invent.kde.org/graphics/digikam/-/blob/master/core/dplugins/generic/view/slideshow/widgets/slideimage.cpp#L76 2 instances are used, internally, both use a common cache to optimize memory usage. One instance preload image in cache, one is used to load current image. Both instance will use a separated thread to run. A signal is emitted when image is available as DImg which thread safe (in opposite of QPixmap). You can convert DImg as QImage or QPixmap of course. API : DImg : https://invent.kde.org/graphics/digikam/-/blob/master/core/libs/dimg/dimg.h PreviewLoadThread : https://invent.kde.org/graphics/digikam/-/blob/master/core/libs/threadimageio/preview/previewloadthread.h 2/ The forever loop here : https://github.com/cathaysia/digikamflowplugin/blob/master/src/PicFlowView.cpp#L258 ...will be time consuming to render large album. Use preview load thread and signal/slot mechanism to not freeze GUI. If you need to play with image data, use a separated thread with QImage, not QPixmap. Only play with widget on main thread at end. All consuming CPU task as loop must be done in separated thread. Use profiling for that. if necessary 3/ Remove definitively the database headers https://github.com/cathaysia/digikamflowplugin/blob/master/src/PicFlowView.cpp#L258 Generic plugin must not use database at all. 4/ why do you mix Qt and C++ API where Qt propose equivalent, optimized, and portable classes ? c++::semaphore for ex. 5/ Please use English comments and documentations everywhere. It's difficult to use a translator over source code to read explanations. 6/ In dependencies list i can see spdlog API. Do not add this extra dependency if Qt do the job with QDebug API and is enough for a plugin... I don't yet compiled your code. I will do it later. Best regards Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 448691] New: Dolphin just sort of randomly crashed in the background
https://bugs.kde.org/show_bug.cgi?id=448691 Bug ID: 448691 Summary: Dolphin just sort of randomly crashed in the background Product: dolphin Version: 21.08.1 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: wodenc...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- Application: dolphin (21.08.1) Qt Version: 5.15.2 Frameworks Version: 5.86.0 Operating System: Linux 5.13.0-25-generic x86_64 Windowing System: X11 Drkonqi Version: 5.22.5 Distribution: Ubuntu 21.10 -- Information about the crash: - What I was doing when the application crashed: I had started uploading a file to a website by dragging it from dolphin to the page. I then switched to a different window and began working on other things. A short while later (a minute or so maybe?), I saw the crash warning. No other applications crashed, just dolphin. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Dolphin (dolphin), signal: Aborted [KCrash Handler] #4 __pthread_kill_implementation (no_tid=0, signo=6, threadid=139761809689024) at pthread_kill.c:44 #5 __pthread_kill_internal (signo=6, threadid=139761809689024) at pthread_kill.c:80 #6 __GI___pthread_kill (threadid=139761809689024, signo=signo@entry=6) at pthread_kill.c:91 #7 0x7f1cd9bc2476 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #8 0x7f1cd9ba87b7 in __GI_abort () at abort.c:79 #9 0x7f1cd9c095e6 in __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f1cd9d5aef4 "*** %s ***: terminated\n") at ../sysdeps/posix/libc_fatal.c:155 #10 0x7f1cd9cb522a in __GI___fortify_fail (msg=msg@entry=0x7f1cd9d5aedc "stack smashing detected") at fortify_fail.c:26 #11 0x7f1cd9cb51f6 in __stack_chk_fail () at stack_chk_fail.c:24 #12 0x7f1cdc25896c in KDirectoryContentsCounter::startWorker (this=0x5568ac7e5180, path=...) at ./src/kitemviews/private/kdirectorycontentscounter.cpp:196 #13 0x7f1cdc22461b in KDirectoryContentsCounter::scanDirectory (path=..., this=) at ./src/kitemviews/private/kdirectorycontentscounter.cpp:78 #14 KFileItemModelRolesUpdater::rolesData (this=this@entry=0x5568abfa62b0, item=...) at ./src/kitemviews/kfileitemmodelrolesupdater.cpp:1331 #15 0x7f1cdc225a1b in KFileItemModelRolesUpdater::slotGotPreview (this=0x5568abfa62b0, item=..., pixmap=...) at ./src/kitemviews/kfileitemmodelrolesupdater.cpp:545 #16 0x7f1cda2ada53 in QtPrivate::QSlotObjectBase::call (a=0x7ffd335b3d50, r=0x5568abfa62b0, this=0x5568b3c2c8c0) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #17 doActivate (sender=0x5568ba58b190, signal_index=25, argv=0x7ffd335b3d50) at kernel/qobject.cpp:3886 #18 0x7f1cda2a6d67 in QMetaObject::activate (sender=sender@entry=0x5568ba58b190, m=m@entry=0x7f1cdbf78780 , local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffd335b3d50) at kernel/qobject.cpp:3946 #19 0x7f1cdbeca88b in KIO::PreviewJob::gotPreview (this=this@entry=0x5568ba58b190, _t1=..., _t2=...) at ./obj-x86_64-linux-gnu/src/widgets/KF5KIOWidgets_autogen/include/moc_previewjob.cpp:198 #20 0x7f1cdbecf011 in KIO::PreviewJobPrivate::emitPreview (this=this@entry=0x5568b6cd0040, thumb=...) at ./src/widgets/previewjob.cpp:951 #21 0x7f1cdbed016c in KIO::PreviewJobPrivate::slotThumbData (this=0x5568b6cd0040, job=, data=...) at ./src/widgets/previewjob.cpp:937 #22 0x7f1cda2ada53 in QtPrivate::QSlotObjectBase::call (a=0x7ffd335b4050, r=0x5568ba58b190, this=0x5568bac2eb70) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #23 doActivate (sender=0x5568b604fc90, signal_index=25, argv=0x7ffd335b4050) at kernel/qobject.cpp:3886 #24 0x7f1cdbc812b8 in KIO::TransferJob::data(KIO::Job*, QByteArray const&) () from /lib/x86_64-linux-gnu/libKF5KIOCore.so.5 #25 0x7f1cda2ada53 in QtPrivate::QSlotObjectBase::call (a=0x7ffd335b4150, r=0x5568b604fc90, this=0x5568b9188700) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #26 doActivate (sender=0x5568b5e1b930, signal_index=3, argv=0x7ffd335b4150) at kernel/qobject.cpp:3886 #27 0x7f1cdbc53c06 in KIO::SlaveInterface::data(QByteArray const&) () from /lib/x86_64-linux-gnu/libKF5KIOCore.so.5 #28 0x7f1cdbc55f62 in KIO::SlaveInterface::dispatch(int, QByteArray const&) () from /lib/x86_64-linux-gnu/libKF5KIOCore.so.5 #29 0x7f1cdbc543cd in KIO::SlaveInterface::dispatch() () from /lib/x86_64-linux-gnu/libKF5KIOCore.so.5 #30 0x7f1cdbc58df2 in KIO::Slave::gotInput() () from /lib/x86_64-linux-gnu/libKF5KIOCore.so.5 #31 0x7f1cda2ada53 in QtPrivate::QSlotObjectBase::call (a=0x7ffd335b4380, r=0x5568b5e1b930, this=0x5568afc48f20) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
[kdevelop] [Bug 448152] Building with Xcode fails `ld: malformed 64-bit a.b.c.d.e version number: 5.7.211201`
https://bugs.kde.org/show_bug.cgi?id=448152 Jeremy W. Murphy changed: What|Removed |Added CC||jeremy.william.murphy@gmail ||.com -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 439832] Kate AppImage process on RHEL7 doesn't terminate when closed
https://bugs.kde.org/show_bug.cgi?id=439832 kde.bugzilla.2022@rancidbacon.com changed: What|Removed |Added CC||kde.bugzilla.2022.dkw@ranci ||dbacon.com --- Comment #2 from kde.bugzilla.2022@rancidbacon.com --- I have encountered this issue with a recent AppImage also and have spent some time digging into it further--because I'm *so* close to being able to use Kate for working with Rust. :) Summary: * A flatpak version that does not hang uses Qt 5.15.3 while an AppImage version that does hang uses Qt 5.15.2. (NB: When I looked on the GitHub Qt mirror there didn't appear to be a tag for Qt 5.15.3 AFAICT.) * A backtrace of the hung process: ``` Thread 1 "AppRun.wrapped" received signal SIGINT, Interrupt. syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 38 ../sysdeps/unix/sysv/linux/x86_64/syscall.S: No such file or directory. (gdb) bt #0 syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 #1 0x72a29224 in QSemaphore::acquire(int) () from //kate-appimage-extracted/squashfs-root/usr/bin/../lib/libQt5Core.so.5 #2 0x72c6aa5e in void doActivate(QObject*, int, void**) () from //kate-appimage-extracted/squashfs-root/usr/bin/../lib/libQt5Core.so.5 #3 0x72c63fff in QObject::destroyed(QObject*) () from //kate-appimage-extracted/squashfs-root/usr/bin/../lib/libQt5Core.so.5 #4 0x72c688b4 in QObject::~QObject() () from //kate-appimage-extracted/squashfs-root/usr/bin/../lib/libQt5Core.so.5 #5 0x72c2fa13 in QCoreApplication::~QCoreApplication() () from //kate-appimage-extracted/squashfs-root/usr/bin/../lib/libQt5Core.so.5 #6 0x73226699 in QGuiApplication::~QGuiApplication() () from //kate-appimage-extracted/squashfs-root/usr/bin/../lib/libQt5Gui.so.5 #7 0x73d32d1b in QApplication::~QApplication() () from //kate-appimage-extracted/squashfs-root/usr/bin/../lib/libQt5Widgets.so.5 #8 0x5558e688 in ?? () #9 0x72217bf7 in __libc_start_main (main=0x5558c2f0, argc=1, argv=0x7fffdd18, init=, fini=, rtld_fini=, stack_end=0x7fffdd08) at ../csu/libc-start.c:310 #10 0x5558fc6a in _start () (gdb) info threads Id Target Id Frame * 1Thread 0x77f9f900 (LWP 31069) "AppRun.wrapped" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 2Thread 0x7fffe242a700 (LWP 31073) "QXcbEventQueue" 0x7230acb9 in __GI___poll (fds=0x7fffe2429ba8, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 3Thread 0x7fffd5d8b700 (LWP 31074) "gmain" 0x7230acb9 in __GI___poll (fds=0x55934490, nfds=2, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 4Thread 0x7fffd5119700 (LWP 31075) "gdbus" 0x7230acb9 in __GI___poll (fds=0x559bbb90, nfds=2, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 ``` * There does appear to be a possibly related code change in the surrounding area/version: https://github.com/qt/qtbase/commit/c1454d07cfc3f4cb8273fdb45b152c8942d04129 Suggestion for possible fix: Bump the Qt version used for the AppImage to Qt v5.15.3 and see if that solves the issue. More system details: > elementary OS 5.1.7 Hera (GNU/Linux 5.4.0-60-generic x86_64) > Built on Ubuntu 18.04.6 LTS [My apologies for the less than comprehensive details in this comment but I've just spent hours signing up for three different KDE accounts & working through various Bugzilla processes/issues on an *extremely* hot day, so wanted to share at least this much information before I ran out of momentum entirely. :) I'll attempt to try to fill in some more details later if beneficial.] -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kconfig] [Bug 427875] On a multi screen setup, KDE app windows do not remember size, position, or the screen they were last opened on. For X11 when the left-most display is not the primary
https://bugs.kde.org/show_bug.cgi?id=427875 smtea...@gmail.com changed: What|Removed |Added CC||smtea...@gmail.com --- Comment #54 from smtea...@gmail.com --- Also still getting this, things seem to remember the correct monitor at least, but size and position is reset for most applications on launch, also using a two monitor setup with my right monitor being the primary, and the left as a secondary As soon as I disable my left most monitor in KDE's display configuration (keeping only my original primary as my single monitor) then applications remember their size and position correctly, re-enabling my left-side secondary monitor again immediately causes these programs to *reset* to how they were opening before, completely forgetting any of the position or size it was using with just my primary monitor active Operating System: Arch Linux KDE Plasma Version: 5.23.5 KDE Frameworks Version: 5.90.0 Qt Version: 5.15.2 Kernel Version: 5.16.1-237-tkg-pds (64-bit) Graphics Platform: X11 Processors: 12 × AMD Ryzen 5 3600 6-Core Processor Memory: 15.6 GiB of RAM Graphics Processor: AMD Radeon RX 570 Series -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 448681] digikam uses abandoned library incompatible with ffmpeg 5.0
https://bugs.kde.org/show_bug.cgi?id=448681 caulier.gil...@gmail.com changed: What|Removed |Added Component|general |Preview-Video CC||caulier.gil...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 448690] New: Discover is very slow when searching
https://bugs.kde.org/show_bug.cgi?id=448690 Bug ID: 448690 Summary: Discover is very slow when searching Product: Discover Version: 5.23.90 Platform: Neon Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: discover Assignee: lei...@leinir.dk Reporter: martin.tlus...@gmail.com CC: aleix...@kde.org Target Milestone: --- SUMMARY When searching for programs, discover takes a lot of time to find anything, but sometimes doesnt't find it anyway (e.g. search for fdupes in discover - takes ~20s, returns empty. Search for it in muon - immediately there). The problem probably comes from searching in knewstuff, but it's making using discover bothersome. STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 448689] New: [FeatureRequest] Add khamburger menu in new virtual desktop overview
https://bugs.kde.org/show_bug.cgi?id=448689 Bug ID: 448689 Summary: [FeatureRequest] Add khamburger menu in new virtual desktop overview Product: plasmashell Version: 5.23.90 Platform: Neon Packages OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: saileshpoud...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Add KHamBurgerMenu at the right corner of the desktop overview effect to minimize all, maximize all and close all windows options which are opened at the current virtual desktop. PURPOSED https://i.imgur.com/GhyOilH.png SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE NEON TESTING KDE Plasma Version: 5.23.90 KDE Frameworks Version: 5.91.0 Qt Version: 5.15.3 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 447038] kdenlive crashes the first time a video clip is loaded in an empty project, when loading the clip causes the profile to change
https://bugs.kde.org/show_bug.cgi?id=447038 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #3 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 447218] Basically, while drawing anything (though I've done my testing just drawing lines) a sort of skipping occurs. So if I'm trying to draw a straight line for example, there will be r
https://bugs.kde.org/show_bug.cgi?id=447218 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #3 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 446080] Crash on launch
https://bugs.kde.org/show_bug.cgi?id=446080 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #3 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 446868] [x11] - 30bit color depth makes dock invisible with broken transparency
https://bugs.kde.org/show_bug.cgi?id=446868 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #9 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 447162] APP INMEDIATELY CLOSE AT OPENING
https://bugs.kde.org/show_bug.cgi?id=447162 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #4 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 447814] Swapping left alt with left win does not work correctly
https://bugs.kde.org/show_bug.cgi?id=447814 --- Comment #6 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 447236] Entire desktop crashes and disappears
https://bugs.kde.org/show_bug.cgi?id=447236 --- Comment #9 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 448688] Minimal overlap placement method does not take recency of activation into account
https://bugs.kde.org/show_bug.cgi?id=448688 Natalie Clarius changed: What|Removed |Added CC||natalie_clar...@yahoo.de -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 448688] New: Minimal overlap placement method does not take recency of activation into account
https://bugs.kde.org/show_bug.cgi?id=448688 Bug ID: 448688 Summary: Minimal overlap placement method does not take recency of activation into account Product: kwin Version: 5.23.5 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: natalie_clar...@yahoo.de Target Milestone: --- SUMMARY *** The minimal overlap placement method should take stacking order into account and prefer not to overlap windows that have recently been active. *** STEPS TO REPRODUCE 1. Select System Settings > Window Management > Window Behavior > Advanced > Window Placement > Minimal Overlapping. 2. Have a bunch of windows open covering most of the screen. 3. Activate a window towards the bottom/right of the screen. 4. Open a new window large enough not to fit into any free space. OBSERVED RESULT The new window is placed in the bottom/right corner, covering the recently active window. EXPECTED RESULT The new window is placed such that overlap with the most recently active window is avoided and a different part of the screen will be occupied instead. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.23.5 KDE Frameworks Version: 5.90.0 Qt Version: 5.15.2 Kernel Version: 5.16.0-arch1-1 (64-bit) Graphics Platform: X11 ADDITIONAL INFORMATION I've been observing that the minimal placement option will often position new windows right on top of the one that has just been worked in. I would imagine that for most use cases it would be preferable to keep recently active windows visible, and accept overlap windows that have been unused for longer instead. If understand the minimal overlap placement algorithm (https://invent.kde.org/plasma/kwin/-/blob/master/src/placement.cpp#L198 ?) correctly , the search does not take window's stacking/last-activated rank into account in computing the overlap, but rather will traverse the screen from left to right and top to bottom and sum up the potential overlaps with all windows equally. However, there is apparently already a penalty for windows set as keep above: https://invent.kde.org/plasma/kwin/-/blob/master/src/placement.cpp#L262 My proposal is to add a similar penalty for recent activity, either a simple extra condition for the one window that has been the most recently active, or a continuous rank based on stacking order. This would make the placement method somewhat "smarter" i.m.o. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 433094] No way to disable tearing prevention
https://bugs.kde.org/show_bug.cgi?id=433094 sameidan...@phaantm.de changed: What|Removed |Added Resolution|FIXED |--- CC||sameidan...@phaantm.de Status|RESOLVED|REOPENED --- Comment #20 from sameidan...@phaantm.de --- ...just why? This is a downgrade. Bring back that essential function. This is similar to Windows 8 FORCING desktop composition, and the resulting backlash. It doesn't matter how well you implement VSync, it introduces latency and not everyone wants it. It's known to cause stutters in many programs. It actively stifles high Hz refresh rate users. This change also made the quick and useful KWin "Suspend Compositing" shortcut completely useless, a dead function. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 448687] New: wayland: can not attach windows
https://bugs.kde.org/show_bug.cgi?id=448687 Bug ID: 448687 Summary: wayland: can not attach windows Product: kdenlive Version: 21.12.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: vdu...@gmail.com Target Milestone: --- Created attachment 145603 --> https://bugs.kde.org/attachment.cgi?id=145603=edit reproduction of the bug SUMMARY Can not attach kdenlive windows to main window while using plasma wayland session. STEPS TO REPRODUCE 1. Unattach window 2. Try to attach it back OBSERVED RESULT Kdenline windows has default titlebar. And its not possible to attach windows back to main window. EXPECTED RESULT SOFTWARE/OS VERSIONS Operating System: Manjaro Linux KDE Plasma Version: 5.23.4 KDE Frameworks Version: 5.89.0 Qt Version: 5.15.2 Kernel Version: 5.15.12-1-MANJARO (64-bit) Graphics Platform: Wayland Processors: 4 × Intel® Core™ i3-3120M CPU @ 2.50GHz Memory: 7.6 GiB of RAM Graphics Processor: Mesa DRI Intel® HD Graphics 4000 ADDITIONAL INFORMATION see attachment -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 383555] Yakuake doesn't show on Screen2 when I'm working on two monitors.
https://bugs.kde.org/show_bug.cgi?id=383555 --- Comment #19 from Josesk Volpe --- (In reply to jumax9 from comment #18) > Is your secondary monitor to the left or to the right? I have this issue in > X11 and for me displays _only_ on the secondary monitor. It's to the left -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 448394] Switching between eraser and pen using the buttons on the pen not working anymore after updating to 5.0.2 [XP-Pen Deco 03 Graphic Tablet]
https://bugs.kde.org/show_bug.cgi?id=448394 wwjubju...@gmail.com changed: What|Removed |Added CC||wwjubju...@gmail.com --- Comment #1 from wwjubju...@gmail.com --- Experiencing this same issue: Huion H1060 Pro tablet, Windows 10 64-bit, winTab In both krita 5.0.0, 5.0.1,and 5.0.2 the pen/eraser toggle shortcut does not toggle. This issue is not present in 4.4.8. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 448680] REGRESSION: no webrunners show up anymore
https://bugs.kde.org/show_bug.cgi?id=448680 Nate Graham changed: What|Removed |Added Ever confirmed|0 |1 Priority|NOR |VHI Status|REPORTED|CONFIRMED Keywords||regression CC||alexander.loh...@gmx.de, ||n...@kde.org --- Comment #1 from Nate Graham --- Can confirm. In the future, when you identify the exact commit (awesome!) feel free to CC the author. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 416655] Text field and spinbox of a non-KDE Qt5 app can be borderless with Breeze style
https://bugs.kde.org/show_bug.cgi?id=416655 Viorel-Cătălin Răpițeanu changed: What|Removed |Added CC||rapiteanu.cata...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[www.kde.org] [Bug 442983] Unclear where to report bugs at https://apps.kde.org/
https://bugs.kde.org/show_bug.cgi?id=442983 kde.bugzilla.2022@rancidbacon.com changed: What|Removed |Added CC||kde.bugzilla.2022.dkw@ranci ||dbacon.com --- Comment #4 from kde.bugzilla.2022@rancidbacon.com --- FWIW, with regard to the previous comment, note that (for me--a new account holder) the page https://invent.kde.org/websites/apps-kde-org/-/issues/new?issue[milestone_id]= has a banner that states: > Please note that all bug reports and feature requests should be filed on > bugs.kde.org > Issues on KDE Invent are used for tracking ongoing work and are for the use > of contributors and developers only. (I know this because I've ended up here because when I went to report an issue about `my.kde.org` on https://invent.kde.org/websites/my-kde-org/-/issues/new?issue[milestone_id]= and was shown the same banner.) -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 448502] Opening system settings makes the main content go back to featured
https://bugs.kde.org/show_bug.cgi?id=448502 Aleix Pol changed: What|Removed |Added Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas |ma/discover/commit/72706124 |ma/discover/commit/aa136091 |ce0010e76799bafca1facfa6d48 |67f9523b901db273c0662e02474 |4e69a |5d1ff --- Comment #5 from Aleix Pol --- Git commit aa13609167f9523b901db273c0662e024745d1ff by Aleix Pol Gonzalez, on behalf of Aleix Pol. Committed on 18/01/2022 at 01:42. Pushed by apol into branch 'Plasma/5.24'. Do not register a unique application when we call with --feedback This way it will not affect running instances. (cherry picked from commit 72706124ce0010e76799bafca1facfa6d484e69a) M +25 -24 discover/main.cpp https://invent.kde.org/plasma/discover/commit/aa13609167f9523b901db273c0662e024745d1ff -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 423493] Entry of Discover appears quickly in Plasma panel when User Feedback kcm is selected on X11
https://bugs.kde.org/show_bug.cgi?id=423493 Aleix Pol changed: What|Removed |Added Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas |ma/discover/commit/906d5e09 |ma/discover/commit/ff1c8f41 |6baccecd80711714d676702b45a |3fb49bcd993ebd412b5a078abd4 |534f0 |17d6e --- Comment #30 from Aleix Pol --- Git commit ff1c8f413fb49bcd993ebd412b5a078abd417d6e by Aleix Pol Gonzalez, on behalf of Aleix Pol. Committed on 18/01/2022 at 01:42. Pushed by apol into branch 'Plasma/5.24'. Mark the window as invisible when calling with --feedback This way it shouldn't glitch into the task manager (cherry picked from commit 906d5e096baccecd80711714d676702b45a534f0) M +4-0discover/main.cpp https://invent.kde.org/plasma/discover/commit/ff1c8f413fb49bcd993ebd412b5a078abd417d6e -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 423493] Entry of Discover appears quickly in Plasma panel when User Feedback kcm is selected on X11
https://bugs.kde.org/show_bug.cgi?id=423493 Aleix Pol changed: What|Removed |Added Resolution|--- |FIXED Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas |ma/discover/commit/35306636 |ma/discover/commit/906d5e09 |7b2bfec5385a22167388e499dce |6baccecd80711714d676702b45a |3819f |534f0 Status|ASSIGNED|RESOLVED --- Comment #29 from Aleix Pol --- Git commit 906d5e096baccecd80711714d676702b45a534f0 by Aleix Pol Gonzalez, on behalf of Aleix Pol. Committed on 18/01/2022 at 01:39. Pushed by apol into branch 'master'. Mark the window as invisible when calling with --feedback This way it shouldn't glitch into the task manager M +4-0discover/main.cpp https://invent.kde.org/plasma/discover/commit/906d5e096baccecd80711714d676702b45a534f0 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 448502] Opening system settings makes the main content go back to featured
https://bugs.kde.org/show_bug.cgi?id=448502 Aleix Pol changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED|RESOLVED Latest Commit||https://invent.kde.org/plas ||ma/discover/commit/72706124 ||ce0010e76799bafca1facfa6d48 ||4e69a --- Comment #4 from Aleix Pol --- Git commit 72706124ce0010e76799bafca1facfa6d484e69a by Aleix Pol Gonzalez, on behalf of Aleix Pol. Committed on 18/01/2022 at 01:39. Pushed by apol into branch 'master'. Do not register a unique application when we call with --feedback This way it will not affect running instances. M +25 -24 discover/main.cpp https://invent.kde.org/plasma/discover/commit/72706124ce0010e76799bafca1facfa6d484e69a -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 448520] Icon of Battery applet is not monochrome with no battery KDE 5.24 beta
https://bugs.kde.org/show_bug.cgi?id=448520 --- Comment #15 from Viorel-Cătălin Răpițeanu --- The 100% battery issue is not the indicators fault. Looking at the charging status using upower, it has a note saying that the value should be ignored (probably not implemented f or MX Master 2S). > upower --dump Device: /org/freedesktop/UPower/devices/mouse_hidpp_battery_1 native-path: hidpp_battery_1 model:Wireless Mouse MX Master 2S power supply: no mouse present: yes rechargeable:yes state: fully-charged warning-level: none battery-level: full percentage: 100% (should be ignored) icon-name: 'battery-full-charged-symbolic' -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 448520] Icon of Battery applet is not monochrome with no battery KDE 5.24 beta
https://bugs.kde.org/show_bug.cgi?id=448520 --- Comment #14 from Viorel-Cătălin Răpițeanu --- > Maybe is related to the VM. This happens on both the KDE Neon VM and my Arch Linux 5.24 beta install (bare metal). > On my laptop running neon unstable the icon is monochrome. > The bug occurs when there is no battery the screen brightness is not > adjustable maybe? Good point. My testing environment is a desktop PC. Also, the 'Battery and Brightness' panel (aside the Manually block sleep checkbox) displays: - On my bare metal Arch system, displays only one entry (the battery status of my Wireless mouse). - On the Neon VM it isn't showing anything. It's just an empty panel. As a side note, the battery status indicator for my mouse (Wireless MX Mouse 2S) displays the incorrect percentage. I haven't recharged it in the last week but somehow it's reported as being 100% full). -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 448686] New: Metadata
https://bugs.kde.org/show_bug.cgi?id=448686 Bug ID: 448686 Summary: Metadata Product: dolphin Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: search Assignee: dolphin-bugs-n...@kde.org Reporter: googlenavega...@hotmail.com CC: kfm-de...@kde.org Target Milestone: --- I have a bunch of videos mkv that have a xml text inside with metadata and, sure, the "KEYWORDS" string. It would be wonderful to make Dolphin find such files in Search bar like the Microsoft's explorer does and even display on the information panel (right) with it. Thank you for this wonderful work. Good day. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 448685] New: Cursor disappears when hovering pen and eraser sides of pen
https://bugs.kde.org/show_bug.cgi?id=448685 Bug ID: 448685 Summary: Cursor disappears when hovering pen and eraser sides of pen Product: krita Version: 5.0.2 Platform: Compiled Sources OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: * Unknown Assignee: krita-bugs-n...@kde.org Reporter: my.head.is.about.to.expl...@gmail.com Target Milestone: --- STEPS TO REPRODUCE 1. Hover the eraser side of a Wacom Intuos pen over the tablet without drawing anything. 2. Do the same with the pen side. OBSERVED RESULT The appropriate brush cursor is displayed for each side hovering. EXPECTED RESULT When switching to either side, a "No" symbol appears very briefly, and then the cursor is rendered invisible until the pen is touched to the tablet to draw something. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 448684] KDevelop process does not terminate.
https://bugs.kde.org/show_bug.cgi?id=448684 Lemuel Simon changed: What|Removed |Added CC||lemuelsimo...@protonmail.co ||m -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 448684] New: KDevelop process does not terminate.
https://bugs.kde.org/show_bug.cgi?id=448684 Bug ID: 448684 Summary: KDevelop process does not terminate. Product: kdevelop Version: 5.7.211201 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: kdevelop-bugs-n...@kde.org Reporter: lemuelsimo...@protonmail.com Target Milestone: --- SUMMARY Upon quitting KDevelop normally (Alt+F4 or closing the window), the window closes, but a `kdevelop` process is left in the background. The process would hog a single thread/CPU core with 100% usage, and it doesn't go away. No errors are thrown and no crashes occur. This is reproducible on every launch and exit of KDevelop. Clearing `~/.cache/kdevduchain` or `~.cache/kdevelop` doesn't change the outcome. Running it with `strace` doesn't show anything useful and running it in the console doesn't show anything either. STEPS TO REPRODUCE 1. Launch KDevelop 2. Quit KDevelop (doesn't matter if a session is chosen or not). OBSERVED RESULT KDevelop doesn't terminate and must be forcefully killed with 'kill -9'. The process hogs the CPU thread or core and upon relaunch (if the process is still active), the new KDevelop instance would complain about a session already being active. EXPECTED RESULT KDevelop's processes terminate normally. No zombie or background processes left behind. ADDITIONAL INFORMATION: I would like to think this was a regression, as this problem didn't occur in previous versions (IIRC). I do not recall having this problem two months ago. SOFTWARE/OS VERSIONS Operating System: openSUSE Leap 15.3 KDE Plasma Version: 5.23.5 KDE Frameworks Version: 5.90.0 Qt Version: 5.15.2 Kernel Version: 5.3.18-59.37-default (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™ i5-3320M CPU @ 2.60GHz Memory: 7.6 GiB of RAM Graphics Processor: Mesa DRI Intel® HD Graphics 4000 -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 448683] New: Password wont be accepted when fingerprint is configured
https://bugs.kde.org/show_bug.cgi?id=448683 Bug ID: 448683 Summary: Password wont be accepted when fingerprint is configured Product: kscreenlocker Version: 5.23.90 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: m.mcn...@gmail.com CC: bhus...@gmail.com Target Milestone: --- SUMMARY With Fingerprints enrolled, putting in my password is not accepted as a valid unlocking method. It prompts for the fingerprint after entering password and enter, then says unlocking failed STEPS TO REPRODUCE 1. lock screen 2. enter password 3. promted for fingerprint, even tho password has been supplied 4.enter password again 5. unlocking failed OBSERVED RESULT Only fingerprint can unlock my session EXPECTED RESULT A password unlocked session SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora KDE 35 KDE Plasma Version: 5.23.90 KDE Frameworks Version: 5.90 Qt Version: 5.15 ADDITIONAL INFORMATION I am using Marc Deop's plasma beta build for Fedroa https://copr.fedorainfracloud.org/coprs/marcdeop/plasma/ -- You are receiving this mail because: You are watching all bug changes.
[xdg-desktop-portal-kde] [Bug 448486] Unable to upload files from remote/network folders
https://bugs.kde.org/show_bug.cgi?id=448486 --- Comment #9 from john --- (In reply to Nate Graham from comment #8) > Definitely sounds like you're using the Portal dialog rather than the > plasmazilla package, and I can reproduce it. ?! But... Is that default on neon??? Because I don't remember changing anything like that! How can I get the "plasmazilla"? -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 448682] New: Feature request: search history
https://bugs.kde.org/show_bug.cgi?id=448682 Bug ID: 448682 Summary: Feature request: search history Product: Discover Version: 5.23.5 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: discover Assignee: lei...@leinir.dk Reporter: m...@kisaragi-hiu.com CC: aleix...@kde.org Target Milestone: --- SUMMARY Right now it is quite easy to lose your current search: when you leave application categories, the search bar is cleared. When you open another page (Settings, About, etc.), the search bar is also cleared. This is perhaps a separate issue, but Discover would be more usable if there is actually a search history. Even if it is truncated to, say, 3 items. STEPS TO REPRODUCE 1. Search something, let's say "camera" 2. Open About and have the search bar cleared 3. Notice how there is no way to get it back SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux (5.10.90-1-lts) KDE Plasma Version: 5.23.5 KDE Frameworks Version: 5.89.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 448681] New: digikam uses abandoned library incompatible with ffmpeg 5.0
https://bugs.kde.org/show_bug.cgi?id=448681 Bug ID: 448681 Summary: digikam uses abandoned library incompatible with ffmpeg 5.0 Product: digikam Version: 7.6.0 Platform: OpenMandriva Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: digikam-bugs-n...@kde.org Reporter: b...@lindev.ch Target Milestone: --- Digikam uses QtAV, which sadly has been abandoned upstream. http://www.qtav.org/blog/new-sdk.html This hasn't been much of a problem so far, but now that ffmpeg 5.0 has been released (and QtAV isn't compatible with it), we'll need a solution for people updating their ffmpeg. In case anyone is interested in forking the last public QtAV code (probably the only solution other than moving to another library), I've submitted a partial patch to make it compatible with ffmpeg 5.0 at https://github.com/wang-bin/QtAV/issues/1377 -- but I don't have the time do debug its various crashes right now (yet the patch may be a good starting point). -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 305136] File associations are broken in gtk/glib apps
https://bugs.kde.org/show_bug.cgi?id=305136 Nicolas Fella changed: What|Removed |Added CC||nicolas.fe...@gmx.de -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 448680] New: REGRESSION: no webrunners show up anymore
https://bugs.kde.org/show_bug.cgi?id=448680 Bug ID: 448680 Summary: REGRESSION: no webrunners show up anymore Product: frameworks-kio Version: git master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kio-bugs-n...@kde.org Reporter: herzensch...@gmail.com CC: kdelibs-b...@kde.org Target Milestone: --- >From this precise commit onwards I can no longer see any webrunners in the Web Search KCM. https://invent.kde.org/frameworks/kio/-/commit/aab35e6e514366e433b612636b520019b2413176 This is definitely a regression. It happens with a new user, I have noticed this after an update to my distro's git packages (Krypton), compiled KIO myself from master and could reproduce it, downgraded to a commit prior to the one I linked above and all webrunners show up again. The commit where things work and the bug is no longer reproducible is: https://invent.kde.org/frameworks/kio/-/commit/102b16b5a51136c2540a1b462f8389e27138a1f9 -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 448417] neon-settings needs updating to 50-kcoreaddons to reflect frameworks update
https://bugs.kde.org/show_bug.cgi?id=448417 --- Comment #6 from popov895 --- Figured it out! I have KDE neon Developer Edition installed on VirtualBox, and the issue appears after installing VirtualBox Guest Additions. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 448520] Icon of Battery applet is not monochrome with no battery KDE 5.24 beta
https://bugs.kde.org/show_bug.cgi?id=448520 --- Comment #13 from galdera --- I updated my VM with latest 5.24 beta packages. Still I see the no battery green icon. However in my case I need to set it to always shown other ways is hidden. Maybe is related to the VM. I hope it helps. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 448520] Icon of Battery applet is not monochrome with no battery KDE 5.24 beta
https://bugs.kde.org/show_bug.cgi?id=448520 galdera changed: What|Removed |Added Summary|Icon of Battery applet is |Icon of Battery applet is |not monochrome in KDE 5.24 |not monochrome with no |beta|battery KDE 5.24 beta -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 448520] Icon of Battery applet is not monochrome in KDE 5.24 beta
https://bugs.kde.org/show_bug.cgi?id=448520 --- Comment #12 from Patrick Silva --- On my laptop running neon unstable the icon is monochrome. The bug occurs when there is no battery the screen brightness is not adjustable maybe? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 448520] Icon of Battery applet is not monochrome in KDE 5.24 beta
https://bugs.kde.org/show_bug.cgi?id=448520 --- Comment #11 from Patrick Silva --- I have applied a 3rd-party global theme, switched back to Breeze global theme and the icon is still green. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 448520] Icon of Battery applet is not monochrome in KDE 5.24 beta
https://bugs.kde.org/show_bug.cgi?id=448520 --- Comment #10 from Viorel-Cătălin Răpițeanu --- (In reply to Nate Graham from comment #9) > Folks who can reproduce this, can you list what you are you using for your > Plasma theme and Icon theme? And can you reproduce it when both are Breeze? I'm using KDE Neon Unstable in a VM (last updated 3 minutes ago) and it's still reproducing. Nothing was changed on this VM from the default (theme/icons/settings/etc). -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 443919] Changes to breeze Qt in 5.23 not synced to GTK(2,3)
https://bugs.kde.org/show_bug.cgi?id=443919 --- Comment #8 from Nate Graham --- Git commit 3a328da00c4c9ae63488844686f2844d142c298f by Nate Graham, on behalf of Artem Grinev. Committed on 17/01/2022 at 22:42. Pushed by ngraham into branch 'master'. gtk3, gtk4: Disable overshoot effect This makes scrolling be more consistent with Breeze QStyle. M +2-127 src/gtk3/widgets/_overshoot.scss M +2-119 src/gtk4/widgets/_overshoot.scss https://invent.kde.org/plasma/breeze-gtk/commit/3a328da00c4c9ae63488844686f2844d142c298f -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 448520] Icon of Battery applet is not monochrome in KDE 5.24 beta
https://bugs.kde.org/show_bug.cgi?id=448520 --- Comment #9 from Nate Graham --- Folks who can reproduce this, can you list what you are you using for your Plasma theme and Icon theme? And can you reproduce it when both are Breeze? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 448520] Icon of Battery applet is not monochrome in KDE 5.24 beta
https://bugs.kde.org/show_bug.cgi?id=448520 --- Comment #8 from Patrick Silva --- On my system the icon is always green. The used visibility mode does no difference. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 448178] Crash when clicking on Logging
https://bugs.kde.org/show_bug.cgi?id=448178 Julius Künzel changed: What|Removed |Added CC||jk.kde...@smartlab.uber.spa ||ce Keywords||wayland -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 448520] Icon of Battery applet is not monochrome in KDE 5.24 beta
https://bugs.kde.org/show_bug.cgi?id=448520 --- Comment #7 from Nate Graham --- Based on the code, I'm not sure how that would make a difference, and indeed, when I give it a try, it doesn't. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 447912] Bugs In Kdenlive
https://bugs.kde.org/show_bug.cgi?id=447912 Julius Künzel changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO CC||jk.kde...@smartlab.uber.spa ||ce --- Comment #3 from Julius Künzel --- Can you please check if the instructions of @emohr help you? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 448679] KWin (desktop effects) shutters picture into triangles on Alt+Tab after sleep
https://bugs.kde.org/show_bug.cgi?id=448679 ratijas changed: What|Removed |Added Assignee|kwin-bugs-n...@kde.org |vlad.zahorod...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 448679] KWin (desktop effects) shutters picture into triangles on Alt+Tab after sleep
https://bugs.kde.org/show_bug.cgi?id=448679 ratijas changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 444725] Inserting ShuttleXpress into USB port while Kdenlive runnign causes kdenlive to crash
https://bugs.kde.org/show_bug.cgi?id=444725 Julius Künzel changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO CC||jk.kde...@smartlab.uber.spa ||ce --- Comment #1 from Julius Künzel --- Thanks for this report too :-) Is this also fixed for you in the meanwhile or does it still happen? If so can you please try to provide a gdb backtrace as described here: https://kdenlive.org/en/bug-reports/? -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 444596] Unnecessary clip jobs when adding clips
https://bugs.kde.org/show_bug.cgi?id=444596 Julius Künzel changed: What|Removed |Added Status|REPORTED|RESOLVED CC||jk.kde...@smartlab.uber.spa ||ce Resolution|--- |NOT A BUG --- Comment #1 from Julius Künzel --- Thanks for your report! These clip jobs create the audio thumbnails for the clips so in fact they are not unnecessary. We recently made some performance improvements that will land with 22.04 however these are mainly for when you open a project (if you want to test check out the Nightly version). Concerning the thumbnail generation there is not much we can improve at the moment. -- You are receiving this mail because: You are watching all bug changes.
[xdg-desktop-portal-kde] [Bug 448486] Unable to upload files from remote/network folders
https://bugs.kde.org/show_bug.cgi?id=448486 Nate Graham changed: What|Removed |Added Assignee|kio-bugs-n...@kde.org |jgrul...@redhat.com Status|REPORTED|CONFIRMED Component|Open/save dialogs |general Product|frameworks-kio |xdg-desktop-portal-kde Version|5.90.0 |5.23.90 Ever confirmed|0 |1 Priority|NOR |HI --- Comment #8 from Nate Graham --- Definitely sounds like you're using the Portal dialog rather than the plasmazilla package, and I can reproduce it. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 91793] Trying to overwrite a file after having modified it (resized) doesn't save the file
https://bugs.kde.org/show_bug.cgi?id=91793 caulier.gil...@gmail.com changed: What|Removed |Added Version Fixed In||7.6.0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 91532] resize image rounding error
https://bugs.kde.org/show_bug.cgi?id=91532 caulier.gil...@gmail.com changed: What|Removed |Added Version Fixed In||7.6.0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 115447] resize EXIF-rotated images doesn't work
https://bugs.kde.org/show_bug.cgi?id=115447 caulier.gil...@gmail.com changed: What|Removed |Added Version Fixed In||7.6.0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 311423] showfoto crashes during "restore photograph" resize
https://bugs.kde.org/show_bug.cgi?id=311423 caulier.gil...@gmail.com changed: What|Removed |Added Version Fixed In||7.6.0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 103243] Logic error in image resize dialog
https://bugs.kde.org/show_bug.cgi?id=103243 caulier.gil...@gmail.com changed: What|Removed |Added Version Fixed In||7.6.0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 149284] digikam resize should bin pixels together
https://bugs.kde.org/show_bug.cgi?id=149284 caulier.gil...@gmail.com changed: What|Removed |Added Version Fixed In||7.6.0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 309857] crash when starting image editor >> improvements >> restaurations
https://bugs.kde.org/show_bug.cgi?id=309857 caulier.gil...@gmail.com changed: What|Removed |Added Resolution|DUPLICATE |FIXED Version Fixed In||7.6.0 --- Comment #2 from caulier.gil...@gmail.com --- Fixed with https://bugs.kde.org/show_bug.cgi?id=303119 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 301526] Restoration enhancement filtering crashes Digikam image editor.
https://bugs.kde.org/show_bug.cgi?id=301526 caulier.gil...@gmail.com changed: What|Removed |Added Version Fixed In||7.6.0 Resolution|DUPLICATE |FIXED --- Comment #3 from caulier.gil...@gmail.com --- Fixed with https://bugs.kde.org/show_bug.cgi?id=303119 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 109255] Improvement suggestions for the Image Restoration tool
https://bugs.kde.org/show_bug.cgi?id=109255 caulier.gil...@gmail.com changed: What|Removed |Added Version Fixed In||7.6.0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 166579] Free Rotation does not show image
https://bugs.kde.org/show_bug.cgi?id=166579 caulier.gil...@gmail.com changed: What|Removed |Added Version Fixed In||7.6.0 Resolution|DUPLICATE |FIXED CC||caulier.gil...@gmail.com --- Comment #6 from caulier.gil...@gmail.com --- Fixed with https://bugs.kde.org/show_bug.cgi?id=166310 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 96251] linking fails (missing -limlib2)
https://bugs.kde.org/show_bug.cgi?id=96251 caulier.gil...@gmail.com changed: What|Removed |Added Version Fixed In||7.6.0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 96488] Free rotation tool not showing in menu
https://bugs.kde.org/show_bug.cgi?id=96488 caulier.gil...@gmail.com changed: What|Removed |Added Version Fixed In||7.6.0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 139742] Free rotation in portrait mode no auto crop for biggest area
https://bugs.kde.org/show_bug.cgi?id=139742 caulier.gil...@gmail.com changed: What|Removed |Added Version Fixed In||7.6.0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 120282] Free rotation tool results in black canvas in image editor
https://bugs.kde.org/show_bug.cgi?id=120282 caulier.gil...@gmail.com changed: What|Removed |Added Version Fixed In||7.6.0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 274631] Applying free rotation to image produces white pixels in some areas which should be near black
https://bugs.kde.org/show_bug.cgi?id=274631 caulier.gil...@gmail.com changed: What|Removed |Added Version Fixed In||7.6.0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 100880] Auto-resize image to keep a rectangular photo
https://bugs.kde.org/show_bug.cgi?id=100880 caulier.gil...@gmail.com changed: What|Removed |Added Version Fixed In||7.6.0 -- You are receiving this mail because: You are watching all bug changes.
