[kwin] [Bug 424311] Severe Rendering Issues on Latest Nvidia Driver (450.57) (Arch)
https://bugs.kde.org/show_bug.cgi?id=424311 --- Comment #58 from samping...@gmail.com --- (In reply to br1ghtch1p from comment #57) > However I still get the notification on resume that desktop effects are > restarted and I just wonder if this is now a normal message to expect on > resume from suspend. For now I have muted out this notification. Yeah I get that too every time I resume my computer from suspend. Is this normal behavior? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 427440] Unity Editor fails to recognise mouse scrolling events
https://bugs.kde.org/show_bug.cgi?id=427440 --- Comment #6 from Vlad Zahorodnii --- > Still happens. Did you run openbox --replace before starting unity? -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 427405] Amarok Crash on Login
https://bugs.kde.org/show_bug.cgi?id=427405 Myriam Schweingruber changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |BACKTRACE --- Comment #1 from Myriam Schweingruber --- Was this a one-time crash or is it reproducible? FWIW: you do not have debugging symbols installed, so the backtrace is not really helpful. If you can reproduce this crash, please install the debugging symbols for Amarok and its dependencies and provide a better backtrace. See also https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 427446] amarok freezes
https://bugs.kde.org/show_bug.cgi?id=427446 Myriam Schweingruber changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #1 from Myriam Schweingruber --- Unfortunately you do not have debugging symbols installed for Amarok, so the backtrace is not really useful. If this crash is reproducible, please install the debugging symbols and provide a better backtrace. Please post it inline, not as an attachment. See also https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 426293] All my Qt clients die when I disconnect my display
https://bugs.kde.org/show_bug.cgi?id=426293 Lewis Lakerink changed: What|Removed |Added CC||le...@retsim.com --- Comment #5 from Lewis Lakerink --- I came here to say that this issue hits me too. I searched up this issue recently, but somehow missed this report or I'd have gotten involved sooner. Docking my laptop works as expected, extra screens are added just fine. But as soon as I undock, all the Qt applications crash. The debugging I did arrived at the same conclusion as Vlad, but I don't have enough knowledge of wayland to help with this bug. I'm using Gentoo live ebuilds for plasma, so I have not reported this issue due to this. Happy to help in any way I can however. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 427473] Curser jumps to the inputs end while typing
https://bugs.kde.org/show_bug.cgi?id=427473 carcinoma changed: What|Removed |Added Platform|Other |Kubuntu Packages -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 427473] New: Curser jumps to the inputs end while typing
https://bugs.kde.org/show_bug.cgi?id=427473 Bug ID: 427473 Summary: Curser jumps to the inputs end while typing Product: dolphin Version: 19.12.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: search Assignee: dolphin-bugs-n...@kde.org Reporter: carcin...@gmx.net CC: kfm-de...@kde.org Target Milestone: --- SUMMARY While typing in the search bar (e.g. changing alread entered sreach string somewhere in the middle) the curser is jumping to the end of the input field. That way user will endup with a mixed up/garbled search string. STEPS TO REPRODUCE 1. Enter a search string into search input 2. Move curser to the middle of the search string 3. start typing OBSERVED RESULT The curser is moved after little time to the end of the string while typing EXPECTED RESULT Cursor stays at the position the user was placing it (while typing the cursor of course will move because of newly added letters). SOFTWARE/OS VERSIONS Windows: - macOS: - Linux/KDE Plasma: Kubuntu 20.04.1 (available in About System) KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.68.0 Qt Version: 5.12.8 ADDITIONAL INFORMATION - -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 426698] Okular crashes starting with 2 differently orientated screens
https://bugs.kde.org/show_bug.cgi?id=426698 --- Comment #11 from David --- Well if it's something to raise against QT they probably want more than try it out on okular and you'll see, which is why it's come to okular first to find out what it's doing. Ideally some kind of simple reproduction that is simulating whatever okular is doing. Possible it's the cause of a number of other bugs I'm going to raise against kwin for daft window placement in this setup, particularly when pulling and replacing the cable. I'm guessing the QT folks are missing some test cases around non-rectangular desktop arrangements. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 427474] New: Export annotation/comments
https://bugs.kde.org/show_bug.cgi?id=427474 Bug ID: 427474 Summary: Export annotation/comments Product: okular Version: unspecified Platform: unspecified OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: PDF backend Assignee: okular-de...@kde.org Reporter: thetawfeqfa...@gmail.com Target Milestone: --- As an advocate for FOSS, I would love for this feature to be implemented into Okular. But so far, I haven't found any open source software with the ability to export annotations/comments. Perhaps it's because people rarely use it, but I myself find this feature to be really useful and essential to what I do. Thus, I'm stuck with using Adobe Reader, and I hate Adobe, just to show my desperation. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 427475] New: Export annotation/comments
https://bugs.kde.org/show_bug.cgi?id=427475 Bug ID: 427475 Summary: Export annotation/comments Product: okular Version: unspecified Platform: unspecified OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: PDF backend Assignee: okular-de...@kde.org Reporter: thetawfeqfa...@gmail.com Target Milestone: --- As an advocate for FOSS, I would love for this feature to be implemented into Okular. But so far, I haven't found any open source software with the ability to export annotations/comments. Perhaps it's because people rarely use it, but I myself find this feature to be really useful and essential to what I do. Thus, I'm stuck with using Adobe Reader, and I hate Adobe, just to show my desperation. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 427476] New: When the top layer is set to invisible (eye closed), you can't create a "new layer from visible"
https://bugs.kde.org/show_bug.cgi?id=427476 Bug ID: 427476 Summary: When the top layer is set to invisible (eye closed), you can't create a "new layer from visible" Product: krita Version: nightly build (please specify the git hash!) Platform: Other OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: Layer Stack Assignee: krita-bugs-n...@kde.org Reporter: rg0...@netcourrier.com Target Milestone: --- git c0166ba, 7de2b88 and preceding SUMMARY When the top layer is set to invisible (eye closed), you can't create a "new layer from visible" STEPS TO REPRODUCE 1. Create an image with several layers 2. Set the top layer to invisible 3. Click "Layer", "New", "New layer from visible" OR right click on the layers and choose "New layer from visible" OBSERVED RESULT Nothing happens EXPECTED RESULT A new layer should be created corresponding to what you saw when you clicked "New layer from visible" SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 427476] When the top layer is set to invisible (eye closed), you can't create a "new layer from visible"
https://bugs.kde.org/show_bug.cgi?id=427476 Boudewijn Rempt changed: What|Removed |Added Ever confirmed|0 |1 CC||b...@valdyas.org Status|REPORTED|CONFIRMED --- Comment #1 from Boudewijn Rempt --- This also shows a safe assert (when enabled): SAFE ASSERT (krita): "putAfter->parent()" in file /home/boud/dev/4.3/libs/image/kis_layer_utils.cpp, line 1376 Full backtrace: [KCrash Handler] #4 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 #5 0x7f7d929cd859 in __GI_abort () at abort.c:79 #6 0x7f7d92e28c39 in QMessageLogger::fatal(char const*, ...) const () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f7d9412d32e in kis_assert_common (assertion=, file=, line=1376, throwException=, isIgnorable=) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qarraydata.h:61 #8 0x7f7d94131585 in kis_safe_assert_recoverable (assertion=assertion@entry=0x7f7d948e3922 "putAfter->parent()", file=file@entry=0x7f7d948e3808 "/home/boud/dev/4.3/libs/image/kis_layer_utils.cpp", line=line@entry=1376) at /home/boud/dev/4.3/libs/global/kis_assert.cpp:117 #9 0x7f7d94724ed8 in KisLayerUtils::mergeMultipleLayersImpl (image=..., mergedNodes=..., putAfter=..., flattenSingleLayer=, actionName=..., cleanupNodes=, layerName=...) at /home/boud/dev/4.3/libs/global/kis_shared_ptr.h:223 #10 0x7f7d9472598e in KisLayerUtils::newLayerFromVisible (image=..., putAfter=...) at /usr/include/c++/9/bits/atomic_base.h:318 #11 0x7f7d957b3ee9 in KisNodeManager::createFromVisible (this=0x562b3f153778) at /home/boud/dev/4.3/libs/global/kis_shared_ptr.h:175 #12 0x7f7d955dbbaa in KisNodeManager::qt_static_metacall (_o=0x562b3f153778, _c=, _id=, _a=0x7fff0619e3a0) at /home/boud/dev/b-4.3/libs/ui/kritaui_autogen/EWIEGA46WW/moc_kis_node_manager.cpp:328 #13 0x7f7d9307d5e0 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #14 0x7f7d93b797f6 in QAction::triggered(bool) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #15 0x7f7d93b7bec8 in QAction::activate(QAction::ActionEvent) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #16 0x7f7d93d06712 in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #17 0x7f7d93d0ddbe in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #18 0x7f7d93d0f052 in QMenu::mouseReleaseEvent(QMouseEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #19 0x7f7d93bc2db6 in QWidget::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #20 0x7f7d93d1165b in QMenu::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #21 0x7f7d93b7fcc3 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #22 0x7f7d93b88ec3 in QApplication::notify(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #23 0x7f7d95abd5ad in KisApplication::notify (this=, receiver=0x562b419a1850, event=0x7fff0619eb00) at /home/boud/dev/4.3/libs/ui/KisApplication.cpp:688 #24 0x7f7d930466aa in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #25 0x7f7d93b87fd7 in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool, bool) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #26 0x7f7d93bdea86 in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #27 0x7f7d93be14dc in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #28 0x7f7d93b7fcc3 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #29 0x7f7d93b88c70 in QApplication::notify(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #30 0x7f7d95abd5ad in KisApplication::notify (this=, receiver=0x562b40fc0580, event=0x7fff0619f000) at /home/boud/dev/4.3/libs/ui/KisApplication.cpp:688 #31 0x7f7d930466aa in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #32 0x7f7d93475f78 in QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) () from /lib/x86_64-linux-gnu/libQt5Gui.so.5 #33 0x7f7d934775b5 in QGuiApplicationPrivate::processWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*) () from /lib/x86_64-linux-gnu/libQt5Gui.so.5 #34 0x7f7d9344f2cb in QWindowSystemInterface::sendWindowSystemEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Gui.so.5 #35 0x7f7d8d5aa99e in ?? () from /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #36 0x7f7d903a5fbd in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #37 0x7f7d903a6240 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #38 0x7f7d903a62e3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #39 0x7f7d930a0e92 in QEventDispatcher
[kdenlive] [Bug 427136] Processing turns the video into a mess
https://bugs.kde.org/show_bug.cgi?id=427136 --- Comment #14 from Jean-Baptiste Mardelle --- @emohr: I can open the project file without crash on linux. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 427440] Unity Editor fails to recognise mouse scrolling events
https://bugs.kde.org/show_bug.cgi?id=427440 --- Comment #7 from David --- (In reply to Vlad Zahorodnii from comment #6) > > Still happens. > Did you run openbox --replace before starting unity? I've just tried, same result. I'm adding another bit of the puzzle here. I've noticed two more things: 1) After a while using the application, it starts loosing responsiveness even to L/R clicks, in every area of the window except the main menu. Have to repeat the click 5-10 times before it's taken. 2)the main menu looks like the app isn't focused. text is gray on white as opposed to the black on white of any other GTK2/3 app on my system. We're dealing with a hell of a problem here. I'm here for any other test you can think of guys, in the meantime thank you. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 424311] Severe Rendering Issues on Latest Nvidia Driver (450.57) (Arch)
https://bugs.kde.org/show_bug.cgi?id=424311 --- Comment #59 from br1ghtc...@gmail.com --- (In reply to sampingu02 from comment #58) > (In reply to br1ghtch1p from comment #57) > > > However I still get the notification on resume that desktop effects are > > restarted and I just wonder if this is now a normal message to expect on > > resume from suspend. For now I have muted out this notification. > > Yeah I get that too every time I resume my computer from suspend. Is this > normal behavior? That's exactly my same question. I don't think the 440 driver had this issue but my intuition tells me this is probably the new normal for the current fix. At least now kwin doesn't crash on resume. -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 427446] amarok freezes
https://bugs.kde.org/show_bug.cgi?id=427446 --- Comment #2 from Germano Massullo --- (In reply to Myriam Schweingruber from comment #1) > Unfortunately you do not have debugging symbols installed for Amarok, so the > backtrace is not really useful. If this crash is reproducible, please > install the debugging symbols and provide a better backtrace. Yes you are right, I have missed some debuginfo because if this weird GDB behaviour in Fedora https://bugzilla.redhat.com/show_bug.cgi?id=1571898 > Please post it inline, not as an attachment. No, it exceeds the maximum chars limit in a message. I think we better close this ticket, I will reopen a new one in case I will get better debuginfos -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 424311] Severe Rendering Issues on Latest Nvidia Driver (450.57) (Arch)
https://bugs.kde.org/show_bug.cgi?id=424311 --- Comment #60 from Fonic --- (In reply to br1ghtch1p from comment #59) > (In reply to sampingu02 from comment #58) > > (In reply to br1ghtch1p from comment #57) > > > > > However I still get the notification on resume that desktop effects are > > > restarted and I just wonder if this is now a normal message to expect on > > > resume from suspend. For now I have muted out this notification. > > > > Yeah I get that too every time I resume my computer from suspend. Is this > > normal behavior? > > That's exactly my same question. I don't think the 440 driver had this issue > but my intuition tells me this is probably the new normal for the current > fix. At least now kwin doesn't crash on resume. I have this with the 440.100 driver and remember having had this for at least a year or so (i.e. with previous versions also). Haven't tried 455.28 yet. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 427474] Export annotation/comments
https://bugs.kde.org/show_bug.cgi?id=427474 Christoph Feck changed: What|Removed |Added Severity|normal |wishlist -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 427475] Export annotation/comments
https://bugs.kde.org/show_bug.cgi?id=427475 Christoph Feck changed: What|Removed |Added Resolution|--- |MOVED Status|REPORTED|RESOLVED --- Comment #1 from Christoph Feck --- Already reported as bug 427474. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 427333] Face detection crashes due to pure virtual method call in LoadingCache
https://bugs.kde.org/show_bug.cgi?id=427333 --- Comment #20 from Simon Westersund --- Created attachment 132231 --> https://bugs.kde.org/attachment.cgi?id=132231&action=edit GDB backtrace with latest master 182bef3be8 Here is a backtrace from the latest testing. The face detection crashed after around 8% completion. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 424311] Severe Rendering Issues on Latest Nvidia Driver (450.57) (Arch)
https://bugs.kde.org/show_bug.cgi?id=424311 --- Comment #61 from br1ghtc...@gmail.com --- (In reply to Fonic from comment #60) > (In reply to br1ghtch1p from comment #59) > > (In reply to sampingu02 from comment #58) > > > (In reply to br1ghtch1p from comment #57) > > > > > > > However I still get the notification on resume that desktop effects are > > > > restarted and I just wonder if this is now a normal message to expect on > > > > resume from suspend. For now I have muted out this notification. > > > > > > Yeah I get that too every time I resume my computer from suspend. Is this > > > normal behavior? > > > > That's exactly my same question. I don't think the 440 driver had this issue > > but my intuition tells me this is probably the new normal for the current > > fix. At least now kwin doesn't crash on resume. > > I have this with the 440.100 driver and remember having had this for at > least a year or so (i.e. with previous versions also). Haven't tried 455.28 > yet. I probably just didn't notice it with the 440 driver or my notification for such things were disabled. Anyway thanks to the Devs for taking time to provide a fix. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 426698] Okular crashes starting with 2 differently orientated screens
https://bugs.kde.org/show_bug.cgi?id=426698 --- Comment #12 from David Hurka --- Maybe we could try to automatically uncheck (once) “Smooth Scrolling” when multiple screens are connected, and then work around QScroller::scrollTo()? A simple test case will not be easy, because no one of us seems to be able to reproduce the bug. If someone tries to write a simple test case, would you be able to test it, David? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 427477] New: /mnt directory not visible in Linux file system / Collection cannot be added from removable media
https://bugs.kde.org/show_bug.cgi?id=427477 Bug ID: 427477 Summary: /mnt directory not visible in Linux file system / Collection cannot be added from removable media Product: digikam Version: 7.1.0 Platform: Debian stable OS: ChromeOS Status: REPORTED Severity: normal Priority: NOR Component: Setup-Collections Assignee: digikam-bugs-n...@kde.org Reporter: frbrig...@gmail.com Target Milestone: --- SUMMARY I have installed digiKam 7.1.0 from Flatpak as a Linux App on my Lenovo Flex 5 Chromebook. The installation appears to have been successful. I wish to add a Collection from an sd card and note that "removable media are supported". The sd card has been "Shared with Linux" and is visible in the /mnt directory via the Terminal. I can see /mnt and link to the sd card in other Linux apps, e.g. Handbrake. However, the mnt directory does not appear in the Linux file system in digiKam when selecting a Collection. STEPS TO REPRODUCE 1. Share sd card with Linux in Chrome OS. 2. Open digiKam and go to Collections Settings. 3. Click on Add Collection and navigate to the top level directories. OBSERVED RESULT The top level directories are visible but not /mnt. EXPECTED RESULT /mnt should be visible allowing the sd card to be shared. Note: The expected result is obtained with other Linux apps such as Handbrake which are installed on the Chromebook and there is no problem reading from or writing to the sd card. SOFTWARE/OS VERSIONS Chrome OS: version 85 Linux: Debian GNU/Linux 10 (Buster) ADDITIONAL INFORMATION The Chrome OS platform with Android apps plus Linux is becoming increasingly popular. In the future I see great opportunity for widespread use of digiKam on Chromebooks. It would therefore be good to provide a fix for this issue. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 426704] Properties dialog shows wrong free space for unlimited Trash
https://bugs.kde.org/show_bug.cgi?id=426704 Bug Janitor Service changed: What|Removed |Added Status|CONFIRMED |ASSIGNED --- Comment #1 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/frameworks/kio/-/merge_requests/156 -- You are receiving this mail because: You are watching all bug changes.
[Smb4k] [Bug 427478] New: New bookmarks discard workgroup
https://bugs.kde.org/show_bug.cgi?id=427478 Bug ID: 427478 Summary: New bookmarks discard workgroup Product: Smb4k Version: unspecified Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: alexander.reinho...@kdemail.net Reporter: priv...@bernhard-lindner.de Target Milestone: --- When adding a bookmark in smb4k 3.0.4 including a workgroup name, I can not see the same work group when visiting the new bookmark in the boomark editing window. Instead the workgroup is empty there. When setting the workgroup again in the editing window, it seems to be accepted properly. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 427463] Imposible to insert annotations to pdf files
https://bugs.kde.org/show_bug.cgi?id=427463 --- Comment #2 from hafid --- Created attachment 132232 --> https://bugs.kde.org/attachment.cgi?id=132232&action=edit a clip showing the bug -- You are receiving this mail because: You are watching all bug changes.
[Smb4k] [Bug 427479] New: No shares visible in user defined settings
https://bugs.kde.org/show_bug.cgi?id=427479 Bug ID: 427479 Summary: No shares visible in user defined settings Product: Smb4k Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: alexander.reinho...@kdemail.net Reporter: priv...@bernhard-lindner.de Target Milestone: --- In smb3k 3.0.4 there are no shares listed in user defined setting, no matter what I do. In a different version (the one used in repositories of outdated KDE Neon 18.04) smb4k used to show shares there and I was able to modify them as intended. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 421926] Konsole new tabs do not respect --profile argument
https://bugs.kde.org/show_bug.cgi?id=421926 Oswald Buddenhagen changed: What|Removed |Added CC||o...@kde.org Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #1 from Oswald Buddenhagen --- when you open a new tab via the menu, you get to select the profile interactively, so that's obviously not the issue here. the issue manifests when the "new tab" action is activated via a key binding, as it does indeed always use the default profile. one way to deal with that would be indeed respecting the --profile option as you suggest. another way would be using the profile of the current tab. there is a precedent for this in form of the profile option to use the current tab's working directory. a third option would be a combination of the two: use --profile if specified, otherwise fall back to current profile. though this would make the behavior somewhat inconsistent, so it might be a tad confusing. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 427480] New: Baloo crashes on Plasma startup and fills system journal with core dump
https://bugs.kde.org/show_bug.cgi?id=427480 Bug ID: 427480 Summary: Baloo crashes on Plasma startup and fills system journal with core dump Product: frameworks-baloo Version: 5.74.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: Baloo File Daemon Assignee: stefan.bru...@rwth-aachen.de Reporter: kdereport.fireha...@slmail.me Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Start Plasma 2. Open journal 3. Observe endless errors OBSERVED RESULT I put some of them in this pastebin, there are a lot more, I believe all similar https://cryptpad.fr/pad/#/2/pad/view/zjHYBS0-PFBZ0KnsRfkvRFUpAu0blFrBULKee5eqipU/ EXPECTED RESULT No errors SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux with Plasma Wayland 5.19.5 KDE Plasma Version: 5.19.5 KDE Frameworks Version: 5.74 Qt Version: qt5 5.15.1 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 427450] -Rendering failure, no matter what-
https://bugs.kde.org/show_bug.cgi?id=427450 --- Comment #1 from Jean-Baptiste Mardelle --- Oh, if I remember correctly on Redhat and derivatives, the "melt" executable was renamed to "mlt-melt" instead of "mlt" on all other distros because of a name conflict. Can you check in Kdenlive Settings, under "Environment", what path is defined in Melt path ? -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 427459] Flathub repo not added by default
https://bugs.kde.org/show_bug.cgi?id=427459 Harald Sitter changed: What|Removed |Added Status|REPORTED|RESOLVED Latest Commit||https://invent.kde.org/neon ||/neon/settings/commit/6a986 ||6159150372b3c1db21a69338e30 ||7c265c21 Resolution|--- |FIXED --- Comment #1 from Harald Sitter --- Git commit 6a9866159150372b3c1db21a69338e307c265c21 by Harald Sitter. Committed on 09/10/2020 at 09:47. Pushed by sitter into branch 'Neon/release-lts'. rejigger flathub setup to anchor on sddm this appears to have broken in 20.04 bc of changes to the critical service chain. instead start the setup along with sddm and handle that the network is conceivably not up. since we have no control over which network manager the user uses we'll assume it's nm but then proceed to try anyway in case it is not. this is a bit unfortunate as sddm is actually a bad service to start with but there's not really any better options on a system level as far as I can tell M +2-3debian/neon-settings-2.neon-flathub.service M +13 -5usr/lib/neon_update/neon_flathub.rb https://invent.kde.org/neon/neon/settings/commit/6a9866159150372b3c1db21a69338e307c265c21 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 427442] Error in render preview
https://bugs.kde.org/show_bug.cgi?id=427442 Jean-Baptiste Mardelle changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #1 from Jean-Baptiste Mardelle --- Can you please give more details ? What do you mean in step 1, changing video track on timeline ? Are you moving a clip to another track? Or disabling the track ? Sometimes a screenshot can help. Please give as much details as possible on each step so that we can understand and reproduce the problem. Thanks -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 427429] Unable to drag a clip region to the timeline using AppImage 20.08.1
https://bugs.kde.org/show_bug.cgi?id=427429 Jean-Baptiste Mardelle changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #1 from Jean-Baptiste Mardelle --- Well it works for me. Does it happen with all clips, or only some ? That could maybe help if you could upload screencast of the problem... -- You are receiving this mail because: You are watching all bug changes.
[kpat] [Bug 405376] Simple Simon no longer autodrops
https://bugs.kde.org/show_bug.cgi?id=405376 cl.eme...@giroll.org changed: What|Removed |Added CC||cl.eme...@giroll.org -- You are receiving this mail because: You are watching all bug changes.
[kpat] [Bug 408582] On the "simple simon" will not push cards up when solving a suit. I have to push "Demo" to push that suit up.
https://bugs.kde.org/show_bug.cgi?id=408582 cl.eme...@giroll.org changed: What|Removed |Added CC||cl.eme...@giroll.org -- You are receiving this mail because: You are watching all bug changes.
[kpat] [Bug 405376] Simple Simon no longer autodrops
https://bugs.kde.org/show_bug.cgi?id=405376 --- Comment #1 from cl.eme...@giroll.org --- Hello, I have the same problem in Xubuntu 20.04.1 Kpat version 19.12.3 (not snap) linux 5.4.0-48-generic X86 64 When I clic on "demonstration" it works -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 425036] Change done in Users kcm is applied despite the password dialog is canceled
https://bugs.kde.org/show_bug.cgi?id=425036 Patrick Silva changed: What|Removed |Added Resolution|FIXED |--- Status|RESOLVED|REOPENED --- Comment #6 from Patrick Silva --- it's still reproducible on neon unstable. Operating System: KDE neon Unstable Edition KDE Plasma Version: 5.20.80 KDE Frameworks Version: 5.75.0 Qt Version: 5.15.0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 427477] /mnt directory not visible in Linux file system / Collection cannot be added from removable media
https://bugs.kde.org/show_bug.cgi?id=427477 Maik Qualmann changed: What|Removed |Added CC||metzping...@gmail.com --- Comment #1 from Maik Qualmann --- Switch to the native file dialogs in the digiKam settings. Is digiKam from AppImage or native Debian packages? Otherwise we already know the problem of broken file dialogs under Debian / Red Hat, this is a package error, the set file filter is not processed correctly. Maik -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 427477] /mnt directory not visible in Linux file system / Collection cannot be added from removable media
https://bugs.kde.org/show_bug.cgi?id=427477 --- Comment #2 from Maik Qualmann --- see you write Flatpak... Maik -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 422948] Startup sound does not play; system muted until after login
https://bugs.kde.org/show_bug.cgi?id=422948 --- Comment #55 from kyrawer...@gmail.com --- Workaround from #49 no longer works in Plasma 5.19.5, sound is now again always muted on startup. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 425138] Unable to add local collection
https://bugs.kde.org/show_bug.cgi?id=425138 Maik Qualmann changed: What|Removed |Added CC||frbrig...@gmail.com --- Comment #8 from Maik Qualmann --- *** Bug 427477 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 427477] /mnt directory not visible in Linux file system / Collection cannot be added from removable media
https://bugs.kde.org/show_bug.cgi?id=427477 Maik Qualmann changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #3 from Maik Qualmann --- *** This bug has been marked as a duplicate of bug 425138 *** -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 383413] Discover crashes in Transaction::isActive() during or after updating
https://bugs.kde.org/show_bug.cgi?id=383413 --- Comment #37 from Fikri Ms --- Created attachment 132233 --> https://bugs.kde.org/attachment.cgi?id=132233&action=edit New crash information added by DrKonqi plasma-discover (5.19.5) using Qt 5.15.1 - What I was doing when the application crashed: After the fetching done, discover was crashed - Custom settings of the application: I don't know -- Backtrace (Reduced): #4 0x7f52d5880246 in QQmlData::wasDeleted(QObject const*) (object=0x5650806672c0) at /usr/src/debug/libqt5-qtdeclarative-5.15.1-2.1.x86_64/include/QtQml/5.15.1/QtQml/private/../../../../../src/qml/qml/qqmldata_p.h:338 #5 QV4::QObjectWrapper::wrap(QV4::ExecutionEngine*, QObject*) (object=0x5650806672c0, engine=0x56507ee0f4f0) at /usr/src/debug/libqt5-qtdeclarative-5.15.1-2.1.x86_64/src/qml/jsruntime/qv4qobjectwrapper_p.h:213 #6 loadProperty(QV4::ExecutionEngine*, QObject*, QQmlPropertyData const&) (v4=0x56507ee0f4f0, object=0x5650807ddfe0, property=...) at /usr/src/debug/libqt5-qtdeclarative-5.15.1-2.1.x86_64/src/qml/jsruntime/qv4qobjectwrapper.cpp:139 #7 0x7f52d5881732 in QV4::QObjectWrapper::getQmlProperty(QV4::ExecutionEngine*, QQmlContextData*, QObject*, QV4::String*, QV4::QObjectWrapper::RevisionMode, bool*, QQmlPropertyData**) (engine=engine@entry=0x56507ee0f4f0, qmlContext=qmlContext@entry=0x565080948260, object=0x5650807ddfe0, name=0x7f52ccfb3628, revisionMode=revisionMode@entry=QV4::QObjectWrapper::IgnoreRevision, hasProperty=hasProperty@entry=0x0, property=0x0) at /usr/src/debug/libqt5-qtdeclarative-5.15.1-2.1.x86_64/src/qml/jsruntime/qv4qobjectwrapper.cpp:388 #8 0x7f52d59c7733 in QV4::QQmlTypeWrapper::virtualGet(QV4::Managed const*, QV4::PropertyKey, QV4::Value const*, bool*) (m=0x7f52ccfb3618, id=..., receiver=0x7f52ccfb3618, hasProperty=0x0) at /usr/src/debug/libqt5-qtdeclarative-5.15.1-2.1.x86_64/include/QtQml/5.15.1/QtQml/private/../../../../../src/qml/common/qv4staticvalue_p.h:325 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 383413] Discover crashes in Transaction::isActive() during or after updating
https://bugs.kde.org/show_bug.cgi?id=383413 Fikri Ms changed: What|Removed |Added CC||fikri.ms.200...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 426905] Plasma crashed on Wayland on switching to another virtual desktop
https://bugs.kde.org/show_bug.cgi?id=426905 Patrick Silva changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #2 from Patrick Silva --- cannot reproduce on neon unstable, let's consider this fixed. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 427481] New: Quick Open plugin does not support nested project directories
https://bugs.kde.org/show_bug.cgi?id=427481 Bug ID: 427481 Summary: Quick Open plugin does not support nested project directories Product: kdevelop Version: git master Platform: Compiled Sources OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: UI: QuickOpen Assignee: kdevelop-bugs-n...@kde.org Reporter: igor...@gmail.com Target Milestone: --- SUMMARY Quick Open plugin assumes that a given path can belong to a single project. See struct ProjectFile in https://commits.kde.org/kdevelop?path=plugins/quickopen/projectfilequickopen.h. When a file belongs to multiple open projects, closing one of the projects removes the file from Quick Open file list. STEPS TO REPRODUCE 1. Open a project that has a subdirectory with a CMakeLists.txt file in it. 2. Check that a file in the aforementioned subdirectory can be opened via Quick Open search. 3. Open the aforementioned project's subdirectory as another project. 4. Check that the file from step 2 can still be opened via Quick Open search. 5. Close the subdirectory project. 6. Check if the file from step 4 can still be opened via Quick Open search. OBSERVED RESULT The file is no longer available in Quick Open list. EXPECTED RESULT The file is still available in Quick Open list. ADDITIONAL INFORMATION First of all: is there a use case for nested project directories? And should KDevelop support file paths that belong to multiple open projects? If this should be supported, a possible fix is to store a QVector projectPaths in the ProjectFile struct. In ProjectFileDataProvider::fileRemovedFromSet(): if the file to be removed has projectPaths.size() > 1, simply remove the project path of the ProjectFileItem from projectPaths; if projectPaths.size() == 1, remove the entire ProjectFile. -- You are receiving this mail because: You are watching all bug changes.
[kinfocenter] [Bug 427482] New: kinfocenter freezes when I click on Energy or Network sections
https://bugs.kde.org/show_bug.cgi?id=427482 Bug ID: 427482 Summary: kinfocenter freezes when I click on Energy or Network sections Product: kinfocenter Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: bugsefor...@gmx.com CC: hubn...@gmail.com Target Milestone: --- STEPS TO REPRODUCE 1. open kinfocenter 2. click on Energy or Network sections in the left side 3. OBSERVED RESULT kinfocenter freezes and window decoration says "Not respondng". EXPECTED RESULT no freezing SOFTWARE/OS VERSIONS Operating System: KDE neon Unstable Edition KDE Plasma Version: 5.20.80 KDE Frameworks Version: 5.75.0 Qt Version: 5.15.0 Thread 9 (Thread 0x7fffcce8d700 (LWP 22828)): #0 0x762c1aff in __GI___poll (fds=0x7fffc4004e60, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x743d61ae in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x743d62e3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x76889e92 in QEventDispatcherGlib::processEvents (this=0x7fffc4000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #4 0x7682e1bb in QEventLoop::exec (this=this@entry=0x7fffcce8cd80, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:141 #5 0x7664c082 in QThread::exec (this=this@entry=0x55ed3640) at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #6 0x757036c9 in QQmlThreadPrivate::run (this=0x55ed3640) at qml/ftw/qqmlthread.cpp:155 #7 0x7664d20c in QThreadPrivate::start (arg=0x55ed3640) at thread/qthread_unix.cpp:342 #8 0x74cf1609 in start_thread (arg=) at pthread_create.c:477 #9 0x762ce293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 8 (Thread 0x7fffda54e700 (LWP 22827)): #0 0x762c1aff in __GI___poll (fds=0x7fffc8004a60, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x743d61ae in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x743d62e3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x76889e92 in QEventDispatcherGlib::processEvents (this=0x7fffc8000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #4 0x7682e1bb in QEventLoop::exec (this=this@entry=0x7fffda54dd80, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:141 #5 0x7664c082 in QThread::exec (this=this@entry=0x55d0c820) at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #6 0x757036c9 in QQmlThreadPrivate::run (this=0x55d0c820) at qml/ftw/qqmlthread.cpp:155 #7 0x7664d20c in QThreadPrivate::start (arg=0x55d0c820) at thread/qthread_unix.cpp:342 #8 0x74cf1609 in start_thread (arg=) at pthread_create.c:477 #9 0x762ce293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 7 (Thread 0x7fffdbfff700 (LWP 22826)): #0 0x762c1aff in __GI___poll (fds=0x7fffd0004e60, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x743d61ae in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x743d62e3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x76889e92 in QEventDispatcherGlib::processEvents (this=0x7fffdb60, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #4 0x7682e1bb in QEventLoop::exec (this=this@entry=0x7fffdbffed80, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:141 #5 0x7664c082 in QThread::exec (this=this@entry=0x559644d0) at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #6 0x757036c9 in QQmlThreadPrivate::run (this=0x559644d0) at qml/ftw/qqmlthread.cpp:155 #7 0x7664d20c in QThreadPrivate::start (arg=0x559644d0) at thread/qthread_unix.cpp:342 #8 0x74cf1609 in start_thread (arg=) at pthread_create.c:477 #9 0x762ce293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 6 (Thread 0x7fffe918b700 (LWP 22825)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x559a43f8) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x559a43a8, cond=0x559a43d0) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x559a43d0, mutex=0x559a43a8) at pthread_cond_wait.c:638 #3 0x7fffeb11b97b in cnd_wait (mtx=0x559a43a8, cond=0x559a43d0) at ../include/c11/threads_posix.h:155 #4 util_queue_thread_func (input=input@entry=0x55822a50) at ../src/util/u_queue.c:275 #5 0x7fffeb11b58b in impl_thrd_routine (p=) at ../include/c11/threads_posix.h:87 #6 0x74cf1609 in star
[frameworks-baloo] [Bug 427480] Baloo crashes on Plasma startup and fills system journal with core dump
https://bugs.kde.org/show_bug.cgi?id=427480 Stefan Brüns changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #1 from Stefan Brüns --- Don't use pastebin. Bugzilla has a file upload feature. And quote a least some of the errors, so one does not have to open the file to see whats going on. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 427483] New: Can't move normal layers
https://bugs.kde.org/show_bug.cgi?id=427483 Bug ID: 427483 Summary: Can't move normal layers Product: krita Version: 4.3.0 Platform: Compiled Sources OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: Layer Stack Assignee: krita-bugs-n...@kde.org Reporter: brah@gmx.net Target Milestone: --- Created attachment 132234 --> https://bugs.kde.org/attachment.cgi?id=132234&action=edit Project file this error occurs in SUMMARY At some point moving layers stopped working. Moving file layers still works. When I make a new project moving works again. Both moving with the move tool and the transform layer don't work. Move tool outputs nothing and transform layer "cannot transform empty layer" even though there is something there. STEPS TO REPRODUCE 1. Drag and drop a picure file (png) into my project 2. select new layer 3. try to move the layer OBSERVED RESULT Layer does not move EXPECTED RESULT layer should move SOFTWARE/OS VERSIONS Windows: Windows 7 macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 425272] install-sessions.sh should set up dbus/polkit/kauth stuff for your built-from-source Plasma desktop
https://bugs.kde.org/show_bug.cgi?id=425272
--- Comment #4 from Nate Graham ---
I use a bash function that does the following now:
function install-dbus-stuff {
echo "Let's install stuff!"
sudo ls > /dev/null
echo "Installing actions from ~/kde/usr/share/polkit-1/actions/ to
/usr/share/polkit-1/actions/"
sudo cp -r ~/kde/usr/share/polkit-1/actions/* /usr/share/polkit-1/actions/
echo "Installing everything from ~/kde/usr/share/dbus-1/ to
/usr/share/dbus-1/"
sudo cp -r ~/kde/usr/share/dbus-1/ /usr/share/
}
Seems to work fine in the absence of an automated solution to this problem.
--
You are receiving this mail because:
You are watching all bug changes.
[frameworks-baloo] [Bug 427480] Baloo crashes on Plasma startup and fills system journal with core dump
https://bugs.kde.org/show_bug.cgi?id=427480 --- Comment #2 from kdereport.fireha...@slmail.me --- Created attachment 132235 --> https://bugs.kde.org/attachment.cgi?id=132235&action=edit The journalctl baloo errors: core dumped -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 427483] Can't move normal layers
https://bugs.kde.org/show_bug.cgi?id=427483 Boudewijn Rempt changed: What|Removed |Added Status|REPORTED|RESOLVED CC||b...@valdyas.org Resolution|--- |NOT A BUG --- Comment #1 from Boudewijn Rempt --- If you're talking about the layer with the brown square, that's because there's an active selection outside the area covered with the brown square, and you're trying to move that selection, but there are no pixels inside the selectio, so Krita refuses to budge. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 427480] Baloo crashes on Plasma startup and fills system journal with core dump
https://bugs.kde.org/show_bug.cgi?id=427480 --- Comment #3 from kdereport.fireha...@slmail.me --- Sorry, my first bug report. -- You are receiving this mail because: You are watching all bug changes.
[plasma-browser-integration] [Bug 427484] New: Preference Page in dark theme should be dark
https://bugs.kde.org/show_bug.cgi?id=427484 Bug ID: 427484 Summary: Preference Page in dark theme should be dark Product: plasma-browser-integration Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Firefox Assignee: k...@privat.broulik.de Reporter: d_debn...@outlook.com Target Milestone: --- The preference page for the extension is light even in dark mode. This is how it looks: https://i.imgur.com/8EjCvxX.png For reference, here's another popular add-on which correctly implements the preference page: https://i.imgur.com/C8Uiw3t.png -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 427480] Baloo crashes on Plasma startup and fills system journal with core dump
https://bugs.kde.org/show_bug.cgi?id=427480 --- Comment #4 from kdereport.fireha...@slmail.me --- The errors seem all to be baloo_file and baloo_file_extr dumped core, not very informative, is there anything I could do to give more info? -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 424529] Feature Request: Rotobrush for fast and automatic rotoscoping powered by Artificial Intelligence
https://bugs.kde.org/show_bug.cgi?id=424529 Christoph Feck changed: What|Removed |Added Version|20.07.80|20.08.0 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 413751] Open links in LSP tooltips
https://bugs.kde.org/show_bug.cgi?id=413751 Christoph Feck changed: What|Removed |Added Version|19.11.70|19.12.3 --- Comment #2 from Christoph Feck --- If you can provide the information requested in comment 1, please add it. -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 426872] Blur on yakuake doesn't work.
https://bugs.kde.org/show_bug.cgi?id=426872 D. Debnath changed: What|Removed |Added Ever confirmed|0 |1 CC||d_debn...@outlook.com Status|REPORTED|CONFIRMED --- Comment #1 from D. Debnath --- I can confirm this bug. -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 427446] amarok freezes
https://bugs.kde.org/show_bug.cgi?id=427446 Myriam Schweingruber changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #3 from Myriam Schweingruber --- Trim it, then. Comments are searchable, attachments not directly. Usually the issue is not at the start of the GDB output, if there is no mention of Amarok strings there, you can easily discard that part. In your particular example only the last thread seems to have been relevant. Closing for now, please reopen if this happens again and you have debugging info. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knotifications] [Bug 422042] KNotification uses transient=true hint incorrectly
https://bugs.kde.org/show_bug.cgi?id=422042 --- Comment #4 from Ulrich Norbisrath --- Just confirming that this is still an issue. We are currently trying to discuss this problem at https://gitlab.xfce.org/apps/xfce4-notifyd/-/issues/25#note_17084, but maybe should move the discussion here. However, I assume that nobody in kde will notice this problem as the notifications do show up in kde's notification log and stay there. -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 427485] New: System Tray icon for Yakuake doesn't match the monochrome style of the other icons
https://bugs.kde.org/show_bug.cgi?id=427485 Bug ID: 427485 Summary: System Tray icon for Yakuake doesn't match the monochrome style of the other icons Product: yakuake Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: h...@kde.org Reporter: d_debn...@outlook.com Target Milestone: --- Created attachment 132236 --> https://bugs.kde.org/attachment.cgi?id=132236&action=edit All System Tray Icons use a monochrome style, except Yakuake Yakuake uses a colourful icon in the system tray, which looks out of place (at least when using the default breeze theme). Screenshot attached. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-qqc2-desktop-style] [Bug 427449] QQC2-Desktop-Style causes RDM to not show toolbar buttons
https://bugs.kde.org/show_bug.cgi?id=427449 Noah Davis changed: What|Removed |Added Status|ASSIGNED|RESOLVED Version Fixed In||5.76 Latest Commit||https://invent.kde.org/fram ||eworks/qqc2-desktop-style/c ||ommit/015891bf58b5f96ae1429 ||20bba48b92fe31ea0e4 Resolution|--- |FIXED --- Comment #6 from Noah Davis --- Git commit 015891bf58b5f96ae142920bba48b92fe31ea0e4 by Noah Davis. Committed on 09/10/2020 at 02:25. Pushed by ndavis into branch 'master'. Add support for qrc icons to StyleItem FIXED-IN: 5.76 M +37 -24 plugin/kquickstyleitem.cpp M +1-0plugin/kquickstyleitem_p.h https://invent.kde.org/frameworks/qqc2-desktop-style/commit/015891bf58b5f96ae142920bba48b92fe31ea0e4 -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 427486] New: tests imported from CMake do not respect ENVIRONMENT properties
https://bugs.kde.org/show_bug.cgi?id=427486
Bug ID: 427486
Summary: tests imported from CMake do not respect ENVIRONMENT
properties
Product: kdevelop
Version: git master
Platform: Compiled Sources
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: Build tools: CMake
Assignee: kdevelop-bugs-n...@kde.org
Reporter: k...@opensource.sf-tec.de
Target Milestone: ---
Brute-force example code to give some hints is here:
https://invent.kde.org/dakon/kdevelop/-/tree/ctest-env
If one does this:
add_test(NAME test_six COMMAND four_test 3 WORKING_DIRECTORY "/foo")
set_property(TEST test_six PROPERTY ENVIRONMENT "foo=bar")
then running the code via ctest will result in getenv("foo") == "bar", which
when I run the same test using the "Unit test" pane it will be getenv("foo") ==
NULL.
--
You are receiving this mail because:
You are watching all bug changes.
[krita] [Bug 408099] SVG File layers are not rendered
https://bugs.kde.org/show_bug.cgi?id=408099 Evan changed: What|Removed |Added CC||e...@neatlogic.co.nz -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 427487] New: Wish : make interaction tools compatible with raster or paint layers
https://bugs.kde.org/show_bug.cgi?id=427487 Bug ID: 427487 Summary: Wish : make interaction tools compatible with raster or paint layers Product: krita Version: 4.4.0-beta2 Platform: unspecified OS: All Status: REPORTED Severity: wishlist Priority: NOR Component: Tools Assignee: krita-bugs-n...@kde.org Reporter: tgdev...@gmail.com Target Milestone: --- SUMMARY This goes into the wishlist and targets Interaction tools' added compatibility with Paint layers. STEPS TO REPRODUCE 1. Select multiple paint/vector layers(at least a total of three selected layers in the stack) 2. Execute any alignment or distribution function in the interaction tools OBSERVED RESULT Currently impossible to align or distribute paint layers(a little bummer; why didn't you think about it earlier ?) EXPECTED RESULT Whether vector or raster layers are selected, they are disposed according to the executed interaction tool. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 427477] /mnt directory not visible in Linux file system / Collection cannot be added from removable media
https://bugs.kde.org/show_bug.cgi?id=427477 --- Comment #4 from Fred Brigham --- Thanks Maik. I switched to "use native file dialogs from system" and I can now see /mnt and the sd card but cannot select a folder. When I select a folder and click on Open the folder is opened but not selected in digiKam. Also it says that the folder I created for the database doesn't exist even though I can see this folder in my home directory. digiKam offers to create the folder but this always fails. Something is still wrong. Perhaps I do not have the correct permissions although my Linux setup on the Chromebook appears to be fine as other apps work correctly. As a beginner to Linux I am struggling with this problem and I wouldn't know how to check the permissions. Not sure whether digiKam is from AppImage or native Debian packages. I installed from flathub which I assume is a reliable source: https://flathub.org/apps/details/org.kde.digikam Fred On Fri, 9 Oct 2020 at 11:36, Maik Qualmann wrote: > https://bugs.kde.org/show_bug.cgi?id=427477 > > Maik Qualmann changed: > >What|Removed |Added > > > CC||metzping...@gmail.com > > --- Comment #1 from Maik Qualmann --- > Switch to the native file dialogs in the digiKam settings. Is digiKam from > AppImage or native Debian packages? Otherwise we already know the problem > of > broken file dialogs under Debian / Red Hat, this is a package error, the > set > file filter is not processed correctly. > > Maik > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 417382] gwenview shows two warnings at the same time if I try to save a file with an invalid extension
https://bugs.kde.org/show_bug.cgi?id=417382 Christoph Feck changed: What|Removed |Added Version|20.07.80|20.08.2 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 427488] New: Feature proposal : dynamic option bar UX according to selected tool
https://bugs.kde.org/show_bug.cgi?id=427488 Bug ID: 427488 Summary: Feature proposal : dynamic option bar UX according to selected tool Product: krita Version: 4.4.0-beta2 Platform: unspecified OS: All Status: REPORTED Severity: wishlist Priority: NOR Component: Tools Assignee: krita-bugs-n...@kde.org Reporter: tgdev...@gmail.com Target Milestone: --- SUMMARY This goes into the wishlist and targets the options bar. The idea is to have different options displayed or not according to the selected tool. For instance, selecting the move tool will display interaction tools buttons on the option bar and remove unnecessary options(opacity or flow) instead of graying them. STEPS TO REPRODUCE 1. Select for instance the brush tool, then switch to the gradient/fill tool then, switch to the move tool. OBSERVED RESULT For the moment, the options bar keeps its options and is static rather than dynamic. This means the possibility for more options is not really possible as of now. EXPECTED RESULT Depending on the tool selected, the options that support the currently selected tool are shown. For instance, selecting the brush tool will display opacity, flow, brush size, brush tip, foreground/background colors etc. Selecting the gradient/fill tool displays opacity, foreground/background color, gradient types, etc, etc. This probably needs to be discussed. I might have to search the krita-artists website for a similar topic or create one if none existed yet. But I leave this here meanwhile. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 427170] Help, It keeps telling me to Recover files and I clicked discard and it deleted a work I took hours on
https://bugs.kde.org/show_bug.cgi?id=427170 --- Comment #10 from audriennastaff...@gmail.com --- Thank you! On Fri, Oct 9, 2020 at 12:33 AM Bug Janitor Service < bugzilla_nore...@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=427170 > > Bug Janitor Service changed: > >What|Removed |Added > > > Resolution|WAITINGFORINFO |--- > Status|NEEDSINFO |REPORTED > > --- Comment #9 from Bug Janitor Service --- > Thanks for your comment! > > Automatically switching the status of this bug to REPORTED so that the KDE > team > knows that the bug is ready to get confirmed. > > In the future you may also do this yourself when providing needed > information. > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 427489] New: Crash when scrubbing to 2nd frame and back to 1st
https://bugs.kde.org/show_bug.cgi?id=427489 Bug ID: 427489 Summary: Crash when scrubbing to 2nd frame and back to 1st Product: krita Version: 4.3.0 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: crash Priority: NOR Component: Animation Assignee: krita-bugs-n...@kde.org Reporter: tomek-kub...@wp.pl Target Milestone: --- Created attachment 132239 --> https://bugs.kde.org/attachment.cgi?id=132239&action=edit Crash log STEPS TO REPRODUCE 1. Switch to 2nd frame of animation 2. Switch back to 1st 3. If didn't crash, repeat OBSERVED RESULT Crash. Windows showed "Application is not responding" dialog SOFTWARE/OS VERSIONS Windows: 8.1 ADDITIONAL INFORMATION The cause might be a faulty graphics card driver (Intel Mobile HD 4000), 'tho reading through log, it looks like maybe unhandled null pointer in kritaui -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 427489] Crash when scrubbing to 2nd frame and back to 1st
https://bugs.kde.org/show_bug.cgi?id=427489 Boudewijn Rempt changed: What|Removed |Added CC||b...@valdyas.org Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #1 from Boudewijn Rempt --- Well, both crashes are in the log. Could you please check whether you can reproduce with the latest beta? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 427490] New: KDE Neon (user edition) freezes in the presentation screen after log-in.
https://bugs.kde.org/show_bug.cgi?id=427490 Bug ID: 427490 Summary: KDE Neon (user edition) freezes in the presentation screen after log-in. Product: plasmashell Version: 5.19.5 Platform: Other OS: Linux Status: REPORTED Severity: grave Priority: NOR Component: Desktop Containment Assignee: notm...@gmail.com Reporter: luckyfdga...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 132240 --> https://bugs.kde.org/attachment.cgi?id=132240&action=edit The system completely frozen in this screen. SUMMARY: I've installed KDE neon (user edition, with default themes, no extensions or customization). I updated my system, and when i restarted the system i logged-in, then plasma opened a black screen asking my kdewallet (i don't have one) and my wifi password. After i insert the wifi password, the system crashes and stucks in the presentation screen. My setup is: Intel Core i5-8265U, 8GB of RAM, 1tb (HD), 256GB (blitzwolf's ssd) <--- where the system is installed, Intel UHD Graphics 620. I tried to reinstall the system, but the same thing happened again STEPS TO REPRODUCE: 1. Install KDE Neon (user edition) in a ssd, with 400 MiB for boot, 8,5 GiB of SWAP and the /home installed in a HD 2. Update the system 3. Restart and Login -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 427490] KDE Neon (user edition) freezes in the presentation screen after log-in.
https://bugs.kde.org/show_bug.cgi?id=427490 --- Comment #1 from Victor Hugo --- Edit:In the steps to reproduce i said to put 400 MiB for the boot, but i tested it now and this bug happen with any quantity for boot, i'm not sure if it happen installing the /home in the same drive, cais i didn't tested it. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 427491] New: Dolphin crashed on close
https://bugs.kde.org/show_bug.cgi?id=427491 Bug ID: 427491 Summary: Dolphin crashed on close Product: dolphin Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: bugsefor...@gmx.com CC: kfm-de...@kde.org Target Milestone: --- Application: dolphin (20.11.70) Qt Version: 5.15.0 Frameworks Version: 5.75.0 Operating System: Linux 5.4.0-47-generic x86_64 Windowing system: Wayland Distribution: KDE neon Unstable Edition -- Information about the crash: - What I was doing when the application crashed: I just closed Dolphin, then Plasma shown a crash notification. The crash does not seem to be reproducible. -- Backtrace: Application: Dolphin (dolphin), signal: Segmentation fault Content of s_kcrashErrorMessage: (null) [New LWP 49358] [New LWP 49359] [New LWP 49360] [New LWP 49361] [New LWP 49362] [New LWP 49363] [New LWP 49851] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". 0x7f9e1fb2aaff in __GI___poll (fds=fds@entry=0x7ffdadbb09e8, nfds=nfds@entry=1, timeout=timeout@entry=1000) at ../sysdeps/unix/sysv/linux/poll.c:29 [Current thread is 1 (Thread 0x7f9e18fd7800 (LWP 49352))] Thread 8 (Thread 0x7f9df67fc700 (LWP 49851)): #0 0x7f9e1fb2aaff in __GI___poll (fds=0x7f9ddc007170, nfds=3, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f9e1bfa31d6 in ?? () from /lib/x86_64-linux-gnu/libpulse.so.0 #2 0x7f9e1bf94841 in pa_mainloop_poll () from /lib/x86_64-linux-gnu/libpulse.so.0 #3 0x7f9e1bf94ec3 in pa_mainloop_iterate () from /lib/x86_64-linux-gnu/libpulse.so.0 #4 0x7f9e1bf94f70 in pa_mainloop_run () from /lib/x86_64-linux-gnu/libpulse.so.0 #5 0x7f9e1bfa311d in ?? () from /lib/x86_64-linux-gnu/libpulse.so.0 #6 0x7f9e1b2be67c in ?? () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-13.99.so #7 0x7f9e1bfe7609 in start_thread (arg=) at pthread_create.c:477 #8 0x7f9e1fb37293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 7 (Thread 0x7f9e068cb700 (LWP 49363)): #0 0x7f9e1b62471f in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f9e1b626185 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f9e1b627aff in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f9e1b628152 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f9e1b6282e3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f9e1d899eab in QEventDispatcherGlib::processEvents (this=0x7f9dfc000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #6 0x7f9e1d83e1bb in QEventLoop::exec (this=this@entry=0x7f9e068cada0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:141 #7 0x7f9e1d65c082 in QThread::exec (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #8 0x7f9e1d65d20c in QThreadPrivate::start (arg=0x55864d4e2050) at thread/qthread_unix.cpp:342 #9 0x7f9e1bfe7609 in start_thread (arg=) at pthread_create.c:477 #10 0x7f9e1fb37293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 6 (Thread 0x7f9e07fff700 (LWP 49362)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x55864d212c98) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x55864d212c48, cond=0x55864d212c70) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x55864d212c70, mutex=0x55864d212c48) at pthread_cond_wait.c:638 #3 0x7f9e166b097b in cnd_wait (mtx=0x55864d212c48, cond=0x55864d212c70) at ../include/c11/threads_posix.h:155 #4 util_queue_thread_func (input=input@entry=0x55864d3eb300) at ../src/util/u_queue.c:275 #5 0x7f9e166b058b in impl_thrd_routine (p=) at ../include/c11/threads_posix.h:87 #6 0x7f9e1bfe7609 in start_thread (arg=) at pthread_create.c:477 #7 0x7f9e1fb37293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 5 (Thread 0x7f9e14f21700 (LWP 49361)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x55864d212c98) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x55864d212c48, cond=0x55864d212c70) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x55864d212c70, mutex=0x55864d212c48) at pthread_cond_wait.c:638 #3 0x7f9e166b097b in cnd_wait (mtx=0x55864d212c48, cond=0x55864d212c70) at ../include/c11/threads_posix.h:155 #4 util_queue_thread_func (input=input@entry=0x55864d3eb2c0) at ../src/util/u_queue.c:275 #5 0x7f9e166b058b in impl_thrd_routine (p=) at ../include/c11/threads_posix.h:87 #6 0x7f9e1bfe7609 in start_thread (arg=) at pthread_create.c:477 #7 0x
[kate] [Bug 427492] New: Weird bar over text in search field with dark theme.
https://bugs.kde.org/show_bug.cgi?id=427492 Bug ID: 427492 Summary: Weird bar over text in search field with dark theme. Product: kate Version: 19.12.3 Platform: Mint (Ubuntu based) OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: search Assignee: kwrite-bugs-n...@kde.org Reporter: dovegl...@yahoo.com Target Milestone: --- Created attachment 132241 --> https://bugs.kde.org/attachment.cgi?id=132241&action=edit Shows bar that covers text in search box. SUMMARY STEPS TO REPRODUCE 1.Use a dark theme. 2.Click search. 3.Type text in box that enters text to be searched. OBSERVED RESULT A cyan bar covers text. EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 427490] KDE Neon (user edition) freezes in the presentation screen after log-in.
https://bugs.kde.org/show_bug.cgi?id=427490 David Edmundson changed: What|Removed |Added Status|REPORTED|NEEDSINFO CC||k...@davidedmundson.co.uk Resolution|--- |WAITINGFORINFO --- Comment #2 from David Edmundson --- Can you VT switch(control+alt+f2) when this happens? If so can you get a snapshot of what's running and ~/.local/share/sddm/xorg-session.log -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 427490] KDE Neon (user edition) freezes in the presentation screen after log-in.
https://bugs.kde.org/show_bug.cgi?id=427490 --- Comment #3 from Victor Hugo --- (In reply to David Edmundson from comment #2) > Can you VT switch(control+alt+f2) when this happens? > > If so can you get a snapshot of what's running > and ~/.local/share/sddm/xorg-session.log No, i can't do it. Nothing happens when i press those keys. Anyway, it's a clean installation, i didn't even downloaded my things or changed any system settings. I think the services that are ruinning in background are the standard of the system. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 427373] kwin hangs systemd until timeout
https://bugs.kde.org/show_bug.cgi?id=427373 --- Comment #1 from Vlad Zahorodnii --- Git commit 08263b534d4a73781fb06b2f875e7557965c729c by Vlad Zahorodnii. Committed on 09/10/2020 at 16:33. Pushed by vladz into branch 'master'. Safely remove all internal clients and override-redirect windows When we destroy all internal clients and override-redirect windows, we assume that corresponding lists will be implicitly detached. However, in some cases, that might be not the case. For example, if the list is not shared, neither begin() nor end() will detach. Therefore, it is possible to hit invalidated iterators if the list is modified inside the loop. This change prevents hitting invalidated iterators by making explicit list copies. M +6-2workspace.cpp https://invent.kde.org/plasma/kwin/commit/08263b534d4a73781fb06b2f875e7557965c729c -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 427373] kwin hangs systemd until timeout
https://bugs.kde.org/show_bug.cgi?id=427373 --- Comment #2 from Vlad Zahorodnii --- Git commit 5df72c6613e588b2cc920863dbefba16ba0b89c7 by Vlad Zahorodnii. Committed on 09/10/2020 at 16:35. Pushed by vladz into branch 'Plasma/5.20'. Safely remove all internal clients and override-redirect windows When we destroy all internal clients and override-redirect windows, we assume that corresponding lists will be implicitly detached. However, in some cases, that might be not the case. For example, if the list is not shared, neither begin() nor end() will detach. Therefore, it is possible to hit invalidated iterators if the list is modified inside the loop. This change prevents hitting invalidated iterators by making explicit list copies. (cherry picked from commit 08263b534d4a73781fb06b2f875e7557965c729c) M +6-2workspace.cpp https://invent.kde.org/plasma/kwin/commit/5df72c6613e588b2cc920863dbefba16ba0b89c7 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 424076] PlasmaComponents3.ComboBox closes popup on click release when editable=true
https://bugs.kde.org/show_bug.cgi?id=424076 Nate Graham changed: What|Removed |Added Version Fixed In||5.76 -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 427493] New: Kwin crashes after login with symbol lookup error
https://bugs.kde.org/show_bug.cgi?id=427493 Bug ID: 427493 Summary: Kwin crashes after login with symbol lookup error Product: neon Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: neon-b...@kde.org Reporter: terce...@gmail.com CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- SUMMARY After todays update kwin can't launch and thus the user is starting on a black screen. Programs can be launched through KRunner or Terminal, but don't have any borders. All Panels are missing. STEPS TO REPRODUCE 1. Update System 2. Restart 3. Login OBSERVED RESULT - Missing background - programs can only be launched with KRunner or through terminal (they lack borders and can't be moved) - no panels - starting Kwin manually returns error: "kwin: symbol lookup error: /usr/lib/x86_64-linux-gnu/libkwin.so.5: undefined symbol: _ZN14KWaylandServer17XdgShellInterface14surfaceCreatedEPNS_24XdgShellSurfaceInterfaceE" EXPECTED RESULT - Boot PC - Log into my account - Use account as usual SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE neon 20.04 5.19 KDE Plasma Version: 5.19.5 KDE Frameworks Version: 5.74.0-0xneon+20.04+focal+buil12 Qt Version: ??? ADDITIONAL INFORMATION There is also a thread in the forums of multiple users getting this error: https://forum.kde.org/viewtopic.php?f=309&t=168189 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 427490] KDE Neon (user edition) freezes in the presentation screen after log-in.
https://bugs.kde.org/show_bug.cgi?id=427490 --- Comment #4 from David Edmundson --- >No, i can't do it. Nothing happens when i press those keys. Then I'm afraid that strongly implies your bug is lower level than Plasma and there won't be much we can do. X handles those keys directly. You should be able to VT switch whilst on the login screen, from there you can install openbox or some such to have a session you can log into. `journalctl -b -1 ` might list something interesting. It'll show logs of the last boot. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 426746] keyboard input is slow on Wayland and can result in repeated characters, like "fireefoox"
https://bugs.kde.org/show_bug.cgi?id=426746 Nate Graham changed: What|Removed |Added Version Fixed In||Plasma 5.20 and Frameworks ||5.75 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 427490] KDE Neon (user edition) freezes in the presentation screen after log-in.
https://bugs.kde.org/show_bug.cgi?id=427490 --- Comment #5 from Victor Hugo --- Oh just a thing: when you finish the installation of the system and it asks you to restart you can login normally, the bug happens when you update the system and restart by the second time after you've finish the installation. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 427494] New: (Removable Devices) Apply button is not available after a device-specific change.
https://bugs.kde.org/show_bug.cgi?id=427494 Bug ID: 427494 Summary: (Removable Devices) Apply button is not available after a device-specific change. Product: systemsettings Version: 5.19.4 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_deviceautomounter Assignee: tdfisc...@kde.org Reporter: 255sh...@gmail.com CC: plasma-b...@kde.org Target Milestone: --- SUMMARY Changing "On Login" or "On Attach" for a specific device does not make the "Apply" button available, and changes cannot be saved. STEPS TO REPRODUCE 1. Open Removable Devices. 2. Make any changes to the checkboxes under the list of "Automatic mount"s. OBSERVED RESULT The "Apply" button is not available. Closing then reopening Removable Devices shows that these changes were not saved. EXPECTED RESULT Making a change for a device should make the "Apply" button available. SOFTWARE/OS VERSIONS Windows: n/a macOS: n/a Linux/KDE Plasma: KDE neon 5.19 (available in About System) KDE Plasma Version: 5.19.4 KDE Frameworks Version: 5.72.0 Qt Version: 5.14.2 ADDITIONAL INFORMATION A workaround to save device-specific changes is to also change one of the other options (eg. uncheck "Enable automatic mounting of removable media") which makes "Apply" available. After clicking "Apply", undo the second change (eg. recheck "Enable automatic mounting of removable media") and "Apply" again. The device-specific changes should now be saved. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 427468] Duplicate subalbums on Windows 10 (format YYYY\MM)
https://bugs.kde.org/show_bug.cgi?id=427468 --- Comment #4 from fernando_...@hotmail.com --- Thanks for the suggestion. I just tested it and worked like a charm. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 427490] KDE Neon (user edition) freezes in the presentation screen after log-in.
https://bugs.kde.org/show_bug.cgi?id=427490 --- Comment #6 from Victor Hugo --- (In reply to David Edmundson from comment #4) > >No, i can't do it. Nothing happens when i press those keys. > > Then I'm afraid that strongly implies your bug is lower level than Plasma > and there won't be much we can do. X handles those keys directly. > > You should be able to VT switch whilst on the login screen, from there you > can install openbox or some such to have a session you can log into. > > `journalctl -b -1 ` > might list something interesting. It'll show logs of the last boot. Ah, i really don't know if in the login screen i can do it. I can't test it anymore cause i've aready installed another distro instead KDE Neon (OpenSUSE) in my computer to i be able to use it. -- You are receiving this mail because: You are watching all bug changes.
[plasma-browser-integration] [Bug 427484] Preference Page in dark theme should be dark
https://bugs.kde.org/show_bug.cgi?id=427484 Patrick Silva changed: What|Removed |Added Status|REPORTED|RESOLVED CC||bugsefor...@gmx.com Resolution|--- |DUPLICATE --- Comment #1 from Patrick Silva --- *** This bug has been marked as a duplicate of bug 423060 *** -- You are receiving this mail because: You are watching all bug changes.
[plasma-browser-integration] [Bug 423060] Preferences tab doesn't respect dark theme
https://bugs.kde.org/show_bug.cgi?id=423060 Patrick Silva changed: What|Removed |Added CC||d_debn...@outlook.com --- Comment #1 from Patrick Silva --- *** Bug 427484 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 427495] New: No plasma shell, black screen after today's update
https://bugs.kde.org/show_bug.cgi?id=427495 Bug ID: 427495 Summary: No plasma shell, black screen after today's update Product: plasmashell Version: master Platform: Neon Packages OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: generic-crash Assignee: plasma-b...@kde.org Reporter: dark.guy.2...@gmail.com Target Milestone: 1.0 SUMMARY https://www.reddit.com/r/kdeneon/comments/j82fgk/kde_neon_latest_update_as_of_today_broke_my/ Okay so I can't post screenshots or anything, I have a bare firefox window with no decorations, plasma or desktop or anything whatsoever. I can't even move windows. Basically, today Discover showed up some updates for KDE apps (as usual), I hit update, all good. Then I decide to reboot the computer and boom. I get the spinning logo where it says "Plasma made by KDE" and it stays there. I have mouse cursor, but only a black background. Running "krunner" doesn't work. Creating a new user didn't work, same result. I can't even logout from it (I could logout from my normal user) so the issue isn't my user/home dir, but the system. I can run ksysguard, but no window decorations, ALT+drag, nada. I can logout, the login manager appears, I can pick either X11 or Wayland. X11 goes through, Wayland just gets me back to the login manager. Any help is greatly welcome, I'm stuck with a faulty system now :( Edit: I was able to go to the console and install openbox and have a rudimentary taskbar with tint2. Plasma is broken though, this feels so 2000... STEPS TO REPRODUCE 1. Update your packages as of today. Discover showed up a bunch of updates for KDE apps 2. Reboot 3. Boom. OBSERVED RESULT Black screen. Can work around it by using ALT+Space to launch other shells (I ran openbox and tint2). Rebooting doesn't work at all. EXPECTED RESULT My normal desktop, I need to work! SOFTWARE/OS VERSIONS Windows: Not relevant macOS: Not relevant Linux/KDE Plasma: 5.19.5 ? Latest as of today (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.
[frameworks-qqc2-desktop-style] [Bug 427449] QQC2-Desktop-Style causes RDM to not show toolbar buttons
https://bugs.kde.org/show_bug.cgi?id=427449 Nate Graham changed: What|Removed |Added CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 427459] Flathub repo not added by default
https://bugs.kde.org/show_bug.cgi?id=427459 --- Comment #2 from Nate Graham --- Thanks Harald! -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 398803] Exec= kcms through systemsettings5 rather than kcmshell5
https://bugs.kde.org/show_bug.cgi?id=398803 --- Comment #8 from Alexander Lohnau --- https://phabricator.kde.org/T13729 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 427495] No plasma shell, black screen after today's update
https://bugs.kde.org/show_bug.cgi?id=427495 --- Comment #1 from Alemar --- Running kquitapp5 plasmashell kstart5 plasmashell Makes it work, but no window decorations, I'm stuck with openbox now. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 427496] New: KWin crashes when disconnecting the second monitor
https://bugs.kde.org/show_bug.cgi?id=427496 Bug ID: 427496 Summary: KWin crashes when disconnecting the second monitor Product: kwin Version: 5.19.5 Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: e...@moskvin.ca Target Milestone: --- Application: kwin_x11 (5.19.5) Qt Version: 5.15.0 Frameworks Version: 5.74.0 Operating System: Linux 5.6.7-050607-generic x86_64 Windowing system: X11 Distribution: KDE neon User Edition 5.19 -- Information about the crash: - What I was doing when the application crashed: It crashes when I dissconnect the external monitor from the laptop. The monitor is connected via HDMI. - Custom settings of the application: Tiling mode is enabled. The crash can be reproduced every time. -- Backtrace: Application: KWin (kwin_x11), signal: Segmentation fault [KCrash Handler] #4 0x7f0309a69dbd in std::__atomic_base::load(std::memory_order) const (__m=std::memory_order_relaxed, this=0x64) at /usr/include/c++/9/bits/atomic_base.h:413 #5 QAtomicOps::loadRelaxed(std::atomic const&) (_q_value=...) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qatomic_cxx11.h:239 #6 QBasicAtomicInteger::loadRelaxed() const (this=0x64) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qbasicatomic.h:107 #7 QtPrivate::RefCount::isShared() const (this=0x64) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qrefcount.h:101 #8 QMap::detach() (this=0x563feb663ce0) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qmap.h:357 #9 QMap::find(KWin::Group* const&) (akey=, this=0x563feb663ce0) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qmap.h:861 #10 KWin::Workspace::constrainedStackingOrder() (this=this@entry=0x563fea81a410) at ./layers.cpp:519 #11 0x7f0309a6a818 in KWin::Workspace::updateStackingOrder(bool) (propagate_new_clients=false, this=0x563fea81a410) at ./layers.cpp:121 #12 KWin::Workspace::updateStackingOrder(bool) (this=0x563fea81a410, propagate_new_clients=propagate_new_clients@entry=false) at ./layers.cpp:114 #13 0x7f0309b4948d in KWin::X11Client::setFrameGeometry(QRect const&, KWin::AbstractClient::ForceGeometry_t) (this=0x563fea94dcd0, rect=..., force=KWin::AbstractClient::NormalGeometrySet) at ./workspace.h:801 #14 0x7f03099b5cd4 in KWin::AbstractClient::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) (_o=_o@entry=0x563fea94dcd0, _c=_c@entry=QMetaObject::WriteProperty, _id=_id@entry=27, _a=_a@entry=0x7ffd7b3fab90) at ./obj-x86_64-linux-gnu/kwin_autogen/EWIEGA46WW/moc_abstract_client.cpp:836 #15 0x7f03099bbecb in KWin::AbstractClient::qt_metacall(QMetaObject::Call, int, void**) (this=this@entry=0x563fea94dcd0, _c=_c@entry=QMetaObject::WriteProperty, _id=27, _a=_a@entry=0x7ffd7b3fab90) at ./obj-x86_64-linux-gnu/kwin_autogen/EWIEGA46WW/moc_abstract_client.cpp:886 #16 0x7f03099bbf5a in KWin::X11Client::qt_metacall(QMetaObject::Call, int, void**) (this=0x563fea94dcd0, _c=QMetaObject::WriteProperty, _id=, _a=0x7ffd7b3fab90) at ./obj-x86_64-linux-gnu/kwin_autogen/EWIEGA46WW/moc_x11client.cpp:269 #17 0x7f0306d218a5 in QQmlPropertyData::writeProperty(QObject*, void*, QFlags) const (this=, target=, value=, flags=...) at ../../include/QtQml/5.15.0/QtQml/private/../../../../../src/qml/qml/qqmlpropertydata_p.h:379 #18 0x7f0306d1d3c4 in QQmlPropertyPrivate::write(QObject*, QQmlPropertyData const&, QVariant const&, QQmlContextData*, QFlags) (object=, property=..., value=..., context=, flags=...) at qml/qqmlproperty.cpp:1301 #19 0x7f0306c3a2ac in QV4::QObjectWrapper::setProperty(QV4::ExecutionEngine*, QObject*, QQmlPropertyData*, QV4::Value const&) (engine=0x563fea945940, object=0x563fea94dcd0, property=0x563feb421898, value=...) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qflags.h:120 #20 0x7f0306c3adbe in QV4::QObjectWrapper::setQmlProperty(QV4::ExecutionEngine*, QQmlContextData*, QObject*, QV4::String*, QV4::QObjectWrapper::RevisionMode, QV4::Value const&) (engine=0x563fea945940, qmlContext=, object=0x563fea94dcd0, name=, revisionMode=QV4::QObjectWrapper::IgnoreRevision, value=...) at jsruntime/qv4qobjectwrapper.cpp:435 #21 0x7f0306c3af37 in QV4::QObjectWrapper::virtualPut(QV4::Managed*, QV4::PropertyKey, QV4::Value const&, QV4::Value*) () at /usr/include/c++/9/bits/atomic_base.h:413 #22 0x7f0306bb842c in QV4::Object::put(QV4::StringOrSymbol*, QV4::Value const&, QV4::Value*) (receiver=0x7f02e63beb38, v=..., name=0x7f02e63beb40, this=0x7f02e63beb38) at ../../include/QtQml/5.15.0/QtQml/private/../../../../../src/qml/jsruntime/qv4string_p.h:167 #23 QV4::Lookup::setterFallback(QV4::Lookup*, QV4::ExecutionEngine*, QV4::Value&, QV4::Value const&) (l=, engine=0x563fea945940, object=..., value=...) at jsruntime/qv4lookup.cpp:497 #24 0x7f0306c667c2 in QV4::Runtime::SetLookupStrict::call(QV4::Function*, QV4::Value const&, i
[kmymoney] [Bug 424998] Reinvest dividend should include accompanying fee
https://bugs.kde.org/show_bug.cgi?id=424998 --- Comment #5 from Jack --- See if those fields show up once you select a category in the fees or interest dropdown. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 425036] Change done in Users kcm is applied despite the password dialog is canceled
https://bugs.kde.org/show_bug.cgi?id=425036 Nate Graham changed: What|Removed |Added Status|REOPENED|CONFIRMED Priority|NOR |VHI --- Comment #7 from Nate Graham --- Can confirm. We now get an error message, but the change is still applied anyway, somehow. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 426349] Layers manipulation is buggy
https://bugs.kde.org/show_bug.cgi?id=426349 amyspark changed: What|Removed |Added CC|a...@amyspark.me | Assignee|a...@amyspark.me |krita-bugs-n...@kde.org Status|ASSIGNED|CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 426014] arm64: implement fmadd and fmsub as Iop_MAdd/Sub instead of Iop_Add plus Iop_Mul
https://bugs.kde.org/show_bug.cgi?id=426014
--- Comment #1 from Mark Wielaard ---
Created attachment 132242
--> https://bugs.kde.org/attachment.cgi?id=132242&action=edit
arm64 VEX backend support for Iop_M{Add,Sub}F{32,64} to fmadd and fmsub
Sassha was experimenting with turning the fmadd/fmsub into Iop_MAdd/Sub only to
discover the VEX arm64 backend doesn't accept those Iops. This patch attempts
to implement them in the backend. It compiles but it is totally untested
otherwise.
--
You are receiving this mail because:
You are watching all bug changes.
[neon] [Bug 427493] Kwin crashes after login with symbol lookup error
https://bugs.kde.org/show_bug.cgi?id=427493 --- Comment #1 from terce...@gmail.com --- In the forum-thread the user "markfergy" traced the error back to the "libkwaylandserver5" package. Downgrading the package solved the issue: "sudo apt-get install libkwaylandserver5=5.19.5-0xneon+20.04+focal+build10" -- You are receiving this mail because: You are watching all bug changes.
