[plasmashell] [Bug 427861] Sometimes desktop loses its settings (wallpaper, widgets, icons settings) after re-login
https://bugs.kde.org/show_bug.cgi?id=427861 --- Comment #46 from tagwer...@innerjoin.org --- (In reply to tagwerk19 from comment #43) > I could have had one issue, leading to the placement of the shortcuts on the > desktop being forgotten, but I wasn't on the ball enough to troubleshoot. I'd say I've seen it again, forgetting the size/placement of the desktop icons (hadn't done any more customisation) Fedora 34 as a guest VM, single screen, virtio graphics, X11... I also noticed an enquiry here: https://old.reddit.com/r/kde/comments/pl5xfq/howwhy_does_ubuntu_periodically_reset_my_plasma/ -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 442189] HEIC photos with GPS coordinates embeded in metadata are not used in digikam database for geolocation
https://bugs.kde.org/show_bug.cgi?id=442189 --- Comment #4 from Maik Qualmann --- Well, the problem is not limited to HEIC files only, we already have an open bug report. It also affects other metadata (photo information, date, etc.). I have not yet been able to reproduce the problem on two different Windows computers, the problem is also unknown under Linux. I suspect an external influence, such as an open Explorer window or an anti-virus program. If you can reproduce it, please download DebugView from Microsoft and set the Debug environment variable as described here for Windows: https://www.digikam.org/contribute/ Try to get a log of the first scan of the HEIC files. Maik -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 441559] Project Render no longer functioning. Hangs at "Waiting"
https://bugs.kde.org/show_bug.cgi?id=441559 --- Comment #8 from LornaI --- I am unsure as to what further info you need me to provide. Having uninstalled and reinstalled the application twice now via snap, the project does now render but the UI popup within the application still sticks at 'waiting' and it is impossible to submit any further jobs without manually removing the job and restarting the application. This is obviously less serious than not rendering at all, but it is still a bug, in my opinion. If you want me to provide logs, please tell me what logs you want, and where to find them. I am an educated user, not a programmer. -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 442134] "const" correctness in Umbrello sources
https://bugs.kde.org/show_bug.cgi?id=442134
Oliver Kellogg changed:
What|Removed |Added
Resolution|--- |FIXED
Latest Commit||https://invent.kde.org/sdk/
||umbrello/commit/0372f89d799
||5a5fbc557e6c6090208bc54950e
||88
Status|ASSIGNED|RESOLVED
--- Comment #4 from Oliver Kellogg ---
Git commit 0372f89d7995a5fbc557e6c6090208bc54950e88 by Oliver Kellogg.
Committed on 10/09/2021 at 05:51.
Pushed by okellogg into branch 'master'.
Fix for "C++ importer does not recognize 'noexcept' keyword" :
lib/cppparser/keywords.h
- Align INSERT calls as table. Add INSERT("noexcept", Token_noexcept).
lib/cppparser/lexer.h
- In enum Type add Token_noexcept.
lib/cppparser/parser.cpp
- In functions skipUntilDeclaration, skipUntilStatement while-loop
switch add case Token_noexcept.
- In function parseExceptionSpecification handle the case
(m_lexer->lookAhead(0) == Token_noexcept).
test/import/cxx/const-methods.h
- Rename file to const-noexcept-methods.h.
test/import/cxx/const-noexcept-methods.h
- Rename class to ConstNoexceptMethodClass.
- Add NoexceptMethod with trailing noexcept.
- Add ConstNoexceptMethod with const noexcept and implementation.
Related: bug 338649
M +84 -83 lib/cppparser/keywords.h
M +1-0lib/cppparser/lexer.h
M +15 -2lib/cppparser/parser.cpp
D +0-3test/import/cxx/const-methods.h
A +5-0test/import/cxx/const-noexcept-methods.h *
The files marked with a * at the end have a non valid license. Please read:
https://community.kde.org/Policies/Licensing_Policy and use the headers which
are listed at that page.
https://invent.kde.org/sdk/umbrello/commit/0372f89d7995a5fbc557e6c6090208bc54950e88
--
You are receiving this mail because:
You are watching all bug changes.
[umbrello] [Bug 338649] Extend C++ import for C++11
https://bugs.kde.org/show_bug.cgi?id=338649
--- Comment #24 from Oliver Kellogg ---
Git commit 0372f89d7995a5fbc557e6c6090208bc54950e88 by Oliver Kellogg.
Committed on 10/09/2021 at 05:51.
Pushed by okellogg into branch 'master'.
Fix for "C++ importer does not recognize 'noexcept' keyword" :
lib/cppparser/keywords.h
- Align INSERT calls as table. Add INSERT("noexcept", Token_noexcept).
lib/cppparser/lexer.h
- In enum Type add Token_noexcept.
lib/cppparser/parser.cpp
- In functions skipUntilDeclaration, skipUntilStatement while-loop
switch add case Token_noexcept.
- In function parseExceptionSpecification handle the case
(m_lexer->lookAhead(0) == Token_noexcept).
test/import/cxx/const-methods.h
- Rename file to const-noexcept-methods.h.
test/import/cxx/const-noexcept-methods.h
- Rename class to ConstNoexceptMethodClass.
- Add NoexceptMethod with trailing noexcept.
- Add ConstNoexceptMethod with const noexcept and implementation.
Related: bug 442134
M +84 -83 lib/cppparser/keywords.h
M +1-0lib/cppparser/lexer.h
M +15 -2lib/cppparser/parser.cpp
D +0-3test/import/cxx/const-methods.h
A +5-0test/import/cxx/const-noexcept-methods.h *
The files marked with a * at the end have a non valid license. Please read:
https://community.kde.org/Policies/Licensing_Policy and use the headers which
are listed at that page.
https://invent.kde.org/sdk/umbrello/commit/0372f89d7995a5fbc557e6c6090208bc54950e88
--
You are receiving this mail because:
You are watching all bug changes.
[frameworks-baloo] [Bug 435024] Baloo hopefully bluffing about indexing its index
https://bugs.kde.org/show_bug.cgi?id=435024 --- Comment #3 from tagwer...@innerjoin.org --- LMDB files are not included in the shared-mime-info database, reported: https://gitlab.freedesktop.org/xdg/shared-mime-info/-/issues/168 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 436905] layers randomly combine without user imput
https://bugs.kde.org/show_bug.cgi?id=436905 --- Comment #6 from haleeang...@gmail.com --- okay, thank you for your patience! :] On Thu, Sep 9, 2021 at 11:36 PM Bug Janitor Service < bugzilla_nore...@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=436905 > > Bug Janitor Service changed: > >What|Removed |Added > > > Resolution|WAITINGFORINFO |--- > Status|NEEDSINFO |REPORTED > > --- Comment #5 from Bug Janitor Service --- > Thanks for your comment! > > Automatically switching the status of this bug to REPORTED so that the KDE > team > knows that the bug is ready to get confirmed. > > In the future you may also do this yourself when providing needed > information. > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 442247] New: [Request] Add ability to assign tags in brush saving dialog
https://bugs.kde.org/show_bug.cgi?id=442247 Bug ID: 442247 Summary: [Request] Add ability to assign tags in brush saving dialog Product: krita Version: 5.0.0-beta1 Platform: Appimage OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: Resource Management Assignee: krita-bugs-n...@kde.org Reporter: tomtomtomreportin...@gmail.com Target Milestone: --- I think the first thing that a lot of people want to do after saving a new brush is adding tags to it. I think it would be a good idea to add something like the tag editor in the Resource Manager to the brush saving dialog. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 442246] New: [Request] Put brush preset backups inside their own separate folder within the paintoppresets folder
https://bugs.kde.org/show_bug.cgi?id=442246 Bug ID: 442246 Summary: [Request] Put brush preset backups inside their own separate folder within the paintoppresets folder Product: krita Version: 5.0.0-beta1 Platform: Appimage OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: Resource Management Assignee: krita-bugs-n...@kde.org Reporter: tomtomtomreportin...@gmail.com Target Milestone: --- I iterate on my custom brushes quite a bit and basically 95% of my paintoppresets folder is backups, making it a bit annoying to pick out actual brushes from the backups. Would it be a problem if these backups were automatically put inside a separate backup folder within the same directory? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 442198] Krita 5.1.0 prealpha(git 8376871) : brush texture blending modes not behaving correctly
https://bugs.kde.org/show_bug.cgi?id=442198 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #3 from Bug Janitor Service --- Thanks for your comment! Automatically switching the status of this bug to REPORTED so that the KDE team knows that the bug is ready to get confirmed. In the future you may also do this yourself when providing needed information. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 441559] Project Render no longer functioning. Hangs at "Waiting"
https://bugs.kde.org/show_bug.cgi?id=441559 --- Comment #7 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.
[krita] [Bug 436905] layers randomly combine without user imput
https://bugs.kde.org/show_bug.cgi?id=436905 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #5 from Bug Janitor Service --- Thanks for your comment! Automatically switching the status of this bug to REPORTED so that the KDE team knows that the bug is ready to get confirmed. In the future you may also do this yourself when providing needed information. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 442236] [Transform tool] Tool options doesn't change if I select different transforming method
https://bugs.kde.org/show_bug.cgi?id=442236 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #3 from Bug Janitor Service --- Thanks for your comment! Automatically switching the status of this bug to REPORTED so that the KDE team knows that the bug is ready to get confirmed. In the future you may also do this yourself when providing needed information. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 429351] Copy and paste in editor is losing kerning property
https://bugs.kde.org/show_bug.cgi?id=429351 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #3 from Bug Janitor Service --- Thanks for your comment! Automatically switching the status of this bug to REPORTED so that the KDE team knows that the bug is ready to get confirmed. In the future you may also do this yourself when providing needed information. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 440870] Krita 5 git 08ccd37: When I converted colorized mask layers to paint layer, the converted layers jump on top of the line art layer (the layer I use for drawing line art)
https://bugs.kde.org/show_bug.cgi?id=440870 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- 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.
[plasmashell] [Bug 441574] Scrolling in the system tray entries section with a touchpad is stuttery
https://bugs.kde.org/show_bug.cgi?id=441574 --- Comment #2 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.
[frameworks-kglobalaccel] [Bug 440761] Keyboard short cuts no longer work after update to fedora 34
https://bugs.kde.org/show_bug.cgi?id=440761 --- Comment #8 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.
[Discover] [Bug 441538] Not correct work search system in Discover program center
https://bugs.kde.org/show_bug.cgi?id=441538 --- Comment #2 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.
[plasmashell] [Bug 438092] Some Hindi words are not displaying in a proper format.
https://bugs.kde.org/show_bug.cgi?id=438092 --- Comment #10 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.
[dolphin] [Bug 411878] Dolphin is not clearing prior filter view if directory is open
https://bugs.kde.org/show_bug.cgi?id=411878 Eduardo changed: What|Removed |Added Assignee|dolphin-bugs-n...@kde.org |eduardo.c...@kdemail.net Status|CONFIRMED |ASSIGNED --- Comment #2 from Eduardo --- I found the bug: void KFileItemModel::applyFilters() in the file src/kitemviews/kfileitemmodel.cpp. The algorithm creates the bug on purpose, but it doesn't have to. I'll try to fix it over the weekend. Assigning to myself. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 427771] Flat/Adaptive pointer acceleration setting does nothing on wayland
https://bugs.kde.org/show_bug.cgi?id=427771 Eduardo changed: What|Removed |Added Ever confirmed|0 |1 Version|5.20.0 |5.22.5 Status|REPORTED|CONFIRMED CC||eduardo.c...@kdemail.net --- Comment #7 from Eduardo --- Happens to me under Wayland on ArchLinux. Under XOrg it works fine. I'm changing to CONFIRMED. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 442173] Conky goes above windows previews on Overview active
https://bugs.kde.org/show_bug.cgi?id=442173
--- Comment #3 from Vladimir Yerilov ---
Sure, here it goes:
_NET_WM_ALLOWED_ACTIONS(ATOM) = _NET_WM_ACTION_CHANGE_DESKTOP
_NET_WM_DESKTOP(CARDINAL) = 0
WM_STATE(WM_STATE):
window state: Normal
icon window: 0x0
_NET_WM_STATE(ATOM) = _NET_WM_STATE_BELOW, _NET_WM_STATE_SKIP_TASKBAR,
_NET_WM_STATE_SKIP_PAGER, _KDE_NET_WM_STATE_SKIP_SWITCHER
_NET_WM_WINDOW_TYPE(ATOM) = _NET_WM_WINDOW_TYPE_NORMAL
_KDE_NET_WM_USER_CREATION_TIME(CARDINAL) = 45458
WM_PROTOCOLS(ATOM): protocols
WM_NAME(STRING) = "conky (reiwa)"
WM_LOCALE_NAME(STRING) = "en_GB.UTF-8"
WM_CLASS(STRING) = "conky", "conky"
WM_HINTS(WM_HINTS):
Client accepts input or input focus: True
Initial state is Normal State.
WM_CLIENT_MACHINE(STRING) = "reiwa"
WM_COMMAND(STRING) = { "/usr/bin/conky", "--pause=1" }
--
You are receiving this mail because:
You are watching all bug changes.
[Bluedevil] [Bug 420100] Can't send file over bluetooth
https://bugs.kde.org/show_bug.cgi?id=420100 Leon changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[Bluedevil] [Bug 420100] Can't send file over bluetooth
https://bugs.kde.org/show_bug.cgi?id=420100 --- Comment #3 from Leon --- I checked and obexd was installed. Re-tested using share and send files options and it seems to be working. The error no loger appears. will mark as fixed -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 441956] Qthread with Python broken in Krita 5
https://bugs.kde.org/show_bug.cgi?id=441956 --- Comment #4 from keyth_qcfx2 --- I was asked a minimal working example not efficiency... in Krita 4.4.5 and below does not go slow and in Krita 5 goes slow, what can I imagine it too be? Because if I did not put it on a QThread it would act slow just like it is in Krita5 but on every version regardless. If QThread does not work it is just like any other class but on the same thread no? That is why I think it is something related to QThread. Thing is my code for how inefficient it might be it WORKS in QThread normal(no freeze frames) and then is best example to detect problems because it is not efficient. Your arguing the survivors bias. Because I have been searching other ways to render this since my lack of QThread or whatever it is and I have found a new way and is almost in real time now. Not to mention despite my example updating with mouseEvent it only uses the image from one second ago, run sends images on it's own it is not triggered to read by mouseMove. but that is beside the point. If I am 100% sure it is QThread. no I am not, but my testings pointed me in that direction because that QThread class only does one thing. if it is not the QThread it is something inside of it, but everything inside seem to be working normal on their own. I don't think it is fractional UI scaling because my other plugins are working correctly with scaling in this Krita 5 environment and they were severely affected by it in Krita4.4.7. And I scale QImage with them too and did not happen to notice issues with them yet. The things that differs for me here is it being inside the QThread and requesting a Thumbnail that I never used before, but I don't making thumbnails changed. -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 187116] Holidays > 1 day show as multiple holidays.
https://bugs.kde.org/show_bug.cgi?id=187116 Bug Janitor Service changed: What|Removed |Added Status|CONFIRMED |ASSIGNED --- Comment #9 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/pim/eventviews/-/merge_requests/41 -- You are receiving this mail because: You are watching all bug changes.
[kpat] [Bug 442245] New: Random crashes in KPat
https://bugs.kde.org/show_bug.cgi?id=442245 Bug ID: 442245 Summary: Random crashes in KPat Product: kpat Version: unspecified Platform: Debian stable OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: co...@kde.org Reporter: spikethehobbitm...@runbox.com CC: kde-games-b...@kde.org Target Milestone: --- Application: kpat (21.8.0) Qt Version: 5.15.2 Frameworks Version: 5.85.0 Operating System: Linux 5.10.0-8-amd64 x86_64 Windowing System: X11 Drkonqi Version: 5.21.5 Distribution: Debian GNU/Linux bookworm/sid -- Information about the crash: - What I was doing when the application crashed: This crash occurred when starting a new game after playing for a while. I don't know if it is related but I often get random display corruption where cards don't render properly. The crash can be reproduced sometimes. -- Backtrace: Application: KPatience (kpat), signal: Segmentation fault [KCrash Handler] #4 0x7f1a51057425 in KSharedDataCache::Private::lock() const (this=0x561e66cee2f0) at ./src/lib/caching/kshareddatacache.cpp:1195 #5 KSharedDataCache::Private::CacheLocker::cautiousLock() (this=this@entry=0x7ffd3fe54b60) at ./src/lib/caching/kshareddatacache.cpp:1219 #6 0x7f1a5105300e in KSharedDataCache::Private::CacheLocker::CacheLocker(KSharedDataCache::Private const*) (_d=, this=0x7ffd3fe54b60) at ./src/lib/caching/kshareddatacache.cpp:1269 #7 KSharedDataCache::find(QString const&, QByteArray*) const (this=this@entry=0x561e66d3e030, key=..., destination=destination@entry=0x7ffd3fe54c30) at ./src/lib/caching/kshareddatacache.cpp:1550 #8 0x7f1a51561624 in KSharedPixmapCacheMixin::findPixmap(QString const&, QPixmap*) const (destination=0x561e66e1a298, key=..., this=0x561e66d3e020) at /usr/include/KF5/KGuiAddons/kimagecache.h:138 #9 KAbstractCardDeckPrivate::requestPixmap(unsigned int, bool) (this=0x561e678bbdd0, id=, faceUp=) at ./src/libkcardgame/kabstractcarddeck.cpp:205 #10 0x7f1a51561935 in KAbstractCardDeck::cardPixmap(unsigned int, bool) (this=, id=, faceUp=) at ./src/libkcardgame/kabstractcarddeck.cpp:516 #11 0x7f1a5156383c in KCard::paint(QPainter*, QStyleOptionGraphicsItem const*, QWidget*) (this=0x561e6797a3f0, painter=0x7ffd3fe552a0, option=, widget=) at ./src/libkcardgame/kcard.cpp:319 #12 0x7f1a50cbc99f in QGraphicsScenePrivate::draw(QGraphicsItem*, QPainter*, QTransform const*, QTransform const*, QRegion*, QWidget*, double, QTransform const*, bool, bool) (this=0x561e67a52360, item=, painter=0x7ffd3fe552a0, viewTransform=0x7ffd3fe552f0, transformPtr=, exposedRegion=0x561e66c2cfa0, widget=, opacity=, effectTransform=, wasDirtyParentSceneTransform=, drawItem=) at graphicsview/qgraphicsscene.cpp:4981 #13 0x7f1a50cbd9c0 in QGraphicsScenePrivate::drawSubtreeRecursive(QGraphicsItem*, QPainter*, QTransform const*, QRegion*, QWidget*, double, QTransform const*) (this=this@entry=0x561e67a52360, item=0x561e6797a400, painter=painter@entry=0x7ffd3fe552a0, viewTransform=viewTransform@entry=0x7ffd3fe552f0, exposedRegion=exposedRegion@entry=0x561e66c2cfa0, widget=, widget@entry=0x561e67902940, parentOpacity=parentOpacity@entry=1, effectTransform=0x0) at graphicsview/qgraphicsscene.cpp:4873 #14 0x7f1a50cbdfe2 in QGraphicsScenePrivate::drawItems(QPainter*, QTransform const*, QRegion*, QWidget*) (this=this@entry=0x561e67a52360, painter=painter@entry=0x7ffd3fe552a0, viewTransform=viewTransform@entry=0x7ffd3fe552f0, exposedRegion=exposedRegion@entry=0x561e66c2cfa0, widget=0x561e67902940) at graphicsview/qgraphicsscene.cpp:4735 #15 0x7f1a50ce15b2 in QGraphicsView::paintEvent(QPaintEvent*) (this=, event=) at ../../include/QtWidgets/../../src/widgets/graphicsview/qgraphicsscene.h:307 #16 0x7f1a509dafae in QWidget::event(QEvent*) (this=this@entry=0x561e670c6b00, event=event@entry=0x7ffd3fe55640) at kernel/qwidget.cpp:9019 #17 0x7f1a50a832fe in QFrame::event(QEvent*) (this=0x561e670c6b00, e=0x7ffd3fe55640) at widgets/qframe.cpp:550 #18 0x7f1a4fe85d33 in QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) (event=, receiver=) at kernel/qcoreapplication.cpp:1189 #19 QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) (receiver=receiver@entry=0x561e67902940, event=event@entry=0x7ffd3fe55640) at kernel/qcoreapplication.cpp:1178 #20 0x7f1a5099b14e in QApplicationPrivate::notify_helper(QObject*, QEvent*) (this=, receiver=0x561e67902940, e=0x7ffd3fe55640) at kernel/qapplication.cpp:3626 #21 0x7f1a4fe85fca in QCoreApplication::notifyInternal2(QObject*, QEvent*) (receiver=0x561e67902940, event=0x7ffd3fe55640) at kernel/qcoreapplication.cpp:1063 #22 0x7f1a509d3116 in QWidgetPrivate::sendPaintEvent(QRegion const&) (this=this@entry=0x561e66bb2e90, toBePainted=...) at kernel/qwidget.cpp:5467 #23 0x7f1a509d3962 in
[kwin] [Bug 371502] Task switcher (task manager) only allows to switch between two windows of application
https://bugs.kde.org/show_bug.cgi?id=371502 Henrique Sant'Anna changed: What|Removed |Added CC||hsanta...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 435667] Overlapping of events produces gaps in month view
https://bugs.kde.org/show_bug.cgi?id=435667 gjditchfi...@acm.org changed: What|Removed |Added Latest Commit||https://invent.kde.org/pim/ ||eventviews/commit/a0a305495 ||1109d11b963df5348c40db61312 ||88eb Status|ASSIGNED|RESOLVED Resolution|--- |FIXED --- Comment #6 from gjditchfi...@acm.org --- Git commit a0a3054951109d11b963df5348c40db6131288eb by Glen Ditchfield, on behalf of Laurent Montel. Committed on 09/09/2021 at 01:18. Pushed by gditchfield into branch 'release/21.08'. Avoid vertical gaps around multi-day events in the month view Given some single-day events and a multi-day event that ends on that day, the layout heuristic would place the single-day events first, leaving a gap above the multi-day event. Placing longer events first tends to produce more compact layouts. M +4-0src/CMakeLists.txt A +3-0src/month/autotests/CMakeLists.txt A +89 -0src/month/autotests/monthitemordertest.cpp [License: GPL(v2.0+)] M +12 -19 src/month/monthitem.cpp M +7-5src/month/monthitem.h https://invent.kde.org/pim/eventviews/commit/a0a3054951109d11b963df5348c40db6131288eb -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 429377] Wayland: zoom effect reverting to proportional mouse-tracking
https://bugs.kde.org/show_bug.cgi?id=429377 --- Comment #8 from Henrique Sant'Anna --- I can reproduce it on wayland. With X11 it works ok. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 429377] Wayland: zoom effect reverting to proportional mouse-tracking
https://bugs.kde.org/show_bug.cgi?id=429377 Henrique Sant'Anna changed: What|Removed |Added CC||hsanta...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 442244] New: firefox
https://bugs.kde.org/show_bug.cgi?id=442244 Bug ID: 442244 Summary: firefox Product: plasmashell Version: 5.22.5 Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: 1995kr...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.22.5) Qt Version: 5.15.3 Frameworks Version: 5.85.0 Operating System: Linux 5.11.0-34-generic x86_64 Windowing System: X11 Drkonqi Version: 5.22.5 Distribution: KDE neon User Edition 5.22 -- Information about the crash: - What I was doing when the application crashed: I uninstalled the browser firefox and then installed it from flatpak, then opened the application menu and there was a failure The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault [New LWP 1436] [New LWP 1443] [New LWP 1444] [New LWP 1445] [New LWP 1446] [New LWP 1447] [New LWP 1657] [New LWP 1682] [New LWP 1691] [New LWP 1704] [New LWP 1708] [New LWP 1853] [New LWP 2020] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". 0x7f4a7f07caff in __GI___poll (fds=0x7ffe346cbf38, nfds=1, timeout=1000) at ../sysdeps/unix/sysv/linux/poll.c:29 [Current thread is 1 (Thread 0x7f4a7b1dc9c0 (LWP 1424))] Thread 14 (Thread 0x7f4a450e6700 (LWP 2020)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x5585df534820) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x5585df5347d0, cond=0x5585df5347f8) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x5585df5347f8, mutex=0x5585df5347d0) at pthread_cond_wait.c:638 #3 0x7f4a7f410f2b in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f4a81068b44 in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #5 0x7f4a81068fb9 in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #6 0x7f4a7f40adbc in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f4a7e360609 in start_thread (arg=) at pthread_create.c:477 #8 0x7f4a7f089293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 13 (Thread 0x7f4a1700 (LWP 1853)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x5585df3bb630) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x5585df3bb5e0, cond=0x5585df3bb608) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x5585df3bb608, mutex=0x5585df3bb5e0) at pthread_cond_wait.c:638 #3 0x7f4a7f410f2b in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f4a81068b44 in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #5 0x7f4a81068fb9 in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #6 0x7f4a7f40adbc in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f4a7e360609 in start_thread (arg=) at pthread_create.c:477 #8 0x7f4a7f089293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 12 (Thread 0x7f4a46d3f700 (LWP 1708)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x5585daa92184) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x5585daa92130, cond=0x5585daa92158) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x5585daa92158, mutex=0x5585daa92130) at pthread_cond_wait.c:638 #3 0x7f4a7f410f2b in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f4a81068b44 in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #5 0x7f4a81068fb9 in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #6 0x7f4a7f40adbc in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f4a7e360609 in start_thread (arg=) at pthread_create.c:477 #8 0x7f4a7f089293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 11 (Thread 0x7f4a4c849700 (LWP 1704)): #0 __GI___libc_read (nbytes=16, buf=0x7f4a4c848990, fd=29) at ../sysdeps/unix/sysv/linux/read.c:26 #1 __GI___libc_read (fd=29, buf=0x7f4a4c848990, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:24 #2 0x7f4a7d976b2f in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f4a7d92debe in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f4a7d92e312 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f4a7d92e4a3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7f4a7f64bfdb in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f4a7f5f026b in QEventLoop::exec(QFlags) () from
[kwin] [Bug 440002] Alternate Zoom effect shortcuts are not saved
https://bugs.kde.org/show_bug.cgi?id=440002 Henrique Sant'Anna changed: What|Removed |Added CC||hsanta...@gmail.com --- Comment #4 from Henrique Sant'Anna --- What do you meant on OBSERVED RESULT when said "It is not saved" ? Are you saying that after setting new shorcuts and pressing OK button to confirm you reopen the setting and the shortcuts are not there anymore? I tested on X11 to set Meta+y as reduce zoom and it works for me. There are some open bugs related to shortcuts not working when there is set multiple keyboard layouts. Does it is your case? Do you have more than one keyboard layout configured? Does it reproduces to any layout? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 441898] zoom breaks when reaching above 4x zoom levels
https://bugs.kde.org/show_bug.cgi?id=441898 Henrique Sant'Anna changed: What|Removed |Added CC||hsanta...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Qt/KDE Flatpak Runtime] [Bug 436864] Grayscale antialiasing in apps using KDE Platform
https://bugs.kde.org/show_bug.cgi?id=436864 davidkace...@gmail.com changed: What|Removed |Added CC||davidkace...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 442243] Latte Dock (Panel) is still marked as 'inhibiting sleep' when the battery applet's 'Inhibit sleep' button is toggled off.
https://bugs.kde.org/show_bug.cgi?id=442243 Lemuel Simon changed: What|Removed |Added CC||lemuelsimo...@protonmail.co ||m -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 442243] New: Latte Dock (Panel) is still marked as 'inhibiting sleep' when the battery applet's 'Inhibit sleep' button is toggled off.
https://bugs.kde.org/show_bug.cgi?id=442243 Bug ID: 442243 Summary: Latte Dock (Panel) is still marked as 'inhibiting sleep' when the battery applet's 'Inhibit sleep' button is toggled off. Product: lattedock Version: 0.10.1 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: application Assignee: mvourla...@gmail.com Reporter: lemuelsimo...@protonmail.com Target Milestone: --- Created attachment 141433 --> https://bugs.kde.org/attachment.cgi?id=141433=edit Screenshot of the battery applet in Latte Dock (panel). After toggling off the 'Inhibit automatic sleep' button in the battery applet, Latte-dock is still being reported as 'inhibiting sleep'. SUMMARY After toggling off the 'Inhibit automatic sleep' button in the battery applet, Latte-dock is still being reported as 'inhibiting sleep and screen locking' in the applet. With Vivaldi, Falkon and Dragon Player, during media playback they show up in the battery applet and disappear when the video is paused or stopped (as they should). However, Latte-dock persists. I've also performed the 'Inhibit' toggle in the battery applet in Plasma's own panel, the error doesn't occur there, it seems specific to Latte-dock. STEPS TO REPRODUCE 1. Open the battery applet on the Latte-dock. 2. Toggle the 'Inhibit screen locking and sleep' button to 'on' 3. Toggle the 'Inhibit screen locking and sleep' button to 'off' OBSERVED RESULT Even when toggled off, the battery applet reports the following: 'lattedock is inhibiting sleep and screen locking (The battery applet has enabled system-wide inhibition)'. EXPECTED RESULT When toggled off, Latte-dock should NOT be marked as inhibiting sleep and screen locking by the battery applet. SOFTWARE/OS VERSIONS Operating System: openSUSE Leap 15.3 KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.85.0 Qt Version: 5.15.2 Kernel Version: 5.3.18-57-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 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 442198] Krita 5.1.0 prealpha(git 8376871) : brush texture blending modes not behaving correctly
https://bugs.kde.org/show_bug.cgi?id=442198 --- Comment #2 from stephen --- (In reply to wolthera from comment #1) > Sorry, that seems to work here. I am afraid you'll have to include a picture. Here are the pictures : https://drive.google.com/file/d/1AQRN4XD_8XVM5j7syEjVWknSwR0EZJci/view?usp=sharing https://drive.google.com/file/d/1zECwQTnDdFPhZjxPJ-qvRraHQZGzKkhm/view?usp=sharing https://drive.google.com/file/d/1nmXqql_neKVUok-b2w4SHcXD9FsyEIHo/view?usp=sharing https://drive.google.com/file/d/1hfBoxXYJD9bo2CEa0fVhAJxvjLjRiPQB/view?usp=sharing https://drive.google.com/file/d/12oNtQjefu4eqRNZ1wPja6CP2zhufPUZf/view?usp=sharing https://drive.google.com/file/d/1luJMwWsMJkh-sysoEJKm-piiwKkbqYpa/view?usp=sharing -- You are receiving this mail because: You are watching all bug changes.
[kdelibs] [Bug 309193] Keyboard shortcuts doesn't work if non-english keyboard layout is set before english one
https://bugs.kde.org/show_bug.cgi?id=309193 Henrique Sant'Anna changed: What|Removed |Added CC||hsanta...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 402913] Alt shortcuts get eaten when adding a second keyboard layout
https://bugs.kde.org/show_bug.cgi?id=402913 Henrique Sant'Anna changed: What|Removed |Added CC||hsanta...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 370618] Cannot sync large amounts of mail through IMAP
https://bugs.kde.org/show_bug.cgi?id=370618 northon_patri...@yahoo.ca changed: What|Removed |Added CC||northon_patri...@yahoo.ca --- Comment #2 from northon_patri...@yahoo.ca --- Same problem here, I had to archive most of my old mail into an archive folder to get my inbox working. But then the archive folder won't sync all my mail, it stop at 16400 emails. If I try again, it seem to restart from the start, never finishing. I am not sure who is the culprit, is yahoo limiting the amount of mail I can sync in one go? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 442098] Krita 5.1.0 prealpha :Ten Brushes, can't switch back to previous preset after pressing key twice
https://bugs.kde.org/show_bug.cgi?id=442098 --- Comment #4 from stephen --- (In reply to Halla Rempt from comment #3) > No, only developers should change the status of a bug. > > Resolved/Worksforme means: it works for me, I cannot investigate this report > anymore since there's nothing left for me to try and test or debug. Then I shall forward a screen recording of the issue at the very least. Just so that you understand it's really not working on my side. It doesn't happen with the first Krita 5.0.0 beta, but with the current 5.1.0 prealpha and current 5.0.0 beta builds, switching back to previous preset is not possible anymore. Recording video will be forwarded in the next message. -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 434121] Allow non-interrupting reminders
https://bugs.kde.org/show_bug.cgi?id=434121 --- Comment #6 from Tusooa Zhu --- (In reply to gjditchfield from comment #4) > (In reply to Tusooa Zhu from comment #3) > > Can confirm. I will work on a fix. > > Great! Just in case you're not on the kde-pim mailing list, there is a > related discussion at > https://mail.kde.org/pipermail/kde-pim/2021-August/047780.html and the start > of a merge request at > https://invent.kde.org/pim/korganizer/-/merge_requests/43/diffs#note_287809 Thanks a lot for telling me about that. It sounds pretty insightful. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 440372] kwin fails to compile with >=libglvnd-1.3.4 on Linux: "invalid conversion from ‘xcb_window_t’"
https://bugs.kde.org/show_bug.cgi?id=440372 desaparecido changed: What|Removed |Added CC||luis.davila...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 441952] Cannot create a gocryptfs vault due to faulty version number checking code
https://bugs.kde.org/show_bug.cgi?id=441952 Ivan Čukić changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED --- Comment #6 from Ivan Čukić --- Should be fixed by https://invent.kde.org/plasma/plasma-vault/-/merge_requests/16 -- for 5.23 -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 429390] Screenshot taken on Wayland via keyboard shortcuts is not copied to clipboard
https://bugs.kde.org/show_bug.cgi?id=429390 Jamon changed: What|Removed |Added CC||kdeb...@jamonterrell.com --- Comment #4 from Jamon --- I'm also having this problem on Manjaro's KDE release, fully updated: local/plasma-wayland-session 5.22.5-1 local/plasma-desktop 5.22.5-1 (plasma) local/plasma-framework 5.85.0-2 (kf5) local/qt5-base 5.15.2+kde+r215-1 (qt qt5) local/linux514 5.14.0-0 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 441934] Media controls don't recognize when media players terminate
https://bugs.kde.org/show_bug.cgi?id=441934 --- Comment #6 from David --- (In reply to Nate Graham from comment #5) > And this is happens with both the 1st Party Media Player widget as well we > the 3rd-party widget you mentioned? Those widgets are showing the same things, it's just that the 3rd party widget has everything showing up up front while in the official ones the controls are more hidden. If you use the official widgets and right-click them you'll see the same issue. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 442240] On wayland certain screen configurations severely limit frame rate to the point of being unusable
https://bugs.kde.org/show_bug.cgi?id=442240 --- Comment #1 from Zamundaaa --- What do you mean with "with the heavy refactoring of late" / do you have a timeframe of when it got worse? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 441945] File Layers not working when opened with "folder icon"
https://bugs.kde.org/show_bug.cgi?id=441945 Przemysław Gołąb changed: What|Removed |Added Summary|File Layers not working as |File Layers not working |expected when opened with |when opened with "folder |"folder icon" |icon" -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 442128] Help > Report Bug feature crashes Krita
https://bugs.kde.org/show_bug.cgi?id=442128 --- Comment #6 from Przemysław Gołąb --- (In reply to Halla Rempt from comment #4) > Please make a zip and share them with me (hallare...@gmail.com) and I'll try > to reproduce on my system and come up with a mitigation... I think it's > simply QTextBrowser that crashes on the size of the file. Sure! Done. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 441934] Media controls don't recognize when media players terminate
https://bugs.kde.org/show_bug.cgi?id=441934 --- Comment #5 from Nate Graham --- And this is happens with both the 1st Party Media Player widget as well we the 3rd-party widget you mentioned? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 442128] Help > Report Bug feature crashes Krita
https://bugs.kde.org/show_bug.cgi?id=442128 --- Comment #5 from Przemysław Gołąb --- Created attachment 141432 --> https://bugs.kde.org/attachment.cgi?id=141432=edit crashing log files -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 442238] Closing a DnD'd view also closes the window it came from
https://bugs.kde.org/show_bug.cgi?id=442238 --- Comment #4 from nsprang...@gmail.com --- Not on 21.08.1 Manjaro... -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 441446] Copying file from FAT32 triggeres endless loop in file.so
https://bugs.kde.org/show_bug.cgi?id=441446 Nate Graham changed: What|Removed |Added CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 441975] difficulties assigning shortcuts after upgrade
https://bugs.kde.org/show_bug.cgi?id=441975 Nate Graham changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #3 from Nate Graham --- Thanks for the screen recording, but now I'm even more confused, because I don't see a problem in it, and also there is no Apply button in that dialog, yet you say the Apply button is not working. Can you please clarify what problem the screen recording is showing? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 438930] Visual glitch in context menu when the shift modifier key is pressed
https://bugs.kde.org/show_bug.cgi?id=438930 Nate Graham changed: What|Removed |Added Version Fixed In|5.22|5.23 -- You are receiving this mail because: You are watching all bug changes.
[juk] [Bug 442242] Filter by Genre, Artist, Album, etc.
https://bugs.kde.org/show_bug.cgi?id=442242 --- Comment #1 from Michael D --- I forgot you can filter by album and artist by playing a song in the category and then clicking the artist or album filter, but there is still no way to filter by genre, and it would anyway be nice to be able to filter by artist and song without having to play a song first. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 442240] On wayland certain screen configurations severely limit frame rate to the point of being unusable
https://bugs.kde.org/show_bug.cgi?id=442240 Nate Graham changed: What|Removed |Added Keywords||regression -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 442240] On wayland certain screen configurations severely limit frame rate to the point of being unusable
https://bugs.kde.org/show_bug.cgi?id=442240 Nate Graham changed: What|Removed |Added CC||n...@kde.org, ||xaver.h...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[juk] [Bug 442242] New: Filter by Genre, Artist, Album, etc.
https://bugs.kde.org/show_bug.cgi?id=442242 Bug ID: 442242 Summary: Filter by Genre, Artist, Album, etc. Product: juk Version: 21.08.0 Platform: Manjaro OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: whee...@kde.org Reporter: nortex...@gmail.com CC: mp...@kde.org Target Milestone: --- It would be nice to have the option to filter by certain categories such as genre. It is possible to search for a genre such as "Rock", say, but that results in showing songs with "Rock" in the title, artist name, etc. and not just showing songs in the genre "Rock". -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 442241] New: Black screen with egl-wayland 1.1.8
https://bugs.kde.org/show_bug.cgi?id=442241 Bug ID: 442241 Summary: Black screen with egl-wayland 1.1.8 Product: plasmashell Version: 5.22.5 Platform: Other OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: mmboss...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY On Arch, plasmashell works fine using egl-wayland 1.1.7 using egl-wayland 1.1.8 process seems to be running, but not is seen on screen. I can´t see any panels or wallpaper STEPS TO REPRODUCE 1. Use Plasma wayland session with egl-wayland 1.1.8 SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.85.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION Let me know if you need any more info. -- You are receiving this mail because: You are watching all bug changes.
[libkgapi] [Bug 441849] libkdexoauth2 fails to build because of newly enabled C99 standard: "duplicate symbol: atof" & similar
https://bugs.kde.org/show_bug.cgi?id=441849 Kevin Funk changed: What|Removed |Added Status|ASSIGNED|RESOLVED Latest Commit||https://invent.kde.org/pim/ ||libkgapi/commit/ad7e81221fb ||8203bdb1b0a9d75bf5001d755f0 ||ca Resolution|--- |FIXED --- Comment #3 from Kevin Funk --- Git commit ad7e81221fb8203bdb1b0a9d75bf5001d755f0ca by Kevin Funk. Committed on 08/09/2021 at 07:32. Pushed by lbeltrame into branch 'master'. saslplugin: Fix build under C99 on all platforms C99 changes the meaning of `extern inline` (https://stackoverflow.com/questions/216510/what-does-extern-inline-do). In our case that has the effect that some headers from glibc are treated differently, i.e. functions like `atof` are actually defined and exported in the object files including the header defining `atof` and friends. More information about this issue: https://gcc.gnu.org/legacy-ml/gcc/2006-11/msg00011.html Normally this should not be the case; the underlying issue is that libkgapi is using a generated config.h (./src/saslplugin/config.h) which is causing issues under C99. Fix this by generating the config.h file using CMake. This patch also updates the 3rdparty plugin_common.* to a more recent version (cyrus-sasl-2.1.27 to be exact), providing also support for "Windows 10 or greater". M +10 -3src/saslplugin/CMakeLists.txt D +0-573 src/saslplugin/config.h A +18 -0src/saslplugin/config.h.in M +480 -532 src/saslplugin/plugin_common.c M +128 -93 src/saslplugin/plugin_common.h https://invent.kde.org/pim/libkgapi/commit/ad7e81221fb8203bdb1b0a9d75bf5001d755f0ca -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 442238] Closing a DnD'd view also closes the window it came from
https://bugs.kde.org/show_bug.cgi?id=442238 --- Comment #3 from Kurt Hindenburg --- I see the same issue on the 21.08 branch. Are you sure you don't see it there? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 436905] layers randomly combine without user imput
https://bugs.kde.org/show_bug.cgi?id=436905 --- Comment #4 from haleeang...@gmail.com --- I haven't seen this recently, so whatever it was is probably gone, but I'm sure it's not due to any of my inputs my pen does have an E button, but none of my other buttons are wired to be JUST control, so I don't see how I could have accidentally pressed ctrl+E On Tue, Sep 7, 2021 at 4:33 AM Halla Rempt wrote: > https://bugs.kde.org/show_bug.cgi?id=436905 > > Halla Rempt changed: > >What|Removed |Added > > > Resolution|--- |WAITINGFORINFO > Status|REPORTED|NEEDSINFO > CC||ha...@valdyas.org >Severity|grave |normal > > --- Comment #3 from Halla Rempt --- > Does this still happen for you? I've never heard of this before, and I > cannot > imagine how this could happen. > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 442240] New: On wayland certain screen configurations severely limit frame rate to the point of being unusable
https://bugs.kde.org/show_bug.cgi?id=442240 Bug ID: 442240 Summary: On wayland certain screen configurations severely limit frame rate to the point of being unusable Product: kwin Version: git master Platform: Neon Packages OS: Linux Status: REPORTED Severity: major Priority: NOR Component: platform-drm Assignee: kwin-bugs-n...@kde.org Reporter: carlosdema...@gmail.com Target Milestone: --- On kwin_wayland master, certain screen configurations makes performance (fps) plummet. When my Intel based laptop is using dumb buffers on the Nvidia driven external output(s), certain configs work at 30-60 fps whilst others at 5-15 fps - rendering it virtually unusable. When the Intel screen is placed to the left or to the top in a two monitor config, performance is good. When the laptop screen is placed to the right, to the bottom or cloned, performance hits a brick wall.. The fps kwin effect places itself on the external screen in these instances. Performance used to be decent in any configuration but has definitely worsened with the heavy refactoring of late. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Neon Unstable (available in About System) KDE Plasma Version: 5.22.80 KDE Frameworks Version: 5.86.0 Qt Version: 5.15.3 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 441446] Copying file from FAT32 triggeres endless loop in file.so
https://bugs.kde.org/show_bug.cgi?id=441446 Bug Janitor Service changed: What|Removed |Added Status|REPORTED|ASSIGNED Ever confirmed|0 |1 --- Comment #1 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/frameworks/kio/-/merge_requests/573 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 438930] Visual glitch in context menu when the shift modifier key is pressed
https://bugs.kde.org/show_bug.cgi?id=438930 Derek Christ changed: What|Removed |Added Latest Commit||https://invent.kde.org/plas ||ma/plasma-desktop/commit/f8 ||30ceeaf012a9f87b7c0b2b2bb9b ||095de107da4 Status|ASSIGNED|RESOLVED Version Fixed In||5.22 Resolution|--- |FIXED --- Comment #3 from Derek Christ --- Git commit f830ceeaf012a9f87b7c0b2b2bb9b095de107da4 by Derek Christ. Committed on 09/09/2021 at 19:01. Pushed by davidedmundson into branch 'master'. Introduce RemoveAction for context menu The RemoveAction can either represent the delete action or the move to trash action, depending on the shift modifier state. This inplace swapping instead of adding and removing both actions fixes a visual glitch that could be noticed by pressing and releasing the shift key multiple times. FIXED-IN: 5.22 M +1-0containments/desktop/plugins/folder/CMakeLists.txt M +28 -46 containments/desktop/plugins/folder/foldermodel.cpp M +0-2containments/desktop/plugins/folder/foldermodel.h A +99 -0containments/desktop/plugins/folder/removeaction.cpp [License: GPL(v2.0+)] A +49 -0containments/desktop/plugins/folder/removeaction.h [License: GPL(v2.0+)] https://invent.kde.org/plasma/plasma-desktop/commit/f830ceeaf012a9f87b7c0b2b2bb9b095de107da4 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 430565] regenerating high-res SVGs is slow
https://bugs.kde.org/show_bug.cgi?id=430565 --- Comment #18 from LTHR --- (In reply to Nate Graham from comment #16) > Could we fall back to using the software renderer automatically if we detect > hardware that's not capable of doing hardware-accelerated rendering, perhaps? Or have an option in KDE config May be I'm wrong but it looks like a bug. Section "Device" Identifier "Device0" VendorName "INTEL Corporation" BoardName"GMA 3600 [GMA500]" Driver "modesetting" Option "AccelMethod" "glamor" # Option "SWCursor" "ON" Option "DPMS" "TRUE" Option "DRI" "3" EndSection DRI3 is fine, glxgears is fine, FULL HD video is fine, Photoshop 19 is fine, smooth graphics, LXQT - fine, XFCE - fine, chromium - smooth graphics and performance, firefox - smooth graphics, not much CPU usage from any of them. I can't image how normally plasmashell can consume more CPU than chromium with 50+ tabs opened for 5+ minutes when mouse is rolled over a menu item it's just 100% and nothing helps, that's the last thing left unsolved for this netbook. If you google you will find a lot of reports about plasmashell taking 100% of CPU all of a sudden. But randomly - the only way to fix it is to kill it. It looks very familiar to my case but in my case - it's always 100% and always re-producible. I believe it's the same bug. It can't normally be that rolling a mouse over an item it KDE menu can require the same amount of CPU as - none-accelerated Full HD VIDEO requires in 7 minutes. It must be a bug. May be fixing it will accelerate KDE to the new performance horizonts. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 442238] Closing a DnD'd view also closes the window it came from
https://bugs.kde.org/show_bug.cgi?id=442238 Kurt Hindenburg changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #2 from Kurt Hindenburg --- yep thanks confirmed on master - I'll have to check 21.08 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 442239] New: Dolphin breadcrumbs in location bar are inconsistent.
https://bugs.kde.org/show_bug.cgi?id=442239
Bug ID: 442239
Summary: Dolphin breadcrumbs in location bar are inconsistent.
Product: dolphin
Version: 20.12.2
Platform: Debian stable
OS: Linux
Status: REPORTED
Severity: wishlist
Priority: NOR
Component: bars: location
Assignee: dolphin-bugs-n...@kde.org
Reporter: philipihmur...@hotmail.com
CC: kfm-de...@kde.org
Target Milestone: ---
SUMMARY
Dolphin breadcrumbs in location bar are inconsistent.
STEPS TO REPRODUCE
1. In Dolphin, in the Home folder, create a folder 'test1' and go into it.
The breadcrumbs show:
> Home > test1
2. Go back to Home folder & go into the Downloads folder.
The breadcrumbs show:
> Downloads
3. Still within the Downloads folder, create subfolder 'test2' & go into it.
The breadcrumbs show:
> Downloads > test2
4. In Dolphin's left panel, click on any folder or a recently used folder that
auto-populates, e.g. "LastFolder" shows on the left side (real directory is
/home/zippy/500gb_b/2ND_LAST/LastFolder)
The breadcrumbs show:
> LastFolder
5. In Dolphin go back to Home & then navigate through to the folder one level
above 'LastFolder', i.e. so far as 2ND_LAST.
The breadcrumbs show:
> Home > 500gb_b > 2ND_LAST
6. Go one step further than #5 and go into "LastFolder" folder.
The breadcrumbs show:
> LastFolder
OBSERVED RESULT:
The breadcrumb convention has changed between 5 & 6. Number 6 dropped all the
higher level folders.
"> Home" is missing from 2 & 3.
EXPECTED RESULT:
1. > Home > test1
2. > Home > Downloads
3. > Home > Downloads > test2
4. > Home > 500gb > 2ND_LAST > Lastfolder
5. > Home > 500gb > 2ND_LAST
6. > Home > 500gb > 2ND_LAST > Lastfolder
NOTES:
Having the breadcumbs consistently stem from 'Home' and show each folder branch
to the folder you're in is a useful navigation tool.
Configuring Dolphin to 'Show full path inside location bar' adds the extra "/ >
Home > USERNAME > " hence isn't quite a solution as it doesn't follow the nicer
convention above ("Home" > Foldername...).
SOFTWARE/OS VERSIONS
Operating System: Debian GNU/Linux 11
KDE Plasma Version: 5.20.5
KDE Frameworks Version: 5.78.0
Qt Version: 5.15.2
Kernel Version: 5.10.0-8-amd64
OS Type: 64-bit
Processors: 4 × Intel® Core™ i5-4570 CPU @ 3.20GHz
Memory: 7.7 GiB of RAM
Graphics Processor: GeForce GTX 750 Ti/PCIe/SSE2
--
You are receiving this mail because:
You are watching all bug changes.
[konsole] [Bug 442238] Closing a DnD'd view also closes the window it came from
https://bugs.kde.org/show_bug.cgi?id=442238 --- Comment #1 from nsprang...@gmail.com --- Also, not present on 21.08.1 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 442238] New: Closing a DnD'd view also closes the window it came from
https://bugs.kde.org/show_bug.cgi?id=442238 Bug ID: 442238 Summary: Closing a DnD'd view also closes the window it came from Product: konsole Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: split-view Assignee: konsole-de...@kde.org Reporter: nsprang...@gmail.com Target Milestone: --- SUMMARY Ran with kdesrc-build konsole && kdesrc-run konsole No bug if there are multiple splits or multiple tabs in the previous window. STEPS TO REPRODUCE 1. Open a second window 2. Create a split-view in second window 3. Drag and drop one view to first window 4. Close the dropped view (by any means: headerbar button, ctl-shift-w, ctl-d, 'exit') OBSERVED RESULT Also closes the window the view was dragged from. EXPECTED RESULT Only close the focused view. 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.
[digikam] [Bug 442189] HEIC photos with GPS coordinates embeded in metadata are not used in digikam database for geolocation
https://bugs.kde.org/show_bug.cgi?id=442189 --- Comment #3 from Francisco Hurtado --- (In reply to Francisco Hurtado from comment #2) > Thanks Maik for (In reply to Maik Qualmann from comment #1) > > Please upload a sample HEIC image with GPS information. If not public, to my > > email address. > > The sample HEIC images that I have with GPS information are displayed > > correctly in digiKam. > > > > It is possible that the GPS information was not recognized during the first > > scan because the files were locked by other programs. As a test, do a > > re-read of the image metadata via the item menu. > > > > Maik > > Thanks Maik for your quick reply. > > I have followed your indication and I did a re-read of metadata > susccessfully. > > This is interesting because, although I created a new album with photos > taken out of an iphone, it seems that videos and jpgs have no problem to be > read at first moment (with te correct metadata for GPS in digikam) but it > seems that there is a problem only with HEICs. > > In fact, a refresh of the album do not fix the problem. I have to select > photos an re-read metadata. > > What do you think? > > I'll keep you posted if I discover anything more. > > Thanks in advance > > Best New information about this rare behaviour. As mentioned, when I re-read metadata for my apple HEIC photo, all was fine and the GPS metadata are read correctly and digikam store geolocation properly. Well, if I take that photo whose metadata was correctly re-read and stored in digikam, then make a copy of it and refresh the album again, this new copy is not read properly and the geolocation info is not shown at all. Again, if re-read metadata all fine. It seems to me that is something that does not work well in the first reading in digikam for HEIC files. Best -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 441975] difficulties assigning shortcuts after upgrade
https://bugs.kde.org/show_bug.cgi?id=441975 empyreal changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #2 from empyreal --- Apply is not grayed out. I can't press it together with other buttons. It happens really in each app on page "Configure Shortcuts". Here is link to video with the problem https://dropmefiles.com/QjZuh -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 442237] New: No file name label for readonly files
https://bugs.kde.org/show_bug.cgi?id=442237 Bug ID: 442237 Summary: No file name label for readonly files Product: frameworks-kio Version: git master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Properties dialog Assignee: kio-bugs-n...@kde.org Reporter: k...@privat.broulik.de CC: kdelibs-b...@kde.org Target Milestone: --- SUMMARY There is no file name displayed in properties dialog for readonly files anymore STEPS TO REPRODUCE 1. Open properties to a readonly file, e.g. something in /usr/share or whatever OBSERVED RESULT File dialog opens and no file name is displayed next to the icon EXPECTED RESULT The file name is displayed next to the icon SOFTWARE/OS VERSIONS Linux/KDE Plasma: git master as of 2021-09-09 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 438874] Disk & Devices applet doesn't show USB removable devices and SD cards after disconnecting and re-connecting them
https://bugs.kde.org/show_bug.cgi?id=438874
--- Comment #44 from Xwang ---
(In reply to Domker from comment #43)
> (In reply to Xwang from comment #41)
> > (In reply to Fabio from comment #37)
> > > I just created a merge request that fixes this bug for me.
> > > It would be nice if someone could confirm if this is working.
> > >
> > > https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/1039
> >
> > Is there any howto which explains how I can test your merge?
> > I'm using archlinux.
>
> Live swapping files is the worst possible way to patch something!!
>
>
> $patch -d "plasma-workspace-5.22.5" -p1 < 1039.patch
>
> (plasma-workspace-5.22.5 - direcotry with source code of plasma-workspace)
>
> patching file applets/devicenotifier/package/contents/ui/DeviceItem.qml
> Hunk #1 FAILED at 31.
> Hunk #2 succeeded at 123 (offset 4 lines).
> Hunk #3 succeeded at 140 (offset 4 lines).
> Hunk #4 FAILED at 189.
> Hunk #5 succeeded at 233 (offset 4 lines).
> Hunk #6 FAILED at 250.
> 3 out of 6 hunks FAILED -- saving rejects to file
> applets/devicenotifier/package/contents/ui/DeviceItem.qml.rej
> patching file applets/devicenotifier/package/contents/ui/devicenotifier.qml
> Hunk #1 succeeded at 88 (offset 13 lines).
> Hunk #2 succeeded at 112 (offset 13 lines).
>
> !! It FAILED becouse patch is for plasma-workspace v5.23, not v5.22.5 !!
>
> >>> You need make own patch file based on differences in "ui" direcotry:
>
> 1. Make new directory:
> $ mkdir test_build && cd "$_"
>
> 2. Clone source package master repo where patch is merged:
> $ git clone https://invent.kde.org/plasma/plasma-workspace.git
>
> 3. Rename it to "b":
> $ mv plasma-workspace b
>
> 4. Download (and extract) source code plasma-workspace (current version)
> present in Arch Linux, rename directory to "a":
> $ wget
> "https://download.kde.org/stable/plasma/5.22.5/plasma-workspace-5.22.5.tar.
> xz" -qO - | tar xvJ
> $ mv plasma-workspace-5.22.5 a
>
> 5. Now you have directory "a" with current source code (plasma-workspace in
> Arch Linux) and direcotry "b" with merged patch. Make own custom.patch with
> differences in "ui" directories:
>
> $ diff -ur a/applets/devicenotifier/package/contents/ui
> b/applets/devicenotifier/package/contents/ui > custom.patch
>
> If You have now "custom.patch" file, remove "a" and "b" directories:
> $ rm -rf a b
>
> >>> Now you need build own patched package "plasma-workspace-5.22.5":
>
> 1. Go to:
> https://github.com/archlinux/svntogit-packages/tree/packages/plasma-
> workspace/trunk and download "PKGBUILD", "kde.pam" files, for quick download
> use this:
>
> $ wget
> "https://raw.githubusercontent.com/archlinux/svntogit-packages/packages/
> plasma-workspace/trunk/PKGBUILD" && wget
> "https://raw.githubusercontent.com/archlinux/svntogit-packages/packages/
> plasma-workspace/trunk/kde.pam"
>
> 2. Edit "PKGBUILD" file:
> source=(https://download.kde.org/stable/plasma/$pkgver/$pkgbase-$pkgver.tar.
> xz{,.sig} kde.pam
>
> https://invent.kde.org/plasma/plasma-workspace/-/commit/6379d1ec.patch)
>
> REPLACE WITH:
>
> source=(https://download.kde.org/stable/plasma/$pkgver/$pkgbase-$pkgver.tar.
> xz{,.sig} kde.pam
>
> https://invent.kde.org/plasma/plasma-workspace/-/commit/6379d1ec.patch
> custom.patch)
>
> AND:
> prepare() {
> patch -d $pkgbase-$pkgver -p1 < 6379d1ec.patch # Fix power management
> inhibition
> }
>
> REPLACE WITH:
> prepare() {
> patch -d $pkgbase-$pkgver -p1 < 6379d1ec.patch # Fix power management
> inhibition
> patch -d $pkgbase-$pkgver -p1 < custom.patch
> }
>
>
>
> SAVE CHANGES in PKGBUILD FILE!
>
> 3. Update checksums in PKGBUILD:
> $ updpkgsums PKGBUILD
>
>
> 3. Now build and install patched "plasma-workspace" package:
> $ makepkg -sri --skippgpcheck PKGBUILD
>
> #option -s (download and install dependencies)
> #option -r (remove dependency after successful package build, in this case:
> pps-tools-1.0.2-1 gpsd-3.23-1 plasma-wayland-protocols-1.4.0-1)
> #option -i (install the package if it has been built)
>
> After installing the package restart your PC. For me, a patch made in this
> way works.
>
> If something doesn't work, just force reinstall plasma-workspace from the
> repository.
> ( sudo rm
> /var/cache/pacman/pkg/plasma-workspace-5.22.5-2-x86_64.pkg.tar.zst{,.sig} &&
> sudo pacman -S plasma-workspace )
Thank you!
I'll try do that next weekend.
Anyway the bug will be in any case fixed when plasma-workspace-5.23 will be
available. Is it correct?
--
You are receiving this mail because:
You are watching all bug changes.
[frameworks-plasma] [Bug 430565] regenerating high-res SVGs is slow
https://bugs.kde.org/show_bug.cgi?id=430565 --- Comment #17 from LTHR --- update : the same performance with 5.21.5 Just for the record : the power of that CPU is underestimated. It's a pure born linux box that works with linux better than with windows With CPU microcode patch it can utilize amd64 arch with 4Gb RAM and thankfully to kernel patches its graphical performance is amazing. I've built Gentoo ADM64 linux for Asus 1025c netbook and it's just something in terms of stability, consistency and performance - it plays FullHD video smoothly, runs Photoshop CS19, chromium, FF. I had a long to-do/fix list over these 6 months of working on it and the only problem I still can't fix is KDE :-( I'm ready to help. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 438874] Disk & Devices applet doesn't show USB removable devices and SD cards after disconnecting and re-connecting them
https://bugs.kde.org/show_bug.cgi?id=438874
--- Comment #43 from Domker ---
(In reply to Xwang from comment #41)
> (In reply to Fabio from comment #37)
> > I just created a merge request that fixes this bug for me.
> > It would be nice if someone could confirm if this is working.
> >
> > https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/1039
>
> Is there any howto which explains how I can test your merge?
> I'm using archlinux.
Live swapping files is the worst possible way to patch something!!
$patch -d "plasma-workspace-5.22.5" -p1 < 1039.patch
(plasma-workspace-5.22.5 - direcotry with source code of plasma-workspace)
patching file applets/devicenotifier/package/contents/ui/DeviceItem.qml
Hunk #1 FAILED at 31.
Hunk #2 succeeded at 123 (offset 4 lines).
Hunk #3 succeeded at 140 (offset 4 lines).
Hunk #4 FAILED at 189.
Hunk #5 succeeded at 233 (offset 4 lines).
Hunk #6 FAILED at 250.
3 out of 6 hunks FAILED -- saving rejects to file
applets/devicenotifier/package/contents/ui/DeviceItem.qml.rej
patching file applets/devicenotifier/package/contents/ui/devicenotifier.qml
Hunk #1 succeeded at 88 (offset 13 lines).
Hunk #2 succeeded at 112 (offset 13 lines).
!! It FAILED becouse patch is for plasma-workspace v5.23, not v5.22.5 !!
>>> You need make own patch file based on differences in "ui" direcotry:
1. Make new directory:
$ mkdir test_build && cd "$_"
2. Clone source package master repo where patch is merged:
$ git clone https://invent.kde.org/plasma/plasma-workspace.git
3. Rename it to "b":
$ mv plasma-workspace b
4. Download (and extract) source code plasma-workspace (current version)
present in Arch Linux, rename directory to "a":
$ wget
"https://download.kde.org/stable/plasma/5.22.5/plasma-workspace-5.22.5.tar.xz;
-qO - | tar xvJ
$ mv plasma-workspace-5.22.5 a
5. Now you have directory "a" with current source code (plasma-workspace in
Arch Linux) and direcotry "b" with merged patch. Make own custom.patch with
differences in "ui" directories:
$ diff -ur a/applets/devicenotifier/package/contents/ui
b/applets/devicenotifier/package/contents/ui > custom.patch
If You have now "custom.patch" file, remove "a" and "b" directories:
$ rm -rf a b
>>> Now you need build own patched package "plasma-workspace-5.22.5":
1. Go to:
https://github.com/archlinux/svntogit-packages/tree/packages/plasma-workspace/trunk
and download "PKGBUILD", "kde.pam" files, for quick download use this:
$ wget
"https://raw.githubusercontent.com/archlinux/svntogit-packages/packages/plasma-workspace/trunk/PKGBUILD;
&& wget
"https://raw.githubusercontent.com/archlinux/svntogit-packages/packages/plasma-workspace/trunk/kde.pam;
2. Edit "PKGBUILD" file:
source=(https://download.kde.org/stable/plasma/$pkgver/$pkgbase-$pkgver.tar.xz{,.sig}
kde.pam
https://invent.kde.org/plasma/plasma-workspace/-/commit/6379d1ec.patch)
REPLACE WITH:
source=(https://download.kde.org/stable/plasma/$pkgver/$pkgbase-$pkgver.tar.xz{,.sig}
kde.pam
https://invent.kde.org/plasma/plasma-workspace/-/commit/6379d1ec.patch
custom.patch)
AND:
prepare() {
patch -d $pkgbase-$pkgver -p1 < 6379d1ec.patch # Fix power management
inhibition
}
REPLACE WITH:
prepare() {
patch -d $pkgbase-$pkgver -p1 < 6379d1ec.patch # Fix power management
inhibition
patch -d $pkgbase-$pkgver -p1 < custom.patch
}
SAVE CHANGES in PKGBUILD FILE!
3. Update checksums in PKGBUILD:
$ updpkgsums PKGBUILD
3. Now build and install patched "plasma-workspace" package:
$ makepkg -sri --skippgpcheck PKGBUILD
#option -s (download and install dependencies)
#option -r (remove dependency after successful package build, in this case:
pps-tools-1.0.2-1 gpsd-3.23-1 plasma-wayland-protocols-1.4.0-1)
#option -i (install the package if it has been built)
After installing the package restart your PC. For me, a patch made in this way
works.
If something doesn't work, just force reinstall plasma-workspace from the
repository.
( sudo rm
/var/cache/pacman/pkg/plasma-workspace-5.22.5-2-x86_64.pkg.tar.zst{,.sig} &&
sudo pacman -S plasma-workspace )
--
You are receiving this mail because:
You are watching all bug changes.
[krunner] [Bug 438388] Krunner still shows duplicate entry after 5.22 update
https://bugs.kde.org/show_bug.cgi?id=438388 --- Comment #11 from Alexander Lohnau --- The issues with KCMs that made d1e2bdf62ba0f1e9448dc690dfdeec2669faa992 necessary is now "solved", because the KCM functionality is split up in a different runner. Are there cases where we need to consider the args? I can only think of flatpaks -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 442236] [Transform tool] Tool options doesn't change if I select different transforming method
https://bugs.kde.org/show_bug.cgi?id=442236 --- Comment #2 from acc4commissi...@gmail.com --- On the toolbar. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 442236] [Transform tool] Tool options doesn't change if I select different transforming method
https://bugs.kde.org/show_bug.cgi?id=442236 Halla Rempt changed: What|Removed |Added Resolution|--- |WAITINGFORINFO CC||ha...@valdyas.org Status|REPORTED|NEEDSINFO --- Comment #1 from Halla Rempt --- Have you got your tool options in the toolbar on in a docker? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 442236] New: [Transform tool] Tool options doesn't change if I select different transforming method
https://bugs.kde.org/show_bug.cgi?id=442236 Bug ID: 442236 Summary: [Transform tool] Tool options doesn't change if I select different transforming method Product: krita Version: git master (please specify the git hash!) Platform: Compiled Sources OS: All Status: REPORTED Severity: normal Priority: NOR Component: Tools/Transform Assignee: krita-bugs-n...@kde.org Reporter: acc4commissi...@gmail.com Target Milestone: --- SUMMARY git b058b37 It's not new. It has been the case for 5.0 nightlies. STEPS TO REPRODUCE 1. Open krita and select Transform tool 2. Try to select transforming methods like warp, cage, liquify etc OBSERVED RESULT The content of the tool option does not change. EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: Win10 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.
[kdenlive] [Bug 414006] Spacer tool is prohibitively slow with many timeline clips
https://bugs.kde.org/show_bug.cgi?id=414006 --- Comment #10 from Bill Robinson --- Created attachment 141430 --> https://bugs.kde.org/attachment.cgi?id=141430=edit large project file causing spacer tool to be slow Please find attached the compressed project file that causes the spacer tool to be really slow for me. I can't attach the clips as they're from a personal family project. Thanks -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 442145] Doesn't open iphone in Dolphin
https://bugs.kde.org/show_bug.cgi?id=442145 --- Comment #2 from Ilya Rodin --- yes these packages are installed ii go-mtpfs 1.0.0-1 amd64 Mount MTP devices over FUSE ii jmtpfs 0.5-3 amd64 FUSE based filesystem for accessing MTP devices ii libmtp-common 1.1.18-1 all Media Transfer Protocol (MTP) common files ii libmtp-runtime 1.1.18-1 amd64 Media Transfer Protocol (MTP) runtime tools ii libmtp9:amd64 1.1.18-1 amd64 Media Transfer Protocol (MTP) library ii mtp-tools 1.1.18-1 amd64 Media Transfer Protocol (MTP) library tools -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 414006] Spacer tool is prohibitively slow with many timeline clips
https://bugs.kde.org/show_bug.cgi?id=414006 --- Comment #9 from Bill Robinson --- Created attachment 141429 --> https://bugs.kde.org/attachment.cgi?id=141429=edit callgrind output using spacer tool on big project I updated to the latest master and also I have tried the sandsmark/martin/texture-cache branch. Both are still about as slow using the spacer tool. I have recorded another doing one move with the spacer tool of a big project with lots of edits. You can uncompress it and then open it with kcachegrind, maybe it's useful. I will also attach the project file -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 441952] Cannot create a gocryptfs vault due to faulty version number checking code
https://bugs.kde.org/show_bug.cgi?id=441952 Ivan Čukić changed: What|Removed |Added Status|CONFIRMED |ASSIGNED -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 342874] Copying text from Okular to Klipper adds a newline
https://bugs.kde.org/show_bug.cgi?id=342874 Albert Astals Cid changed: What|Removed |Added Latest Commit||https://invent.kde.org/grap ||hics/okular/commit/376925a1 ||0d3ec125ab09d7a7f8fdbcb58e7 ||88f09 Resolution|--- |FIXED Status|ASSIGNED|RESOLVED --- Comment #9 from Albert Astals Cid --- Git commit 376925a10d3ec125ab09d7a7f8fdbcb58e788f09 by Albert Astals Cid. Committed on 09/09/2021 at 17:33. Pushed by aacid into branch 'release/21.08'. Remove \n if it's the last char of the selected text M +3-3autotests/parttest.cpp M +4-0part/pageview.cpp https://invent.kde.org/graphics/okular/commit/376925a10d3ec125ab09d7a7f8fdbcb58e788f09 -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 442228] Latte-dock causes Microsoft Edge to crash
https://bugs.kde.org/show_bug.cgi?id=442228 --- Comment #4 from Pango Gillespi --- I normally don't use the default layout, but for troubleshooting on this I did test with the default layout and that has the same issue. -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 441952] Cannot create a gocryptfs vault due to faulty version number checking code
https://bugs.kde.org/show_bug.cgi?id=441952 --- Comment #5 from Ivan Čukić --- This is the reason I didn't want to support gocryptfs at first, as it didn't have the --version standardized (depends on how it was compiled, it could even be empty). When we got the patch for adding gocryptfs to Vault, I was told this has been fixed in gocryptfs since then. I'll fix this, but I expect it to break again at some point... -- You are receiving this mail because: You are watching all bug changes.
[Bluedevil] [Bug 420100] Can't send file over bluetooth
https://bugs.kde.org/show_bug.cgi?id=420100 --- Comment #2 from albrub...@hotmail.com --- Installing bluez-obexd solved the issue for me. -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 441952] Cannot create a gocryptfs vault due to faulty version number checking code
https://bugs.kde.org/show_bug.cgi?id=441952 Nate Graham changed: What|Removed |Added Summary|Cannot create a gocryptfs |Cannot create a gocryptfs |vault |vault due to faulty version ||number checking code -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 441952] Cannot create a gocryptfs vault
https://bugs.kde.org/show_bug.cgi?id=441952 --- Comment #4 from Nate Graham --- Urgh -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 442222] Kwin crashes in KWin::belongToSameGroup() in "Dim Inactive" effect when closing Audacity
https://bugs.kde.org/show_bug.cgi?id=44 Nate Graham changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #5 from Nate Graham --- Thanks for confirming. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 442222] Kwin crashes in KWin::belongToSameGroup() in "Dim Inactive" effect when closing Audacity
https://bugs.kde.org/show_bug.cgi?id=44 --- Comment #4 from linus.kardell+kdeb...@gmail.com --- Yes, the crash does not happen if dim inactive is disabled. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 438310] Toolbar brush option sliders get stuck on Pattern Scale setting
https://bugs.kde.org/show_bug.cgi?id=438310 --- Comment #5 from voronw...@gmail.com --- Created attachment 141428 --> https://bugs.kde.org/attachment.cgi?id=141428=edit Pattern scale slider in Windows (In reply to Halla Rempt from comment #4) > Created attachment 141427 [details] > pattenr scale kicking out the selection dropdown Interesting, I have no idea why it might be doing that. In Windows it works fine. Unfortunately, I don't have Linux or MacOS on any of my machines, so I can't test those. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 442222] Kwin crashes in KWin::belongToSameGroup() in "Dim Inactive" effect when closing Audacity
https://bugs.kde.org/show_bug.cgi?id=44 Nate Graham changed: What|Removed |Added Summary|Kwin crashes when closing |Kwin crashes in |Audacity|KWin::belongToSameGroup() ||in "Dim Inactive" effect ||when closing Audacity Component|compositing |effects-desktop-grid --- Comment #3 from Nate Graham --- Thanks, that's helpful. Now we can tell that the problem is caused by the Dim Inactive effect. As a workaround, are you able to stop the crash by disabling that effect? -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 441952] Cannot create a gocryptfs vault
https://bugs.kde.org/show_bug.cgi?id=441952 --- Comment #3 from Fabian Vogt --- (In reply to Nate Graham from comment #1) > Confirmed. I thought I recalled someone submitting a merge request to fix > this, but now I can't find it... Just this in IRC on 2021-08-19: 19:12 < fvogt> LiveLM[m]: and gocryptfs --version? 19:13 < LiveLM[m]> `gocryptfs v2.1; go-fuse [vendored]; 2021-08-18 go1.17 linux/amd64` 19:13 < fvogt> That's probably it 19:14 < fvogt> It expects a x.x.x version 19:14 < fvogt> So 2.1 doesn't match 19:14 < tomz[m]> heh, thats just gotten a new release (full message at https://libera.ems.host/_matrix/media/r0/download/libera.chat/39e3097bc221fd4fb8325d702ed7f47ea8ed9d3a) 19:15 < tomz[m]> fvogt: sounds like a silly bug :-) 19:17 < fvogt> The version check code of plasma-vault has always been rather fragile 19:17 < fvogt> It's overly generic 19:18 < LiveLM[m]> > <@tomz:matrix.org> heh, thats just gotten a new release (full message at https://libera.ems.host/_matrix/media/r0/download/libera.chat/8eabccdb9c037ad2e194ce9db928eef19f15b21a) 19:19 < fvogt> You're just part of the QA team ;-) 19:21 < NateGraham[m]> Sounds like you found out why they call it the "bleeding edge!" 19:33 < LiveLM[m]> 藍 19:33 < LiveLM[m]> Anyways, thanks for the help guys! 19:33 < LiveLM[m]> Much appreciated 19:34 < NateGraham[m]> anyone wanna fix the bug in vaults? And then silence... -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 442195] Remote shortcut on desktop no longer opened by Dolphin
https://bugs.kde.org/show_bug.cgi?id=442195 --- Comment #3 from Nate Graham --- You can reproduce the issue by creating a desktop file with the contents listed in the original report: [Desktop Entry] Charset= Icon=folder-remote Name=Willow Type=Link URL=ftp://ian@willow:21/share I was able to reproduce the issue with that. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 438310] Toolbar brush option sliders get stuck on Pattern Scale setting
https://bugs.kde.org/show_bug.cgi?id=438310 --- Comment #4 from Halla Rempt --- Created attachment 141427 --> https://bugs.kde.org/attachment.cgi?id=141427=edit pattenr scale kicking out the selection dropdown -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 438310] Toolbar brush option sliders get stuck on Pattern Scale setting
https://bugs.kde.org/show_bug.cgi?id=438310 --- Comment #3 from Halla Rempt --- It might be a matter of which style is used; the appimage doesn't have breeze. -- You are receiving this mail because: You are watching all bug changes.
