[kmymoney] [Bug 425363] Add new category - KMM crashes
https://bugs.kde.org/show_bug.cgi?id=425363 --- Comment #2 from Peter Richards --- (In reply to Thomas Baumgart from comment #1) > 5.0.6 has been released almost exactly a year ago (see > https://kmymoney.org/2019/08/18/kmymoney-5-0-6-released.html) and has been > superseded by three update versions in the meantime. > > If those are not available in your distribution, please try to see if using > the AppImage version (KMyMoney 5.1.0) solves the problem. You can download > and run it without uninstalling your current version. See > https://kmymoney.org/appimage.html for details how easy that is. > > We look forward to your reply if that solves the problem. I downloaded the AppImage yesterday. Then today I tried adding a new category via KMM (not with AppImage) and it worked okay. Was able to add some more test categories under the same heirarchy as before ? Why did that work now ? Anyway, used the AppImage and was able to successfully add a new (sub) category. Do I continue to use KMM as previously, or now use AppImage ? I assume there is no 'safe' method to install/use the libraries that AppImage is using, as there could well be library clashes, is that correct ? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 392731] Allow two clicks to rename items like in Dolphin
https://bugs.kde.org/show_bug.cgi?id=392731 --- Comment #2 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/plasma/plasma-desktop/-/merge_requests/114 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 423014] kwin_x11 black screen with Depth 30 and compositing (intel and amdgpu)
https://bugs.kde.org/show_bug.cgi?id=423014 David Kredba changed: What|Removed |Added CC||nheghathivhis...@gmail.com --- Comment #6 from David Kredba --- I am affected by the same. Gentoo ~amd64, amdgpu. Compositor is allowed to start with KDE. KDE Plasma Version: 5.19.4 KDE Frameworks Version: 5.73.0 Qt Version: 5.15.0 mesa: 20.2.0_rc2 libdrm: 2.4.102 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 424860] No EXIF display on CR3 images
https://bugs.kde.org/show_bug.cgi?id=424860 --- Comment #3 from caulier.gil...@gmail.com --- Git commit c5afd10f76b1dc89d30cf022ac2ce1728823740a by Gilles Caulier. Committed on 16/08/2020 at 05:46. Pushed by cgilles into branch 'master'. DMetadata::libraw loader: if RAW file contains XMP data, pass the XMP byte-array extracted by libraw to DMetadata instance M +7-0core/libs/metadataengine/dmetadata/dmetadata_libraw.cpp M +2-0core/libs/rawengine/drawdecoder_p.cpp M +2-1core/libs/rawengine/drawinfo.cpp M +6-0core/libs/rawengine/drawinfo.h https://invent.kde.org/graphics/digikam/commit/c5afd10f76b1dc89d30cf022ac2ce1728823740a -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 425359] First face tag moves intermittently
https://bugs.kde.org/show_bug.cgi?id=425359 --- Comment #5 from Maik Qualmann --- Not in the camera settings of the camera, but in the digiKam camera settings in the digiKam setup. ((:-)) In the Renaming section of the import tool you will see a link stating whether metadata is being used. The link takes you to the digiKam camera settings under Behavior there is the option. Maik -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 425404] Digikam crash when making a maintenance
https://bugs.kde.org/show_bug.cgi?id=425404 caulier.gil...@gmail.com changed: What|Removed |Added CC||caulier.gil...@gmail.com Component|general |Maintenance-Engine --- Comment #1 from caulier.gil...@gmail.com --- It crash in qDebug message handling from Qt. Your system probably dispatch user space application traces to log files. This problem have been fixed in last stable digiKam 7.0.0. Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 422426] Implement Wayland Primary Selection Protocol bridge with XWayland
https://bugs.kde.org/show_bug.cgi?id=422426 --- Comment #3 from ber...@codewiz.org --- Is there any hack / workaround we could put in place if GTK takes their time to add zwp_primary_selection? This is quite a showstopper for moving to Wayland, at least for me. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 422426] Implement Wayland Primary Selection Protocol bridge with XWayland
https://bugs.kde.org/show_bug.cgi?id=422426 ber...@codewiz.org changed: What|Removed |Added CC||ber...@codewiz.org --- Comment #2 from ber...@codewiz.org --- Perhaps this is the cause of this bug I'm seeing in Wayland sessions. How to reproduce: 1. select any text in a Qt app such as konsole or kate 2. middle-click in a GTK app such as Chrome or Tilix Expected result: pastes the text selected at (1) Actual result: pastes the last selection made in any GTK app -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 425411] Cancelling KDE Neon 20.04 Focal Fossa upgrade results in broken Flatpak and System Information
https://bugs.kde.org/show_bug.cgi?id=425411 --- Comment #1 from Ben --- After rebooting, the system almost unusable. The login screen will show a new interface but I cannot log in because the Enter key does not let me submit the password. Also it defaults to the on screen keyboard. Even when I use the onscreen keyboard, clicking the Enter button does not work. I can still press CTRL+ALT+F2 to get to a console screen and log in. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 424879] plasmashell aborted shortly after logging in with the error The Wayland connection experienced a fatal error: Invalid argument
https://bugs.kde.org/show_bug.cgi?id=424879 Matt Fagnani changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #4 from Matt Fagnani --- I installed plasma-wayland-protocols-1.1.1-1.fc33. I have seen other plasmashell crashes since then, but not with this specific error. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 425411] New: Cancelling KDE Neon 20.04 Focal Fossa upgrade results in broken Flatpak and System Information
https://bugs.kde.org/show_bug.cgi?id=425411 Bug ID: 425411 Summary: Cancelling KDE Neon 20.04 Focal Fossa upgrade results in broken Flatpak and System Information Product: neon Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: neon-b...@kde.org Reporter: ben...@protonmail.com CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- SUMMARY Cancelling KDE Neon 20.04 Focal Fossa upgrade results in broken Flatpak and System Information. STEPS TO REPRODUCE 1. click the upgrade icon in system tray to initiate the 20.04 upgrade screen and let it download but don't actually install anything. 2. When the upgrade screen displays what would be removed, installed, etc, then click on Cancel to not proceed. OBSERVED RESULT Afterwards, flatpak is no longer installed and I cannot reinstall it nor run my flatpak apps. Also the About System or System Information no longer appear in the Start menu. ~$ sudo apt install flatpak [sudo] password for user: Reading package lists... Done Building dependency tree Reading state information... Done Starting pkgProblemResolver with broken count: 1 Starting 2 pkgProblemResolver with broken count: 1 Investigating (0) flatpak:amd64 < none -> 1.6.2-1+18.04+bionic+build5 @rc puN Ib > Broken flatpak:amd64 Depends on bubblewrap:amd64 < 0.2.1-1ubuntu0.1 @ii mK > (>= 0.4.0) Considering bubblewrap:amd64 0 as a solution to flatpak:amd64 Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: flatpak : Depends: bubblewrap (>= 0.4.0) Recommends: xdg-desktop-portal (>= 1.6) Recommends: xdg-desktop-portal-gtk (>= 1.6) or xdg-desktop-portal-backend E: Unable to correct problems, you have held broken packages. ~$ sudo apt install bubblewrap Reading package lists... Done Building dependency tree Reading state information... Done bubblewrap is already the newest version (0.2.1-1ubuntu0.1). Starting pkgProblemResolver with broken count: 0 Starting 2 pkgProblemResolver with broken count: 0 Done The following packages were automatically installed and are no longer required: appmenu-gtk-module-common appmenu-gtk2-module appmenu-gtk3-module drkonqi fonts-wine gir1.2-gdesktopenums-3.0 gnome-desktop3-data gnome-session-common ibus-table ibus-table-emoji ieee-data kde-style-oxygen-qt5 kded5 kgamma5 kuserfeedback-doc lib32gcc1 libappmenu-gtk2-parser0 libappmenu-gtk3-parser0 libappstream-glib8 libc6-i386 libcolorcorrect5 libgps23 libkf5emoticons-bin libkf5emoticons-data libkf5emoticons5 libkfontinst5 libkfontinstui5 libksysguardsensorfaces1 libksysguardsensors1 libkuserfeedbackcore1 libnotificationmanager1 libostree-1-1 liboxygenstyle5-5 liboxygenstyleconfig5-5 libpam-kwallet-common libpam-kwallet5 libpipewire-0.2-1 libplasma-geolocation-interface5 libqalculate14 libqalculate14-data libqt5webengine5 libscim8v5 libtaskmanager6 libweather-ion7 libwine-development libxcb-record0 pipewire plasma-desktop-data plasma-integration plasma-workspace-wallpapers python-notify python3-distro python3-evdev python3-setproctitle qdbus-qt5 qml-module-org-kde-activities qml-module-org-kde-kholidays qml-module-org-kde-ksysguard qml-module-org-kde-kwindowsystem qml-module-org-kde-quickcharts qml-module-org-kde-solid qml-module-org-kde-userfeedback qml-module-qt-labs-folderlistmodel qml-module-qt-labs-settings qml-module-qtwebengine sddm socat winetricks xdg-dbus-proxy Use 'sudo apt autoremove' to remove them. 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. ~$ sudo apt-get install xdg-desktop-portal Reading package lists... Done Building dependency tree Reading state information... Done Starting pkgProblemResolver with broken count: 0 Starting 2 pkgProblemResolver with broken count: 0 Done The following packages were automatically installed and are no longer required: appmenu-gtk-module-common appmenu-gtk2-module appmenu-gtk3-module drkonqi fonts-wine gir1.2-gdesktopenums-3.0 gnome-desktop3-data gnome-session-common ibus-table ibus-table-emoji ieee-data kde-style-oxygen-qt5 kded5 kgamma5 kuserfeedback-doc lib32gcc1 libappmenu-gtk2-parser0 libappmenu-gtk3-parser0 libappstream-glib8 libc6-i386 libcolorcorrect5 libgps23 libkf5emoticons-bin libkf5emoticons-data libkf5emoticons5 libkfontinst5 libkfontinstui5 libksysguardsensorfaces1 libksysguardsensors1 libkuserfeedbackcore1 libnotificationmanager1 libostree-1-1 liboxygenstyle5-5 liboxygenstyleconfig5-5 libpam-kw
[systemsettings] [Bug 315626] kcm_mouse (cursortheme): add cursor theme choice to ~/.Xresources
https://bugs.kde.org/show_bug.cgi?id=315626 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #5 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 424879] plasmashell aborted shortly after logging in with the error The Wayland connection experienced a fatal error: Invalid argument
https://bugs.kde.org/show_bug.cgi?id=424879 --- 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.
[konsole] [Bug 425408] Vertical blue line appears at the left side of window when scrolling in Konsole 20.08.
https://bugs.kde.org/show_bug.cgi?id=425408 Benjamin Smith changed: What|Removed |Added Status|RESOLVED|CLOSED -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 425174] global menu widget doesn't have panning between sections
https://bugs.kde.org/show_bug.cgi?id=425174 D. Debnath changed: What|Removed |Added CC||d_debn...@outlook.com Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #1 from D. Debnath --- I can confirm this. See this reddit thread: https://www.reddit.com/r/kde/comments/i8tvq7/global_menu_padding_broken/ -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 425056] KWin crashes/dies after resume from sleep
https://bugs.kde.org/show_bug.cgi?id=425056 --- Comment #5 from Joe --- OK, so, an update: The system settings issue never went away - it always has the black side bar after resume. The compositing being broken, however, did seem to fix itself - until I resumed today, at least, and now the compositor always breaks after resume again. I have yet to try to ree-nable the screen locker, though, and see if the black screen w/ cursor persists. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 425056] KWin crashes/dies after resume from sleep
https://bugs.kde.org/show_bug.cgi?id=425056 --- Comment #4 from Joe --- Created attachment 130905 --> https://bugs.kde.org/attachment.cgi?id=130905&action=edit Updated segfault on resume -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 425410] New: Names of tag categories suddenly have superfluous ampersands added to them
https://bugs.kde.org/show_bug.cgi?id=425410 Bug ID: 425410 Summary: Names of tag categories suddenly have superfluous ampersands added to them Product: kphotoalbum Version: 5.7.0 Platform: Debian testing OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Annotation Dialog Assignee: kpab...@willden.org Reporter: thinksimi...@gmail.com Target Milestone: --- SUMMARY After upgrading to kphotoalbum 5.7.0 via Debian package, all existing tag categories have their names display like so: "Subjects" is now "S&ubjects" "Tags" is now "Ta&gs" "Places" is now "&Places" "Events" is now "E&vents" "Trips" is now "T&rips" "Taken by" is now "T&aken by" "Rating is now "Rat&ing" Additionally, the built-in "Description" field now appears as "D&escription" SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.17.5-3 KDE Frameworks Version: 5.70.0 Qt Version: 5.14.2 -- You are receiving this mail because: You are watching all bug changes.
[kactivitymanagerd] [Bug 425409] After switching between different activities and making some modifications, the switching will default to abnormal activities
https://bugs.kde.org/show_bug.cgi?id=425409 --- Comment #2 from jack9603301 --- Comment on attachment 130904 --> https://bugs.kde.org/attachment.cgi?id=130904 b If you do the following: 1. Switch to new activity area 2.Perform some operations 3. Switch back to default activity 4. Force logout and delete the new activity area What will happen is as shown in Figure b -- You are receiving this mail because: You are watching all bug changes.
[kactivitymanagerd] [Bug 425409] After switching between different activities and making some modifications, the switching will default to abnormal activities
https://bugs.kde.org/show_bug.cgi?id=425409 --- Comment #1 from 欧阳春晖 --- Created attachment 130904 --> https://bugs.kde.org/attachment.cgi?id=130904&action=edit b If you do the following: 1. Switch to new activity area 2.Perform some operations 3. Switch back to default activity 4. Forcibly log out and delete new events What will happen is as shown in Figure b -- You are receiving this mail because: You are watching all bug changes.
[kactivitymanagerd] [Bug 425409] New: After switching between different activities and making some modifications, the switching will default to abnormal activities
https://bugs.kde.org/show_bug.cgi?id=425409 Bug ID: 425409 Summary: After switching between different activities and making some modifications, the switching will default to abnormal activities Product: kactivitymanagerd Version: 5.18.5 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: ivan.cu...@kde.org Reporter: jack9603...@163.com CC: plasma-b...@kde.org Target Milestone: --- Created attachment 130903 --> https://bugs.kde.org/attachment.cgi?id=130903&action=edit a After I did the following: 1. Switch to new activity area 2. Modify desktop configuration 3 Switch back to default activity What will happen is as shown in Figure a -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 406130] Keyboard shortcut for wallpaper change
https://bugs.kde.org/show_bug.cgi?id=406130 mattbu...@protonmail.com changed: What|Removed |Added CC||mattbu...@protonmail.com --- Comment #2 from mattbu...@protonmail.com --- I'm also hoping this can be implemented. I've spent some time looking for a acceptable workaround and there isn't a good one I can see. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 425408] Vertical blue line appears at the left side of window when scrolling in Konsole 20.08.
https://bugs.kde.org/show_bug.cgi?id=425408 Benjamin Smith changed: What|Removed |Added Resolution|FIXED |NOT A BUG --- Comment #1 from Benjamin Smith --- I'm sorry. This is a new feature called "Highlight the lines coming into view." It can be disabled in the Profile settings under Scrolling. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 425408] Vertical blue line appears at the left side of window when scrolling in Konsole 20.08.
https://bugs.kde.org/show_bug.cgi?id=425408 Benjamin Smith changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 425408] New: Vertical blue line appears at the left side of window when scrolling in Konsole 20.08.
https://bugs.kde.org/show_bug.cgi?id=425408 Bug ID: 425408 Summary: Vertical blue line appears at the left side of window when scrolling in Konsole 20.08. Product: konsole Version: 20.08.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: emulation Assignee: konsole-de...@kde.org Reporter: bsmith7...@gmail.com Target Milestone: --- Created attachment 130902 --> https://bugs.kde.org/attachment.cgi?id=130902&action=edit Screenshot of Konsole window with the blue line visible. SUMMARY A blue line appears at the left side of the Konsole window. I am running Arch Linux, kernel 5.8.1, Qt 5.15, Plasma 5.15.4, Frameworks 5.73, Intel UHD graphics 620. This glitch started after the upgrade to KDE Applications 20.08. STEPS TO REPRODUCE 1. Allow the Konsole window to accumulate enough text to scroll. 2. Scroll upward and downward in the window. OBSERVED RESULT A blue line appears to the left of the text in the Konsole window. The shade of blue varies while scrolling. Usually, the line runs from top to bottom of the window. Sometimes, the line is only at one section of the window. EXPECTED RESULT No vertical line of various shades of blue to the left of Konsole text. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux, kernel 5.8.1 (available in About System) KDE Plasma Version: 5.19.4 KDE Frameworks Version: 5.73 Qt Version: 5.15 -- You are receiving this mail because: You are watching all bug changes.
[kcharselect] [Bug 425365] KCharselect when in full-screen mode, the panel overlaps some parts of KCharselect.
https://bugs.kde.org/show_bug.cgi?id=425365 --- Comment #3 from Christoph Feck --- Oh, indeed I see Fullscreen mode is disabled for KCalc. Any other KDE application you tried? I don't see anything special in KCharSelect that should make it behave differently than other KDE applications. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 425397] kdeinit5 crash each time I launch Dolphin
https://bugs.kde.org/show_bug.cgi?id=425397 Christoph Feck changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |BACKTRACE --- Comment #1 from Christoph Feck --- Please add the backtrace for the crash. For more information, please see 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.
[frameworks-plasma] [Bug 424076] PlasmaComponents3.ComboBox closes popup on click release when editable=true
https://bugs.kde.org/show_bug.cgi?id=424076 --- Comment #3 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/frameworks/qqc2-desktop-style/-/merge_requests/19 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 425407] Notifications open in the middle of the panel if it's visibility is set to "auto hide"
https://bugs.kde.org/show_bug.cgi?id=425407 twinshadows...@gmail.com changed: What|Removed |Added Summary|Simple menu opens in the|Notifications open in the |middle of the panel if it's |middle of the panel if it's |visibility is set to "auto |visibility is set to "auto |hide" |hide" Component|general |Panel Version|unspecified |5.19.4 Product|plasma-simplemenu |plasmashell Target Milestone|--- |1.0 Assignee|h...@kde.org|plasma-b...@kde.org Platform|Other |openSUSE RPMs --- Comment #1 from twinshadows...@gmail.com --- It seems that it happens with all notifications -- You are receiving this mail because: You are watching all bug changes.
[plasma-simplemenu] [Bug 425407] New: Simple menu opens in the middle of the panel if it's visibility is set to "auto hide"
https://bugs.kde.org/show_bug.cgi?id=425407 Bug ID: 425407 Summary: Simple menu opens in the middle of the panel if it's visibility is set to "auto hide" Product: plasma-simplemenu Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: h...@kde.org Reporter: twinshadows...@gmail.com CC: plasma-b...@kde.org Target Milestone: --- Created attachment 130901 --> https://bugs.kde.org/attachment.cgi?id=130901&action=edit screenshot STEPS TO REPRODUCE 1. Set panel's visibility to auto hide 2. Open the menu OBSERVED RESULT Menu opens at the middle of the panel EXPECTED RESULT Menu opens above the panel SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20200813 KDE Plasma Version: 5.19.4 KDE Frameworks Version: 5.73.0 Qt Version: 5.15.0 Kernel Version: 5.8.0-1-default OS Type: 64-bit -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 425406] New: Effects and title clips are one frame less
https://bugs.kde.org/show_bug.cgi?id=425406 Bug ID: 425406 Summary: Effects and title clips are one frame less Product: kdenlive Version: 20.08.0 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: Effects & Transitions Assignee: vpi...@kde.org Reporter: czart.and...@gmail.com Target Milestone: --- SUMMARY Add a title clip to the project bin, and the length is 00:04.59 while 00:05.00 is set in the settings. Also, when you add the fade effects, the effects are shorter by one frame. Here is a video about it: https://drive.google.com/file/d/1OTB_ji2j5YrxHERvqZN9GZK84Ie3KRUy/view?usp=sharing STEPS TO REPRODUCE 1. open a new project 2. create a title clip 3. add the title clip to the timeline, add a fade out effect OBSERVED RESULT the added title clip is 4.59 long instead of 5.00, also the fade out effect is shorter by 1 frame EXPECTED RESULT The title clip and the effect should be exactly as long as it is set in the kdenlive settings: 00:05.00 and 00:03.00 SOFTWARE/OS VERSIONS Windows: Win 10 current Kdenlive: 20.08.0 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 423526] "Switch user" functionality has disappeared from Kicker and Kickoff
https://bugs.kde.org/show_bug.cgi?id=423526 dyeg...@gmail.com changed: What|Removed |Added CC||dyeg...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 425405] New: systemsettings crashes when adding a new script to autostart
https://bugs.kde.org/show_bug.cgi?id=425405 Bug ID: 425405 Summary: systemsettings crashes when adding a new script to autostart Product: systemsettings Version: unspecified Platform: Compiled Sources OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: k...@sdht.in Target Milestone: --- Application: systemsettings5 (5.19.80) (Compiled from sources) Qt Version: 5.15.0 Frameworks Version: 5.74.0 Operating System: Linux 5.8.1-arch1-1 x86_64 Windowing system: X11 Distribution: Arch Linux -- Information about the crash: I was testing out the new autostart implementation. On adding a new script, I'm getting a crash. I tried adding 2 "scripts" (Add.. -> Add login script", one a random .conf file and another .sh file. System settings crashes on selection both files, but after restarting, I can see that the .sh file has been added to the list. Another issue I noted is that "Add login script" is missing the option to select between pre-startup (~/.config/plasma-workspace/env) vs startup (~/.config/autostart-scripts). Is this expected or a regression? I depend on a pre-startup script to start a ssh-agent session. -- Backtrace: Application: System Settings (systemsettings5), signal: Segmentation fault Content of s_kcrashErrorMessage: (null) [KCrash Handler] #6 0x7f968e4f3f8a in QUrl::path(QFlags) const () at /usr/lib/libQt5Core.so.5 #7 0x7f968e4f4246 in QUrl::fileName(QFlags) const () at /usr/lib/libQt5Core.so.5 #8 0x7f964b2411c6 in operator() (theJob=0x55a325fe7da0, __closure=0x55a32840a940) at /usr/include/qt/QtCore/qflags.h:121 #9 QtPrivate::FunctorCall, QtPrivate::List, void, AutostartModel::addScript(const QUrl&, AutostartModel::AutostartEntrySource):: >::call (arg=, f=...) at /usr/include/qt/QtCore/qobjectdefs_impl.h:146 #10 QtPrivate::Functor, 1>::call, void> (arg=, f=...) at /usr/include/qt/QtCore/qobjectdefs_impl.h:256 #11 QtPrivate::QFunctorSlotObject, 1, QtPrivate::List, void>::impl(int, QtPrivate::QSlotObjectBase *, QObject *, void **, bool *) (which=, this_=0x55a32840a930, r=, a=, ret=) at /usr/include/qt/QtCore/qobjectdefs_impl.h:443 #12 0x7f968e5e4a26 in () at /usr/lib/libQt5Core.so.5 #13 0x7f968e9110aa in KJob::finished(KJob*, KJob::QPrivateSignal) (this=this@entry=0x55a325fe7da0, _t1=, _t1@entry=0x55a325fe7da0, _t2=...) at /usr/src/debug/build/src/lib/KF5CoreAddons_autogen/include/moc_kjob.cpp:555 #14 0x7f968e911cee in KJob::finishJob(bool) (this=0x55a325fe7da0, emitResult=) at /usr/src/debug/kcoreaddons/src/lib/jobs/kjob.cpp:93 #15 0x7f968e5e4a26 in () at /usr/lib/libQt5Core.so.5 #16 0x7f968e9111fd in KJob::result(KJob*, KJob::QPrivateSignal) (this=this@entry=0x55a326835390, _t1=, _t1@entry=0x55a326835390, _t2=...) at /usr/src/debug/build/src/lib/KF5CoreAddons_autogen/include/moc_kjob.cpp:576 #17 0x7f968e911d1c in KJob::finishJob(bool) (this=0x55a326835390, emitResult=) at /usr/src/debug/kcoreaddons/src/lib/jobs/kjob.cpp:96 #18 0x7f968e5e4a26 in () at /usr/lib/libQt5Core.so.5 #19 0x7f968c1937d6 in KIO::SlaveInterface::dispatch(int, QByteArray const&) (this=0x55a327528c50, _cmd=104, rawdata=...) at /usr/src/debug/kio/src/core/slaveinterface.cpp:149 #20 0x7f968c191f3a in KIO::SlaveInterface::dispatch() (this=0x55a327528c50) at /usr/src/debug/kio/src/core/slaveinterface.cpp:78 #21 0x7f968c195a3b in KIO::Slave::gotInput() (this=0x55a327528c50) at /usr/src/debug/kio/src/core/slave.cpp:402 #22 0x7f968e5e4a26 in () at /usr/lib/libQt5Core.so.5 #23 0x7f968e5da1d2 in QObject::event(QEvent*) () at /usr/lib/libQt5Core.so.5 #24 0x7f968f1f6702 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #25 0x7f968e5ad7ba in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #26 0x7f968e5b02a3 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /usr/lib/libQt5Core.so.5 #27 0x7f968e606cf4 in () at /usr/lib/libQt5Core.so.5 #28 0x7f968c2ae43c in g_main_context_dispatch () at /usr/lib/libglib-2.0.so.0 #29 0x7f968c2fc1d9 in () at /usr/lib/libglib-2.0.so.0 #30 0x7f968c2ad221 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #31 0x7f968e606331 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #32 0x7f968e5ac13c in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #33 0x7f968e5b45c4 in QCoreApplication::exec() () at /usr/lib/libQt5Core.so.5 #34 0x55a3248e1806 in main(int, char**) (argc=, argv=0x7ffcef914450) at /usr/src/debug/systemsettings/app/main.cpp:168 [Inferior 1 (process 30068) detached] Possible duplicates by query: bug 425205, bug 424644, bug 423766, bug 423719, bug 423459. Reported using DrKonqi -- You are receiving
[krita] [Bug 425199] Program closed down after I click on a tool
https://bugs.kde.org/show_bug.cgi?id=425199 Eoin O'Neill changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #9 from Eoin O'Neill --- No worries Lauren, glad I could help. I am closing this bug for now as it seems like this is resolved. *** This bug has been marked as a duplicate of bug 424037 *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 424037] Animation: Crash when selecting a range of frames that's not visible on startup in the timeline docker
https://bugs.kde.org/show_bug.cgi?id=424037 Eoin O'Neill changed: What|Removed |Added CC||lauren16ke...@gmail.com --- Comment #12 from Eoin O'Neill --- *** Bug 425199 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 425344] Pop up palette not showing brushes on android
https://bugs.kde.org/show_bug.cgi?id=425344 Anna Medonosova changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED CC||anna.medonosova@protonmail. ||com --- Comment #1 from Anna Medonosova --- I can reproduce this on my tablet. I have also tried changing the number of palette presets, it does not help. When the configuration is reset, default presets appear on the palette. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 425398] new-tab does not open a new tab, opens a new window
https://bugs.kde.org/show_bug.cgi?id=425398 Patafurdio changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 425398] new-tab does not open a new tab, opens a new window
https://bugs.kde.org/show_bug.cgi?id=425398 --- Comment #3 from Patafurdio --- (In reply to tcanabrava from comment #2) > Please go to konsole settings -> General -> Run all konsole windows in a > single session. > > This happens because a fix for konsole multi-session mode changed the > behavior, and now if konsole runs with multiple sessions there's no way to > open a tab in a specified PID. > > *currently* this is considered more an annoyance (as it's fixed by a simple > settings change) but we are looking for alternatives on how to properly fix > this even in multiple PID's. Thanks, it works. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 416257] mailto feature does not work anymore
https://bugs.kde.org/show_bug.cgi?id=416257 Alexander Potashev changed: What|Removed |Added CC||aspotas...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 416940] Scrollback limit in megabytes
https://bugs.kde.org/show_bug.cgi?id=416940 --- Comment #6 from Alexander Potashev --- > random security key I meant: random encryption [private] key -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 416940] Scrollback limit in megabytes
https://bugs.kde.org/show_bug.cgi?id=416940 --- Comment #5 from Alexander Potashev --- > random security key I meant: random encryption [private] key -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 416940] Scrollback limit in megabytes
https://bugs.kde.org/show_bug.cgi?id=416940 --- Comment #4 from Alexander Potashev --- (In reply to Kurt Hindenburg from comment #3) > I've abandoned that patch; it would better to use an OS encrypted > folder/file/HD This would be less secure (than a random security key per Konsole tab) because a user typically has access to the encrypted files, therefore the Konsole scrollback can be recovered by an attacker in a case when the encryption key is revealed. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 424760] KOrganiser crash when changing calendar of an event
https://bugs.kde.org/show_bug.cgi?id=424760 Ahmad Samir changed: What|Removed |Added Resolution|--- |WAITINGFORINFO CC||a.samir...@gmail.com Status|REPORTED|NEEDSINFO --- Comment #1 from Ahmad Samir --- Can you still reproduce this issue? I tested with current git master of kdepim-runtime, didn't hit a crash. -- 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 Fonic changed: What|Removed |Added CC||fonic.max...@live.com --- Comment #22 from Fonic --- Same issues here: - system settings displays black box to the left - screen locker only shows mouse cursor, have to unlock manually from console Patch '0001-Use-glXGetProcAddress-for-context-creation.patch' does not seem to have any effect. Gentoo Linux (amd64, stable) Linux Kernel 5.4.48 NVIDIA drivers 450.57 KWin 5.18.5 Qt 5.14.2 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 425398] new-tab does not open a new tab, opens a new window
https://bugs.kde.org/show_bug.cgi?id=425398 tcanabr...@kde.org changed: What|Removed |Added CC||tcanabr...@kde.org --- Comment #2 from tcanabr...@kde.org --- Please go to konsole settings -> General -> Run all konsole windows in a single session. This happens because a fix for konsole multi-session mode changed the behavior, and now if konsole runs with multiple sessions there's no way to open a tab in a specified PID. *currently* this is considered more an annoyance (as it's fixed by a simple settings change) but we are looking for alternatives on how to properly fix this even in multiple PID's. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 388680] Untranslatable " (auto-detected)" in camera name
https://bugs.kde.org/show_bug.cgi?id=388680 --- Comment #5 from Alexander Potashev --- The string is still hard-coded in English: https://invent.kde.org/graphics/digikam/-/blob/master/core/utilities/import/views/cameranamehelper.cpp#L32 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 409381] Put "Unmount" in the first item of context menu again
https://bugs.kde.org/show_bug.cgi?id=409381 --- Comment #4 from Alexander Potashev --- I don't use the Unmount option that often anymore, so I'm okay with keeping the current menu layout. Maybe running a survey (e.g. through Google Forms) would help make a long term decision. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 425343] [Wayland] Keyboard Layout applet doesn't follow actual layout switching
https://bugs.kde.org/show_bug.cgi?id=425343 Alexander Potashev changed: What|Removed |Added CC||aspotas...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 425398] new-tab does not open a new tab, opens a new window
https://bugs.kde.org/show_bug.cgi?id=425398 Axel changed: What|Removed |Added CC||navarroa...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 425404] New: Digikam crash when making a maintenance
https://bugs.kde.org/show_bug.cgi?id=425404 Bug ID: 425404 Summary: Digikam crash when making a maintenance Product: digikam Version: 6.4.0 Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: digikam-bugs-n...@kde.org Reporter: chabot.daniel...@gmail.com Target Milestone: --- Application: digikam (6.4.0) Qt Version: 5.13.2 Frameworks Version: 5.70.0 Operating System: Linux 5.7.11-100.fc31.x86_64 x86_64 Windowing system: X11 Distribution: Fedora 31 (KDE Plasma) -- Information about the crash: - What I was doing when the application crashed: I don't see a directory in my album so y make a maintenance and select just lok for new photos and digikam crashe. When I drag one or more photos or videos from Digikam to an external program and select move, Dolphin for example, and select move, these photo dosen't desappear from digikam until I make a maintenance on digikam DB. -- Backtrace: Application: digiKam (digikam), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f71e155c940 (LWP 6655))] Thread 18 (Thread 0x7f714bfff700 (LWP 6730)): #0 0x7f71f1883d45 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f71eaf714ac in base::ConditionVariable::Wait() () at /lib64/libQt5WebEngineCore.so.5 #2 0x7f71eaf71f90 in base::WaitableEvent::TimedWaitUntil(base::TimeTicks const&) () at /lib64/libQt5WebEngineCore.so.5 #3 0x7f71eaf720bf in base::WaitableEvent::Wait() () at /lib64/libQt5WebEngineCore.so.5 #4 0x7f71eaf29c56 in base::internal::SchedulerWorker::Delegate::WaitForWork(base::WaitableEvent*) () at /lib64/libQt5WebEngineCore.so.5 #5 0x7f71eaf2ceeb in base::internal::SchedulerWorker::RunWorker() () at /lib64/libQt5WebEngineCore.so.5 #6 0x7f71eaf2d454 in base::internal::SchedulerWorker::RunSharedWorker() () at /lib64/libQt5WebEngineCore.so.5 #7 0x7f71eaf7442a in base::(anonymous namespace)::ThreadFunc(void*) () at /lib64/libQt5WebEngineCore.so.5 #8 0x7f71f187d4e2 in start_thread () at /lib64/libpthread.so.0 #9 0x7f71f38d86c3 in clone () at /lib64/libc.so.6 Thread 17 (Thread 0x7f714b7fe700 (LWP 6700)): #0 0x7f71f38c943c in read () at /lib64/libc.so.6 #1 0x7f71f203f5af in g_wakeup_acknowledge () at /lib64/libglib-2.0.so.0 #2 0x7f71f1ff73b7 in g_main_context_check () at /lib64/libglib-2.0.so.0 #3 0x7f71f1ff7812 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #4 0x7f71f1ff79a3 in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #5 0x7f71f3e7a8a3 in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #6 0x7f71f3e2423b in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #7 0x7f71f3c74cd5 in QThread::exec() () at /lib64/libQt5Core.so.5 #8 0x7f71f3c75e26 in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #9 0x7f71f187d4e2 in start_thread () at /lib64/libpthread.so.0 #10 0x7f71f38d86c3 in clone () at /lib64/libc.so.6 Thread 16 (Thread 0x7f717d7fa700 (LWP 6683)): #0 0x7f71f1883d45 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f71eaf714ac in base::ConditionVariable::Wait() () at /lib64/libQt5WebEngineCore.so.5 #2 0x7f71eaf71f90 in base::WaitableEvent::TimedWaitUntil(base::TimeTicks const&) () at /lib64/libQt5WebEngineCore.so.5 #3 0x7f71eaf720bf in base::WaitableEvent::Wait() () at /lib64/libQt5WebEngineCore.so.5 #4 0x7f71eaf29c56 in base::internal::SchedulerWorker::Delegate::WaitForWork(base::WaitableEvent*) () at /lib64/libQt5WebEngineCore.so.5 #5 0x7f71eaf2ceeb in base::internal::SchedulerWorker::RunWorker() () at /lib64/libQt5WebEngineCore.so.5 #6 0x7f71eaf2d494 in base::internal::SchedulerWorker::RunDedicatedWorker() () at /lib64/libQt5WebEngineCore.so.5 #7 0x7f71eaf7442a in base::(anonymous namespace)::ThreadFunc(void*) () at /lib64/libQt5WebEngineCore.so.5 #8 0x7f71f187d4e2 in start_thread () at /lib64/libpthread.so.0 #9 0x7f71f38d86c3 in clone () at /lib64/libc.so.6 Thread 15 (Thread 0x7f717dffb700 (LWP 6682)): #0 0x7f71f385de0b in __lll_lock_wait_private () at /lib64/libc.so.6 #1 0x7f71f38457de in buffered_vfprintf () at /lib64/libc.so.6 #2 0x7f71f3842664 in __vfprintf_internal () at /lib64/libc.so.6 #3 0x7f71f38e6cf3 in __fprintf_chk () at /lib64/libc.so.6 #4 0x7f71e2426916 in event_logv_ () at /lib64/libevent-2.1.so.6 #5 0x7f71e2426ae9 in event_warn () at /lib64/libevent-2.1.so.6 #6 0x7f71e2428548 in epoll_dispatch () at /lib64/libevent-2.1.so.6 #7 0x7f71e241e0b5 in event_base_loop () at /lib64/libevent-2.1.so.6 #8 0x7f71eaf78298 in base::MessagePumpLibevent::Run(base::MessagePump::Delegate*) () at /lib64/libQt5WebEngineCore.so.5 #9 0x7f71eaf03517 i
[systemsettings] [Bug 425403] New: Standalone KCMs launched via shortcut on desktop have Wayland generic icon in window decoration and task switcher
https://bugs.kde.org/show_bug.cgi?id=425403 Bug ID: 425403 Summary: Standalone KCMs launched via shortcut on desktop have Wayland generic icon in window decoration and task switcher Product: systemsettings Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: bugsefor...@gmx.com Target Milestone: --- Created attachment 130900 --> https://bugs.kde.org/attachment.cgi?id=130900&action=edit screenshot STEPS TO REPRODUCE 1. open your apps laucnher and search for some KCM, let's say Global Theme 2. right-click on "global theme" search result and choose "Add to desktop" 3. launch Global Theme kcm via its icon created on desktop OBSERVED RESULT As we can see in the attached screenshot, the window decoration of the launched KCM has Wayland generic icon. Task switcher (alt+tab) shows the same icon. EXPECTED RESULT Window decoration and task switcher should show the same icon observed in the task manager. SOFTWARE/OS VERSIONS Operating System: KDE neon Unstable Edition KDE Plasma Version: 5.19.80 KDE Frameworks Version: 5.74.0 Qt Version: 5.14.2 -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 425402] Application Dashboard doesn't cover Plasma panel on Wayland
https://bugs.kde.org/show_bug.cgi?id=425402 Patrick Silva changed: What|Removed |Added Keywords||wayland -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 425402] New: Application Dashboard doesn't cover Plasma panel on Wayland
https://bugs.kde.org/show_bug.cgi?id=425402 Bug ID: 425402 Summary: Application Dashboard doesn't cover Plasma panel on Wayland Product: kdeplasma-addons Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Application Dashboard Assignee: h...@kde.org Reporter: bugsefor...@gmx.com CC: plasma-b...@kde.org Target Milestone: --- Created attachment 130899 --> https://bugs.kde.org/attachment.cgi?id=130899&action=edit screenshot STEPS TO REPRODUCE 1. open Application Dashboard on Wayland session 2. 3. OBSERVED RESULT as we can see in the attached screenshot, Application Dashboard doesn't cover Plasma panel EXPECTED RESULT Application Dashboard in full screen mode SOFTWARE/OS VERSIONS Operating System: KDE neon Unstable Edition KDE Plasma Version: 5.19.80 KDE Frameworks Version: 5.74.0 Qt Version: 5.14.2 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 425401] New: Audio playback during preview stopped working
https://bugs.kde.org/show_bug.cgi?id=425401 Bug ID: 425401 Summary: Audio playback during preview stopped working Product: kdenlive Version: 20.04.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: mrpuzzle1...@gmail.com Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. 100% failure rate 2. reboot system - still fails 100% 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 425400] The -o command line option is ignored
https://bugs.kde.org/show_bug.cgi?id=425400 tlemaillet changed: What|Removed |Added CC||t.lemail...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 425400] New: The -o command line option is ignored
https://bugs.kde.org/show_bug.cgi?id=425400
Bug ID: 425400
Summary: The -o command line option is ignored
Product: Spectacle
Version: 20.08.0
Platform: Archlinux Packages
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: General
Assignee: m...@baloneygeek.com
Reporter: t.lemail...@gmail.com
CC: k...@david-redondo.de
Target Milestone: ---
SUMMARY
Capturing an image from the command line with "$ spectacle -bo /tmp/test" does
not save the image at the specified location, it instead saves it at the
default location configured in the settings. ("$HOME/Pictures/Screenshots" in
my case)
STEPS TO REPRODUCE
Open a terminal and enter any valid spectacle command with the -o option
OBSERVED RESULT
Resulting image is saved at the default location
EXPECTED RESULT
Resulting image should be saved at the location specified with the -o option
SOFTWARE/OS VERSIONS
Operating System: Arch Linux
KDE Plasma Version: 5.19.4
KDE Frameworks Version: 5.73.0
Qt Version: 5.15.0
Kernel Version: 5.8.1-arch1-1
OS Type: 64-bit
ADDITIONAL NOTES
The previous working version I updated from was 20.04.3
--
You are receiving this mail because:
You are watching all bug changes.
[kwin] [Bug 425399] New: Moving/Resizing keyboard shortcut stop working after typing in a window
https://bugs.kde.org/show_bug.cgi?id=425399 Bug ID: 425399 Summary: Moving/Resizing keyboard shortcut stop working after typing in a window Product: kwin Version: 5.19.4 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: l...@app-gateway.nl Target Milestone: --- Created attachment 130898 --> https://bugs.kde.org/attachment.cgi?id=130898&action=edit Screen record After upgrading from 18.04 to 20.04, the keyboard shortcuts for moving/resizing the active window, for example, to the left side of the screen or to expand the window to full screen, stopped working for me. As soon as a window is opened, for example, the Konsole window, the keyboard shortcuts work, but as soon as the window receives input from the keyboard, the window title ceases to be active and the keyboard shortcuts stop working until the window is minimized and maximized again. STEPS TO REPRODUCE 1. Setup keyboard shortcut for moving/resizing windows (System Preferences=>Shortcuts=>KWin) 2. Open any window 3. Try moving/resizing with shortcuts (it will work) 4. Press any keys on your keyboard (at this point, the window title will become inactive) 5. Try moving/resizing with shortcuts again (it won't work anymore) 6. Minimize the window and maximize it 7. Try your shortcuts again (this will work again) Below I have attached a video that shows the problem. Operating System: KDE neon 5.19 KDE Plasma Version: 5.19.4 KDE Frameworks Version: 5.72.0 Qt Version: 5.14.2 Kernel Version: 5.4.0-42-generic OS Type: 64-bit Processors: 8 × Intel® Core™ i5-8265U CPU @ 1.60GHz Memory: 15.5 GiB of RAM Graphics Processor: GeForce MX130/PCIe/SSE2 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 425398] new-tab does not open a new tab, opens a new window
https://bugs.kde.org/show_bug.cgi?id=425398 --- Comment #1 from Patafurdio --- Downgraded to 20.04 and it works again.I have konsole-20.04.3-1-x86_64.pkg.tar.zst on my cache. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 425398] New: new-tab does not open a new tab, opens a new window
https://bugs.kde.org/show_bug.cgi?id=425398 Bug ID: 425398 Summary: new-tab does not open a new tab, opens a new window Product: konsole Version: 20.08.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: patafurdio@protonmail.ch Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. open konsole 2. konsole --new-tab -e /bin/sh -c "cd /media/; ./program.sh;" 3. konsole --new-tab -e /bin/sh -c "cd /media-other/; ./other-program.sh;" OBSERVED RESULT opens a new window in version 20.08 in the first time it is executed step number 2 opens a new window when executed step 3 EXPECTED RESULT to open a new window on step 2 but it should open new-tab (on second window) on step number 3, but instead opens a new window SOFTWARE/OS VERSIONS Linux: 5.8.1-arch1-1 KDE Plasma: 5.85.19.4 (available in About System) KDE Frameworks Version: 5.73.0 Qt Version: 5.15.0 ADDITIONAL INFORMATION usually open one konsole, paste several commands that open a second window and all other commands are in new-tabs on the second window. this was working fine before unti 20.04 but in 20.08 just opens new windows. I updated today my Arch Linux. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 424640] Handles for resizing a window work unreliably with Opera and Xorg
https://bugs.kde.org/show_bug.cgi?id=424640 --- Comment #7 from Patrick Silva --- right -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 356914] Add an option to don't start playing media when call ends
https://bugs.kde.org/show_bug.cgi?id=356914 Rijul Gulati changed: What|Removed |Added CC||gri...@protonmail.ch --- Comment #4 from Rijul Gulati --- I'd like to work on this one. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 424640] Handles for resizing a window work unreliably with Opera and Xorg
https://bugs.kde.org/show_bug.cgi?id=424640 --- Comment #6 from Alexander Shchadilov --- (In reply to Patrick Silva from comment #5) > humm, I can resize Opera 70.0.3728.106 on neon unstable by dragging any of > its borders, but it's hard to enter in resizing mode, mainly with > crappy/imprecise touchpad like mine. Just to be sure - that was in Xorg, right? -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 425397] New: kdeinit5 crash each time I launch Dolphin
https://bugs.kde.org/show_bug.cgi?id=425397 Bug ID: 425397 Summary: kdeinit5 crash each time I launch Dolphin Product: dolphin Version: unspecified Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: snake...@protonmail.com CC: kfm-de...@kde.org Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Open Dolphin in Sway OBSERVED RESULT kdeinit5 crash handler EXPECTED RESULT dolphin's open without kdeinit5 crash handler window SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Linux (available in About System) WM: swaywm Qt Version: 5.15 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 425369] Imported photo in album other than date taken
https://bugs.kde.org/show_bug.cgi?id=425369 --- Comment #5 from im...@juno.com --- (In reply to Maik Qualmann from comment #3) > We know the cause. The correct EXIF date is not available to us when > importing, as the file date is usually used when using the GPhotos driver. > You can try to activate the loading of the metadata in the camera settings > (this makes the connection slower). To fix this and other bugs related to > metadata, a major change to the import tool is required. We have to download > the temporary file first so that all metadata is available locally. > > Maik Well, it’s a slow connection vs spending personal time moving images to appropriate albums and renaming albums to appropriate names/dates. Can you suggest somewhere to read about how to activate loading of metadata in the camera settings? -- You are receiving this mail because: You are watching all bug changes.
[i18n] [Bug 423703] Edit menu Tamil translation error: Block Selection Mode
https://bugs.kde.org/show_bug.cgi?id=423703 Christoph Cullmann changed: What|Removed |Added Component|general |ta Assignee|kwrite-bugs-n...@kde.org|ssha...@yahoo.com CC||cullm...@kde.org Product|kate|i18n -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 425396] New: New folder named ":foo" always created in home dir
https://bugs.kde.org/show_bug.cgi?id=425396 Bug ID: 425396 Summary: New folder named ":foo" always created in home dir Product: dolphin Version: 19.12.3 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: na...@crans.org CC: kfm-de...@kde.org Target Milestone: --- When I try to create a new folder in any folder, if I give it a name starting with ':' (a colon), the folder is created under my home dir (/home/mylogin) instead of the current dir. Observed in Dolphin 19.04.3 (up-to-date Kubuntu 19.10) and 19.12.3 (Kubuntu 20.04). Same behavior in Konqueror. STEPS TO REPRODUCE 1. In Dolphin, open /tmp or any folder other than /home/mylogin 2. In the main area, right click > Create new > Folder 3. Type in ":Abc", Enter OBSERVED RESULT There is no :Abc folder in the current folder but there is an :Abc folder in /home/mylogin EXPECTED RESULT There is a :Abc folder in the current folder and no :Abc folder in /home/mylogin SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.4.0-42-generic (Kubuntu 20.04) (available in About System) KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.68.0 Qt Version: 5.12.8 -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 425394] Latest Neon User Edition ISO image is 18.04 based, not 20.04.
https://bugs.kde.org/show_bug.cgi?id=425394 jdally987 changed: What|Removed |Added CC||jdally...@gmail.com --- Comment #2 from jdally987 --- Created attachment 130897 --> https://bugs.kde.org/attachment.cgi?id=130897&action=edit md5sum.txt Yep same here - attached md5sum.txt from root of "neon-user-20200813-1119.iso" (sha256: 946123A877C1514E68E910A137DFB69E69D854DD447344A9962992DA6FB3DE14) -- You are receiving this mail because: You are watching all bug changes.
[i18n] [Bug 423705] Better Tamil translation of File -> New and 'Untitled'
https://bugs.kde.org/show_bug.cgi?id=423705 Christoph Cullmann changed: What|Removed |Added Assignee|kwrite-bugs-n...@kde.org|ssha...@yahoo.com Product|kate|i18n CC||cullm...@kde.org Component|general |ta -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 425264] Kate flickers when part of the window is outside display borders
https://bugs.kde.org/show_bug.cgi?id=425264 Christoph Cullmann changed: What|Removed |Added Assignee|kwrite-bugs-n...@kde.org|kwin-bugs-n...@kde.org CC||cullm...@kde.org Version|20.04.1 |5.18.5 Product|kate|kwin Component|general |general --- Comment #1 from Christoph Cullmann --- That is not something Kate itself will trigger. Might this be some issue with KWin or the graphics stack? -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 425367] Setting the indentation to "Normal" through the menu Tools->Indentation never sticks
https://bugs.kde.org/show_bug.cgi?id=425367 Christoph Cullmann changed: What|Removed |Added Resolution|--- |INTENTIONAL Status|REPORTED|RESOLVED CC||cullm...@kde.org --- Comment #1 from Christoph Cullmann --- If you want to alter this, you need to go to the settings -> editor component -> open/save there is the Mode/Filetypes tab, you can set there the default indentation behavior for the filetype. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 359813] images inserted in mail with CID are not displayed
https://bugs.kde.org/show_bug.cgi?id=359813 Wolfgang Bauer changed: What|Removed |Added CC||wba...@tmo.at --- Comment #14 from Wolfgang Bauer --- (In reply to Volker Helm from comment #13) > I'm sorry to open the bug again. > > The image of the CID will shown in text-view at the bottom of the mail. > > If you enter html-view, the image of the CID will not shown. For example > [cid:image001.png@01D66AF3.EA9EC840]. > But you can save the image to a file. > > Also the image will not shown, if you change to text-view again. > > I can send an example if needed. Might be the same as bug#423267 which should be fixed in kontact 5.15.0 (20.08.0). Which version are you using? -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 423267] Image Files Not Showing In Messages Again
https://bugs.kde.org/show_bug.cgi?id=423267 Wolfgang Bauer changed: What|Removed |Added CC||axel.br...@gmx.de --- Comment #4 from Wolfgang Bauer --- *** Bug 425393 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 425393] Embedded picture not displayed
https://bugs.kde.org/show_bug.cgi?id=425393 Wolfgang Bauer changed: What|Removed |Added Status|REPORTED|RESOLVED CC||wba...@tmo.at Resolution|--- |DUPLICATE --- Comment #1 from Wolfgang Bauer --- Sounds like bug#423267 that should be fixed in 5.15.0 (20.08.0). *** This bug has been marked as a duplicate of bug 423267 *** -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 425395] New: Synch touchpad settings with SDDM
https://bugs.kde.org/show_bug.cgi?id=425395 Bug ID: 425395 Summary: Synch touchpad settings with SDDM Product: systemsettings Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: kcm_sddm Assignee: k...@davidedmundson.co.uk Reporter: bugsefor...@gmx.com CC: plasma-b...@kde.org Target Milestone: --- SUMMARY By default cursor movement is slow when I use my touchpad then I adjust "pointer speed" slider in Touchpad kcm to improve it. Furthermore, I always enable "tap to click" feature. However, cursor movement is still slow and "Tap to click" does not work in SDDM. A way to also apply Touchpad settings to SDDM would be a nice usability improvement. SOFTWARE/OS VERSIONS Operating System: KDE neon Unstable Edition KDE Plasma Version: 5.19.80 KDE Frameworks Version: 5.74.0 Qt Version: 5.14.2 -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 425394] Latest Neon User Edition ISO image is 18.04 based, not 20.04.
https://bugs.kde.org/show_bug.cgi?id=425394 --- Comment #1 from Clay Weber --- Created attachment 130896 --> https://bugs.kde.org/attachment.cgi?id=130896&action=edit Image showing the output of lsb_release, as well as the iso file name -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 425394] Latest Neon User Edition ISO image is 18.04 based, not 20.04.
https://bugs.kde.org/show_bug.cgi?id=425394 Clay Weber changed: What|Removed |Added Summary|Latest ISO image|Latest Neon User Edition |20200813-1119 is 18.04 |ISO image is 18.04 based, |based |not 20.04. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 425394] New: Latest ISO image 20200813-1119 is 18.04 based
https://bugs.kde.org/show_bug.cgi?id=425394 Bug ID: 425394 Summary: Latest ISO image 20200813-1119 is 18.04 based Product: neon Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Live/Install images Assignee: neon-b...@kde.org Reporter: c...@claydoh.com CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- SUMMARY Downloading the ISO from the link on the KDE Neon website is a Bionic image STEPS TO REPRODUCE 1. Go to https://neon.kde.org/download 2. Click the link to download the User Edition Live/Install Image 3. Create live USB stick, or use in a virtual machine, and boot the image 4. Check the resulkt from the command : lsb_release -a OBSERVED RESULT Result shows a system based on Ubuntu 18.04 Bionic EXPECTED RESULT The image should be based on 20.04 Focal The last image version built was Focal based. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 419008] Always crash in Regional Setting within System Settings
https://bugs.kde.org/show_bug.cgi?id=419008 Wolfgang Bauer changed: What|Removed |Added CC||wba...@tmo.at --- Comment #33 from Wolfgang Bauer --- Well, the crash apparently only occured with Qt 5.13 or lower, as mentioned in bug#404518#c20 . But Plasma 5.19 requires Qt 5.14 as minimum anyway, so it's no wonder why it's not reproducible with that version anymore. Although I don't know about Qt 5.12.9, the last one I tried was 5.12.7 (as shipped in openSUSE Leap 15.2) where it did still crash. (until the kirigami change was reverted in the distribution package to avoid this crash) -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 425328] Forgets FiiO BTR5 DAC connected to USB after sleep
https://bugs.kde.org/show_bug.cgi?id=425328 --- Comment #6 from Rajinder Yadav --- Created attachment 130895 --> https://bugs.kde.org/attachment.cgi?id=130895&action=edit Not working after a while The following config setting work for a little while, have a louder audio and I would like to see it not stop working after 1 minute? -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 425328] Forgets FiiO BTR5 DAC connected to USB after sleep
https://bugs.kde.org/show_bug.cgi?id=425328 --- Comment #5 from Rajinder Yadav --- Created attachment 130894 --> https://bugs.kde.org/attachment.cgi?id=130894&action=edit Working config setting This is the only combination setting that seems to work, the others will stop playing any audio after a while for some reason? -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 425328] Forgets FiiO BTR5 DAC connected to USB after sleep
https://bugs.kde.org/show_bug.cgi?id=425328 --- Comment #4 from Rajinder Yadav --- Here is the output with a working FiiO BTR using the USB DAC Config setting: 1. FiioO BTR (hardware) set to Analog Stereo Output 2. Fiio BTR5 (headphone) set to OFF Sink #12 State: SUSPENDED Name: alsa_output.usb-FiiO_FiiO_BTR5-00.analog-stereo Description: FiiO BTR5 Analog Stereo Driver: module-alsa-card.c Sample Specification: s16le 2ch 44100Hz Channel Map: front-left,front-right Owner Module: 37 Mute: no Volume: front-left: 39320 / 60% / -13.31 dB, front-right: 39320 / 60% / -13.31 dB balance 0.00 Base Volume: 65536 / 100% / 0.00 dB Monitor Source: alsa_output.usb-FiiO_FiiO_BTR5-00.analog-stereo.monitor Latency: 0 usec, configured 0 usec Flags: HARDWARE DECIBEL_VOLUME LATENCY Properties: alsa.resolution_bits = "16" device.api = "alsa" device.class = "sound" alsa.class = "generic" alsa.subclass = "generic-mix" alsa.name = "USB Audio" alsa.id = "USB Audio" alsa.subdevice = "0" alsa.subdevice_name = "subdevice #0" alsa.device = "0" alsa.card = "3" alsa.card_name = "FiiO BTR5" alsa.long_card_name = "FiiO FiiO BTR5 at usb-:03:00.0-9, high speed" alsa.driver_name = "snd_usb_audio" device.bus_path = "pci-:03:00.0-usb-0:9:1.0" sysfs.path = "/devices/pci:00/:00:01.3/:03:00.0/usb1/1-9/1-9:1.0/sound/card3" udev.id = "usb-FiiO_FiiO_BTR5-00" device.bus = "usb" device.vendor.id = "2972" device.vendor.name = "FiiO" device.product.id = "0047" device.product.name = "FiiO BTR5" device.serial = "FiiO_FiiO_BTR5" device.string = "front:3" device.buffering.buffer_size = "352800" device.buffering.fragment_size = "176400" device.access_mode = "mmap+timer" device.profile.name = "analog-stereo" device.profile.description = "Analog Stereo" device.description = "FiiO BTR5 Analog Stereo" module-udev-detect.discovered = "1" device.icon_name = "audio-card-usb" Ports: analog-output: Analog Output (priority: 9900) Active Port: analog-output Formats: = Here is another output when the 2nd Fiio BTR5 device which becomes active after a few seconds when the FiiO DAC is plugged is or Turned on. This causes the audio to stop working as I showed in the attached pic and I have go and set it to "Off". Where ever the FiiO BTR5 (headphone) not set to "Off" after some time the audio will just stop playing, this period seems to vary but eventually the audio goes silent. Sink #12 State: SUSPENDED Name: alsa_output.usb-FiiO_FiiO_BTR5-00.analog-stereo Description: FiiO BTR5 Analog Stereo Driver: module-alsa-card.c Sample Specification: s16le 2ch 44100Hz Channel Map: front-left,front-right Owner Module: 37 Mute: no Volume: front-left: 39320 / 60% / -13.31 dB, front-right: 39320 / 60% / -13.31 dB balance 0.00 Base Volume: 65536 / 100% / 0.00 dB Monitor Source: alsa_output.usb-FiiO_FiiO_BTR5-00.analog-stereo.monitor Latency: 0 usec, configured 0 usec Flags: HARDWARE DECIBEL_VOLUME LATENCY Properties: alsa.resolution_bits = "16" device.api = "alsa" device.class = "sound" alsa.class = "generic" alsa.subclass = "generic-mix" alsa.name = "USB Audio" alsa.id = "USB Audio" alsa.subdevice = "0" alsa.subdevice_name = "subdevice #0" alsa.device = "0" alsa.card = "3" alsa.card_name = "FiiO BTR5" alsa.long_card_name = "FiiO FiiO BTR5 at usb-:03:00.0-9, high speed" alsa.driver_name = "snd_usb_audio" device.bus_path = "pci-:03:00.0-usb-0:9:1.0" sysfs.path = "/devices/pci:00/:00:01.3/:03:00.0/usb1/1-9/1-9:1.0/sound/card3" udev.id = "usb-FiiO_FiiO_BTR5-00" device.bus = "usb" device.vendor.id = "2972" device.vendor.name = "FiiO" device.product.id = "0047" device.product.name = "FiiO BTR5" device.serial = "FiiO_FiiO_BTR5" device.string = "front:3" device.buffering.buffer_size = "352800"
[okular] [Bug 425291] Cannot click link under text markup
https://bugs.kde.org/show_bug.cgi?id=425291 Albert Astals Cid changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Ever confirmed|0 |1 Status|NEEDSINFO |CONFIRMED --- Comment #3 from Albert Astals Cid --- yep, i was sure we had a unitest to make sure that worked, but clearly not :/ -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 425393] New: Embedded picture not displayed
https://bugs.kde.org/show_bug.cgi?id=425393 Bug ID: 425393 Summary: Embedded picture not displayed Product: kontact Version: 5.14.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: mail Assignee: kdepim-b...@kde.org Reporter: axel.br...@gmx.de Target Milestone: --- Created attachment 130893 --> https://bugs.kde.org/attachment.cgi?id=130893&action=edit example for display f HTML mail Create a mail with KMail and have a picture embedded (e.g. screenshot from spectacle Actual result: Picture is displayed as icon in the text (HTML-Mail) Expected result: Picture is displayed in the flow of text -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 425354] In recent version 1.11 the actions are mostly wrong
https://bugs.kde.org/show_bug.cgi?id=425354 Albert Astals Cid changed: What|Removed |Added CC||aa...@kde.org, ||simg...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 425376] Disconnect between Mousewheel and page control Area of scrolbar
https://bugs.kde.org/show_bug.cgi?id=425376 Albert Astals Cid changed: What|Removed |Added CC||aa...@kde.org, ||keziolio...@gmail.com, ||oliver.san...@tu-dresden.de --- Comment #1 from Albert Astals Cid --- I'm 94% sure this is a duplicate of the multiple bugs that are caused by the qscroller patches. -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 425328] Forgets FiiO BTR5 DAC connected to USB after sleep
https://bugs.kde.org/show_bug.cgi?id=425328 --- Comment #3 from Rajinder Yadav --- Created attachment 130892 --> https://bugs.kde.org/attachment.cgi?id=130892&action=edit pulse audio config dialog -- You are receiving this mail because: You are watching all bug changes.
[elisa] [Bug 425392] New: Elisa does not list certain songs under Artists and Albums views and fails to detect their durations under Tracks view
https://bugs.kde.org/show_bug.cgi?id=425392 Bug ID: 425392 Summary: Elisa does not list certain songs under Artists and Albums views and fails to detect their durations under Tracks view Product: elisa Version: 20.08.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: matthieu_gall...@yahoo.fr Reporter: bugsefor...@gmx.com Target Milestone: --- Created attachment 130891 --> https://bugs.kde.org/attachment.cgi?id=130891&action=edit screen recording SUMMARY This issue affects both Elisa 20.08 and Elisa master. Something weird occurs between Elisa and some of my mp3 files. I add their path to Elisa settings but Elisa does not show them under Albums and Artists views despite their correct tags. These mp3 files are only listed under Tracks view and the duration of all of them is 0:00. However, when I add them to playlist the playback occurs as expected and I can see their correct durations. Watch the attached screen recording please. Enabling file system indexing in Elisa settings does no difference and Elisa started via Konsole shows no suspicious message. Furthermore, I have several music players installed on my system and Elisa is the only one that does not handle these mp3 files as expected. EXPECTED RESULT Elisa should list all files under Artists and Albums views and correctly detect their durations SOFTWARE/OS VERSIONS Operating System: KDE neon Unstable Edition KDE Plasma Version: 5.19.80 KDE Frameworks Version: 5.74.0 Qt Version: 5.14.2 -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 425328] Forgets FiiO BTR5 DAC connected to USB after sleep
https://bugs.kde.org/show_bug.cgi?id=425328 --- Comment #2 from Rajinder Yadav --- Created attachment 130890 --> https://bugs.kde.org/attachment.cgi?id=130890&action=edit pactl log I just came out of sleep now and Pulse Audio Config. is showing me even less options today. It has been flaky like this for a while. I am using opensuse tumbleweed. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 425333] no pre-defined account templates on a mac
https://bugs.kde.org/show_bug.cgi?id=425333 Dawid Wróbel changed: What|Removed |Added Assignee|kmymoney-de...@kde.org |m...@dawidwrobel.com Status|REPORTED|CONFIRMED CC||m...@dawidwrobel.com Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 400318] [Wayland] Window shadows Plasma panels when "Keep above others" feature is enabled and when I use the task switcher to walk through maximized windows running natively on Way
https://bugs.kde.org/show_bug.cgi?id=400318 Patrick Silva changed: What|Removed |Added Version|5.19.0 |5.19.4 Summary|[Wayland] Window shadows|[Wayland] Window shadows |Plasma panels when "Keep|Plasma panels when "Keep |above others" feature is|above others" feature is |enabled |enabled and when I use the ||task switcher to walk ||through maximized windows ||running natively on Wayland -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 425380] Discover gets stuck at "Still looking" and never loads the list of app/plasma addons from KDE Store
https://bugs.kde.org/show_bug.cgi?id=425380 Alexander Lohnau changed: What|Removed |Added Ever confirmed|0 |1 CC||alexander.loh...@gmx.de Status|REPORTED|CONFIRMED --- Comment #1 from Alexander Lohnau --- Can confirm, installing KNS 5.72 and discover 5.19.4 made no difference. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 420144] Visual Studio Code desktop action doesn't launch
https://bugs.kde.org/show_bug.cgi?id=420144 --- Comment #5 from codingko...@gmail.com --- No longer able to reproduce. The "New Empty Window" action works without issue, as I test it right now. Aside from the "Icon" key of the desktop entry being changed to "com.visualstudio.code.oss", the desktop entry doesn't seem to have changed since I opened this bug. -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 425391] New: Sometimes sound applet does not detect sound device after re-login on neon unstable
https://bugs.kde.org/show_bug.cgi?id=425391 Bug ID: 425391 Summary: Sometimes sound applet does not detect sound device after re-login on neon unstable Product: plasma-pa Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: applet Assignee: now...@gmail.com Reporter: bugsefor...@gmx.com CC: plasma-b...@kde.org Target Milestone: --- SUMMARY Sometimes a diagonal red line overlaps the sound applet in systray after I restart X11 or Wayland session on neon unstable. When I click on sound applet, its popup opens and says that there is no sound device, but my speakers work as expected when I open an audio file. Apparently it's a random problem and another re-login almost always solves it. EXPECTED RESULT sound applet should always detect sound devices SOFTWARE/OS VERSIONS Operating System: KDE neon Unstable Edition KDE Plasma Version: 5.19.80 KDE Frameworks Version: 5.74.0 Qt Version: 5.14.2 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 425390] New: Dolphin crashes upon moving to second monitor
https://bugs.kde.org/show_bug.cgi?id=425390 Bug ID: 425390 Summary: Dolphin crashes upon moving to second monitor Product: dolphin Version: 20.04.3 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: krueglingz...@gmx.com CC: kfm-de...@kde.org Target Milestone: --- Application: dolphin (20.04.3) Qt Version: 5.15.0 Frameworks Version: 5.73.0 Operating System: Linux 5.8.1-2.g553537d-default x86_64 Windowing system: Wayland Distribution: "openSUSE Tumbleweed" -- Information about the crash: I started wayland using the option "Plasma (Full Wayland)" and I noticed that Dolphin would crash almost instantly upon dragging to another monitor. Moving around on one monitor is fine and everything else works from what i can tell, but it just crashes when moving to my secondary monitor. The crash can be reproduced every time. -- Backtrace: Application: Dolphin (dolphin), signal: Aborted [KCrash Handler] #4 0x7f33f93ae4b1 in raise () from /lib64/libc.so.6 #5 0x7f33f9397539 in abort () from /lib64/libc.so.6 #6 0x7f33f72a0c27 in qt_message_fatal (message=..., context=...) at global/qlogging.cpp:1914 #7 QMessageLogger::fatal (this=this@entry=0x7ffc25f09aa0, msg=msg@entry=0x7f33f27ba0b8 "The Wayland connection broke. Did the Wayland compositor die?") at global/qlogging.cpp:893 #8 0x7f33f2735ef9 in QtWaylandClient::QWaylandDisplay::checkError (this=) at /usr/include/qt5/QtCore/qlogging.h:90 #9 QtWaylandClient::QWaylandDisplay::checkError (this=) at qwaylanddisplay.cpp:204 #10 0x7f33f273b029 in QtWaylandClient::QWaylandShmBackingStore::resize (this=this@entry=0x55fba820b950, size=...) at qwaylandshmbackingstore.cpp:289 #11 0x7f33f273b24d in QtWaylandClient::QWaylandShmBackingStore::ensureSize (this=this@entry=0x55fba820b950) at qwaylandshmbackingstore.cpp:206 #12 0x7f33f273b279 in QtWaylandClient::QWaylandShmBackingStore::beginPaint (this=this@entry=0x55fba820b950, region=...) at qwaylandshmbackingstore.cpp:181 #13 0x7f33f7b81f5e in QBackingStore::beginPaint (this=0x55fba82739f0, region=...) at ../../include/QtGui/5.15.0/QtGui/private/../../../../../src/gui/kernel/qhighdpiscaling_p.h:203 #14 0x7f33f80dc792 in QWidgetRepaintManager::paintAndFlush (this=this@entry=0x55fba8270800) at kernel/qwidgetrepaintmanager.cpp:976 #15 0x7f33f80dd19b in QWidgetRepaintManager::sync (this=0x55fba8270800, exposedWidget=0x55fba7f599f0, exposedRegion=...) at kernel/qwidgetrepaintmanager.cpp:743 #16 0x7f33f81277e8 in QWidgetWindow::event (this=0x55fba8170630, event=0x7ffc25f0a0d0) at kernel/qwidgetwindow.cpp:342 #17 0x7f33f80cc0cf in QApplicationPrivate::notify_helper (this=, receiver=0x55fba8170630, e=0x7ffc25f0a0d0) at kernel/qapplication.cpp:3671 #18 0x7f33f74b9c1a in QCoreApplication::notifyInternal2 (receiver=0x55fba8170630, event=0x7ffc25f0a0d0) at ../../include/QtCore/5.15.0/QtCore/private/../../../../../src/corelib/thread/qthread_p.h:325 #19 0x7f33f79b66bd in QGuiApplicationPrivate::processExposeEvent (e=0x55fba83820a0) at kernel/qguiapplication.cpp:3193 #20 0x7f33f798b51b in QWindowSystemInterface::sendWindowSystemEvents (flags=flags@entry=...) at kernel/qwindowsysteminterface.cpp:1175 #21 0x7f33f798b798 in QWindowSystemInterface::flushWindowSystemEvents (flags=...) at kernel/qwindowsysteminterface.cpp:1139 #22 0x7f33f74e5b41 in QObject::event (this=0x55fba801a6a0, e=0x55fba87881b0) at kernel/qobject.cpp:1314 #23 0x7f33f80cc0cf in QApplicationPrivate::notify_helper (this=, receiver=0x55fba801a6a0, e=0x55fba87881b0) at kernel/qapplication.cpp:3671 #24 0x7f33f74b9c1a in QCoreApplication::notifyInternal2 (receiver=0x55fba801a6a0, event=0x55fba87881b0) at ../../include/QtCore/5.15.0/QtCore/private/../../../../../src/corelib/thread/qthread_p.h:325 #25 0x7f33f74bc641 in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x55fba7eab2b0) at kernel/qcoreapplication.cpp:1815 #26 0x7f33f75119d3 in postEventSourceDispatch (s=0x55fba7f319a0) at kernel/qeventdispatcher_glib.cpp:277 #27 0x7f33f53382b7 in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0 #28 0x7f33f5338638 in ?? () from /usr/lib64/libglib-2.0.so.0 #29 0x7f33f53386ef in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #30 0x7f33f751105f in QEventDispatcherGlib::processEvents (this=0x55fba7f31980, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #31 0x7f33f74b85db in QEventLoop::exec (this=this@entry=0x7ffc25f0a570, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:141 #32 0x7f33f74c0840 in QCoreApplication::exec () at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #33 0x7f33f79a8a8c in QGuiApplication::e
[digikam] [Bug 424727] "Failed to connect to camera" error with iPhone 6s
https://bugs.kde.org/show_bug.cgi?id=424727 --- Comment #9 from im...@juno.com --- (In reply to caulier.gilles from comment #8) > Hi, > > I never tuned my macbook pro 2012 with this kind of settings to be able to > download image through the Gphoto2 driver. It sound like a specific > configuration, i don't have other explanation. > > Gilles Caulier I may have confused others with my explanation about my work around. I couldn’t find a method to edit my comment, so I’ll just add to a reply. The settings were done to the iphone, NOT the MacBook Pro. So, for one reason or another, I must force the iphone to “trust” the MacBook Pro each time I reconnect to allow the digikam app to detect the iphone when attached by usb. I wouldn’t know whether it’s a specific configuration of the Mac or the iphone unless I restore both to factory. Something I’m not wanting to do at this time since I don’t want to use the current OS nor iOS because of incompatibilities of some apps I want to use. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 425341] [Feature Request] Add ability to configure mouse buttons
https://bugs.kde.org/show_bug.cgi?id=425341 caulier.gil...@gmail.com changed: What|Removed |Added Version|unspecified |7.0.0 CC||caulier.gil...@gmail.com --- Comment #2 from caulier.gil...@gmail.com --- Thiago, This solution is for Plasma desktop only. digiKam work on all Linux Desktops, MacOS and Windows. So it's not suitable. Solution: to have a low level settings in digiKam configure panel, but of course, you will said, hey, another application setting... Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 392007] Face tags and regular tags are mixed together and cannot be told apart.
https://bugs.kde.org/show_bug.cgi?id=392007 caulier.gil...@gmail.com changed: What|Removed |Added Version|5.9.0 |7.0.0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 425359] First face tag moves intermittently
https://bugs.kde.org/show_bug.cgi?id=425359 --- Comment #4 from Tom Cunningham --- It may also have something to do with cropping and/or rotating the image in the Editor; I've been able to reproduce it just using those changes. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 392007] Face tags and regular tags are mixed together and cannot be told apart.
https://bugs.kde.org/show_bug.cgi?id=392007 --- Comment #5 from MarcP --- The situation still applies. I don't think there is an easy solution, but I would leave it open because we might take it into consideration in the future. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 425389] New: Filesystem expose: raw:* and msd:* entries error out on Debian
https://bugs.kde.org/show_bug.cgi?id=425389
Bug ID: 425389
Summary: Filesystem expose: raw:* and msd:* entries error out
on Debian
Product: kdeconnect
Version: unspecified
Platform: Other
OS: Unspecified
Status: REPORTED
Severity: normal
Priority: NOR
Component: android-application
Assignee: albertv...@gmail.com
Reporter: gwmeeqqhvjyhpan...@ttirv.org
Target Milestone: ---
On my Samsung Galaxy A21S (stock Android 10, f-droid's KDE Connect 1.14.2),
the "filesystem expose" plugin directories include
- raw:/storage/emulated/0/Download/k
- Debian fails when trying to create a file or directory in a raw:* dir:
"File already exists".
- strace mkdir abc
mkdir("abc", 0777) = -1 EEXIST
- msd:19
- How to create:
Click to add a storage location, choose a dir in the file list that opens,
click the blue button at the bottom to allow access.
- Debian creates files and dirs in msd:* dirs, however it still prints
an error: "No such file or directory".
- strace mkdir ghi
mkdir("ghi", 0777) = -1 ENOENT
- primary:Download
- How to create:
Click to add a storage location, click on the sandwich menu at the left,
choose the internal memory ("Galaxy A21S"), navigate and choose the dir,
click the blue button at the bottom to allow access.
- Works flawlessly on Debian.
Debian is Debian 10 KDE with no third-party repos and kdeconnect 1.3.3-2.
Additional info:
- All permissions were granted to the app.
- "Share and receive" works, on the same network, between this phone and older
phones that run older Android versions.
- "Filesystem expose" works, on the same network, between the PC and older
phones that run older Android versions.
- Other phones with older Android and KDE Connect 1.14.2 only have primary:*
entries, and they work on Debian.
--
You are receiving this mail because:
You are watching all bug changes.
