[kwin] [Bug 312146] limit size of the last window in the present windows effect
https://bugs.kde.org/show_bug.cgi?id=312146 Jin Liu changed: What|Removed |Added CC||ad.liu@gmail.com Resolution|FIXED |--- Status|RESOLVED|REOPENED --- Comment #4 from Jin Liu --- The padding is lost in the current version. Not sure if it's intended or not. Distro: archlinux Plasma: 5.23.3 KDE Framework: 21.08.3 QT: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 445412] Zoom effect causes screen to stop updating
https://bugs.kde.org/show_bug.cgi?id=445412 --- Comment #7 from Duncan <1i5t5.dun...@cox.net> --- Bisect results, kwin on top of kwayland-server 6cc372683 to get eglstreams back: e2a086384 works, a07aae828 broken and thus the culprit! * commit a07aae828 | Author: Xaver Hugl | AuthorDate: Fri Oct 8 10:52:01 2021 +0200 | Commit: Xaver Hugl | CommitDate: Tue Nov 9 22:15:31 2021 +0100 | | platforms/drm: delay presentation for modesets | | Currently KWin is combining modesets with presentation, which causes problems | when multiple monitors are used and crtcs need to be switched around, because | taking away a CRTC from another output causes the driver to disable the | other output. In order to avoid such problems, delay presentation until | all pipelines are ready to present and then do a modeset with a single atomic | commit. To process the resulting page flip events properly this commit also | ports KWin to page_flip_handler2 and changes how the pageFlipped and | notifyFrameFailed signals are processed. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 445346] GStreamer with waylandsink in KDE Plasma Wayland session: Video doesn't update (works in GNOME or using Weston)
https://bugs.kde.org/show_bug.cgi?id=445346 Vlad Zahorodnii changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED|RESOLVED Latest Commit||https://invent.kde.org/plas ||ma/kwayland-server/commit/9 ||aa436dc48f12e7ab4cb8fc9f9a0 ||6266b3ea1a1a --- Comment #4 from Vlad Zahorodnii --- Git commit 9aa436dc48f12e7ab4cb8fc9f9a06266b3ea1a1a by Vlad Zahorodnii. Committed on 16/11/2021 at 07:24. Pushed by vladz into branch 'master'. Calculate correct surface-to-buffer matrix with only upscaled viewport Currently, if a wp_viewport upscales the surface but doesn't set the source rectangle, the surface-to-buffer matrix will be calculated incorrectly. If the source rect is not set, we need to calculate the source size based on the buffer size and compare it with the destination size. If the two are not the same, add a scale transform. M +11 -2src/server/surface_interface.cpp https://invent.kde.org/plasma/kwayland-server/commit/9aa436dc48f12e7ab4cb8fc9f9a06266b3ea1a1a -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 445566] New: "Turn off screen" keyboard shortcut doesn't work
https://bugs.kde.org/show_bug.cgi?id=445566 Bug ID: 445566 Summary: "Turn off screen" keyboard shortcut doesn't work Product: Powerdevil Version: 5.23.3 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: ad.liu@gmail.com Target Milestone: --- SUMMARY In systemsettings, the "Turn off screen" shortcut under "Power management" doesn't work. When pressed, the screen turns off then immediately on again. STEPS TO REPRODUCE 1. Open systemsettings 2. In keyboard shortcut - power management, set a custom shortcut for "turn off screen" 3. Press that shortcut OBSERVED RESULT Screen turns off then immediately on. EXPECTED RESULT Screen turns off. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.23.3 KDE Frameworks Version: 21.08.3 Qt Version: 5.15.2 ADDITIONAL INFORMATION Setting a custom shortcut with the following command (from the kdeconnect document) works: sleep 0.1 && qdbus org.kde.kglobalaccel /component/org_kde_powerdevil invokeShortcut "Turn Off Screen" So my guess it is the key depressing event turned the screen back on, so a sleep is necessary. -- You are receiving this mail because: You are watching all bug changes.
[plasma4] [Bug 275286] [steps] Plasma crash on logout if user closes a window in a task bar group and then closes the whole group [TaskGroupItem::~TaskGroupItem]
https://bugs.kde.org/show_bug.cgi?id=275286 --- Comment #245 from Antonio Rojas --- *** Bug 298565 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 298565] KDE(plasma-destop (0.4) closes with segmentation fault
https://bugs.kde.org/show_bug.cgi?id=298565 Antonio Rojas changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #4 from Antonio Rojas --- Please don't necrobump old bug reports with unrelated issues. *** This bug has been marked as a duplicate of bug 275286 *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 444516] Crash while painting
https://bugs.kde.org/show_bug.cgi?id=444516 --- Comment #21 from Dmitry Kazakov --- Hm.. the crash logs look really weird. Here is what I can tell from inspecting them: 1) "Still unsignalled after processed 129 tiles" should not be related to the crash. It is just a debug notification, we should probably hide it from the release. 2) The crash happens in the GUI thread, most probably, due to a memory corruption (see fluctuations between SIGSEGV and SIGBUS) 3) This memory corruption happens long before the actual crash 4) In at least 4 crashes of 12, the worker tread has been working on ending the stroke (destroying the brushes and superseded undo commands). That might be related actually. I will make a build with ASAN, so David could catch then actual memory corruption :) -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 433993] Dolphin Crash when creating a folder in remote folder (kio-Gdrive, FTP)
https://bugs.kde.org/show_bug.cgi?id=433993 Jiri Slaby changed: What|Removed |Added CC||jirisl...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 444861] Dolphin crashed when I created a new folder in google drive using kio-gdrive
https://bugs.kde.org/show_bug.cgi?id=444861 Jiri Slaby changed: What|Removed |Added Resolution|--- |DUPLICATE CC||jirisl...@gmail.com Status|REPORTED|RESOLVED --- Comment #2 from Jiri Slaby --- *** This bug has been marked as a duplicate of bug 433993 *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 433993] Dolphin Crash when creating a folder in remote folder (kio-Gdrive, FTP)
https://bugs.kde.org/show_bug.cgi?id=433993 Jiri Slaby changed: What|Removed |Added CC||alf...@gmail.com --- Comment #17 from Jiri Slaby --- *** Bug 444861 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444742] Plasma crash right after login
https://bugs.kde.org/show_bug.cgi?id=444742 --- Comment #2 from t.zas...@gmx.de --- Created attachment 143611 --> https://bugs.kde.org/attachment.cgi?id=143611=edit New crash information added by DrKonqi plasmashell (5.23.2) using Qt 5.15.2 - What I was doing when the application crashed: 1. Start my Laptop (Tuxedo Infinity Book S 15 (Gen 6 with OpenSUSE thumbleweed). 2. Type in the password for drive encryption. 3. Type in the password to login. 4. I got the report, that KDE is crashed. - Unusual behavior I noticed: Not sure but to my mind this bug occures since I tried out KDE with Wayland. -- Backtrace (Reduced): #6 QQuickWindowPrivate::dirtyItem (this=0x37) at /usr/src/debug/libqt5-qtdeclarative-5.15.2+kde36-1.1.x86_64/src/quick/items/qquickwindow.cpp:1335 #7 0x7fb8fded1248 in QQuickItemPrivate::dirty (this=this@entry=0x5627f6c849d0, type=type@entry=QQuickItemPrivate::ChildrenChanged) at /usr/src/debug/libqt5-qtdeclarative-5.15.2+kde36-1.1.x86_64/src/quick/items/qquickitem.cpp:6189 #8 0x7fb8fded9755 in QQuickItemPrivate::addChild (this=0x5627f6c849d0, child=, child@entry=0x7fb8e8019830) at /usr/src/debug/libqt5-qtdeclarative-5.15.2+kde36-1.1.x86_64/src/quick/items/qquickitem.cpp:2929 #9 0x7fb8fdedb832 in QQuickItem::setParentItem (this=0x7fb8e8019830, parentItem=parentItem@entry=0x5627f6c86ab0) at /usr/src/debug/libqt5-qtdeclarative-5.15.2+kde36-1.1.x86_64/src/quick/items/qquickitem.cpp:2702 #10 0x7fb8fdefe780 in qquickitem_autoParent (obj=0x7fb8e8019830, parent=0x5627f6c86ab0) at /usr/src/debug/libqt5-qtdeclarative-5.15.2+kde36-1.1.x86_64/src/quick/items/qquickitemsmodule.cpp:139 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444742] Plasma crash right after login
https://bugs.kde.org/show_bug.cgi?id=444742 t.zas...@gmx.de changed: What|Removed |Added CC||t.zas...@gmx.de -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 445533] Zip compressing a php file with name index.php with just the opening php tags will make it not openable in Ark
https://bugs.kde.org/show_bug.cgi?id=445533 --- Comment #2 from Richard M --- Created attachment 143610 --> https://bugs.kde.org/attachment.cgi?id=143610=edit Have attached the zip file. can be extracted in the terminal but cannot be opened with ark -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 444993] Incorrect ColorScheme set in kdeglobals after applying Breeze Dark Global Theme
https://bugs.kde.org/show_bug.cgi?id=444993 --- Comment #3 from Seth --- (In reply to Nate Graham from comment #2) > Cannot reproduce the issue. And the ColorScheme= key is set correctly in the > theme definition: > https://invent.kde.org/plasma/plasma-workspace/-/blob/master/lookandfeel. > dark/contents/defaults#L5. > > So if there is a bug here, it must be in the logic that applies it, somehow. > > What were your color scheme and global theme set to before you changed the > global theme to Breeze Dark? I used the Light Theme preset in the Quick Settings panel in settings. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 445565] New: crash while editing python
https://bugs.kde.org/show_bug.cgi?id=445565
Bug ID: 445565
Summary: crash while editing python
Product: kdevelop
Version: 5.6.2
Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: general
Assignee: kdevelop-bugs-n...@kde.org
Reporter: jtam...@gmail.com
Target Milestone: ---
Application: kdevelop (5.6.2)
Qt Version: 5.15.2
Frameworks Version: 5.87.0
Operating System: Linux 5.14.14-2-default x86_64
Windowing System: X11
Distribution: "openSUSE Tumbleweed"
DrKonqi: 5.23.2 [KCrashBackend]
-- Information about the crash:
- What I was doing when the application crashed:
I was just editing a member, deleting something old and starting to write
something new.
I noticed that it stopped to refresh and react to keystrokes, and then the
crash.
The reporter is unsure if this crash is reproducible.
-- Backtrace:
Application: KDevelop (kdevelop), signal: Segmentation fault
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = {}}
[KCrash Handler]
#6 std::__atomic_base::load
(__m=std::memory_order_relaxed, this=0x1008) at
/usr/include/c++/11/bits/atomic_base.h:836
#7 std::atomic::load
(__m=std::memory_order_relaxed, this=0x1008) at
/usr/include/c++/11/atomic:570
#8
QAtomicOps::loadRelaxed
(_q_value=...) at
../../include/QtCore/../../src/corelib/thread/qatomic_cxx11.h:239
#9 QBasicAtomicPointer::loadRelaxed
(this=0x1008) at
../../include/QtCore/../../src/corelib/thread/qbasicatomic.h:248
#10 QObjectPrivate::isSignalConnected (this=this@entry=0x557013836f00,
signalIndex=signalIndex@entry=0, checkDeclarative=checkDeclarative@entry=true)
at kernel/qobject.cpp:459
#11 0x7fa7165b33d8 in QObject::~QObject (this=this@entry=0x557013836ea0,
__in_chrg=) at kernel/qobject.cpp:991
#12 0x7fa714edce7d in
KDevelop::PersistentMovingRangePrivate::~PersistentMovingRangePrivate
(this=, this=) at
/usr/src/debug/kdevelop5-5.6.2-2.4.x86_64/build/kdevplatform/language/KDevPlatformLanguage_autogen/3HAKN7MTYQ/../../../../../kdevplatform/language/editor/persistentmovingrangeprivate.h:30
#13 KDevelop::PersistentMovingRangePrivate::~PersistentMovingRangePrivate
(this=, this=) at
/usr/src/debug/kdevelop5-5.6.2-2.4.x86_64/build/kdevplatform/language/KDevPlatformLanguage_autogen/3HAKN7MTYQ/../../../../../kdevplatform/language/editor/persistentmovingrangeprivate.h:30
#14 0x7fa6b742e803 in
QExplicitlySharedDataPointer::~QExplicitlySharedDataPointer
(this=, this=) at
/usr/include/qt5/QtCore/qshareddata.h:184
#15
QExplicitlySharedDataPointer::~QExplicitlySharedDataPointer
(this=, this=) at
/usr/include/qt5/QtCore/qshareddata.h:184
#16 QList
>::node_destruct (to=0x5570139749f0, from=0x5570139610b0, this=)
at /usr/include/qt5/QtCore/qlist.h:526
#17 QList
>::dealloc(QListData::Data*) [clone .constprop.0] (data=0x5570139610a0,
this=) at /usr/include/qt5/QtCore/qlist.h:921
#18 0x7fa6b74295d8 in
QList >::~QList
(this=, this=) at
/usr/include/qt5/QtCore/qlist.h:871
#19 QList
>::~QList (this=, this=) at
/usr/include/qt5/QtCore/qlist.h:871
#20 ViewHighlights::~ViewHighlights (this=, this=) at
/usr/src/debug/kdevelop5-5.6.2-2.4.x86_64/plugins/contextbrowser/contextbrowser.h:85
#21 QMapNodeBase::callDestructorIfNecessary (t=...) at
/usr/include/qt5/QtCore/qmap.h:100
#22 QMapNode::destroySubTree
(this=0x557002d87060) at /usr/include/qt5/QtCore/qmap.h:125
#23 QMapData::destroy (this=0x556ffe5b5e70)
at /usr/include/qt5/QtCore/qmap.h:249
#24 0x7fa6b741fa25 in QMap::~QMap
(this=, this=) at
/usr/include/qt5/QtCore/qmap.h:338
#25 QMap::operator= (other=...,
this=0x556ff4d8ef40) at /usr/include/qt5/QtCore/qmap.h:349
#26 QMap::clear (this=0x556ff4d8ef40) at
/usr/include/qt5/QtCore/qmap.h:656
#27 ContextBrowserPlugin::updateForView (this=this@entry=0x556ff4d8ef00,
view=) at
/usr/src/debug/kdevelop5-5.6.2-2.4.x86_64/plugins/contextbrowser/contextbrowser.cpp:839
#28 0x7fa6b7420b5c in ContextBrowserPlugin::updateViews
(this=0x556ff4d8ef00) at
/usr/src/debug/kdevelop5-5.6.2-2.4.x86_64/plugins/contextbrowser/contextbrowser.cpp:925
#29 0x7fa7165b5043 in QtPrivate::QSlotObjectBase::call (a=0x7ffe48e07ef0,
r=0x556ff4d8ef00, this=0x556ff4e08dd0) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#30 doActivate (sender=0x556ff4e08d10, signal_index=3,
argv=0x7ffe48e07ef0) at kernel/qobject.cpp:3886
#31 0x7fa7165ae50f in QMetaObject::activate (sender=,
m=m@entry=0x7fa716854c00 ,
local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffe48e07ef0)
at kernel/qobject.cpp:3946
#32 0x7fa7165b8efa in QTimer::timeout (this=, _t1=...) at
.moc/moc_qtimer.cpp:205
#33 0x7fa7165aaf0f in QObject::event (this=0x556ff4e08d10,
e=0x7ffe48e08070) at kernel/qobject.cpp:1336
#34 0x7fa717310a7f in QApplicationPrivate::notify_helper (this=, receiver=0x556ff4e08d10, e=0x7ffe48e08070) at
[kwin] [Bug 445412] Zoom effect causes screen to stop updating
https://bugs.kde.org/show_bug.cgi?id=445412 --- Comment #6 from Duncan <1i5t5.dun...@cox.net> --- Bisected both and got a working hit: * kwayland-server back to 6cc372683, immediately b4 eglstreams removal * kwin back to efa08b1f3, before scenes move. That works! So assuming the breakage is in kwin not kwayland-server, we're looking at the range efa08b1f3 (Nov 8) to bad575211 (Nov 10). Looks like ~36 commits. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 445412] Zoom effect causes screen to stop updating
https://bugs.kde.org/show_bug.cgi?id=445412 --- Comment #5 from Duncan <1i5t5.dun...@cox.net> --- Attempting bisect, regressed kwin back to (commit) bad575211, committed Nov 10, which kills eglstream, and zoom is still broken. f91ae3e97 is the immediately previous commit and won't build with an error about missing eglstream.h (or similar) in kwayland-server, so regressing kwin to before bad575211 seems to require regressing kwayland-server back to when it supported eglstream as well. Not sure whether I'll try regressing both together any further, but that should eliminate /some/ possibilities. (FWIW I'm on amdgpu so eglstream itself, being nvidia, shouldn't directly affect me at all. Glad to be rid of its complications in kwin, but the removal is complicating this bisect.) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 442544] Krita 5.0's Shift modifier to change brush size is not behaving as expected.
https://bugs.kde.org/show_bug.cgi?id=442544 --- Comment #9 from Tyson Tan --- Thank you Emmet! :) -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 445416] Dolphin keeps asking for credentials of Windows share
https://bugs.kde.org/show_bug.cgi?id=445416 --- Comment #10 from Alex Levkovich --- No one is going to fix a thing, right? I'd like to hear an answer from a responsible person. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 445550] Frequent SIGSEGV just after rebasing on `master`
https://bugs.kde.org/show_bug.cgi?id=445550 --- Comment #4 from personalizedrefrigera...@gmail.com --- (In reply to personalizedrefrigerator from comment #3) > Here's an easier way to reproduce the bug: > • Open vim > • Press `a` > • Hold down `Enter` > > You can find my .vimrc here: > https://github.com/personalizedrefrigerator/dotfiles/blob/main/.vimrc I am suspicious of these lines in my .vimrc: ``` " Change cursor when entering insert mode " Ref: https://stackoverflow.com/questions/6488683/how-do-i-change-the-cursor-between-normal-and-insert-modes-in-vim let _SI = "\e[6 q" let _EI = "\e[2 q" ``` -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 445550] Frequent SIGSEGV just after rebasing on `master`
https://bugs.kde.org/show_bug.cgi?id=445550 --- Comment #3 from personalizedrefrigera...@gmail.com --- Here's an easier way to reproduce the bug: • Open vim • Press `a` • Hold down `Enter` You can find my .vimrc here: https://github.com/personalizedrefrigerator/dotfiles/blob/main/.vimrc -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 445564] New: With HiDPI scaling, rotating canvas back and forth cause offset of viewport.
https://bugs.kde.org/show_bug.cgi?id=445564 Bug ID: 445564 Summary: With HiDPI scaling, rotating canvas back and forth cause offset of viewport. Product: krita Version: unspecified Platform: Compiled Sources OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: asr...@gmail.com Target Milestone: --- SUMMARY With HiDPI scaling(probably >= 175%), rotating canvas back and forth cause offset of viewport. STEPS TO REPRODUCE 1. create image under OS 200% scaling 2. use mouse middle button + shift to rotate canvas back and forth several times. OBSERVED RESULT The canvas moved a little bit towards the left top corner. EXPECTED RESULT Canvas stays at center. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Debian sid Qt Version: 5.15.2 ADDITIONAL INFORMATION This seems to be caused by snapToDevicePixel in KisCoordinatesConverter::correctOffsetToTransformation, a quick dirty fix is to add an float offset dp to the point passed in, depending on scaling factor. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444701] Deleting a file on the desktop sometimes causes a crash.
https://bugs.kde.org/show_bug.cgi?id=444701 --- 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.
[gwenview] [Bug 443874] Affichage image impossible
https://bugs.kde.org/show_bug.cgi?id=443874 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.
[Breeze] [Bug 443804] Theme switching bug
https://bugs.kde.org/show_bug.cgi?id=443804 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.
[systemsettings] [Bug 444774] QML ConnectionItem: Binding loop detected
https://bugs.kde.org/show_bug.cgi?id=444774 --- 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.
[lattedock] [Bug 443539] The dock's behaviour is very unpredictable. I cannot click on any icons on the dock
https://bugs.kde.org/show_bug.cgi?id=443539 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #5 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.
[krusader] [Bug 442216] Saving a file edited in a remote directory
https://bugs.kde.org/show_bug.cgi?id=442216 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|NOT A BUG |WORKSFORME --- Comment #8 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 444641] Crash wl_display@1: error 1: invalid arguments for org_kde_plasma_window@207.get_icon
https://bugs.kde.org/show_bug.cgi?id=444641 --- 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.
[Breeze] [Bug 444637] Rhythmbox Unable to see if a button is pushed or not
https://bugs.kde.org/show_bug.cgi?id=444637 --- 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.
[krita] [Bug 444751] The application will open like normal but when I try to open any Krita saved file, or try to create a new project, Krita will automatically crash.
https://bugs.kde.org/show_bug.cgi?id=444751 --- 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.
[kwin] [Bug 444594] Tiling Extension on wayland
https://bugs.kde.org/show_bug.cgi?id=444594 --- Comment #3 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.
[Spectacle] [Bug 361036] No support for 30bpp X11 display
https://bugs.kde.org/show_bug.cgi?id=361036 Mia Herkt changed: What|Removed |Added Resolution|--- |FIXED Status|REOPENED|RESOLVED --- Comment #11 from Mia Herkt --- (In reply to Mia Herkt from comment #10) > Looks like it’s regressed as of Spectacle 21.08.3. More precisely it looks > like the color channels are swapped. Actually fixed in e6d64481699c5bfac8d552455c0ffc2a8ac68f4f: https://invent.kde.org/graphics/spectacle/-/commit/e6d64481699c5bfac8d552455c0ffc2a8ac68f4f -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 442544] Krita 5.0's Shift modifier to change brush size is not behaving as expected.
https://bugs.kde.org/show_bug.cgi?id=442544 Emmet O'Neill changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |NOT A BUG -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 444535] Window filtering conditions for custom shortcuts (usually) don't work
https://bugs.kde.org/show_bug.cgi?id=444535 --- Comment #3 from Dmitry Alexandrov --- Adam Fontenot wrote: > I was able to repro this with a shortcut group with a window type selected. > Attached. Hmm... I was about to write again that it works for me, when upon changing the trigger back and forth, it had stopped. So, yes, there is bug, namely: some state is accumulated, that is not reflected in in the UI. Workaround is to create a _new_ action, rather that edit an existing one. >> (In meanwhile, I guess, that you are forgetting to select window type.) > > That sounds like a really nasty bug, though. Surely if you don't select a > window type the expected behavior would be to match all window types! Yes, I also think that it worth at least reporting. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 445319] System freezes when "enter edit mode"
https://bugs.kde.org/show_bug.cgi?id=445319 shaber...@gmail.com changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|BACKTRACE |FIXED --- Comment #4 from shaber...@gmail.com --- (In reply to qydwhotmail from comment #3) > It's likely to be caused by a hidden bug in task manager model. I can't get plasmashell to crash again in order to get the gdb backtrace, since it's working with no issues. All is good now. Thanks. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 445319] System freezes when "enter edit mode"
https://bugs.kde.org/show_bug.cgi?id=445319 qydwhotm...@gmail.com changed: What|Removed |Added CC||qydwhotm...@gmail.com --- Comment #3 from qydwhotm...@gmail.com --- It's likely to be caused by a hidden bug in task manager model. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 445539] Icons look blurry while using evolution (email client)
https://bugs.kde.org/show_bug.cgi?id=445539 --- Comment #1 from David --- Just noticed they also look like this while waiting for a KDE vault to open after putting the password there. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 445319] System freezes when "enter edit mode"
https://bugs.kde.org/show_bug.cgi?id=445319 --- Comment #2 from shaber...@gmail.com --- (In reply to Nate Graham from comment #1) > Sounds like plasmashell is crashing. Can you get a backtrace of the crash? > See > https://community.kde.org/Guidelines_and_HOWTOs/Debugging/ > How_to_create_useful_crash_reports Hi, seems like it doesn't happen anymore, maybe one of the KDE updates fixed it. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 445412] Zoom effect causes screen to stop updating
https://bugs.kde.org/show_bug.cgi?id=445412 --- Comment #4 from Duncan <1i5t5.dun...@cox.net> --- (In reply to Duncan from comment #3) > I'm considering trying one of the other zoom effects (I'm on > full-display zoom ATM) to see if it's broken too -- guessing it is. Can't get looking glass effect to work at all (not sure whether it was before the recent changes or not). Magnifier works but is bugged with an apparently unrelated bug that could have been there all along on wayland (three rectangles instead of one, center is the expected size but outline-only, unmagnified inside the outline, with two half-size rectangles splitting the actual magnified area to the left and right of the center rectangle). Guess I'll see about filing one on that after this bug gets resolved, if it's still there. But with looking-glass apparently broken entirely (not triggering at all), looks like I can set that to disable zoom so I don't keep forgetting its broken and end up disabling my desktop until I kwin_wayland --replace. =:^) -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 298565] KDE(plasma-destop (0.4) closes with segmentation fault
https://bugs.kde.org/show_bug.cgi?id=298565 hea...@126.com changed: What|Removed |Added Status|RESOLVED|REPORTED Assignee|act...@kde.org |unassigned-b...@kde.org Product|Active |kde Target Milestone|unscheduled |--- Component|Applications|general Resolution|DUPLICATE |--- CC||hea...@126.com --- Comment #3 from hea...@126.com --- Hi, I created some vnc sessions on my server, and they will be killed by xserver after some times, from the .vnc log file in user home, I can see below error: XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":4"^M after 217 requests (217 known processed) with 0 events remaining.^M XIO: fatal IO error 11 (资源暂时不可用) on X server ":4"^M after 78 requests (78 known processed) with 0 events remaining.^M klipper: Fatal IO error: client killed kdeinit4: Fatal IO error: client killed kded4: Fatal IO error: client killed kdeinit4: sending SIGHUP to children. kwalletd: Fatal IO error: client killed kglobalaccel: Fatal IO error: client killed klauncher: Exiting on signal 1 kactivitymanagerd: Fatal IO error: client killed kdeinit4: Fatal IO error: client killed ksmserver: Fatal IO error: client killed kdeinit4: sending SIGHUP to children. kwin: Fatal IO error: client killed knotify4: Fatal IO error: client killed plasma-desktop: Fatal IO error: client killed krunner: Fatal IO error: client killed XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":4"^M kmix: Fatal IO error: client killed kwin: Fatal IO error: client killed Gdk-Message: 15:49:08.166: abrt: Fatal IO error 11 (资源暂时不可用) on X server :4. polkit-kde-authentication-agent-1: Fatal IO error: client killed And from /var/log/messages, I can only see below error: __Nov 15 15:49:07 login06 systemd-logind: New session 234654 of user slurmtest. Nov 15 15:49:07 login06 systemd: Started Session 234654 of user slurmtest. Nov 15 15:49:08 login06 org.kde.kuiserver: kuiserver: Fatal IO error: client killed Nov 15 15:49:08 login06 org.a11y.atspi.Registry: XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":4" Nov 15 15:49:08 login06 org.a11y.atspi.Registry: after 21 requests (21 known processed) with 0 events remaining. Nov 15 15:49:08 login06 com.redhat.imsettings: [ 1636962548.166866]: IMSettings-Daemon[21558]: INFO: Release the ownership of com.redhat.imsettings Nov 15 15:49:08 login06 org.gtk.vfs.Daemon: A connection to the bus can't be made Nov 15 15:49:08 login06 journal: Error releasing name org.freedesktop.portal.IBus: 连接已关闭 Nov 15 15:49:08 login06 com.redhat.imsettings: [ 1636962548.191227]: IBus[21918]: Nov 15 15:49:08 login06 com.redhat.imsettings: [ 1636962548.191658]: IMSettings-Daemon[21558]: INFO: Stopped main process for IBus with the status 0 [pid: 21918] Nov 15 15:49:08 login06 com.redhat.imsettings: Exiting... Nov 15 15:49:08 login06 com.redhat.imsettings: [ 1636962548.192246]: GLib-GIO[21558]: CRITICAL **: Error while sending AddMatch() message: The connection is closed Nov 15 15:49:08 login06 com.redhat.imsettings: [ 1636962548.192706]: GLib-GIO[21558]: CRITICAL **: Error while sending AddMatch() message: The connection is closed Nov 15 15:49:08 login06 com.redhat.imsettings: [ 1636962548.193242]: IMSettings-Daemon[21558]: INFO: Unloading imesttings module: qt Nov 15 15:49:08 login06 com.redhat.imsettings: [ 1636962548.193732]: IMSettings-Daemon[21558]: INFO: Unloading imesttings module: gsettings Nov 15 15:49:08 login06 com.redhat.imsettings: [ 1636962548.194156]: IMSettings-Daemon[21558]: INFO: imsettings-daemon is shut down.__ This issue bothered me for about one month, could someone provide some help? Thanks very much Harvey -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 445412] Zoom effect causes screen to stop updating
https://bugs.kde.org/show_bug.cgi?id=445412 Duncan <1i5t5.dun...@cox.net> changed: What|Removed |Added CC||1i5t5.dun...@cox.net --- Comment #3 from Duncan <1i5t5.dun...@cox.net> --- Seeing this myself (also on live-git, here from the gentoo/kde overlay live-git packages) and was just searching bugzi to see if the bug had been already filed before filing it myself. =:^) Highly frustrating as I use zoom often enough it's instinctual, and find myself forgetting I can't ATM because its broken! (I'm wayland-only but for xwayland, having uninstalled xorg, tho I'm comfortable at the CLI and have weston installed as a backup wayland compositor if plasma/kwin_wayland live-git gets too broken.) Additional information on dual monitor behavior: On zoom, one monitor seems to continue working normally, while the other freezes and is subject to VT-switching-locked refresh-rate, as you put it. =:^) My keyboard has three keys I have dedicated to zoom, in/out/actual. After zooming in, I can zoom out, and *often* the frozen monitor comes back to life and starts refreshing normally. However, the actual-size key is broken and won't return me to normal/actual, even on the still-refreshing monitor -- I have to use the zoom-out key. I haven't fully qualified when I can get the second monitor back working and when not, but it seems that if I move the pointer to the frozen-while-zoomed monitor, it stays frozen. Sometimes the cursor disappears and I can't get it back even moving back over the otherwise working monitor, other times it stays visible on the otherwise frozen monitor and the cursor changes if I move it over something where it would normally change, even with the rest of that monitor (including a conky sysmon I'd normally see update every second) stays frozen. Since xorg isn't installed I can't test behavior there, tho you already did. But I'm considering trying one of the other zoom effects (I'm on full-display zoom ATM) to see if it's broken too -- guessing it is. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 443540] Dolphin glitch after packing directory to 7z
https://bugs.kde.org/show_bug.cgi?id=443540 --- Comment #11 from Vladimir Garistov --- Created attachment 143609 --> https://bugs.kde.org/attachment.cgi?id=143609=edit New crash information added by DrKonqi dolphin (21.08.3) using Qt 5.15.2 - What I was doing when the application crashed: After moving a newly created .7z archive to trash and attempting to create it again with the same filename Dolphin crashes. The archive is created successfuly. The crash only happens when the name of the archive matches the filename of a file that was moved to trash. Otherwise a different behaviour is observed (described below). - Unusual behavior I noticed: I compressed a folder in Dolphin to a .7z archive. A notification popped up in the bottom right corner of the screen, as usual. However, it never changed its status to 'Finished'. The archive was created successfuly (as far as I can tell) and can be opened without issues. The notification remains stuck at full progress bar forever. This happens every time a new .7z archive is created. Compressing to .zip for example finishes as expected. - Custom settings of the application: None -- Backtrace (Reduced): #5 0x7fa8a0d5a0dd in KJob::result(KJob*, KJob::QPrivateSignal) () from /usr/lib/libKF5CoreAddons.so.5 #6 0x7fa8a0d5b5cc in KJob::finishJob(bool) () from /usr/lib/libKF5CoreAddons.so.5 [...] #8 0x7fa8901749e3 in Kerfuffle::ReadOnlyArchiveInterface::finished(bool) () from /usr/lib/libkerfuffle.so.21 [...] #10 0x7fa89fa706f9 in QProcess::finished(int, QProcess::ExitStatus) () from /usr/lib/libQt5Core.so.5 [...] #14 0x7fa89fb41c70 in QSocketNotifier::activated(QSocketDescriptor, QSocketNotifier::Type, QSocketNotifier::QPrivateSignal) () from /usr/lib/libQt5Core.so.5 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 443540] Dolphin glitch after packing directory to 7z
https://bugs.kde.org/show_bug.cgi?id=443540 Vladimir Garistov changed: What|Removed |Added CC||vl.garis...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 445428] Widgets that have been manually added but subsequently removed shall appear after restart.
https://bugs.kde.org/show_bug.cgi?id=445428 Duncan <1i5t5.dun...@cox.net> changed: What|Removed |Added CC||1i5t5.dun...@cox.net --- Comment #2 from Duncan <1i5t5.dun...@cox.net> --- User running most of kde/plasma live-git here, and I /think/ this may now be fixed, by the following commit to plasma-framework (select-copied from git log), not sure what release version it should appear in, but frameworks version is reported as 5.89.0 ATM, here (with that commit), so should be in frameworks 5.89 if it didn't make 5.88 (which is what you reported). So if it's not fixed in 5.89, a similar fix needs applied elsewhere. In the mean time a couple workarounds. 1) Here, I've found running the following command from krunner saves plasmashell config as it quits and restarts. killall plasmashell; sleep 1; plasmashell 2) Judging by the comment in the git log below, another workaround may be to add a panel and immediately remove it, thereby triggering plasma to save its config. * commit 1f0df3dd2 | Author: Jan Blackquill | AuthorDate: Tue Oct 5 12:56:42 2021 -0400 | Commit: Jan Blackquill | CommitDate: Tue Oct 5 13:04:48 2021 -0400 | | Corona: save after ending edit mode | | Plasma can be somewhat amnesiac if you make changes to it that don't | involve adding/removing panels and it subsequently unexpectedly ends, | such as when it or the compositor crashes. | | Calling requireConfigSync after edit mode ends guarantees that any changes | made by the user in edit mode will be applied. | | src/plasma/corona.cpp | 4 | 1 file changed, 4 insertions(+) -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 445563] New: When Dolphin is first opened in a different Activity, extracting a .zip from Dolphin open on a different Activity does the extracting, but brings the first Activity to focu
https://bugs.kde.org/show_bug.cgi?id=445563 Bug ID: 445563 Summary: When Dolphin is first opened in a different Activity, extracting a .zip from Dolphin open on a different Activity does the extracting, but brings the first Activity to focus. Product: dolphin Version: 21.08.3 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: random1123581...@protonmail.com CC: kfm-de...@kde.org Target Milestone: --- SUMMARY Pretty much the summary above STEPS TO REPRODUCE 1. Open Dolphin in an Activity, which I will call Activity 1 here. 2. Open a different Activity, which I call Activity 2 here. 3. In Activity 2, open Dolphin, and extract a .zip file using the right click Extract. OBSERVED RESULT Dolphin from Activity 1 comes into focus, and the current Activity is also changed. EXPECTED RESULT The extract-ing should not change Activity, and should not bring to focus the Activity in which Dolphin was first opened. SOFTWARE/OS VERSIONSOperating System: KDE neon 5.23 KDE Plasma Version: 5.23.3 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION none -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433907] plasmashell works slow when displaying textual list of grouped tasks for big group
https://bugs.kde.org/show_bug.cgi?id=433907 Nate Graham changed: What|Removed |Added Version Fixed In||5.24 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433907] plasmashell works slow when displaying textual list of grouped tasks for big group
https://bugs.kde.org/show_bug.cgi?id=433907 Nate Graham changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas |ma/plasma-desktop/commit/b6 |ma/plasma-desktop/commit/ec |3a6c9b16f261ecac99e5d1abbd7 |2d3d56a7eb0ac7bd6eb2a3fb860 |2c52349cb95 |38fad0f000e --- Comment #38 from Nate Graham --- Git commit ec2d3d56a7eb0ac7bd6eb2a3fb86038fad0f000e by Nate Graham, on behalf of Fushan Wen. Committed on 16/11/2021 at 01:33. Pushed by ngraham into branch 'master'. taskmanager: Port PlasmaExtras.ScrollArea to PC3.ScrollView in GroupDialog 1. Port `PlasmaExtras.ScrollArea` to `PC3.ScrollView`, and port `Repeater` to `ListView` so only visible tasks are loaded. 2. Rework activeTask mechanism to fit `ListView`, so the highlight can be restored after opening the same textual list (`findActiveTaskIndex()`). 3. Drop `updateSize()` function because it's more distinct to use size bindings, and the text width is updated by `updateMaxTextWidth()`. 4. Drop `attachModel()` function and set model property directly in `ListView`. 5. Add `isGroupDialog` bool property to `MouseHandler` because `ListView` uses `itemAt` instead of `childAt` to get the item at the cursor position, so drag and drop still works. 6. Several hacks to prevent warning messages, including "Binding loop detected" and "trying to show an empty dialog". 7. Add `iconMargin` and `labelMargin`, so those properties can be shared between `Task` and `GroupDialog`. M +61 -219 applets/taskmanager/package/contents/ui/GroupDialog.qml M +7-1applets/taskmanager/package/contents/ui/MouseHandler.qml M +6-6applets/taskmanager/package/contents/ui/Task.qml M +2-0applets/taskmanager/package/contents/ui/code/layout.js https://invent.kde.org/plasma/plasma-desktop/commit/ec2d3d56a7eb0ac7bd6eb2a3fb86038fad0f000e -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 443192] Add scrollbar to annotation toolbar
https://bugs.kde.org/show_bug.cgi?id=443192 Nate Graham changed: What|Removed |Added Status|CONFIRMED |RESOLVED Latest Commit||https://github.com/ksnip/kI ||mageAnnotator/commit/969866 ||68fd70104b350e5d640e6557239 ||d7e7944 Resolution|--- |UPSTREAM --- Comment #9 from Nate Graham --- Very cool, thanks a lot for that! -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 444149] Spectacle "annotate mode window" is too small to display all tools by default
https://bugs.kde.org/show_bug.cgi?id=444149 Nate Graham changed: What|Removed |Added See Also|https://bugs.kde.org/show_b | |ug.cgi?id=429833| -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 429833] Resize window while annotating to show full image (or maximize when the images is larger than the window can be)
https://bugs.kde.org/show_bug.cgi?id=429833 Nate Graham changed: What|Removed |Added See Also|https://bugs.kde.org/show_b | |ug.cgi?id=444149| -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 429833] Resize window while annotating to show full image (or maximize when the images is larger than the window can be)
https://bugs.kde.org/show_bug.cgi?id=429833 Nate Graham changed: What|Removed |Added CC||pos...@posteo.eu --- Comment #3 from Nate Graham --- *** Bug 444149 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 444149] Spectacle "annotate mode window" is too small to display all tools by default
https://bugs.kde.org/show_bug.cgi?id=444149 --- Comment #4 from Nate Graham --- *** This bug has been marked as a duplicate of bug 429833 *** -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 445447] Window Placement Centered Appears not to be Working on Wayland
https://bugs.kde.org/show_bug.cgi?id=445447 Duncan <1i5t5.dun...@cox.net> changed: What|Removed |Added CC||1i5t5.dun...@cox.net --- Comment #1 from Duncan <1i5t5.dun...@cox.net> --- Two questions/comments: 1) Is it still happening with updates from Nov 14/15? I'm on live-git plasma/wayland (only, no X but xwayland, with weston as my falllback if plasma/kwin fails) using gentoo/kde's live-git packages here, updated late yesterday (14th) and again today (to see if an unrelated bug is fixed yet, it isn't and I came across this going thru new bugs looking to see if it's filed yet), and as of yesterday's update anyway, the new default-to-centered-placement worked. I prefer minimal overlapping however and immediately switched back to that. 2) Of course some apps will remember positioning (unless you have window rules set to prevent that) and will go to wherever they were last, which given the previous default to minimal-overlap, would have likely been in a corner. So I'm wondering if you just caught the updates at the wrong point (#1) and it's now fixed, or if you possibly only tried with apps that remember their position and went back to it, thus not getting the centering. Because the new centered-by-default definitely took here, likely with an update a few hours to a day after yours, and I had to reset it to my preferred mimimal-overlap behavior. If it's still not centering after a new update (and you didn't deliberately reset to minimal-overlap as I did), then yes, you definitely are seeing a continuing bug (that I'm not), as it definitely worked here. (Not sure whether as another user it'd be polite/reasonable to set bug status to NEEDSINFO or not, so I'll defer on that, but that's what I'd consider it now, because with luck you just updated at the wrong time and it's already fixed if you update again.) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 437429] Broken color display in the Palette docker with an active OCIO config
https://bugs.kde.org/show_bug.cgi?id=437429 amyspark changed: What|Removed |Added Assignee|a...@amyspark.me |krita-bugs-n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 445561] Krita 5 opens this PNG corrupted
https://bugs.kde.org/show_bug.cgi?id=445561
--- Comment #2 from amyspark ---
Does the following patch help?
```
diff --git a/libs/ui/kis_png_converter.cpp b/libs/ui/kis_png_converter.cpp
index 0ec098ff4f..6d6173623b 100644
--- a/libs/ui/kis_png_converter.cpp
+++ b/libs/ui/kis_png_converter.cpp
@@ -490,6 +490,11 @@ KisImportExportErrorCode
KisPNGConverter::buildImage(QIODevice* iod)
(png_get_valid(png_ptr, info_ptr, PNG_INFO_tRNS))) {
png_set_expand(png_ptr);
}
+
+#if defined(PNG_READ_INTERLACING_SUPPORTED)
+png_set_interlace_handling(png_ptr);
+#endif
+
png_read_update_info(png_ptr, info_ptr);
// Read information about the png
```
--
You are receiving this mail because:
You are watching all bug changes.
[krita] [Bug 445561] Krita 5 opens this PNG corrupted
https://bugs.kde.org/show_bug.cgi?id=445561 amyspark changed: What|Removed |Added CC||a...@amyspark.me --- Comment #1 from amyspark --- File imports correctly on Windows (fd399d7a20 (upstream/krita/5.0, krita/5.0) ASL: reasign UUID for resources that share one). However, the following is logged: libpng warning: Interlace handling should be turned on when using png_read_image -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 445516] Cache-related visual glitches when Plasma theme SVGs or Plasma Components are updated
https://bugs.kde.org/show_bug.cgi?id=445516 Nate Graham changed: What|Removed |Added Assignee|now...@gmail.com|notm...@gmail.com Component|applet |libplasma Summary|The sliders' nubs in the|Cache-related visual |audio applet have a box |glitches when Plasma theme |around them |SVGs or Plasma Components ||are updated Priority|NOR |VHI Product|plasma-pa |frameworks-plasma Version|5.23.3 |5.87.0 Ever confirmed|0 |1 Severity|minor |normal CC||n...@kde.org Status|REPORTED|CONFIRMED --- Comment #3 from Nate Graham --- I have seen multiple reports of it. Clearing the Plasma SVG cache fixes it. Do this: `rm ~/.cache/*plasma* ; killall plasmashell && kstart5 plasmashell` In the meantime, we really need to get to the bottom of what's behind these caching issues when we update SVGs or Plasma Components code. It happens almost every time, and it provides a really negative impression for our users. :( -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 443356] Clicking on the settings icon in the applet should open the audio KCM
https://bugs.kde.org/show_bug.cgi?id=443356 Nate Graham changed: What|Removed |Added CC||jess...@jessicamaybe.com --- Comment #7 from Nate Graham --- *** Bug 445452 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 445452] Swap the "Configure Audio Volume" Button with "Configure Audio Devices.." when right clicking tray icon
https://bugs.kde.org/show_bug.cgi?id=445452 Nate Graham changed: What|Removed |Added CC||n...@kde.org Status|CONFIRMED |RESOLVED Component|general |applet Resolution|--- |DUPLICATE --- Comment #1 from Nate Graham --- Will be fixed automatically by the fix for Bug 443356, and we can't fix it independently of that. Marking as a duplicate. *** This bug has been marked as a duplicate of bug 443356 *** -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 445562] New: long subject line in UTF-8 is decoded incorrectly
https://bugs.kde.org/show_bug.cgi?id=445562 Bug ID: 445562 Summary: long subject line in UTF-8 is decoded incorrectly Product: kmail2 Version: 5.14.2 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: zhuravlov...@ya.ru Target Milestone: --- SUMMARY *** When message's subject is: 1) in UTF-8, 2) encoded by Base64 as multi-line, 3) has a character which codepoint is splitted among lines,- then this character is decoded incorrectly. *** STEPS TO REPRODUCE 1. Receive a message with subject e.g. Кассовый чек от ФГАОУВО "ДВФУ" за 16.11.2021 which is encoded as: Subject: =?utf-8?B?0JrQsNGB0YHQvtCy0YvQuSDRh9C10Log0L7RgiDQpNCT0JDQ?= =?utf-8?B?ntCj0JLQniAi0JTQktCk0KMiINC30LAgMTYuMTEuMjAyMQ==?= 2. View this message in message list OBSERVED RESULT Subject is displayed as: Кассовый чек от ФГА��УВО "ДВФУ" за 16.11.2021 EXPECTED RESULT Subject should be displayed as: Кассовый чек от ФГАОУВО "ДВФУ" за 16.11.2021 SOFTWARE/OS VERSIONS Linux: 5.3.18-lp152.98-default , x86_64 KDE Plasma Version: 5.18.6 KDE Frameworks Version: 5.71.0 Qt Version: 5.12.7 (built with version 5.12.7) ADDITIONAL INFORMATION If message is composed in KMail2 itself, then its subject is single-lined: Subject: =?UTF-8?B?0JrQsNGB0YHQvtCy0YvQuSDRh9C10Log0L7RgiDQpNCT0JDQntCj0JLQniAi0JTQktCk0KMiINC30LA=?= 16.11.2021 and this problem doesn't appear. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 444535] Window filtering conditions for custom shortcuts (usually) don't work
https://bugs.kde.org/show_bug.cgi?id=444535 --- Comment #2 from Adam Fontenot --- Created attachment 143608 --> https://bugs.kde.org/attachment.cgi?id=143608=edit test khotkeys group (In reply to Dmitry Alexandrov from comment #1) > Works for me. > > > 2. Set the action to be anything involving an active window. I set mine so > > that the window title has to contain "a". > > Please provide an exact config (*.khotkeys) instead of a loose description. > > (In meanwhile, I guess, that you are forgetting to select window type.) I was able to repro this with a shortcut group with a window type selected. Attached. Worth pointing out that I use a non-qwerty layout and that this issue might somehow be related to that. (There are *many* open bugs related to khotkeys handling of variant keyboard layouts.) That sounds like a really nasty bug, though. Surely if you don't select a window type the expected behavior would be to match all window types! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 445561] New: Krita 5 opens this PNG corrupted
https://bugs.kde.org/show_bug.cgi?id=445561 Bug ID: 445561 Summary: Krita 5 opens this PNG corrupted Product: krita Version: 5.0.0-beta2 Platform: macOS (DMG) OS: macOS Status: REPORTED Severity: normal Priority: NOR Component: File formats Assignee: krita-bugs-n...@kde.org Reporter: ghe...@gmail.com Target Milestone: --- The png opens tiled not in the correct order and some parts transparent. The only difference I see from this PNG inside krita process is the popup of color profile. The file might be corrupt however it opens fine in 4.x branch. The file imports correctly as File Layer and dragging and dropping from the GUI. only opening the file fresh causes the tiling issue. File can be get from: https://i.redd.it/40xye7z2arp21.png or attached to this bug report -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 444516] Crash while painting
https://bugs.kde.org/show_bug.cgi?id=444516 --- Comment #20 from David REVOY --- Created attachment 143607 --> https://bugs.kde.org/attachment.cgi?id=143607=edit Krita log + command line log Hey, so I got the crash again and could catch the Krita log and what happened in the command line (in attachement). In short; I had: Still unsignalled after processed 129 tiles increased number of buffers to 256 Bus error Not really useful, I guess. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444904] Unrecoverable plasma shell crash on dragging firefox tab in wayland.
https://bugs.kde.org/show_bug.cgi?id=444904 Shubham Arora changed: What|Removed |Added Keywords||wayland -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 444520] Baloo content indexing resurrects itself after being killed *and* disabled
https://bugs.kde.org/show_bug.cgi?id=444520 Adam Fontenot changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 444520] Baloo content indexing resurrects itself after being killed *and* disabled
https://bugs.kde.org/show_bug.cgi?id=444520 --- Comment #3 from Adam Fontenot --- Created attachment 143606 --> https://bugs.kde.org/attachment.cgi?id=143606=edit log of requested debugging commands (In reply to Nate Graham from comment #1) > kreadconfig5 --file baloofilerc --group "Basic Settings" --key > Indexing-Enabled > > systemctl --user status plasma-plasmashell.service > > systemctl --user status kde-baloo.service > > systemctl --user status plasma-baloorunner.service I am attaching the output as a text file, since the output from systemctl is extremely long. Note that I reported this bug after the issue occurred, and when that happened I once again killed Baloo and (if I recall correctly) deleted all of its cached files. The issue has not reoccured since then. So I'm not sure whether this information will be useful. That said, I have not changed any settings since the issue originally appeared. File content indexing continues to be disabled in the settings window, while basic indexing is enabled. The first command you gave prints no output (even when I correct the file name of the baloofilerc file to be the one on my system). However, examining the file, I see that "only basic indexing" is set to true. Note: my best guess for the cause of this issue is that if Baloo has a file content indexing operation in progress, this operation is terminated, and then file content indexing is disabled, in at least certain cases when normal file indexing is resumed thereafter, it will also resume trying to index the content of the file / files that were in progress previously. If those files were causing the file indexer to hang, Baloo will also hang once again. For that reason, disabling file content indexing *and* deleting Baloo's cache (which had grown to an enormous size on this small SSD) prevented the problem from appearing again, because any leftovers from the in-progress indexing operation were deleted. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 445560] New: [Feature Request] Add ability to snooze a notification
https://bugs.kde.org/show_bug.cgi?id=445560 Bug ID: 445560 Summary: [Feature Request] Add ability to snooze a notification Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: Notifications Assignee: k...@privat.broulik.de Reporter: justin.zo...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 A button that can snooze the notification would be great. I often get notifications in the middle of doing something else and I would like to be reminded of it at a later time without it disappearing or staying on my screen. This would be great for those like me with horrible memory retention. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 445559] New: Add "minimal" mode showing only essential options
https://bugs.kde.org/show_bug.cgi?id=445559 Bug ID: 445559 Summary: Add "minimal" mode showing only essential options Product: systemsettings Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: tobi.goerg...@gmail.com Target Milestone: --- SUMMARY Hey there, as I noticed, what's loved about desktop environments like GNOME is it's simplicity and that it's not fearing users by the shear number of available settings. To make KDE more appealing to new users, KDE should feature a "minimal mode", where only essential options are shown. While this takes flexibility from the user, it adds simplicity that's desired by not few users. This option should e.g. only show one "theme" setting, that only changes the global theme, as this is the only essential option in this category, every other theme option is set when changing the global theme. Everything else should be hidden in this mode from the user (though the "extended" mode showing all options can always be activated ofc) This should be applied to every settings category, really questioning if the shown setting is essential to a new user or if actions can be simplified and more obvious what they actually change. The general scheme of the settings should not be changed, as this might confuse users, if they activate the "extended mode" and all settings are at a different place. For example, there should still be settings to configure which applications show notifications, but maybe not exactly, which notifications of an application will come through. Or hiding the setting for the position of the notification completely and showing it always next to the notification icon. Another example might be the compositor setting: would your grandma know what this setting is for and wouldn't be feared to change it? Mine would be, she wouldn't know what it is and also not care, so why show it to hear and frighten her. This mode should in a next step also be included in KDE applications respecting this setting, only making the really necessary configurable and everything else rely on defaults, This could e.g. mean that the position of the dock might be changeable, but not how tall it is or how transparent it is. This could also have the effect that applications make sure that their defaults are user-friendly and the application is easily usable at first start without the user having to fiddle around, making the desktop more polished and removing papercuts, making our all lives easier. The drawback of course is that the dev has to care about the defaults, though that should be the case anyway. I don't think that an argument like "it's hiding functionality from the user" is applicable here, as a) that's the intention of this option and b) it's only optional. For example, every application could feature a prominent option to switch to "minimal mode" / "extended mode" instantaneously. Also, a "welcome app" is currently in the works, that could ask at first start "Hey, are you a new user? Use this simple mode making your life easier. Are you an experienced user? Use the extended mode with more functionality" This mode could also mean that the system monitor hides the "processes" page in minimal mode, making sure the user doesn't accidentally closes system processes but shows the applications page listing the open applications. Or Dolphin not showing hidden folders starting with a dot, as these folders mostly contain folders and inexperienced users probably don't need to access them. If they still do, they can easily enable the "extended mode" and bam, there's an option to show hidden folders. Or they google, find the hint to press ctrl+h to show them. What should dolphin do? Show a prompt saying "Hey, you're trying to show hidden folders. To do this, you have to enter the extended mode. Are you sure?" Inexperienced users will then know that what they do doesn't seem to be trivial and will think about this again. But whey still have the choice to still show it. All in all, with this setting we protect the system from the user, as it's not that easily possible to do something harmful anymore and the user is protected from the system, as he's not overwhelmed by the amount of available settings. The applications will get saner defaults with a better focus on usability out-of-the-box, while also making Plasma more accessible to new users who can get to know plasma's features, power and flexibility step-by-step. Any thoughts, critics or recommendations are always welcome! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 445316] On Wayland containments are randomly moved between screens on login, often resulting in disappearing panel
https://bugs.kde.org/show_bug.cgi?id=445316 Nate Graham changed: What|Removed |Added Version Fixed In||5.24 Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |FIXED --- Comment #5 from Nate Graham --- Yeah, even though I would expect that to fix it, it's not really a bugfix so much as a re-imagining of how panels get assigned to screens on Wayland. However, given that it's already been merged for 5.24 and it does fix the problem, and 5.23 isn't an LTS release, I doubt there are development resources to fix and produce a patch before 5.23's last bugfix release. Marking as fixed in 5.24. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kholidays] [Bug 445324] Winter solstice inappropriately listed as a holiday
https://bugs.kde.org/show_bug.cgi?id=445324 Nate Graham changed: What|Removed |Added Summary|Calendar of the digital |Winter solstice |clock shows winter solstice |inappropriately listed as a |even though astronomical|holiday |events are disabled | Status|NEEDSINFO |CONFIRMED Component|Digital Clock |general Version|5.21.5 |5.88.0 Product|plasmashell |frameworks-kholidays Ever confirmed|0 |1 Resolution|WAITINGFORINFO |--- Assignee|plasma-b...@kde.org |kdepim-b...@kde.org Target Milestone|1.0 |--- --- Comment #3 from Nate Graham --- I can reproduce with the en_us holiday package, so it seems to be a problem that's not unique to a single one. Moving to the kholidays framework. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 436113] “Typewriter effect” for Title Clips Incorrectly Renders Unicode Characters
https://bugs.kde.org/show_bug.cgi?id=436113 --- Comment #11 from Julius Künzel --- Git commit 7e1a2251e42f59ccdd29f45a3b28a96e81360697 by Julius Künzel. Committed on 15/11/2021 at 23:31. Pushed by jlskuz into branch 'release/21.12'. Typewriter effect should not be blacklisted! Related: bug 445232 M +1-1data/blacklisted_effects.txt https://invent.kde.org/multimedia/kdenlive/commit/7e1a2251e42f59ccdd29f45a3b28a96e81360697 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 445232] typwriter effect missing, author Rafal Lalik
https://bugs.kde.org/show_bug.cgi?id=445232 Julius Künzel changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED Latest Commit||https://invent.kde.org/mult ||imedia/kdenlive/commit/7e1a ||2251e42f59ccdd29f45a3b28a96 ||e81360697 --- Comment #2 from Julius Künzel --- Git commit 7e1a2251e42f59ccdd29f45a3b28a96e81360697 by Julius Künzel. Committed on 15/11/2021 at 23:31. Pushed by jlskuz into branch 'release/21.12'. Typewriter effect should not be blacklisted! Related: bug 436113 M +1-1data/blacklisted_effects.txt https://invent.kde.org/multimedia/kdenlive/commit/7e1a2251e42f59ccdd29f45a3b28a96e81360697 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 445558] New: Not Printing With Print Dialog Shortcut
https://bugs.kde.org/show_bug.cgi?id=445558 Bug ID: 445558 Summary: Not Printing With Print Dialog Shortcut Product: krita Version: nightly build (please specify the git hash!) Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: major Priority: NOR Component: Usability Assignee: krita-bugs-n...@kde.org Reporter: 1celebstu...@gmail.com Target Milestone: --- STEPS TO REPRODUCE 1. Open Krita On Windows Nighly (krita-nightly-x64-5.1.0-prealpha-cd9295eea4) 2. CNTRL P 3. IT DONT PRINT DUD OBSERVED RESULT it dosnt print on nightly but on stable it does EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION NEVER GONNA GIVE YOU UP ALSO WHO FARTED -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 440023] Selecting transition of a mix with shortcut is not working.
https://bugs.kde.org/show_bug.cgi?id=440023 Julius Künzel changed: What|Removed |Added Version Fixed In||21.12.0 Resolution|--- |FIXED Latest Commit||https://invent.kde.org/mult ||imedia/kdenlive/commit/e1cd ||395adb4741a8b9610e6bf91bf52 ||3bb418325 Status|CONFIRMED |RESOLVED --- Comment #3 from Julius Künzel --- Git commit e1cd395adb4741a8b9610e6bf91bf523bb418325 by Julius Künzel. Committed on 15/11/2021 at 23:17. Pushed by jlskuz into branch 'release/21.12'. Fix "Select Transition" should select mixes too FIXED-IN: 21.12.0 M +8-2src/mainwindow.cpp M +5-0src/timeline2/model/trackmodel.cpp M +2-0src/timeline2/model/trackmodel.hpp M +39 -3src/timeline2/view/timelinecontroller.cpp M +3-1src/timeline2/view/timelinecontroller.h https://invent.kde.org/multimedia/kdenlive/commit/e1cd395adb4741a8b9610e6bf91bf523bb418325 -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 445557] New: KIO doesn't work with smbclient > 4.13
https://bugs.kde.org/show_bug.cgi?id=445557 Bug ID: 445557 Summary: KIO doesn't work with smbclient > 4.13 Product: kio-extras Version: 21.08.3 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Samba Assignee: plasma-b...@kde.org Reporter: tobi.goerg...@gmail.com CC: sit...@kde.org Target Milestone: --- SUMMARY As discussed here https://bugs.kde.org/show_bug.cgi?id=445416 KIO doesn't work properly on systems with smbclient > 4.13 installed. This leads to network shares not being accessible anymore. STEPS TO REPRODUCE 1. install smbclient > 4.13 and KDE Plasma Desktop 2. try to access a samba shares with specific config OBSERVED RESULT access to share not possible EXPECTED RESULT share should be accessed as on smbclient < 4.14 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.
[krita] [Bug 442544] Krita 5.0's Shift modifier to change brush size is not behaving as expected.
https://bugs.kde.org/show_bug.cgi?id=442544 --- Comment #8 from Emmet O'Neill --- Git commit 4807d9c8992454e1eb741edc96dc061c9fd42299 by Emmet O'Neill. Committed on 15/11/2021 at 23:09. Pushed by emmetoneill into branch 'master'. Revert "Freehand Tool: Shift-Vertical Drag can now be used to resize too." This reverts commit 4cb4711b0315b01b79d8064865ede596d1205368. Dexterity considerations. (cherry picked from commit 366e42d4448463b8571560a1c57aa651c6eaee27) M +2-3libs/ui/tool/kis_tool_freehand.cc https://invent.kde.org/graphics/krita/commit/4807d9c8992454e1eb741edc96dc061c9fd42299 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 442544] Krita 5.0's Shift modifier to change brush size is not behaving as expected.
https://bugs.kde.org/show_bug.cgi?id=442544 --- Comment #7 from Emmet O'Neill --- Git commit 366e42d4448463b8571560a1c57aa651c6eaee27 by Emmet O'Neill. Committed on 15/11/2021 at 23:06. Pushed by emmetoneill into branch 'krita/5.0'. Revert "Freehand Tool: Shift-Vertical Drag can now be used to resize too." This reverts commit 4cb4711b0315b01b79d8064865ede596d1205368. Dexterity considerations. M +2-3libs/ui/tool/kis_tool_freehand.cc https://invent.kde.org/graphics/krita/commit/366e42d4448463b8571560a1c57aa651c6eaee27 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 445416] Dolphin keeps asking for credentials of Windows share
https://bugs.kde.org/show_bug.cgi?id=445416 Tobias G. changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REPORTED|RESOLVED --- Comment #9 from Tobias G. --- (In reply to Alex Levkovich from comment #7) > Created attachment 143564 [details] > modified pkgbuild re-building the package actually fixed the issue for me, so this really is at least a workaround, until the issue is fixed. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 445556] New: add way to export current settings
https://bugs.kde.org/show_bug.cgi?id=445556 Bug ID: 445556 Summary: add way to export current settings Product: systemsettings Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: tobi.goerg...@gmail.com Target Milestone: --- SUMMARY Migrating from one system to another would be way easier, if KDE featured an option to export the configuration of the current system settings. Obviously, this should not include hardware-specific configurations like network or sound configuration and security-relevant configurations like the firewall (though these might be optional via opt-in). This export feature should include all settings but the following: - Users (obviously) - KDE-password-storage (optional) - online-access (optional) - backups (optional?) - all settings of the network category (though e.g. firewall might be optional) - everything of the hardware-category (though energy-settings might be optional) - software updates (might be a security / stability issue?) Every option remaining should be de-selectable or selectable, if only partial exports are wanted. Selected themes should either be included as a link to the theme that's then downloaded or optionally directly in the export-file, without the need to download it (might be useful if themes are not available anymore) It might also be worth a thought if every KDE program should include such an option, saving all exports in one specific location, making it possible to export the configuration of the system and the used programs, that's ones imported on another system (recognizing, which settings config belongs to which program) and applying the configuration once making a new installation of a highly customized system way easier. This approach also spreads the responsibility for this feature, so that plasma's system settings doesn't have to include the export logic for all KDE programs, but every application is responsible on it's own. Importing settings should also be handled on a per-application level, so that system settings would only forward the to-be-imported settings to the application, which itself applies the settings (so that system settings only works like a "hub" connecting the config export-and-import functionality of the applications, only calling them to export their config or import it, though it might be smarter if the export is handled actually on a per-application-level and only the import is triggered on one place of the system. This could also include the feature on supported systems to install applications, which have a config file to be restored that's not installed on the system, making the configuration of a new system even faster, maybe including an option to export a list of installed applications that should be exported as well. Settings that potentially include personal information should be disabled by default. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 442733] The task manager and cursor animation for starting applications in wayland only works if no other windows are already open.
https://bugs.kde.org/show_bug.cgi?id=442733 carlo changed: What|Removed |Added Version|5.22.90 |5.23.3 --- Comment #7 from carlo --- Since the bug is still present on 5.23.3 I changed the version as 5.22.90 was a beta version. I hope it goes well. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 443961] plasmashell crashes in StatusNotifierItemSource::id() on launch
https://bugs.kde.org/show_bug.cgi?id=443961 --- Comment #18 from Konrad Materka --- I think I was able to reproduce. I restarted kded5 few times using: kquitapp5 kded5; kstart5 kded5 Usually it worked fine, but randomly it caused plasma to crash or all SNI icons where duplicated (Skype, Dropbox etc). Keyboard layout is a plasmoid on my system so it was not affected - I don't have IBus icon). -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 429981] Annotation mode should have visible Undo/Redo buttons
https://bugs.kde.org/show_bug.cgi?id=429981 --- Comment #3 from Nate Graham --- Hmm, in retrospect this should probably be done upstream in KImageAnnotator. Ctrl+Z already works within it so clearly it already has all the logic. It just needs a button. If that's total nonsense because KImageAnnotator was designed to expose its undo action externally so the surrounding app can implement it itself, ignore me and proceed with that design. :) But while we're at it, let's move the undo and redo buttons away from thew two existing buttons so people don't accidentally save or cancel their annotation when trying to click on an undo button. You always want to separate those kinds of buttons. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 444975] Resources > Workspaces: Can't overwrite different workspace of the same name.
https://bugs.kde.org/show_bug.cgi?id=444975 Eoin O'Neill changed: What|Removed |Added Latest Commit|https://invent.kde.org/grap |https://invent.kde.org/grap |hics/krita/commit/e715c2676 |hics/krita/commit/88a68a541 |cfa97e72e9e0bd869359d827524 |90b34617b6c688e0c9eee7135a0 |d2f4|cec2 --- Comment #9 from Eoin O'Neill --- Git commit 88a68a54190b34617b6c688e0c9eee7135a0cec2 by Eoin O'Neill. Committed on 15/11/2021 at 22:46. Pushed by eoinoneill into branch 'krita/5.0'. Fix workspace import overwrite issues. Resolution to MR1155. Patch file by tiar. Tested and seems to work appropriately. (cherry picked from commit e715c2676cfa97e72e9e0bd869359d827524d2f4) M +2-1libs/resources/KisResourceCacheDb.cpp M +1-0libs/resources/KisResourceCacheDb.h M +6-2libs/resources/KisResourceLocator.cpp M +32 -2libs/resources/KisResourceModel.cpp https://invent.kde.org/graphics/krita/commit/88a68a54190b34617b6c688e0c9eee7135a0cec2 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 444975] Resources > Workspaces: Can't overwrite different workspace of the same name.
https://bugs.kde.org/show_bug.cgi?id=444975 Eoin O'Neill changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED Latest Commit||https://invent.kde.org/grap ||hics/krita/commit/e715c2676 ||cfa97e72e9e0bd869359d827524 ||d2f4 --- Comment #8 from Eoin O'Neill --- Git commit e715c2676cfa97e72e9e0bd869359d827524d2f4 by Eoin O'Neill. Committed on 15/11/2021 at 22:43. Pushed by eoinoneill into branch 'master'. Fix workspace import overwrite issues. Resolution to MR1155. Patch file by tiar. Tested and seems to work appropriately. M +2-1libs/resources/KisResourceCacheDb.cpp M +1-0libs/resources/KisResourceCacheDb.h M +6-2libs/resources/KisResourceLocator.cpp M +32 -2libs/resources/KisResourceModel.cpp https://invent.kde.org/graphics/krita/commit/e715c2676cfa97e72e9e0bd869359d827524d2f4 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 445555] New: Add alternative layouts as easily selectable options
https://bugs.kde.org/show_bug.cgi?id=44 Bug ID: 44 Summary: Add alternative layouts as easily selectable options Product: systemsettings Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: kcm_desktoptheme Assignee: plasma-b...@kde.org Reporter: tobi.goerg...@gmail.com Target Milestone: --- SUMMARY Hey there, I noticed that KDE Plasma ships with one default layout (the dock at the bottom) and nothing else, other layouts have to be configured manually. As I think that most of the users would use one of the following layouts, I think it would be useful to add them as easily selectable options: - Windows-like (current default) - MacOS-like - GNOME-like - Unity-like This could also include an option to add custom layouts and make them visible there as well. Customizing one of the default layouts automatically creates a custom layout. This menu could look like on Zorin-OS (https://bit.ly/3FiPa0e) or feren OS (https://bit.ly/3HzVfay) AFAIk this already kind of exists, as global themes can ship with a custom layout; but this has some disadvantages: - custom layouts are not available in a default installation - unexperienced users might overlook the checkbox at the bottom and might wonder why the layout changed / didn't change as intended - layouts can't be distributed independent of global themes - easier accessibility and better understanding of how applying new layouts work Global themes could still also include a custom layout, but just as window decoration or the cursor, the layout should also be selectable independently. As said, this would also allow users to upload layouts without also having to include a complete global theme. This feature would also have to have a way to register panels, also by third-party-software like latte-dock, so that these docks are saved as well (though I think there already is an interface for other applications to tell kwin that they added a panel?) I think this whole idea would remove another small papercut from the KDE shell, as I, a user of KDE for about 5 years now, only learned today that global themes come with a layout (or I might just be exceptionally blind and dumb to not understand how this works :D) -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 429981] Annotation mode should have visible Undo/Redo buttons
https://bugs.kde.org/show_bug.cgi?id=429981 Antonio Prcela changed: What|Removed |Added CC||antonio.prc...@gmail.com --- Comment #2 from Antonio Prcela --- Created attachment 143605 --> https://bugs.kde.org/attachment.cgi?id=143605=edit example of a possible solution Would this be ok? Or see into kImageAnnotator to include undo and redo (another upstream change)? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 445554] Trying to move the Panel crashes the whole desktop
https://bugs.kde.org/show_bug.cgi?id=445554 lrdarkne...@yahoo.de changed: What|Removed |Added CC||lrdarkne...@yahoo.de -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 445554] New: Trying to move the Panel crashes the whole desktop
https://bugs.kde.org/show_bug.cgi?id=445554 Bug ID: 445554 Summary: Trying to move the Panel crashes the whole desktop Product: plasmashell Version: 5.23.3 Platform: Manjaro OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: lrdarkne...@yahoo.de Target Milestone: 1.0 Created attachment 143604 --> https://bugs.kde.org/attachment.cgi?id=143604=edit Journalctl dump SUMMARY I am using a 4K display with 125% scaling as my primary screen and a FHD display as my secondary. I try to switch to KDE Plasma but the Wayland state doesn't seem robust yet. Today i discovered a bug when i try to move the panel to my primary screen. For some reason it always appears on my secondary smaller screen, even when i moved it to my primary screen before (when it doesn't crash). If you don't be careful, the panel just disappears between the two screens and everything becomes unresponsive. Eventually the whole desktop crashes and gets blacked out. I hope that logs that i got from journalctl are somewhat informative. STEPS TO REPRODUCE 1. Have a display setup like mine. 2. Use Plasma Wayland session 3. Move the panel from the secondary smaller screen to the primary OBSERVED RESULT The move is very buggy and if you try a bit, you can make the panel disappear between (?) both displays. This did happen by accident to me quite a few times and makes the whole system pretty unusable. EXPECTED RESULT The move should be less buggy and shouldn't crash the whole desktop. SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.23.3 KDE Frameworks Version: ? Qt Version: ? ADDITIONAL INFORMATION I wasn't able to find a screen recorder that supports Wayland, so i tried to film the behavior with my phone. Sorry for that. It exceeds the upload limits, so I uploaded it to my Nextcloud here: https://nc.horbach5x.de/s/gesa8jLqpc5pgFS As you can see in the video, the context menu is also very buggy. It shows as a whole, but when you hover over it, the upper part disappears... But this should get a separate issue I guess. -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 445533] Zip compressing a php file with name index.php with just the opening php tags will make it not openable in Ark
https://bugs.kde.org/show_bug.cgi?id=445533 Albert Astals Cid changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #1 from Albert Astals Cid --- Can you attach such a zip file? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 445551] Missing of slash '/' to terminate the HTML Bold mode in the description text
https://bugs.kde.org/show_bug.cgi?id=445551 amyspark changed: What|Removed |Added Ever confirmed|0 |1 CC||a...@amyspark.me Status|REPORTED|ASSIGNED Assignee|krita-bugs-n...@kde.org |a...@amyspark.me -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 445553] New: OSD calls action "Switch to laptop screen", despite device not being a laptop
https://bugs.kde.org/show_bug.cgi?id=445553 Bug ID: 445553 Summary: OSD calls action "Switch to laptop screen", despite device not being a laptop Product: KScreen Version: 5.22.5 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: kded Assignee: kscreen-bugs-n...@kde.org Reporter: sergiovargas1...@gmail.com Target Milestone: --- Pressing Super+P brings up the OSD with several options, including "Switch to laptop screen". I'm using a standard desktop though, and I don't see much reason that the option shouldn't be called "Switch to main screen" or "Switch to primary screen" instead. My use case is to manage the connection to a TV. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 445196] Open/Save File Dialog suffers from horrible tearing in Wayland under certain circumstances.
https://bugs.kde.org/show_bug.cgi?id=445196 --- Comment #6 from Jan Rathmann --- Oh, my bad, the original report is from a system with Frameworks 5.87, so it doesn't seem to be a regression (I can also reproduce the bug with an alternate installation with fresh home dir containing Frameworks 5.87). -- You are receiving this mail because: You are watching all bug changes.
[colord-kde] [Bug 445552] Color Corrections does not work in KDE Plasma5 desktop (KDE Plasma5 issue)
https://bugs.kde.org/show_bug.cgi?id=445552 --- Comment #2 from floww...@live.com --- EDIT: I forgot, these are the messages that are shown now: "You don't have any devices registered" "Make sure colord module on kded is running" before installing the .so file, it gave something like "shared library is missing" AFAIR -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 445456] Multiple GPU hangs upon display of notifications or hovering-over a panel
https://bugs.kde.org/show_bug.cgi?id=445456 --- Comment #4 from Ludovic Jozeau --- Ok, for now, I found a work-around, by using linux-lts 5.10.79 and correctly removing ~/.Xauthority (remove then logout then be sure it's removed in a tty then log in then reboot) so it seems to be a problem with latest linux 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 443961] plasmashell crashes in StatusNotifierItemSource::id() on launch
https://bugs.kde.org/show_bug.cgi?id=443961 --- Comment #17 from Konrad Materka --- Created attachment 143603 --> https://bugs.kde.org/attachment.cgi?id=143603=edit Script to list SNI services Hi Jason, could you run attached script? It lists registered SNI services, I want to confirm if there are duplicates in DBUS services. Some logs would be useful too, could you run this please? journalctl -b 0 | grep "system tray" So far I was not able too reproduce this issue, but I didn't try to configure with multiple keyboard layouts - I will try that later. -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 445437] QML errors and crashing when removing processes with search open in tree view
https://bugs.kde.org/show_bug.cgi?id=445437 --- Comment #2 from nyanpasu64 --- Created attachment 143602 --> https://bugs.kde.org/attachment.cgi?id=143602=edit endRemoveRows warnings printed by plasma-systemmonitor Note that this crash occurs inconsistently. I retested where I slowly scrolled through the list of processes, making sure to load all 200 perl processes. Then when I closed the Konsole tab, the entire process list went empty, a few seconds later the terminal filled with "QAbstractItemModel::endRemoveRows: Invalid index ( ### , 3 ) in model ComponentCacheProxyModel(0x5636510d77e0)" warnings (full log attached), then a few seconds later plasma-systemmonitor segfaulted. However I tried a few more times. Sometimes the program seemed to work fine and unload the processes without any visible symptoms. One time it segfaulted anyway, without having printed errors beforehand. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 445196] Open/Save File Dialog suffers from horrible tearing in Wayland under certain circumstances.
https://bugs.kde.org/show_bug.cgi?id=445196 --- Comment #5 from Jan Rathmann --- Created attachment 143601 --> https://bugs.kde.org/attachment.cgi?id=143601=edit Graphical corruptions in file dialog -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 445196] Open/Save File Dialog suffers from horrible tearing in Wayland under certain circumstances.
https://bugs.kde.org/show_bug.cgi?id=445196 Jan Rathmann changed: What|Removed |Added CC||jan.rathm...@gmx.de --- Comment #4 from Jan Rathmann --- I think I see the same thing, additional information how I reproduce this: 1. Open app that uses the KDE file dialog (tested with Ark, Kate, Firefox), try to open a file 2. Everything seems fine first 3. Ensure that the information pane on the right side (F11) in file dialog is enabled 4. Go to a directory that contains archive files (e.g. /var/log on my system) 5. Hover over files/scroll. 6. Graphical corruptions start to appear (see attached screenshot). 7. The graphical corruptions will appear in every directory until the file dialog gets closed. 8. If I invoke the MinimizeAll kwin function, the corruptions on an open file dialog go away temporarily until I scroll or hover over the items. (Minimizing the dialog window with via minimize button from the title bar leaves the corrupted window content unchanged.) Workaround: Disable the information pane in file dialog (F11). I'll try to check if this is maybe a regression in the KDE Frameworks update to 5.88 that I installed this morning. My system: Kubuntu 21.10 with Kubuntu-backports Plasma 5.23.3 Frameworks 5.88.0 Graphics: Asus AMD Radeon R7 240 Kind regards, Jan -- You are receiving this mail because: You are watching all bug changes.
[colord-kde] [Bug 445552] Color Corrections does not work in KDE Plasma5 desktop (KDE Plasma5 issue)
https://bugs.kde.org/show_bug.cgi?id=445552 --- Comment #1 from floww...@live.com --- EDIT: this part was after 'sudo make install': 'systemctl status colord' or 'sudo service colord start/stop/status' gave: colord.service - Manage, Install and Generate Color Profiles Loaded: loaded (/lib/systemd/system/colord.service; static; vendor preset: enabled) Active: active (running) since Mon 2021-11-15 19:52:36 CET; 1s ago Main PID: 20368 (colord) Tasks: 9 (limit: 3409) Memory: 16.9M CGroup: /system.slice/colord.service ├─20368 /usr/lib/colord/colord └─20372 /usr/lib/colord/colord-sane Nov 15 19:52:36 x3k30c-Azalia systemd[1]: Starting Manage, Install and Generate Color Profiles... Nov 15 19:52:36 x3k30c-Azalia systemd[1]: Started Manage, Install and Generate Color Profiles. before 'sudo make install' it showed loaded, active colord-sane and the two last lines were missing AFAIR -- You are receiving this mail because: You are watching all bug changes.
