[digikam] [Bug 467871] When adding thumbnail to parent tag, not require parent tag to be applied.
https://bugs.kde.org/show_bug.cgi?id=467871 Maik Qualmann changed: What|Removed |Added Status|REPORTED|RESOLVED Version Fixed In||8.0.0 Latest Commit||https://invent.kde.org/grap ||hics/digikam/commit/7e5b74f ||9aa4ef0df41e57f9b7da9f5a7d1 ||83dc2a Resolution|--- |FIXED --- Comment #1 from Maik Qualmann --- Git commit 7e5b74f9aa4ef0df41e57f9b7da9f5a7d183dc2a by Maik Qualmann. Committed on 29/03/2023 at 06:35. Pushed by mqualmann into branch 'master'. allow tag thumbnail in the same tag hierarchy FIXED-IN: 8.0.0 M +7-1NEWS M +42 -57 core/app/dragdrop/tagdragdrop.cpp M +2-1core/libs/album/manager/albummanager.h M +22 -1core/libs/album/manager/albummanager_talbum.cpp https://invent.kde.org/graphics/digikam/commit/7e5b74f9aa4ef0df41e57f9b7da9f5a7d183dc2a -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 467865] Realloc failure on certain files
https://bugs.kde.org/show_bug.cgi?id=467865 --- Comment #8 from tagwer...@innerjoin.org --- (In reply to Aaron Williams from comment #7) > Tracking it down it looks like LMDB is returning MDB_PAGE_NOTFOUND, > indicating the database is corrupt. That seems conclusive :-( I've noticed times where "having to index" a *very* large number of new files pushed baloo over the edge. At the moment it makes its internal list of files to index (in memory) and commits only when it's done. That can be a demanding on memory. I'm suspicious abut whether this works if extending into swap but could not reproduce the issue though... Probably a not a problem for you with the amount of RAM you've got available. Maybe time to dig up a backup and find an earlier .local/share/baloo -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 458419] Octave plots won't show
https://bugs.kde.org/show_bug.cgi?id=458419 Alexander Semke changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED Version Fixed In||23.04 --- Comment #1 from Alexander Semke --- This was fixed in the upcoming release 23.04. Please give this release a try once it's available. -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 465277] Cantor doesn't handle multi-command cells very well
https://bugs.kde.org/show_bug.cgi?id=465277
Alexander Semke changed:
What|Removed |Added
Latest Commit|https://invent.kde.org/educ |https://invent.kde.org/educ
|ation/cantor/commit/5484889 |ation/cantor/commit/872008a
|e50b28b95ce468a1fbeb1854e87 |2ca0a983adb49141dd7e866f549
|da6dde |658176
--- Comment #6 from Alexander Semke ---
Git commit 872008a2ca0a983adb49141dd7e866f549658176 by Alexander Semke.
Committed on 29/03/2023 at 06:26.
Pushed by asemke into branch 'release/23.04'.
Squash commit of multiple fixes that need to go into 23.04.
[tests] make initTestCase() in the base class a slot so it's properly found by
QtTest
and skip two tests in Maxima and Python that are failing on CI right now,
will be activated once the underlying issue is fixed.
[tests] skip testInterrupt for python.
[lua] refactored and fixed the parsing of LuaJIT's output.
The current implementation doesn't work at all, the output of LuaJIT doesn't
fit to the parsing logic (anymore) that was implemented initially.
The refactored code works and handles also multi-line commands where the tests
were deactivated earlier for.
More testing and more investment is still probably required to cover more code
syntax in Lua/LuaJIT.
This commit makes the lua backend in Cantor working now first, more
improvements will come later.
Related: bug 461135
FIXED-IN: 23.03
[maxima] always trim the command string and remove line breaks and not only for
plot commands so we get one single response in stdout from Maxima
instead of multiple outputs that we only partially handle. This addresses
multiple issues with multi-line commands with $ and ; endings.
FIXED-IN: 23.03
Added changes that were forgotten in the previous two commits.
When using cantor in labplot, connectToShell() is called after widget()
inDocumentationPanelWidget.
We need to add one more connect in connectToShell() so the actions are also
working in labplot.
[octave] evaluate the option "integrate plots" on every expression execution
and not only during the login
so the user doesn't need to restart Cantor if the options is being changed.
Previously, this option was evaluate at the very beginning and send to Octave
via set (0, "defaultfigurevisible","off")
during the login. In this commit we switch to figure('visible','on') and
figure('visible','off') that are prepended to every expression
containing plot commands.
Also, we set the recommended version of Octave to 7.2 which is available for
one year already.
[octave] restored the slot OctaveSession::processError() that was deleted in
the previous commit.
M +1-1src/backends/lua/luabackend.cpp
M +17 -4src/backends/lua/luaexpression.cpp
M +31 -107 src/backends/lua/luasession.cpp
M +10 -16 src/backends/lua/luasession.h
M +64 -29 src/backends/lua/testlua.cpp
M +2-6src/backends/lua/testlua.h
M +10 -10 src/backends/maxima/maximaexpression.cpp
M +1-1src/backends/maxima/maximasession.cpp
M +57 -16 src/backends/maxima/testmaxima.cpp
M +6-2src/backends/maxima/testmaxima.h
M +1-1src/backends/octave/octavebackend.cpp
M +13 -4src/backends/octave/octaveexpression.cpp
M +45 -65 src/backends/octave/octavesession.cpp
M +5-8src/backends/octave/octavesession.h
M +4-4src/backends/python/testpython.cpp
M +3-1src/lib/test/backendtest.h
M +6-1src/panelplugins/documentationpanel/documentationpanelplugin.cpp
https://invent.kde.org/education/cantor/commit/872008a2ca0a983adb49141dd7e866f549658176
--
You are receiving this mail because:
You are watching all bug changes.
[cantor] [Bug 461135] Lua backend locks up on evaluate
https://bugs.kde.org/show_bug.cgi?id=461135
Alexander Semke changed:
What|Removed |Added
Latest Commit|https://invent.kde.org/educ |https://invent.kde.org/educ
|ation/cantor/commit/3aa4202 |ation/cantor/commit/872008a
|cfcd52cb6c335c4fda9957164c1 |2ca0a983adb49141dd7e866f549
|04d3e8 |658176
--- Comment #3 from Alexander Semke ---
Git commit 872008a2ca0a983adb49141dd7e866f549658176 by Alexander Semke.
Committed on 29/03/2023 at 06:26.
Pushed by asemke into branch 'release/23.04'.
Squash commit of multiple fixes that need to go into 23.04.
[tests] make initTestCase() in the base class a slot so it's properly found by
QtTest
and skip two tests in Maxima and Python that are failing on CI right now,
will be activated once the underlying issue is fixed.
[tests] skip testInterrupt for python.
[lua] refactored and fixed the parsing of LuaJIT's output.
The current implementation doesn't work at all, the output of LuaJIT doesn't
fit to the parsing logic (anymore) that was implemented initially.
The refactored code works and handles also multi-line commands where the tests
were deactivated earlier for.
More testing and more investment is still probably required to cover more code
syntax in Lua/LuaJIT.
This commit makes the lua backend in Cantor working now first, more
improvements will come later.
Related: bug 465277
FIXED-IN: 23.03
[maxima] always trim the command string and remove line breaks and not only for
plot commands so we get one single response in stdout from Maxima
instead of multiple outputs that we only partially handle. This addresses
multiple issues with multi-line commands with $ and ; endings.
FIXED-IN: 23.03
Added changes that were forgotten in the previous two commits.
When using cantor in labplot, connectToShell() is called after widget()
inDocumentationPanelWidget.
We need to add one more connect in connectToShell() so the actions are also
working in labplot.
[octave] evaluate the option "integrate plots" on every expression execution
and not only during the login
so the user doesn't need to restart Cantor if the options is being changed.
Previously, this option was evaluate at the very beginning and send to Octave
via set (0, "defaultfigurevisible","off")
during the login. In this commit we switch to figure('visible','on') and
figure('visible','off') that are prepended to every expression
containing plot commands.
Also, we set the recommended version of Octave to 7.2 which is available for
one year already.
[octave] restored the slot OctaveSession::processError() that was deleted in
the previous commit.
M +1-1src/backends/lua/luabackend.cpp
M +17 -4src/backends/lua/luaexpression.cpp
M +31 -107 src/backends/lua/luasession.cpp
M +10 -16 src/backends/lua/luasession.h
M +64 -29 src/backends/lua/testlua.cpp
M +2-6src/backends/lua/testlua.h
M +10 -10 src/backends/maxima/maximaexpression.cpp
M +1-1src/backends/maxima/maximasession.cpp
M +57 -16 src/backends/maxima/testmaxima.cpp
M +6-2src/backends/maxima/testmaxima.h
M +1-1src/backends/octave/octavebackend.cpp
M +13 -4src/backends/octave/octaveexpression.cpp
M +45 -65 src/backends/octave/octavesession.cpp
M +5-8src/backends/octave/octavesession.h
M +4-4src/backends/python/testpython.cpp
M +3-1src/lib/test/backendtest.h
M +6-1src/panelplugins/documentationpanel/documentationpanelplugin.cpp
https://invent.kde.org/education/cantor/commit/872008a2ca0a983adb49141dd7e866f549658176
--
You are receiving this mail because:
You are watching all bug changes.
[krita] [Bug 467914] Every file type Krita is set to open by default is labeled simply "Image File" with no distinction
https://bugs.kde.org/show_bug.cgi?id=467914 Alvin Wong changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|ASSIGNED CC||al...@alvinhc.com Assignee|krita-bugs-n...@kde.org |al...@alvinhc.com -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 467915] New: Missing/jumbled letters on UI.
https://bugs.kde.org/show_bug.cgi?id=467915 Bug ID: 467915 Summary: Missing/jumbled letters on UI. Classification: Applications Product: kdeconnect Version: 22.12.3 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: major Priority: NOR Component: windows-application Assignee: piyushaggarwal...@gmail.com Reporter: ellacai...@gmail.com Target Milestone: --- Created attachment 157680 --> https://bugs.kde.org/attachment.cgi?id=157680&action=edit Screenshot of missing letters. SUMMARY KDE Connect UI suddenly broke on startup one day. Windows 11 22H2. Operated normally in previous days. No windows updates, or app updates conducted. Uninstalled app and reinstalled from Microsoft store, issue persists. Uninstalled and reinstalled using offline installers on KDE website. Version 22.12.3 and issue identical. App can be closed and opened normally but jumbled UI persists. NOTE: The UI is jumbled in the exact same way each time the app is opened! UI missing letters, but the app however, functions normally. Files can be shared and received provided one is good at deciphering the letters on the screen. As menus are moved through and the UI is interacted with, letters are continually missing/jumbled. Unable to produce a screen with correct letters and display. Screenshot attached. STEPS TO REPRODUCE 1. Unsure how to describe this. 2. 3. OBSERVED RESULT Letters are missing/jumbled across UI. App functions normally. EXPECTED RESULT UI Should not have missing or jumbled letters. SOFTWARE/OS VERSIONS Windows: 22H2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 467914] New: Every file type Krita is set to open by default is labeled simply "Image File" with no distinction
https://bugs.kde.org/show_bug.cgi?id=467914 Bug ID: 467914 Summary: Every file type Krita is set to open by default is labeled simply "Image File" with no distinction Classification: Applications Product: krita Version: 5.1.5 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: File formats Assignee: krita-bugs-n...@kde.org Reporter: unduemar...@dismail.de Target Milestone: --- Created attachment 157679 --> https://bugs.kde.org/attachment.cgi?id=157679&action=edit Three photos each of two image files (a PNG on the left and a JPEG on the right) being labeled in different ways, put together into a collage. SUMMARY Every single file type is labeled in File Explorer as just "Image File" if the user has set Krita to open files with their extensions onto by default. For example, if you have Windows set to open both .png and .jpg files in Krita, the "Type" section in relevant viewports (like the Details view, as well as the Details pane in the right sidebar if that's turned on) simply labels each file as just "Image File". This, despite the file types having multiple well-known differences in how image data is stored. Other apps don't give each file type a name, so the Windows File Explorer default is just "$EXTENSION File", like "PNG File" or "JPG File". (See attachments 5 and 6 for the Windows 10|11 built-in Photos app.) Certain programs, like LibreOffice Draw, go out of their way to provide more detailed descriptions of a file's type, like labeling a .png as "Portable Network Graphics". (See attachments 3 and 4). STEPS TO REPRODUCE 1. Open File Explorer. 2. Go to a folder with both a .png file and a .jpg file on them. 3. Make sure Windows is set to open Krita for both file types by default. (To be sure, right-click, then "Open with >", then "Choose another app", then select "Krita", then "Always" button.) 4. In File Explorer's top bar, click the "View" dropdown, select "Details". (Alternatively or additionally, "View" then "Show >" then check "Details pane".) OBSERVED RESULT See both of them labeled under "Type" column as "Image File", with no distinction between PNGs and JPEGs. (See attachments 1 and 2.) EXPECTED RESULT See the .png file labeled as "PNG File", or much better, "Portable Network Graphics File". Then see the .jpg file labeled as "JPG File" or "Joint Photographic Experts Group File". SOFTWARE/OS VERSIONS Windows: 11 22H2 (detected by System Information log as "10.0.22621"?) KDE Frameworks Version: 5 Qt Version: 5.12.12 (I'm on Krita 5.1.5) ADDITIONAL INFORMATION Reported on the subreddit 3 years ago(!!): https://www.reddit.com/r/krita/comments/fucfas/file_types/ (I can't blame him tbh) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 467913] kwin_wayland crashed in KWin::GLVertexBufferPrivate::interleaveArrays when the cursor was moved to the top-left of the splash screen
https://bugs.kde.org/show_bug.cgi?id=467913 Bug Janitor Service changed: What|Removed |Added Severity|normal |crash -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 467865] Realloc failure on certain files
https://bugs.kde.org/show_bug.cgi?id=467865 --- Comment #7 from Aaron Williams --- ./baloo-checkdb.py Loading DB from /home/aaronw/.local/share/baloo/index... Traceback (most recent call last): File "/fast2/aaronw/programming/kde/./baloo-checkdb.py", line 265, in db.check() File "/fast2/aaronw/programming/kde/./baloo-checkdb.py", line 235, in check self.load_all() File "/fast2/aaronw/programming/kde/./baloo-checkdb.py", line 52, in load_all self._load_posting() File "/fast2/aaronw/programming/kde/./baloo-checkdb.py", line 87, in _load_posting for (key, value) in txn.cursor(): lmdb.PageNotFoundError: mdb_cursor_get: MDB_PAGE_NOTFOUND: Requested page not found Tracking it down it looks like LMDB is returning MDB_PAGE_NOTFOUND, indicating the database is corrupt. Note that I have seen the Baloo database suddenly grow to 4PiB in size several times. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 467913] New: kwin_wayland crashed in KWin::GLVertexBufferPrivate::interleaveArrays when the cursor was moved to the top-left of the splash screen
https://bugs.kde.org/show_bug.cgi?id=467913 Bug ID: 467913 Summary: kwin_wayland crashed in KWin::GLVertexBufferPrivate::interleaveArrays when the cursor was moved to the top-left of the splash screen Classification: Plasma Product: kwin Version: 5.27.3 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: matt.fagn...@bell.net Target Milestone: --- Created attachment 157678 --> https://bugs.kde.org/attachment.cgi?id=157678&action=edit Full trace of all threads of kwin_wayland crash SUMMARY I logged in to Plasma 5.27.3 on Wayland in a Fedora 38 KDE Plasma installation. I moved the mouse cursor to the top-left of the screen when the splash screen was shown. The screen went black for a couple seconds with just a text cursor at the top-left. The effect where the splash screen shrinks and a grey blurred border is shown around it wasn't displayed. Plasma started after a few seconds. coredumpctl showed that kwin_wayland crashed in KWin::GLVertexBufferPrivate::interleaveArrays. Core was generated by `/usr/bin/kwin_wayland --wayland-fd 7 --socket wayland-0 --xwayland-fd 8 --xwayl'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x7efe4c52e870 in KWin::GLVertexBufferPrivate::interleaveArrays (this=0x5651eaf62390, count=4, texcoords=0x7ffdefec3e30, vertices=0x7ffdefec3e58, dim=, dst=0x4) at /usr/src/debug/kwin-5.27.3-2.fc38.x86_64/src/libkwineffects/kwinglutils.cpp:1674 1674*(dst++) = *(vertices++); (gdb) bt #0 0x7efe4c52e870 in KWin::GLVertexBufferPrivate::interleaveArrays(float*, int, float const*, float const*, int) (this=0x5651eaf62390, count=4, texcoords=0x7ffdefec3e30, vertices=0x7ffdefec3e58, dim=, dst=0x4) at /usr/src/debug/kwin-5.27.3-2.fc38.x86_64/src/libkwineffects/kwinglutils.cpp:1674 #1 KWin::GLVertexBuffer::setData(int, int, float const*, float const*) (this=0x5651eb028160, vertexCount=, dim=, vertices=, texcoords=) at /usr/src/debug/kwin-5.27.3-2.fc38.x86_64/src/libkwineffects/kwinglutils.cpp:1894 #2 0x7efe4c52987a in KWin::GLTexture::render(QRegion const&, QRect const&, double, bool) (this=0x5651eaf59520, region=..., rect=, scale=, hardwareClipping=) at /usr/src/debug/kwin-5.27.3-2.fc38.x86_64/src/libkwineffects/kwingltexture.cpp:546 #3 0x7efe4c529aae in KWin::GLTexture::render(QRect const&, double) (this=this@entry=0x5651eaf59520, rect=..., scale=scale@entry=1) at /usr/src/debug/kwin-5.27.3-2.fc38.x86_64/src/libkwineffects/kwingltexture.cpp:511 #4 0x7efe4c040f32 in KWin::EffectsHandlerImpl::renderOffscreenQuickView(KWin::OffscreenQuickView*) const (this=0x5651e98374b0, w=0x5651eabce980) at /usr/src/debug/kwin-5.27.3-2.fc38.x86_64/src/effects.cpp:1793 #5 0x7efe4c0347a9 in KWin::EffectsHandlerImpl::paintScreen(int, QRegion const&, KWin::ScreenPaintData&) (this=0x5651e98374b0, mask=, region=, data=) at /usr/src/debug/kwin-5.27.3-2.fc38.x86_64/src/effects.cpp:396 #6 0x7efe4c0347a9 in KWin::EffectsHandlerImpl::paintScreen(int, QRegion const&, KWin::ScreenPaintData&) (this=0x5651e98374b0, mask=, region=, data=) at /usr/src/debug/kwin-5.27.3-2.fc38.x86_64/src/effects.cpp:396 --Type for more, q to quit, c to continue without paging--c #7 0x7efe4c0347a9 in KWin::EffectsHandlerImpl::paintScreen(int, QRegion const&, KWin::ScreenPaintData&) (this=0x5651e98374b0, mask=, region=, data=) at /usr/src/debug/kwin-5.27.3-2.fc38.x86_64/src/effects.cpp:396 #8 0x5651e87b4286 in KWin::ScreenEdgeEffect::paintScreen(int, QRegion const&, KWin::ScreenPaintData&) (this=0x5651ea7bd8d0, mask=, region=, data=...) at /usr/src/debug/kwin-5.27.3-2.fc38.x86_64/src/effects/screenedge/screenedgeeffect.cpp:72 #9 0x7efe4c0347a9 in KWin::EffectsHandlerImpl::paintScreen(int, QRegion const&, KWin::ScreenPaintData&) (this=0x5651e98374b0, mask=, region=, data=) at /usr/src/debug/kwin-5.27.3-2.fc38.x86_64/src/effects.cpp:396 #10 0x7efe4c0b6c0a in KWin::WorkspaceScene::paint(KWin::RenderTarget*, QRegion const&) (this=this@entry=0x5651e9b1f2a0, renderTarget=renderTarget@entry=0x7ffdefec42a0, region=...) at /usr/src/debug/kwin-5.27.3-2.fc38.x86_64/src/scene/workspacescene.cpp:357 #11 0x7efe4c0416f8 in KWin::EffectsHandlerImpl::renderScreen(KWin::EffectScreen*) (this=0x5651e98374b0, screen=) at /usr/src/debug/kwin-5.27.3-2.fc38.x86_64/src/effects.cpp:1868 #12 0x5651e87ad999 in operator() (__closure=0x5651ea81f480) at /usr/src/debug/kwin-5.27.3-2.fc38.x86_64/src/effects/screentransform/screentransform.cpp:90 #13 QtPrivate::FunctorCall, QtPrivate::List<>, void, KWin::ScreenTransformEffect::addScreen(KWin::EffectScreen*):: >::call (arg=, f=...) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:146 #14 Qt
[digikam] [Bug 467911] digiKam 8.0.0 crashes after second invocation of G'MIC-Qt
https://bugs.kde.org/show_bug.cgi?id=467911 caulier.gil...@gmail.com changed: What|Removed |Added Status|REPORTED|RESOLVED Version Fixed In||8.0.0 Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 463225] Akonadi server crashed when switching user
https://bugs.kde.org/show_bug.cgi?id=463225 rarsa changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG --- Comment #9 from rarsa --- I don't know if this will help someone else but for me the error didn't have anything to do with KDE. I normally use fish shell and I copied the configuration (config.fish) from a different system without a display manager. Given that fish is the default shell, I was executing "startx" inside that file. That was causing the problem. At least my problem can be marked as "resolved". -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 462580] Icon size doesn't change
https://bugs.kde.org/show_bug.cgi?id=462580 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.
[kstars] [Bug 465720] Train not identified on manual connection profiles, crashes when capturing an image
https://bugs.kde.org/show_bug.cgi?id=465720 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- 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 466331] Application Menu and Icon Only Task Manager become uninteractable after right click opening from favorites.
https://bugs.kde.org/show_bug.cgi?id=466331 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #7 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 467311] Plasmashell crashes occasionally when I click on a taskbar icon to attempt to switch applications
https://bugs.kde.org/show_bug.cgi?id=467311 --- Comment #4 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 467289] In the Raven Shadow: Unable to access top-left corner during gameplay
https://bugs.kde.org/show_bug.cgi?id=467289 --- 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.
[krusader] [Bug 464808] plantage tentative ouverture ''Vue F3'' fichiers .docx
https://bugs.kde.org/show_bug.cgi?id=464808 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.
[plasmashell] [Bug 466347] Wallpaper is zoomed in when display is scaled on Wayland
https://bugs.kde.org/show_bug.cgi?id=466347 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- 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.
[krusader] [Bug 460019] Krusader crashes when pressing F3 on zip file
https://bugs.kde.org/show_bug.cgi?id=460019 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #3 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 458066] Sound icon is not available for flatpak apps
https://bugs.kde.org/show_bug.cgi?id=458066 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #6 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.
[kpat] [Bug 450314] kpat randomly crashes
https://bugs.kde.org/show_bug.cgi?id=450314 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.
[kpat] [Bug 435110] The Spider Solitaire app crashes when completing the solitaire layout.
https://bugs.kde.org/show_bug.cgi?id=435110 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #6 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 467259] autoconnecting to captive portal enabled network makes session unuseable
https://bugs.kde.org/show_bug.cgi?id=467259 --- Comment #4 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 467249] Unwanted popup on login - wayland only
https://bugs.kde.org/show_bug.cgi?id=467249 --- Comment #5 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 467119] Tooltips are oftentimes cut when they intersect with something
https://bugs.kde.org/show_bug.cgi?id=467119 --- Comment #5 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.
[systemsettings] [Bug 467174] On fresh Arch install with Firefox installed, nothing is set as default web browser
https://bugs.kde.org/show_bug.cgi?id=467174 --- Comment #4 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kuserfeedback] [Bug 466888] Violation of KDE Software Privacy Policy
https://bugs.kde.org/show_bug.cgi?id=466888 --- Comment #4 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 467076] after login black screen in plasmashell 5.27.0. Deleted all plasmashell / kde .config folders. Black screen in bookworm sid 12
https://bugs.kde.org/show_bug.cgi?id=467076 --- Comment #9 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 312382] edit fields are not editable anymore after certain actions
https://bugs.kde.org/show_bug.cgi?id=312382 --- Comment #10 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 467911] digiKam 8.0.0 crashes after second invocation of G'MIC-Qt
https://bugs.kde.org/show_bug.cgi?id=467911 --- Comment #5 from Tom Cunningham --- (In reply to caulier.gilles from comment #4) > I tried to run more than one time GMIC-Qt on the same image while the same > Image Editor instance, and it do not crash. > > Gilles Caulier It doesn't crash with digiKam-8.0.0-20230328T121705-Win64.exe. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466019] Allow saving tiling layouts
https://bugs.kde.org/show_bug.cgi?id=466019 d.ber...@gmail.com changed: What|Removed |Added CC||d.ber...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 467825] Plasmashell crashes when using Mullvad GUI App system tray context menu
https://bugs.kde.org/show_bug.cgi?id=467825 --- Comment #5 from Fushan Wen --- This looks like a QtBug: https://bugreports.qt.io/browse/QTBUG-88498 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 467911] digiKam 8.0.0 crashes after second invocation of G'MIC-Qt
https://bugs.kde.org/show_bug.cgi?id=467911 --- Comment #4 from caulier.gil...@gmail.com --- I tried to run more than one time GMIC-Qt on the same image while the same Image Editor instance, and it do not crash. Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 467911] digiKam 8.0.0 crashes after second invocation of G'MIC-Qt
https://bugs.kde.org/show_bug.cgi?id=467911 --- Comment #3 from caulier.gil...@gmail.com --- Please try the last pre-release build available here: https://files.kde.org/digikam/ -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 467912] Image Editor ignores former window size at startup
https://bugs.kde.org/show_bug.cgi?id=467912 caulier.gil...@gmail.com changed: What|Removed |Added CC||caulier.gil...@gmail.com Component|ImageEditor-Core|Usability-Ergonomy -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 467911] digiKam 8.0.0 crashes after second invocation of G'MIC-Qt
https://bugs.kde.org/show_bug.cgi?id=467911 --- Comment #2 from Tom Cunningham --- (In reply to caulier.gilles from comment #1) > Which version of Windows installer did you use exactly ? digiKam-8.0.0-beta1-Win64.exe -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 467825] Plasmashell crashes when using Mullvad GUI App system tray context menu
https://bugs.kde.org/show_bug.cgi?id=467825 --- Comment #4 from Eric R --- (In reply to Fushan Wen from comment #2) > Can you run `QDBUS_DEBUG=1 plasmashell --replace` in a console, reproduce > the crash and paste the output of plasmashell here? I tried this, but after running that command and plasma restarted, when I disconnected and reconnected from the system tray icon a couple of times, I couldn't reproduce the error. Maybe the crash was a one-off? Thanks for taking a look! -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 467906] Digikam is crash when use slideshow
https://bugs.kde.org/show_bug.cgi?id=467906 caulier.gil...@gmail.com changed: What|Removed |Added Version Fixed In||8.0.0 Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #2 from caulier.gil...@gmail.com --- Fixed with bug #463785 fix come with next 8.0.0 release Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 467912] New: Image Editor ignores former window size at startup
https://bugs.kde.org/show_bug.cgi?id=467912 Bug ID: 467912 Summary: Image Editor ignores former window size at startup Classification: Applications Product: digikam Version: 8.0.0 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: ImageEditor-Core Assignee: digikam-bugs-n...@kde.org Reporter: twcunningham...@outlook.com Target Milestone: --- SUMMARY The Image Editor window always starts small when digiKam is first started, even though it was full-screen previously. *** STEPS TO REPRODUCE 1. Start digiKam. 2. Start the Image Editor. 3. Maximize Image Editor window. 4. Exit Image Editor. 5. Exit digiKam. 6. Start digiKam. 7. Start Image Editor. OBSERVED RESULT Image Editor window is small. EXPECTED RESULT Image Editor window is full-screen. SOFTWARE/OS VERSIONS Windows: 11 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 467911] digiKam 8.0.0 crashes after second invocation of G'MIC-Qt
https://bugs.kde.org/show_bug.cgi?id=467911 --- Comment #1 from caulier.gil...@gmail.com --- Which version of Windows installer did you use exactly ? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 467911] digiKam 8.0.0 crashes after second invocation of G'MIC-Qt
https://bugs.kde.org/show_bug.cgi?id=467911 caulier.gil...@gmail.com changed: What|Removed |Added Component|ImageEditor-Plugins |Plugin-Editor-GmicQt CC||caulier.gil...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 467895] Add The Option To Ignore Raw And JPEG Photos With The Same File Name When Searching For Duplicates In The Similarity Tab
https://bugs.kde.org/show_bug.cgi?id=467895 caulier.gil...@gmail.com changed: What|Removed |Added Component|Maintenance-Similarities|Searches-Similarity -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 467911] New: digiKam 8.0.0 crashes after second invocation of G'MIC-Qt
https://bugs.kde.org/show_bug.cgi?id=467911 Bug ID: 467911 Summary: digiKam 8.0.0 crashes after second invocation of G'MIC-Qt Classification: Applications Product: digikam Version: 8.0.0 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: crash Priority: NOR Component: ImageEditor-Plugins Assignee: digikam-bugs-n...@kde.org Reporter: twcunningham...@outlook.com Target Milestone: --- SUMMARY In the Image Editor, if you invoke G'MIC-Qt and perform an operation on the image, say Denoise Smooth, the operation will complete and G'MIC-Qt will exit. If you attempt to invoke G'MIC-Qt again, it crashes digiKam. STEPS TO REPRODUCE 1. Open an image in the Image Editor. 2. Open G'MIC-Qt from the Enhance pulldown. 3. Under Repair, perform a Denoise Smooth operation on the image. 4. Close G'MIC-Qt. 5. Attempt to open G'MIC-Qt again. digiKam crashes. OBSERVED RESULT digiKam crashes. EXPECTED RESULT G'MIC-Qt exits back to the Image Editor. SOFTWARE/OS VERSIONS Windows: 11 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 467910] New: Keyboard brightness controls turn off backlight completely when reaching 0%
https://bugs.kde.org/show_bug.cgi?id=467910 Bug ID: 467910 Summary: Keyboard brightness controls turn off backlight completely when reaching 0% Classification: I don't know Product: kde Version: unspecified Platform: Manjaro OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: nikolai.bjerke.sakariass...@gmail.com Target Milestone: --- Changing the backlight to 0% turns the backlight off entirely, rather than setting a low brightness amount. However, changing the brightness to 0% through the battery widget does not have the same problem. I would suggest keeping this bugged behavior as a setting somewhere, as it might be nice to have in some cases. SOFTWARE/OS VERSIONS Kernel: 6.1.19-1-MANJARO KDE Plasma Version: 5.26.5 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 467878] RDP remote sessions: don't apply exit options for close, restart, poweroff, etc.
https://bugs.kde.org/show_bug.cgi?id=467878 --- Comment #2 from Rubén Gómez Antolà --- Hi Aleix, Thanks for your fast answer. (In reply to Aleix Pol from comment #1) > How do you start sessions? it seems like they are not getting started > properly. Sound possible since loginctl don't show the sessions started with XRDP. Sessions are started across XRDP methods, I don't know very well but, croncretly my workmate start across Sesman, a XRDP display manager, that launch user session. If I don't remember bad, I do not need to touch anything of the default setup except /home/user/.xinitrc, that looks like: - Cut from console -- $ cat ~/.xinitrc #!/bin/sh # # ~/.xinitrc # # Executed by startx (run your window manager from here) userresources=$HOME/.Xresources usermodmap=$HOME/.Xmodmap sysresources=/etc/X11/xinit/.Xresources sysmodmap=/etc/X11/xinit/.Xmodmap if [ -d /etc/X11/xinit/xinitrc.d ] ; then for f in /etc/X11/xinit/xinitrc.d/?*.sh ; do [ -x "$f" ] && . "$f" done unset f fi export DESKTOP_SESSION=plasma exec /usr/lib/plasma-dbus-run-session-if-needed startplasma-x11 --- end of cut from console ` > Also please check that nothing is crashing. You can do that by using > coredumpctl. Ok, I'll send you tomorrow since my workmate needs to close his session, my session have permission to poweroff the machine (but still shows the same problem with show all exit options) Thanks again. Best regards. R. Gómez Antolà -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 467906] Digikam is crash when use slideshow
https://bugs.kde.org/show_bug.cgi?id=467906 caulier.gil...@gmail.com changed: What|Removed |Added Component|Preview-Image |Plugin-Generic-SlideShow CC||caulier.gil...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 467909] Connecting external monitor and attempting to extend desktop caused plasma crash
https://bugs.kde.org/show_bug.cgi?id=467909 --- Comment #1 from Michael Magyar --- Created attachment 157677 --> https://bugs.kde.org/attachment.cgi?id=157677&action=edit New crash information added by DrKonqi DrKonqi auto-attaching complete backtrace. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 467909] New: Connecting external monitor and attempting to extend desktop caused plasma crash
https://bugs.kde.org/show_bug.cgi?id=467909 Bug ID: 467909 Summary: Connecting external monitor and attempting to extend desktop caused plasma crash Classification: Plasma Product: plasmashell Version: 5.27.3 Platform: Neon OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: michael.mag...@live.ca CC: k...@davidedmundson.co.uk Target Milestone: 1.0 Application: plasmashell (5.27.3) Qt Version: 5.15.8 Frameworks Version: 5.104.0 Operating System: Linux 5.19.0-35-generic x86_64 Windowing System: X11 Distribution: KDE neon 5.27 DrKonqi: 5.27.3 [CoredumpBackend] -- Information about the crash: Initially only the internal display of my laptop was available. After connecting my external displays using a USB-C displayport connection I used the fn+F7 hot key to try to extend my desktop. After clicking 'extend to the right' plasma crashed. The crash can be reproduced sometimes. -- Backtrace (Reduced): #6 0x7f6dde65b0dd in QQuickItemPrivate::addToDirtyList() (this=this@entry=0x557add99cf70) at items/qquickitem.cpp:6258 #7 0x7f6dde65fc9e in QQuickItemPrivate::dirty(QQuickItemPrivate::DirtyType) (this=this@entry=0x557add99cf70, type=type@entry=QQuickItemPrivate::Visible) at items/qquickitem.cpp:6242 #8 0x7f6dde66185a in QQuickItemPrivate::setEffectiveVisibleRecur(bool) (this=0x557add99cf70, newEffectiveVisible=) at items/qquickitem.cpp:6105 #9 0x7f6dde6618cb in QQuickItemPrivate::setEffectiveVisibleRecur(bool) (this=0x557add99cbb0, newEffectiveVisible=) at items/qquickitem.cpp:6115 #10 0x7f6dde6618cb in QQuickItemPrivate::setEffectiveVisibleRecur(bool) (this=0x557addcf4190, newEffectiveVisible=) at items/qquickitem.cpp:6115 The reporter indicates this bug may be a duplicate of or related to bug 466629. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 467908] New: QCompelter window display error if qt use qt.qpa.wayland plugins
https://bugs.kde.org/show_bug.cgi?id=467908 Bug ID: 467908 Summary: QCompelter window display error if qt use qt.qpa.wayland plugins Classification: Plasma Product: kwin Version: 5.27.3 Platform: Ubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: core Assignee: kwin-bugs-n...@kde.org Reporter: upcliu...@outlook.com Target Milestone: --- SUMMARY In qt App using wayland display server（Set QT_QPA_PLATFORM to wayland）with a QLineEdit which has been set a QCompleter，if I type some words which is in the wordlist of QCompleter the QCompleter window should show under the QLineEdit, but some time it will show at error pos with error windowType（with title bar）。 STEPS TO REPRODUCE 1. Type a word in QLineEdit to make the QCompleter show； 2. Press down BackSpace will delete the word in QLineEdit and the QCompleter will hide; 3. Keeping Press BackSpace, type a word make QCompleter show again, the QCompleter will show at error pos with error windowType（with title bar） OBSERVED RESULT QCompleter will show at error pos with error windowType（with title bar）. EXPECTED RESULT QCompleter show without error. SOFTWARE/OS VERSIONS Linux/KDE Plasma: ubuntu 22.10 KDE Plasma Version: The latest version on ubuntu 22.10 KDE Frameworks Version: The latest version on ubuntu 22.10 Qt Version: The latest version on ubuntu 22.10 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 467519] Keyboard input doesn't work in plasmoids / plasma widgets
https://bugs.kde.org/show_bug.cgi?id=467519 Trip Ericson changed: What|Removed |Added CC||rov...@quelorant.com --- Comment #7 from Trip Ericson --- I seem to be having this same issue suddenly after rebooting by Kubuntu 22.04 machine, presumably caused by a previous update that I didn't close my session for (I'd had about 90 days of uptime). For me it's broader than this ticket suggests though, as it seems to have impacted Konsole as well, at least. It was fine upon first logging in, but after several hours, I had the same issue with the application launcher including only being able to type a single letter, and Konsole stopped accepting input from the keyboard as well. If I tried to open a new window from that existing Konsole, I could not type in that one either, but opening Konsole separately from the Alt+Space launcher did allow me to type in the new Konsole window. The keyboard continued to work on other programs including Firefox at the same time. I found a few other posts in other places apparently mentioning the issue as well. https://forum.kde.org/viewtopic.php?f=289&t=175962 https://bbs.archlinux.org/viewtopic.php?id=265917 My system is an Asus G752VY-RH71. My KDE version is 5.24.7. Please let me know what other information I can provide. -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 467907] New: Playing HTML5 video doesnt lock screen deactivation
https://bugs.kde.org/show_bug.cgi?id=467907 Bug ID: 467907 Summary: Playing HTML5 video doesnt lock screen deactivation Classification: Applications Product: Falkon Version: 22.12.3 Platform: Flatpak OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: now...@gmail.com Reporter: amanita+kdeb...@mailbox.org Target Milestone: --- SUMMARY Normally playing videos should lock the screensaver somehow. This is currently not implemented in Falkon, after a while the screen goes off SOFTWARE/OS VERSIONS Operating System: Fedora Linux 37 KDE Plasma Version: 5.27.3 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.8 Kernel Version: 6.2.8-200.fc37.x86_64 (64-bit) Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 467603] Okular crashed when using the 'Save Form' button in a PDF form
https://bugs.kde.org/show_bug.cgi?id=467603 --- Comment #2 from auberg...@outlook.com.au --- Created attachment 157676 --> https://bugs.kde.org/attachment.cgi?id=157676&action=edit Australian Government form The PDF I was having issues with. The 'Save Form' button crashes Okular. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 467906] Digikam is crash when use slideshow
https://bugs.kde.org/show_bug.cgi?id=467906 --- Comment #1 from mag...@gmail.com --- I don´t know how to send crash report -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 467906] New: Digikam is crash when use slideshow
https://bugs.kde.org/show_bug.cgi?id=467906 Bug ID: 467906 Summary: Digikam is crash when use slideshow Classification: Applications Product: digikam Version: 7.10.0 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: crash Priority: NOR Component: Preview-Image Assignee: digikam-bugs-n...@kde.org Reporter: mag...@gmail.com Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Click on slide show 2. Click to browse some photos 3. click ESC key to exit slide show OBSERVED RESULT After close slide show, Digikam crash EXPECTED RESULT back to main screen withsou crash SOFTWARE/OS VERSIONS Windows: Windows 10 Home Single Language 22H2 19045.2788 Windows Feature Experience Pack 120.2212.4190.0 macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 467905] New: Wayland screensharing starts normally but doesnt work
https://bugs.kde.org/show_bug.cgi?id=467905 Bug ID: 467905 Summary: Wayland screensharing starts normally but doesnt work Classification: Applications Product: Falkon Version: 22.12.3 Platform: Flatpak OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: now...@gmail.com Reporter: amanita+kdeb...@mailbox.org Target Milestone: --- SUMMARY It seems Falkon has an early implementation of the screensharing portal. It shows normally, I grant the permission, but in the end it doesnt share my screen. If I can help with debug logs I am happy to. STEPS TO REPRODUCE 1. Go to a BBB or jitsi meeting (Proprietary services are veeery complicated I guess) 2. Start screensharing, grant the permission in Falkon 3. Select a screen to share OBSERVED RESULT Everything goes normally until that point. But the screenshare is black / does not receive anything. EXPECTED RESULT I guess some fix at receiving the Wayland protocol screenshare? SOFTWARE/OS VERSIONS Operating System: Fedora Linux 37 KDE Plasma Version: 5.27.3 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.8 Kernel Version: 6.2.8-200.fc37.x86_64 (64-bit) Graphics Platform: Wayland Processors: 8 × AMD Ryzen 5 PRO 3500U w/ Radeon Vega Mobile Gfx Memory: 13.5 GiB of RAM Graphics Processor: AMD Radeon Vega 8 Graphics ADDITIONAL INFO tested with BBB and Jitsi -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 467904] New: Bookmarks displayed incorrectly
https://bugs.kde.org/show_bug.cgi?id=467904 Bug ID: 467904 Summary: Bookmarks displayed incorrectly Classification: Applications Product: Falkon Version: 22.12.3 Platform: Flatpak OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: now...@gmail.com Reporter: amanita+kdeb...@mailbox.org Target Milestone: --- SUMMARY I have a load of Bookmarks on Firefox. They are all in the visible bar, with many folders and subfolders and along way too many unsorted ones, all in the same bar. Firefox solves this by cutting off the display and having a scrollable dropdown Menu. Falkon seems to have a bug here. STEPS TO REPRODUCE 1. Import a long list of bookmarks to falkons visible bookmark bar 2. set it to always show 3. hover over it OBSERVED RESULT It seems "Chromium-Tab-like" the size of the bookmark entries can shrink indefinetly, so they are actually there and clickable but show no text or icons. When hovering over them it shows a slim bar, what would normally be the highlighting of them, but its like 2px wide. EXPECTED RESULT Have a minimum width for the bookmarks just like for the tabs. Use the exact same dropdown menu for the overflow entries. ADDITIONAL INFORMATION Falkon is great -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 467903] New: Datebar sometimes grays out non-empty units
https://bugs.kde.org/show_bug.cgi?id=467903 Bug ID: 467903 Summary: Datebar sometimes grays out non-empty units Classification: Applications Product: kphotoalbum Version: 5.10.0 Platform: Other OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: Datebar Assignee: kpab...@willden.org Reporter: johan...@zarl-zierl.at Target Milestone: --- SUMMARY As pointed out by Pierre Etchemaïté at https://invent.kde.org/graphics/kphotoalbum/-/commit/2d5b87c0430a791b4afb3a660bef923464d5376f#note_650503, the algorithm for graying out the empty margin areas of the DateBar can sometimes gray out non-empty time units. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 448681] digikam uses abandoned library incompatible with ffmpeg 5.0
https://bugs.kde.org/show_bug.cgi?id=448681 Ken Rushia changed: What|Removed |Added CC||k...@kenrushia.com -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 412798] Feature Request Enlarge text encoding/decoding capability to include BD mpls files
https://bugs.kde.org/show_bug.cgi?id=412798 Waqar Ahmed changed: What|Removed |Added Resolution|--- |UPSTREAM CC||waqar@gmail.com Status|REPORTED|RESOLVED --- Comment #1 from Waqar Ahmed --- We use QStringEncoder provided by Qt for encoding/decoding. Please report this to Qt instead. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 461101] Database connections are lost when closing Kate
https://bugs.kde.org/show_bug.cgi?id=461101 Waqar Ahmed changed: What|Removed |Added CC||waqar@gmail.com Component|encoding|application -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 443414] Emmet script does not work in this case
https://bugs.kde.org/show_bug.cgi?id=443414 Waqar Ahmed changed: What|Removed |Added Status|REPORTED|RESOLVED CC||waqar@gmail.com Resolution|--- |NOT A BUG --- Comment #1 from Waqar Ahmed --- > Select a line as a whole It works only if the selection is a number. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 454982] Cannot override /add to LSP settings in $HOME/.config/kate/lspclient/settings.json
https://bugs.kde.org/show_bug.cgi?id=454982 Waqar Ahmed changed: What|Removed |Added CC||waqar@gmail.com Resolution|--- |DOWNSTREAM Status|REPORTED|RESOLVED --- Comment #1 from Waqar Ahmed --- Please report this to pylsp, we just pass the config to the server -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 467348] Cover overlay "Play" and "Add to Playlist" buttons do not work when using the app in a non-English language
https://bugs.kde.org/show_bug.cgi?id=467348 --- Comment #5 from Nate Graham --- ...I mean `LANG=en_GB elisa` and `LANG=en_US elisa`, of course. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 438308] Subpar UX when opening the terminal panel but Konsole is not installed
https://bugs.kde.org/show_bug.cgi?id=438308 Waqar Ahmed changed: What|Removed |Added Component|scripting |application -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 458701] Kate cannot edit a system file on nixos
https://bugs.kde.org/show_bug.cgi?id=458701 Waqar Ahmed changed: What|Removed |Added Component|scripting |application CC||waqar@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 467902] New: Akonadi Server crashes when resizing window with rules
https://bugs.kde.org/show_bug.cgi?id=467902 Bug ID: 467902 Summary: Akonadi Server crashes when resizing window with rules Classification: Frameworks and Libraries Product: Akonadi Version: 5.22.3 Platform: Archlinux OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: server Assignee: kdepim-b...@kde.org Reporter: n3verg0nnagiveyouup+kdeb...@disroot.org Target Milestone: --- SUMMARY Akonadi Server crashes when I try to violate max window size rules STEPS TO REPRODUCE 1. Open an app (for my case it was the KDE Emoji Picker) 2. Open the window rules utility 3. Add a forced max size to the window (nothing more) 4. Apply 5. Restart this app 6. Try to resize the window in such a way the rule is violated OBSERVED RESULT KDE Plasma crashes, then drKonqi notify me that Akonadi Server just crashed EXPECTED RESULT The window should just lock its dimensions, without crashing the entire Desktop Environment SOFTWARE/OS VERSIONS Linux: 6.2.8-arch1-1 (64-bit) KDE Plasma Version: 5.27.3 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.8 Windowing System: Wayland BACKTRACE Application: Akonadi Server (akonadiserver), signal: Segmentation fault [KCrash Handler] #4 0x5640712455c3 in ?? () #5 0x7f82ce0b1bb0 in QObject::event(QEvent*) () from /usr/lib/libQt5Core.so.5 #6 0x7f82ce08df2c in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/libQt5Core.so.5 #7 0x7f82ce08ea53 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib/libQt5Core.so.5 #8 0x7f82ce0d4e88 in ?? () from /usr/lib/libQt5Core.so.5 #9 0x7f82cc50f53b in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #10 0x7f82cc56c219 in ?? () from /usr/lib/libglib-2.0.so.0 #11 0x7f82cc50e1a2 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #12 0x7f82ce0d8c6c in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #13 0x7f82ce0866ec in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #14 0x7f82ce091219 in QCoreApplication::exec() () from /usr/lib/libQt5Core.so.5 #15 0x56407123af4d in ?? () #16 0x7f82cd83c790 in ?? () from /usr/lib/libc.so.6 #17 0x7f82cd83c84a in __libc_start_main () from /usr/lib/libc.so.6 #18 0x56407123dcf5 in ?? () [Inferior 1 (process 19499) detached] -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 467865] Realloc failure on certain files
https://bugs.kde.org/show_bug.cgi?id=467865 --- Comment #6 from tagwer...@innerjoin.org --- (In reply to Aaron Williams from comment #2) > ... hence I use XFS. It might still be worth the "sanity check" of running, for a file you know has been indexed: baloosearch -i filename:the-file-name and see whether you get just the one hit. The number is the "docID", a combination of the device and inode number. If you see several hits with different docID's, you are on shifting sands. I'm afraid I don't know how XFS behaves (and whether you have any extra layers) but it's worth keeping an eye on the results from stat the-file-name and see if the device and inode numbers for the file change (for example over reboots). Igor Poboiko has a python "baloo-checkdb.py" script that checks the index for consistency https://invent.kde.org/frameworks/baloo/uploads/bdc9f5f17fc96490b7bd4a22ac664843/baloo-checkdb.py See https://invent.kde.org/frameworks/baloo/-/merge_requests/87#note_535270 for context I would worry about trying it on such a large index, but who knows... -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 467901] New: digiKam cannot be installed in Neon through Discover
https://bugs.kde.org/show_bug.cgi?id=467901 Bug ID: 467901 Summary: digiKam cannot be installed in Neon through Discover Classification: KDE Neon Product: neon Version: unspecified Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Packages Testing Edition Assignee: neon-b...@kde.org Reporter: valterm...@gmail.com CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- SUMMARY *** The program *digiKam* cannot be installed from Discover *** STEPS TO REPRODUCE 1. open Discover 2. search and try to install digiKam 3. OBSERVED RESULT Discover returns an error pop-up, warning: "dependency resolution failed" EXPECTED RESULT It should be work as expected, digiKam should be installed regularly SOFTWARE/OS VERSIONS Operating System: KDE neon Testing Edition KDE Plasma Version: 5.27.3 KDE Frameworks Version: 5.105.0 Qt Version: 5.15.8 Kernel Version: 5.19.0-38-generic (64-bit) Graphics Platform: X11 Graphics Processor: NVE7 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 456701] view.selection() returns ReferenceError: Range is not defined
https://bugs.kde.org/show_bug.cgi?id=456701 Bug Janitor Service changed: What|Removed |Added Ever confirmed|0 |1 Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |ASSIGNED --- Comment #3 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/frameworks/ktexteditor/-/merge_requests/530 -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 465889] With pre-existing screen configs, primary Display Cannot be adjusted in 5.27.0, KDE Panel doesn't move with it
https://bugs.kde.org/show_bug.cgi?id=465889 --- Comment #25 from Michael Butash --- (In reply to Nate Graham from comment #24) > I don't see anything suspicious in the Plasma config files, which leaves > KScreen as the culprit. Unfortunately KScreen configs are basically > impossible to diff so I suspect we'll never truly know what weird old config > data was causing this. Thanks so much anyway! Agreed, I did the same, and other than a bunch of application specific windowing parameters, I didn't see much. What was odd was under the plasmascreenrc was the [ScreenConnectors] portion, that wasn't present under the last, but didn't seem suspect otherwise, just don't know what those definitions were used by or for. This laptop is only about 6mo old, I doubt it began with too old of plasma to pick up too much cruft along the way. I think some of it is the collection too of all the various "what if's" that collect over time, such my plethora of kscreen variations in that folder that likely I would venture conflict with one another. Now that I understand from your guidance more about how kde stores display params, I can diagnose this more, otherwise I know at least to purge those settings. Now my next biggest challenge is why the kwin script for restoreToScreen never works for restoring window placements working randomly, less often than more. With 4 displays, it's maddening when my dock glitches, and moves ALL my 50-some windows away from my 3x 50" TV's to my 15" laptop screen, forcing me to manually move stuff around back where I want them. KDE really should handle this natively better than a script plugin. Thanks again Nate and David! -- You are receiving this mail because: You are watching all bug changes.
[kio-gdrive] [Bug 467900] Security concern for login in with KDE Online Accounts
https://bugs.kde.org/show_bug.cgi?id=467900 siloco...@gmail.com changed: What|Removed |Added CC||siloco...@gmail.com Platform|Other |Ubuntu -- You are receiving this mail because: You are watching all bug changes.
[kio-gdrive] [Bug 467900] New: Security concern for login in with KDE Online Accounts
https://bugs.kde.org/show_bug.cgi?id=467900 Bug ID: 467900 Summary: Security concern for login in with KDE Online Accounts Classification: Frameworks and Libraries Product: kio-gdrive Version: 22.08.1 Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: elvis.angelac...@kde.org Reporter: siloco...@gmail.com Target Milestone: --- Created attachment 157675 --> https://bugs.kde.org/attachment.cgi?id=157675&action=edit KDE Online Account popup hard to identify target or browser. The issue is when I want to connect KDE Online Accounts and I get what looks like the Google login page. The login page should be a separate browser based window showing the complete google url that you want to use to connect. Currently it is just a plain popup which means I have no way of trusting it with my password that in fact it is KDE's Online Accounts popup or someone else's man in the middle popup as KDE. Here is the example signup window I am talking about: [url]https://ibb.co/HNkMLFd[/url] Normally when I connect accounts using google, Chrome or some other legit browser pops up with the full URL displayed at the top that you can verify the request is going to Google for authentication. I think it should looks something like this. Notice how it is a browser window with full URL in display. https://ibb.co/zm53QT8 Is there possibly another way to connect the KDE Online Account that clearly shows a legitimate browser and it's URL. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kcoreaddons] [Bug 387663] Dolphin doesn't update view (doesn't show new files)
https://bugs.kde.org/show_bug.cgi?id=387663 --- Comment #72 from b2 --- Thanks for the explanation, hopefully this will be tackled one day. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 464087] highlight selection broken in RTL text when Line Height Multiplier > 1
https://bugs.kde.org/show_bug.cgi?id=464087 Bug Janitor Service changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|ASSIGNED --- Comment #1 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/frameworks/ktexteditor/-/merge_requests/529 -- You are receiving this mail because: You are watching all bug changes.
[marble] [Bug 467898] marble-qt starts with small window which is empty
https://bugs.kde.org/show_bug.cgi?id=467898 --- Comment #1 from Petr Schonmann --- Created attachment 157674 --> https://bugs.kde.org/attachment.cgi?id=157674&action=edit marble qt mint at startup -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 467215] macOS 11.74 Big Sur: digikam crashes unexpectedly after launching G'MIC (theme settings relevant)
https://bugs.kde.org/show_bug.cgi?id=467215 --- Comment #29 from No_Planet_2 --- Sources: https://github.com/aferrero2707/gimp-plugins-collection/releases/download/continuous/GMIC-Gimp-2.10-osx.tgz https://download.gimp.org/gimp/v2.10/macos/gimp-2.10.34-x86_64.dmg Silicon https://download.gimp.org/gimp/v2.10/macos/gimp-2.10.34-arm64.dmg -- You are receiving this mail because: You are watching all bug changes.
[kio-gdrive] [Bug 391356] KIO GDrive should provide file transnsfer stats for uploads and downloads
https://bugs.kde.org/show_bug.cgi?id=391356 siloco...@gmail.com changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #3 from siloco...@gmail.com --- Posted in wrong thread -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 467858] Digikam starts with small window which is empty and starts very slow when first screen is set to MAP
https://bugs.kde.org/show_bug.cgi?id=467858 --- Comment #4 from Petr Schonmann --- Thanks for advice, now digikam is more usable :) I started new bug in marble project, because when i run marble-qt, same issue is there. Its bug #467898 -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 467899] New: Extracting .zip file via dolphin extract menu ignores that libzip is disabled in settings
https://bugs.kde.org/show_bug.cgi?id=467899 Bug ID: 467899 Summary: Extracting .zip file via dolphin extract menu ignores that libzip is disabled in settings Classification: Applications Product: ark Version: 22.12.3 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: elvis.angelac...@kde.org Reporter: firma@gmail.com CC: aa...@kde.org, rthoms...@gmail.com Target Milestone: --- SUMMARY After unpacking a zip file with symlinks using Ark, the symlinks appear as regular files and don't point anywhere. While disabling libzip plugin in Ark settings is a temporary workaround, rightclicking zip file in Dolphin and choosing any of the extract options forces archive to be decompressed with libzip, even though libzip is disabled in settings. This is linked to bug 415723. STEPS TO REPRODUCE 1. Repeat steps from bug 415723 . 2. Go to Ark Settings, disable libzip plugin. 3. Extract archive using Ark's GUI extract option. Notice that symlink is linked correctly 4. Remove extracted files and close Ark. 5. Extract the same archive rightclicking it in dolphin -> Extract -> any of the options OBSERVED RESULT Symlinks are not created correctly. Additionaly, monitoring dolphin's process with strace produces lines mentioning "Ark.libzip" despite libzip plugin being disabled. EXPECTED RESULT Symlinks are to be created correctly and libzip should not be used. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 6.2.8-arch1-1 (64bit) KDE Plasma Version: 5.27.3 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[marble] [Bug 467898] New: marble-qt starts with small window which is empty
https://bugs.kde.org/show_bug.cgi?id=467898 Bug ID: 467898 Summary: marble-qt starts with small window which is empty Classification: Applications Product: marble Version: 21.12.3 Platform: Mint (Ubuntu based) OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: marble-b...@kde.org Reporter: pschonm...@gmail.com Target Milestone: --- SUMMARY *** I observed it in digikam #467858 at first but confirmed when installed marble-qt. Bug is there too. When launched marble only, the window isnt displayed. Its probably related only in qt version *** STEPS TO REPRODUCE 1. Just run program 2. 3. OBSERVED RESULT See attachement EXPECTED RESULT Dont display empty window :) SOFTWARE/OS VERSIONS Linux/KDE Plasma: Mint 21.1 (available in About System) KDE Frameworks Version: Qt Version: 5.15.3 ADDITIONAL INFORMATION pschonmann@E495:~/temp/digikam$ dpkg -l | grep marble ii libmarble-dev 4:21.12.3-0ubuntu1 amd64development files for the Marble globe widget library ii libmarblewidget-qt5-28:amd64 4:21.12.3-0ubuntu1 amd64Marble globe widget library ii marble 4:21.12.3-0ubuntu1 amd64globe and map widget ii marble-data 4:21.12.3-0ubuntu1 all data files for Marble ii marble-plugins:amd64 4:21.12.3-0ubuntu1 amd64plugins for Marble ii marble-qt 4:21.12.3-0ubuntu1 amd64globe and map widget (no KDE dependencies) ii marble-qt-data 4:21.12.3-0ubuntu1 all Qt-only data files for Marble -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 467348] Cover overlay "Play" and "Add to Playlist" buttons do not work when using the app in a non-English language
https://bugs.kde.org/show_bug.cgi?id=467348 --- Comment #4 from Nate Graham --- Even when running `en_GB elisa`, I can reproduce the bug. What's happening under the hood is that in abstractmediaproxymodel.cpp, the enqueue() signal is emitted but MediaPlayListProxyModel::enqueue is not connected to it, so nothing happens. However when running `en_US elisa`, the connection is made so MediaPlayListProxyModel::enqueue handles the signal and does what it needs to do. I have not yet figured out why the connection isn't getting made when using any locale other than en_US. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 467895] Add The Option To Ignore Raw And JPEG Photos With The Same File Name When Searching For Duplicates In The Similarity Tab
https://bugs.kde.org/show_bug.cgi?id=467895 caulier.gil...@gmail.com changed: What|Removed |Added OS|Unspecified |All Version|unspecified |8.0.0 CC||caulier.gil...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 467897] brush hardness and opacity blending bug
https://bugs.kde.org/show_bug.cgi?id=467897 --- Comment #3 from Jessie --- Created attachment 157673 --> https://bugs.kde.org/attachment.cgi?id=157673&action=edit Better look at the bug -- You are receiving this mail because: You are watching all bug changes.
[kio-gdrive] [Bug 391356] KIO GDrive should provide file transnsfer stats for uploads and downloads
https://bugs.kde.org/show_bug.cgi?id=391356 --- Comment #2 from siloco...@gmail.com --- The issue is when I want to use KDE Online Accounts and I get what looks like the Google login page. The login page should be a separate browser window showing the complete google url that you want to use to connect. Currently it is just a plain popup which means I have no way of trusting it that in fact it is KDE's Online Accounts popup or someone else's man in the middle popup as KDE. Here is the example signup window I am talking about: https://ibb.co/HNkMLFd Normally when I connect accounts using google, Chrome or some other legit browser pops up with the full URL displayed at the top that you can verify the request is going to Google for authentication. Is there possibly another way to connect the KDE Online Account that clearly shows a legitimate browser and it's URL -- You are receiving this mail because: You are watching all bug changes.
[kio-gdrive] [Bug 391356] KIO GDrive should provide file transnsfer stats for uploads and downloads
https://bugs.kde.org/show_bug.cgi?id=391356 siloco...@gmail.com changed: What|Removed |Added CC||siloco...@gmail.com --- Comment #1 from siloco...@gmail.com --- Created attachment 157672 --> https://bugs.kde.org/attachment.cgi?id=157672&action=edit KDE Online Accounts Shows what the popup looks like when to connecting KDE Online Accounts. No way to tell if this popup is legit or man in the middle. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 467897] brush hardness and opacity blending bug
https://bugs.kde.org/show_bug.cgi?id=467897 --- Comment #2 from Jessie --- Created attachment 157671 --> https://bugs.kde.org/attachment.cgi?id=157671&action=edit Video of bug https://youtu.be/2QZobGEOJgo longer version -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 467897] brush hardness and opacity blending bug
https://bugs.kde.org/show_bug.cgi?id=467897 --- Comment #1 from Jessie --- https://youtu.be/2QZobGEOJgo I couldn't attach the video file so I uploaded it to YouTube -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 467215] macOS 11.74 Big Sur: digikam crashes unexpectedly after launching G'MIC (theme settings relevant)
https://bugs.kde.org/show_bug.cgi?id=467215 --- Comment #28 from No_Planet_2 --- I find this very well solved, the second version is more precise. But it's probably beyond the scope of digikam's 'manpages' to go into the peculiarities of G'MIC that only insiders might know about. Pity. _ OT: I'm probably interpreting this in layman's terms, but I see *two* options in G'MIC to load external data updated via the web: 1. via the reload button to the left of the text 'Internet' under the filter column, i.e. the middle column. I guess this is just the basic filter settings as plain text. 2. via the about/download external data menu, where you are warned that large amounts of data (about 85MB:) might be involved. In both cases probably no executable code is updated, otherwise this would not work under a prehistoric G'MIC 2.7.3 with current GIMP 2.10.34. And that also only with a patched mbp 2012 (OpenCore Legacy Patcher) running 11.7.5. but *not* with a Mini 2014 with the same macOS *without* the patch (SIP enabled, SSV disabled) Apple, I hear you trapsen... -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 467897] New: brush hardness and opacity blending bug
https://bugs.kde.org/show_bug.cgi?id=467897 Bug ID: 467897 Summary: brush hardness and opacity blending bug Classification: Applications Product: krita Version: 5.1.5 Platform: Android OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Brush Engine/Bristle Assignee: krita-bugs-n...@kde.org Reporter: youcanthaha...@gmail.com Target Milestone: --- SUMMARY *** When painting using a smudge brush or any brush with the ability to blend, sometimes it will randomly glitch out, creating ransom small pixels or usually on the edges of strokes that when drawn over completely make the brush black , regardless of what colour is used, the brush becomes hard , fully opaque and retains that state fir a little while. STEPS TO REPRODUCE 1. Using Samsung s pen on a Samsung s8 ultra, any brush with blending. Just pain, usually fast until ransom pixels appear or the brush suddenly glitches 2. 3. OBSERVED RESULT as seen in video, I outlined it in red EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION log thingy Krita Version: 5.1.5 Hidpi: true Qt Version (compiled): 5.12.12 Version (loaded): 5.12.12 OS Information Build ABI: arm64-little_endian-lp64 Build CPU: arm64 CPU: arm64 Kernel Type: linux Kernel Version: 5.10.136-android12-9-25884040-abX900XXU3BWB4 Pretty Productname: Android (13.0) Product Type: android Product Version: 13.0 Product Model: Samsung SM-X900 Locale Languages: en_GB, en_Latn_GB C locale: C.UTF-8 QLocale current: en QLocale system: en QTextCodec for locale: UTF-8 OpenGL Info Vendor: "Qualcomm" Renderer: "Adreno (TM) 730" Version: "OpenGL ES 3.2 V@0615.0 (GIT@9f2ab69d70, I3813e70165, 1669012005) (Date:11/20/22)" Shading language: "OpenGL ES GLSL ES 3.20" Requested format: QSurfaceFormat(version 2.0, options QFlags(), depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::DoubleBuffer, swapInterval 0, colorSpace QSurfaceFormat::DefaultColorSpace, profile QSurfaceFormat::NoProfile) Current format: QSurfaceFormat(version 3.2, options QFlags(), depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, stencilBufferSize 8, samples 0, swapBehavior QSurfaceFormat::DefaultSwapBehavior, swapInterval 0, colorSpace QSurfaceFormat::DefaultColorSpace, profile QSurfaceFormat::NoProfile) Version: 3.2 Supports deprecated functions false is OpenGL ES: true supportsBufferMapping: true supportsBufferInvalidation: false forceDisableTextureBuffers: false Extensions: "GL_OES_texture_float" "GL_EXT_fragment_invocation_density" "GL_QCOM_validate_shader_binary" "GL_QCOM_YUV_texture_gather" "GL_OES_depth24" "GL_EXT_tessellation_shader" "GL_OES_depth_texture_cube_map" "GL_EXT_texture_type_2_10_10_10_REV" "GL_KHR_texture_compression_astc_hdr" "GL_OES_shader_multisample_interpolation" "GL_EXT_multisampled_render_to_texture2" "GL_OES_surfaceless_context" "GL_EXT_geometry_shader" "GL_ARM_shader_framebuffer_fetch_depth_stencil" "GL_OES_EGL_image" "GL_KHR_no_error" "GL_ANDROID_extension_pack_es31a" "GL_EXT_blend_func_extended" "GL_OVR_multiview_multisampled_render_to_texture" "GL_OES_texture_3D" "GL_EXT_protected_textures" "GL_EXT_shader_io_blocks" "GL_EXT_EGL_image_external_wrap_modes" "GL_OES_standard_derivatives" "GL_OES_framebuffer_object" "GL_EXT_disjoint_timer_query" "GL_EXT_blit_framebuffer_params" "GL_EXT_color_buffer_float" "GL_QCOM_texture_foveated2" "GL_NV_shader_noperspective_interpolation" "GL_QCOM_texture_foveated" "GL_OES_EGL_image_external_essl3" "GL_QCOM_shader_framebuffer_fetch_rate" "GL_EXT_EGL_image_storage" "GL_OES_rgb8_rgba8" "GL_OES_vertex_half_float" "GL_QCOM_render_shared_exponent" "GL_EXT_texture_filter_anisotropic" "GL_KHR_debug" "GL_EXT_texture_sRGB_decode" "GL_EXT_copy_image" "GL_QCOM_shading_rate" "GL_KHR_texture_compression_astc_ldr" "GL_EXT_primitive_bounding_box" "GL_EXT_external_buffer" "GL_OES_sample_shading" "GL_EXT_texture_buffer" "GL_KHR_robust_buffer_access_behavior" "GL_OES_texture_half_float" "GL_OES_texture_float_linear" "GL_OES_texture_view" "GL_KHR_blend_equation_advanced_coherent" "GL_QCOM_shader_framebuffer_fetch_noncoherent" "GL_OES_texture_stencil8" "GL_EXT_shader_non_constant_global_initializers" "GL_EXT_discard_framebuffer" "
[krita] [Bug 467896] New: brush hardness and opacity blending bug
https://bugs.kde.org/show_bug.cgi?id=467896 Bug ID: 467896 Summary: brush hardness and opacity blending bug Classification: Applications Product: krita Version: 5.1.5 Platform: Android OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Brush Engine/Bristle Assignee: krita-bugs-n...@kde.org Reporter: youcanthaha...@gmail.com Target Milestone: --- SUMMARY *** When painting using a smudge brush or any brush with the ability to blend, sometimes it will randomly glitch out, creating ransom small pixels or usually on the edges of strokes that when drawn over completely make the brush black , regardless of what colour is used, the brush becomes hard , fully opaque and retains that state fir a little while. STEPS TO REPRODUCE 1. Using Samsung s pen on a Samsung s8 ultra, any brush with blending. Just pain, usually fast until ransom pixels appear or the brush suddenly glitches 2. 3. OBSERVED RESULT as seen in video, I outlined it in red EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION log thingy Krita Version: 5.1.5 Hidpi: true Qt Version (compiled): 5.12.12 Version (loaded): 5.12.12 OS Information Build ABI: arm64-little_endian-lp64 Build CPU: arm64 CPU: arm64 Kernel Type: linux Kernel Version: 5.10.136-android12-9-25884040-abX900XXU3BWB4 Pretty Productname: Android (13.0) Product Type: android Product Version: 13.0 Product Model: Samsung SM-X900 Locale Languages: en_GB, en_Latn_GB C locale: C.UTF-8 QLocale current: en QLocale system: en QTextCodec for locale: UTF-8 OpenGL Info Vendor: "Qualcomm" Renderer: "Adreno (TM) 730" Version: "OpenGL ES 3.2 V@0615.0 (GIT@9f2ab69d70, I3813e70165, 1669012005) (Date:11/20/22)" Shading language: "OpenGL ES GLSL ES 3.20" Requested format: QSurfaceFormat(version 2.0, options QFlags(), depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::DoubleBuffer, swapInterval 0, colorSpace QSurfaceFormat::DefaultColorSpace, profile QSurfaceFormat::NoProfile) Current format: QSurfaceFormat(version 3.2, options QFlags(), depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, stencilBufferSize 8, samples 0, swapBehavior QSurfaceFormat::DefaultSwapBehavior, swapInterval 0, colorSpace QSurfaceFormat::DefaultColorSpace, profile QSurfaceFormat::NoProfile) Version: 3.2 Supports deprecated functions false is OpenGL ES: true supportsBufferMapping: true supportsBufferInvalidation: false forceDisableTextureBuffers: false Extensions: "GL_OES_texture_float" "GL_EXT_fragment_invocation_density" "GL_QCOM_validate_shader_binary" "GL_QCOM_YUV_texture_gather" "GL_OES_depth24" "GL_EXT_tessellation_shader" "GL_OES_depth_texture_cube_map" "GL_EXT_texture_type_2_10_10_10_REV" "GL_KHR_texture_compression_astc_hdr" "GL_OES_shader_multisample_interpolation" "GL_EXT_multisampled_render_to_texture2" "GL_OES_surfaceless_context" "GL_EXT_geometry_shader" "GL_ARM_shader_framebuffer_fetch_depth_stencil" "GL_OES_EGL_image" "GL_KHR_no_error" "GL_ANDROID_extension_pack_es31a" "GL_EXT_blend_func_extended" "GL_OVR_multiview_multisampled_render_to_texture" "GL_OES_texture_3D" "GL_EXT_protected_textures" "GL_EXT_shader_io_blocks" "GL_EXT_EGL_image_external_wrap_modes" "GL_OES_standard_derivatives" "GL_OES_framebuffer_object" "GL_EXT_disjoint_timer_query" "GL_EXT_blit_framebuffer_params" "GL_EXT_color_buffer_float" "GL_QCOM_texture_foveated2" "GL_NV_shader_noperspective_interpolation" "GL_QCOM_texture_foveated" "GL_OES_EGL_image_external_essl3" "GL_QCOM_shader_framebuffer_fetch_rate" "GL_EXT_EGL_image_storage" "GL_OES_rgb8_rgba8" "GL_OES_vertex_half_float" "GL_QCOM_render_shared_exponent" "GL_EXT_texture_filter_anisotropic" "GL_KHR_debug" "GL_EXT_texture_sRGB_decode" "GL_EXT_copy_image" "GL_QCOM_shading_rate" "GL_KHR_texture_compression_astc_ldr" "GL_EXT_primitive_bounding_box" "GL_EXT_external_buffer" "GL_OES_sample_shading" "GL_EXT_texture_buffer" "GL_KHR_robust_buffer_access_behavior" "GL_OES_texture_half_float" "GL_OES_texture_float_linear" "GL_OES_texture_view" "GL_KHR_blend_equation_advanced_coherent" "GL_QCOM_shader_framebuffer_fetch_noncoherent" "GL_OES_texture_stencil8" "GL_EXT_shader_non_constant_global_initializers" "GL_EXT_discard_framebuffer" "
[Spectacle] [Bug 467890] On Wayland, when taking a no-delay rectangular region or full screen screenshot from the main window, a ghost of the main window can appear in the screenshot when using a slow
https://bugs.kde.org/show_bug.cgi?id=467890 Patrick Silva changed: What|Removed |Added CC||bugsefor...@gmx.com -- You are receiving this mail because: You are watching all bug changes.
[KBibTeX] [Bug 467803] User preferences are no longer saved
https://bugs.kde.org/show_bug.cgi?id=467803 --- Comment #6 from Thomas Fischer --- (In reply to Kishore Gopalakrishnan from comment #5) > I can still reproduce the bug after uninstalling kbibtex and building it > using the command you mentioned. You can test if you are actually running the bugfix version if you go to the Babel language combobox. Before, there was just English, Swedish, and German. Now there is a much longer list (taken from Babel's docs). Which list do you have? Then, maybe I fixed a different bug. Can you please specify exactly for which setting you can reproduce the bug? In case of doubt, add a screenshot (in English, please). Then, start KBibTeX from the command line and submit anything printed to this bug report. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 467283] [Wayland][Intel][HiDPI] Laggy maximize animation with custom Aurorae theme
https://bugs.kde.org/show_bug.cgi?id=467283 --- Comment #1 from farlin...@yandex.ru --- ?) -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 465551] E-Mail signed with gnupg subkey not properly shown as valid when opened in composer/preview pane
https://bugs.kde.org/show_bug.cgi?id=465551 mail2h...@gmail.com changed: What|Removed |Added CC||mail2h...@gmail.com --- Comment #3 from mail2h...@gmail.com --- I'm so glad to find this bug because at first I thought I messed up my whole encryption system. But now I'm calmed;) I'm on openSUSE Tumbleweed with KMail Version 5.22.3 (22.12.3) on KDE. Firstly I thought it has to do with my hardware key I copied the key to but. But it seems to be a subkey problem. When I click on the key in KMail I get redirected to the correct certificate in Kleopatra, but the border still stays yellow. I also signed the vice versa and put it on good trust. Nothing helped. In older versions, it seems to work (openSUSE Leap 15.4). Greetings fhihu -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 424306] Add reverse DNS name symlinks for app icons to support theming Flatpak app icons
https://bugs.kde.org/show_bug.cgi?id=424306 Nate Graham changed: What|Removed |Added Version Fixed In||5.105 Status|ASSIGNED|RESOLVED Resolution|--- |FIXED Latest Commit||https://invent.kde.org/fram ||eworks/breeze-icons/commit/ ||f6a1617865eb7d47f8556184339 ||88a972a8cfdc4 --- Comment #6 from Nate Graham --- Git commit f6a1617865eb7d47f855618433988a972a8cfdc4 by Nate Graham, on behalf of Alois Wohlschlager. Committed on 28/03/2023 at 20:02. Pushed by ngraham into branch 'master'. Create symlinks for reverse DNS app identifiers When apps are installed using flatpak, the relevant icon is looked up under its reverse DNS app identifier, and not under its plain name. Create appropriate symlinks, so that flatpak-installed apps get their proper icons. FIXED-IN: 5.105 A +151 -0create-app-symlinks.py M +3-0icons-dark/CMakeLists.txt M +10 -0icons/CMakeLists.txt D +0-1icons/apps/48/com.github.ztefn.haguichi.svg D +0-1icons/apps/48/io.gitlab.Goodvibes.svg D +0-1icons/apps/48/org.inkscape.Inkscape.svg D +0-1icons/apps/48/org.kde.skanlite.svg D +0-1icons/apps/48/org.telegram.desktop.svg https://invent.kde.org/frameworks/breeze-icons/commit/f6a1617865eb7d47f855618433988a972a8cfdc4 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 464592] Scrolling speed setting has no effect since Plasma 5.27 beta
https://bugs.kde.org/show_bug.cgi?id=464592 Bug Janitor Service changed: What|Removed |Added Status|CONFIRMED |ASSIGNED --- Comment #13 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/plasma/kwin/-/merge_requests/3900 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 467895] New: Add The Option To Ignore Raw And JPEG Photos With The Same File Name When Searching For Duplicates In The Similarity Tab
https://bugs.kde.org/show_bug.cgi?id=467895 Bug ID: 467895 Summary: Add The Option To Ignore Raw And JPEG Photos With The Same File Name When Searching For Duplicates In The Similarity Tab Classification: Applications Product: digikam Version: unspecified Platform: unspecified OS: Unspecified Status: REPORTED Severity: wishlist Priority: NOR Component: Maintenance-Similarities Assignee: digikam-bugs-n...@kde.org Reporter: michael2macdon...@gmail.com Target Milestone: --- SUMMARY When searching for duplicates, it often finds JPEG and RAW images from my camera and lists them as duplicates. This is not desirable for obvious reasons, and it clutters the search results making it hard to find actual duplicate images. Adding the option to ignore RAW and JPEG/PNG/TIFF photos with the same file name when searching for duplicates in the similarity tab would fix this issue and make finding actual duplicates easier. STEPS TO REPRODUCE 1. Import both RAW and JPEG (or any two image types) versions of your photos into Digikam 2. Select your desired album(s) containing these photos in the similarity/duplicates tab 3. Update image fingerprints and scan for duplicates OBSERVED RESULT The RAW and JPEG versions of the same image are marked as duplicates EXPECTED RESULT Images with the same name but of a different file type should not show up as duplicates unless the user selects/deselects an option to show duplicates with differing file types. SOFTWARE/OS VERSIONS N/A ADDITIONAL INFORMATION This is a feature request and it applies to all versions of the software and all platforms to my knowledge. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 467828] File dialogs: awkward keyboard interaction
https://bugs.kde.org/show_bug.cgi?id=467828 Frann changed: What|Removed |Added Status|RESOLVED|CLOSED --- Comment #2 from Frann --- Oh, OK, thanks. I guess this is Qt then - the appimage version of Krita doesn't allow for native file dialogs (hence me posting here, thinking they were krita-specific). -- You are receiving this mail because: You are watching all bug changes.
