[www.kde.org] [Bug 482285] New: on kde.org/plasma-desktop, the most recent version is listed as 5.27, not 6.0
https://bugs.kde.org/show_bug.cgi?id=482285 Bug ID: 482285 Summary: on kde.org/plasma-desktop, the most recent version is listed as 5.27, not 6.0 Classification: Websites Product: www.kde.org Version: unspecified Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kde-...@kde.org Reporter: char...@binkle.co.uk Target Milestone: --- SUMMARY On the main website for kde plasma desktop, the floating window icon still shows plasma 5.27 in latest release. Most other sections of the website have been updated accordingly with the 6.0 megarelease. STEPS TO REPRODUCE 1. navigate to https://kde.org/plasma-desktop/ 2. scroll down to the second major element. OBSERVED RESULT Under the heading "about plasma 5.27" there is text saying "Latest Release: 5.27" EXPECTED RESULT The heading should be "about plasma 6.0" and the text should say "Latest release: 6.0" SOFTWARE/OS VERSIONS *** This behavior has been reproduced on two different linux/sway computers and my mobile phone *** Linux/sway: linux 6.7.6 Firefox: 123.0 ADDITIONAL INFORMATION Many distros (e.g. arch linux/debian stable) are still shipping 5.27, so at the moment it is not a big issue, but after the recent 6.0 release, it seems sensible to update the website to reflect that. The "see announcements" button in the same element also links back to the same page, but that should be a separate issue. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 465535] An error occurred while running the python3 script
https://bugs.kde.org/show_bug.cgi?id=465535 Charlie Ramirez Animation Studios MX changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=480074 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 480074] Configure Error While Running Python3 Script
https://bugs.kde.org/show_bug.cgi?id=480074 Charlie Ramirez Animation Studios MX changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=465535 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 480074] Configure Error While Running Python3 Script
https://bugs.kde.org/show_bug.cgi?id=480074 --- Comment #1 from Charlie Ramirez Animation Studios MX --- Created attachment 165057 --> https://bugs.kde.org/attachment.cgi?id=165057=edit Error in Transcode refering Missing dll -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 480074] New: Configure Error While Running Python3 Script
https://bugs.kde.org/show_bug.cgi?id=480074 Bug ID: 480074 Summary: Configure Error While Running Python3 Script Classification: Applications Product: kdenlive Version: 23.08.4 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: Installation Assignee: j...@kdenlive.org Reporter: todo.ciencia.y.electron...@gmail.com Target Milestone: --- Created attachment 165056 --> https://bugs.kde.org/attachment.cgi?id=165056=edit Python Error in Configure SUMMARY *** As the title suggests, The program returns a Python error referencing scripts not found when opening configuration. This error could be preventing the execution of other processes such as clip transcoding. The installation is completely clean (first time on the machine) I tried to reinstall again without success *** STEPS TO REPRODUCE 1. Do a Clean install of KDEnlive 23.08.4 on a Windows 11 machine 2.Open Configure. One or several error windows should be displayed immediately referring to python errors. 3. Try adding a GIF or file that requires a Transcode (All transcodes will fail because they call Nvidia dependencies even if you don't have one). OBSERVED RESULT The errors suggest that the program is trying to make calls to missing .py dependencies in the installation folder It could be related to this other bug that occurred in Arch Linux in 2023 https://bugs.kde.org/show_bug.cgi?id=465535 EXPECTED RESULT The program should be able to install the "missing" .py and .dll from its installation folder or reference whether it already has or is compatible with a version of python currently installed SOFTWARE/OS VERSIONS Kdenlive: 23.08.4 Package Type: Unknown/Default MLT: 7.21.0 Qt: 5.15.10 (built against 5.15.10 x86_64-little_endian-llp64) Frameworks: 5.112.0 System: Windows 11 Version 2009 Kernel: winnt 10.0.22631 CPU: x86_64 Windowing System: windows Movit (GPU): disabled Track Compositing: qtblend Python 3.12 (64bit) Installed ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 476513] Cannot turn off automatic share from the device
https://bugs.kde.org/show_bug.cgi?id=476513 Charlie changed: What|Removed |Added CC||rossc...@gmail.com --- Comment #3 from Charlie --- Thanks for that tip. Copying the config to the right place does seem to allow me to turn off the automatic sharing. Not sure if it is related or not, but the "Send clipboard" option from the menu seems to do nothing. So, for now it seems to be "always" or "never". :-) -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 477123] New: Feature Suggestion
https://bugs.kde.org/show_bug.cgi?id=477123 Bug ID: 477123 Summary: Feature Suggestion Classification: Applications Product: kmymoney Version: 5.1.3 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kmymoney-de...@kde.org Reporter: charleseng...@gmail.com Target Milestone: --- I would like to have the ability to schedule a transaction on the same weekday each month. For example, I would like to automatically enter a Social Security deposit on the second Wednesday of each month. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 470915] Discover on Debian 12 does not show the top bar button window
https://bugs.kde.org/show_bug.cgi?id=470915 --- Comment #4 from Charlie Ramirez Animation Studios MX --- Created attachment 161983 --> https://bugs.kde.org/attachment.cgi?id=161983=edit Screenshot - Fixed Theme Change -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 470915] Discover on Debian 12 does not show the top bar button window
https://bugs.kde.org/show_bug.cgi?id=470915 Charlie Ramirez Animation Studios MX changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #3 from Charlie Ramirez Animation Studios MX --- (In reply to Nate Graham from comment #1) > Well this is strange. > > Can you reproduce the issue if you use the default Breeze window decorations? > > Or after updating Debian with the latest updates? Fixed with Theme Exchange. -Apparently it can be caused by custom settings in the desktop appearance. (try using the Plastik Buttons in Dark Breeze with Adapta icons) Because it was a clean install of Debian 12 using the user's saved settings from Debian 11. The Adapta theme apparently is not installed completely (Reinstallation of Adapta was done in the global theme settings) This could have caused the problem However, during the Theme change, a slight crash of the application was generated - See [Bug 475070] I had to rebuild my custom Window Theme but there don't seem to be any more problems at the moment. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 475070] Soft Crash after Changing global Theme (due to graphical bug after updating debian 11 to 12)
https://bugs.kde.org/show_bug.cgi?id=475070 --- Comment #1 from Charlie Ramirez Animation Studios MX --- Created attachment 161982 --> https://bugs.kde.org/attachment.cgi?id=161982=edit Dr.KonkiBacktrace -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 475070] New: Soft Crash after Changing global Theme (due to graphical bug after updating debian 11 to 12)
https://bugs.kde.org/show_bug.cgi?id=475070 Bug ID: 475070 Summary: Soft Crash after Changing global Theme (due to graphical bug after updating debian 11 to 12) Classification: Applications Product: systemsettings Version: 5.27.5 Platform: Debian stable OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: todo.ciencia.y.electron...@gmail.com Target Milestone: --- Application: systemsettings (5.27.5) Qt Version: 5.15.8 Frameworks Version: 5.103.0 Operating System: Linux 6.1.0-12-amd64 x86_64 Windowing System: Wayland Distribution: Debian GNU/Linux 12 (bookworm) DrKonqi: 5.27.5 [KCrashBackend] -- Information about the crash: The error was triggered after trying to fix Switch to the classic Breeze theme due to Discover not correctly displaying the window button bar (close, maximize, etc.) after doing a clean install of Debian 12 using previous user settings made in Debian 11. [Discover] [Bug 470915] System Settings has closed unexpectedly, however the theme change was performed correctly. -During the attempt to Change Dark Breze to Light and come back to dark The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Preferencias del sistema (systemsettings), signal: Segmentation fault [KCrash Handler] #4 0x7ff02426b96c in QQuickWindowPrivate::sendFilteredPointerEventImpl(QQuickPointerEvent*, QQuickItem*, QQuickItem*) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #5 0x7ff02426b869 in QQuickWindowPrivate::sendFilteredPointerEventImpl(QQuickPointerEvent*, QQuickItem*, QQuickItem*) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #6 0x7ff02426b869 in QQuickWindowPrivate::sendFilteredPointerEventImpl(QQuickPointerEvent*, QQuickItem*, QQuickItem*) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #7 0x7ff02426b869 in QQuickWindowPrivate::sendFilteredPointerEventImpl(QQuickPointerEvent*, QQuickItem*, QQuickItem*) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #8 0x7ff02426c674 in QQuickWindowPrivate::deliverToPassiveGrabbers(QVector > const&, QQuickPointerEvent*) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #9 0x7ff024272a4f in QQuickWindowPrivate::deliverMouseEvent(QQuickPointerMouseEvent*) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #10 0x7ff0242740dd in QQuickWindowPrivate::deliverPointerEvent(QQuickPointerEvent*) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #11 0x7ff0265493f5 in QWindow::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Gui.so.5 #12 0x7ff026d62fae in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #13 0x7ff0260b16f8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #14 0x7ff024d7e057 in QQuickWidget::mouseReleaseEvent(QMouseEvent*) () from /lib/x86_64-linux-gnu/libQt5QuickWidgets.so.5 #15 0x7ff026da4db8 in QWidget::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #16 0x7ff026d62fae in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #17 0x7ff026d6b552 in QApplication::notify(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #18 0x7ff0260b16f8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #19 0x7ff026d6965e in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool, bool) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #20 0x7ff026dbdbd8 in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #21 0x7ff026dc0f60 in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #22 0x7ff026d62fae in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #23 0x7ff0260b16f8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #24 0x7ff02653d3ed in QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) () from /lib/x86_64-linux-gnu/libQt5Gui.so.5 #25 0x7ff026511cac in QWindowSystemInterface::sendWindowSystemEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Gui.so.5 #26 0x7ff023f664b0 in ?? () from /lib/x86_64-linux-gnu/libQt5WaylandClient.so.5 #27 0x7ff02471e7a9 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #28 0x7ff02471ea38 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #29 0x7ff02471eacc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #30 0x7ff026109836 in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #31 0x7ff0260b017b in QEventLoop::exec(QFlags) () from
[kdenlive] [Bug 471177] New: Position and Zoom effect causes unwanted blue blur on render and other tracks
https://bugs.kde.org/show_bug.cgi?id=471177 Bug ID: 471177 Summary: Position and Zoom effect causes unwanted blue blur on render and other tracks Classification: Applications Product: kdenlive Version: 23.04.2 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: major Priority: NOR Component: Effects & Transitions Assignee: j...@kdenlive.org Reporter: todo.ciencia.y.electron...@gmail.com Target Milestone: --- Created attachment 159756 --> https://bugs.kde.org/attachment.cgi?id=159756=edit Screenshot Blue Bug Effect SUMMARY *** As the title suggests, the Position and Zoom effect generates unwanted blue blur on other tracks. This particularly tends to occur on the trailing end of video tracks and short videos, in projects where split screen videos are intended. The effect "smears" the screen with a blue tint over all space not covered by the effect track that cannot be removed unless the effect is turned off completely. -The installation of Kdenlive is clean (in an also clean installation of Windows 11). Checking on the subreddit, other users are experiencing the same unwanted effect and suggest that it may be a problem with 23.X releases in general as it doesn't happen or they have muddled by going back to 22.x releases. The users of the subreddit suggest trying "Transform" instead of Position and zoom... This "First Aid" the problem (At least for what we want to do which is to create simple split screens) *** STEPS TO REPRODUCE 1. use kdenlive version 23.04.2 create a 1080p project (Preferably portrait, but seems to happen the same regardless of orientation) 2. Add two video tracks in the same way as creating a split screen -Add the Position and Zoom effect to both tracks to enhance the arrangement 3. Make some cuts with the cutting tool to adjust the duration (making cuts from start to end) -Around the end of one of the tracks The effect will start generating the Blue Filter bug, This "stain cannot be removed" unless you disable the effect completely. OBSERVED RESULT -Around the end of one of the tracks The effect will begin to generate an unwanted blue Filter that will cover the entire playback area not covered by the track containing the effect, this is impossible to remove unless you disable the effect completely. It also affects the Rendering process, leaving the project unusable. -Saving the project and reopening it, as well as removing and placing it again does not solve the problem. -try Placing the same file on the timeline (as if it were a separate file) by cropping the already present part and applying the effect It also doesn't prevent the problem and the problem persists. -It is not a problem for previous versions --# Substituting "Transform" instead of Position and Zoom fixes the issue temporarily#-- EXPECTED RESULT Position and zoom should not generate this blue filter. SOFTWARE/OS VERSIONS Windows: 11 Edition Windows 11 Pro Version 22H2 Installed on2023-02-04 OS build22621.1848 Experience Windows Feature Experience Pack 1000.22642.1000.0 Processor AMD Ryzen 5 3500U with Radeon Vega Mobile Gfx 2.10 GHz Installed RAM 16.0 GB (13.9 GB usable) System type 64-bit operating system, x64-based processor Pen and touch Pen support KDE Framework Version 5.107.0 Qt: Version 5.15.9 (built against 5.15.9) MLT: Version 7.17.0 ADDITIONAL INFORMATION Same issue Subreddit https://www.reddit.com/r/kdenlive/comments/139lx7y/issue_with_position_and_zoom/ -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 470915] New: Discover on Debian 12 does not show the top bar button window
https://bugs.kde.org/show_bug.cgi?id=470915 Bug ID: 470915 Summary: Discover on Debian 12 does not show the top bar button window Classification: Applications Product: Discover Version: 5.27.5 Platform: Debian stable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: discover Assignee: plasma-b...@kde.org Reporter: todo.ciencia.y.electron...@gmail.com CC: aleix...@kde.org Target Milestone: --- Created attachment 159604 --> https://bugs.kde.org/attachment.cgi?id=159604=edit Screenshot buttons not appear SUMMARY As the title suggests, on debian 12 systems with KDE Plasma Desktop the Discover window does not Generate window buttons (Close maximize/minimize etc.) -Debian 12 Stable was released on June 10, so there are no pending updates. STEPS TO REPRODUCE 1. Install or Update to a Debian 12 Stable release. [Clean Instalation using previous User Settings backup from a Deb11 with testing repository] 2. Open discover [default included with Deb12] - App work as normal but the top bar buttons the upper buttons are not generated although they maintain the functions if they are clicked (blind click) 3. - Restarting don't fix issue. (other windows or apps work/have buttons normally) OBSERVED RESULT The program operates normally and continues to maintain the functions of the window buttons if you click on them, (they are simply not visible) EXPECTED RESULT Discover should generate Window buttons SOFTWARE/OS VERSIONS Linux/KDE Plasma: Operating System: Debian GNU/Linux 12 KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 6.1.0-9-amd64 (64-bit) Graphics Platform: Wayland Processors: 8 × AMD Ryzen 5 3500U with Radeon Vega Mobile Gfx Memory: 13.6 GiB of RAM Graphics Processor: AMD Radeon Vega 8 Graphics Manufacturer: HP Product Name: HP 245 G7 Notebook PC ADDITIONAL INFORMATION -KDE Plasma Dark theme with Plastik theme windows, Adapta icons. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 470483] New: Only the active window becomes translucent when adjusting custom tiles
https://bugs.kde.org/show_bug.cgi?id=470483 Bug ID: 470483 Summary: Only the active window becomes translucent when adjusting custom tiles Classification: Plasma Product: kwin Version: 5.27.4 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: effects-various Assignee: kwin-bugs-n...@kde.org Reporter: char...@binkle.co.uk Target Milestone: --- Created attachment 159366 --> https://bugs.kde.org/attachment.cgi?id=159366=edit screenshot showing what happens when resizing tiles SUMMARY When clicking and dragging the border between two tiles, only the active window* has the translucency effect applied to it; even if there are multiple windows being resized. *or if the active window is not among those being resized, the closest tile to it. STEPS TO REPRODUCE 1. ensure the translucency effect is enabled via "workspace behaviour>desktop effects>translucency" 2. set up a tile layout with more than one tile using meta+t 3. put one window on each tile (doesn't matter which application) using shift+dragging 4. click and drag the border between two windows OBSERVED RESULT only the active window becomes translucent (if the active window was not one of the resized windows, the nearest resized window to it will become translucent) EXPECTED RESULT When resizing multiple windows using custom tiling, all the resized windows should become translucent. SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.25.4 KDE Frameworks Version: 5.105.0 Qt Version: 5.15.9 ADDITIONAL INFORMATION I am not entirely sure whether the bug is still present in the latest builds, (I have not been able to test them yet). I am also not entirely sure whether this is an issue with the effect itself, or the tiling, or the way that kwin handles windows and resizing in general -- I don't know much about the implementation of any of them. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 467769] New: baloo_file crashes on login to Gnome Desktop On Fedora 37 Wayland
https://bugs.kde.org/show_bug.cgi?id=467769 Bug ID: 467769 Summary: baloo_file crashes on login to Gnome Desktop On Fedora 37 Wayland Classification: Frameworks and Libraries Product: frameworks-baloo Version: 5.104.0 Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: Baloo File Daemon Assignee: baloo-bugs-n...@kde.org Reporter: phi...@hotmail.com Target Milestone: --- Application: baloo_file_extractor (5.104.0) Qt Version: 5.15.8 Frameworks Version: 5.104.0 Operating System: Linux 6.1.18-200.fc37.x86_64 x86_64 Windowing System: Wayland Distribution: "Fedora release 37 (Thirty Seven)" DrKonqi: 5.27.3 [KCrashBackend] -- Information about the crash: balobaloo_file crashes on logino_file crashes on login The crash can be reproduced every time. -- Backtrace: Application: Baloo File Extractor (baloo_file_extractor), signal: Aborted [KCrash Handler] #4 0x7fa6ec0afe5c in __pthread_kill_implementation () from /lib64/libc.so.6 #5 0x7fa6ec05fa76 in raise () from /lib64/libc.so.6 #6 0x7fa6ec0497fc in abort () from /lib64/libc.so.6 #7 0x7fa6ec4c738c in mdb_assert_fail.constprop () from /lib64/liblmdb.so.0.0.0 #8 0x7fa6ec4c56f3 in mdb_page_dirty.lto_priv[cold] () from /lib64/liblmdb.so.0.0.0 #9 0x7fa6ec4d2fc6 in mdb_page_alloc.isra () from /lib64/liblmdb.so.0.0.0 #10 0x7fa6ec4ca7d3 in mdb_page_touch () from /lib64/liblmdb.so.0.0.0 #11 0x7fa6ec4cc3ec in mdb_cursor_touch () from /lib64/liblmdb.so.0.0.0 #12 0x7fa6ec4d067d in mdb_cursor_del () from /lib64/liblmdb.so.0.0.0 #13 0x7fa6ec4d1e24 in mdb_del0 () from /lib64/liblmdb.so.0.0.0 #14 0x7fa6ed42e606 in Baloo::DocumentTimeDB::del(unsigned long long) () from /lib64/libKF5BalooEngine.so.5 #15 0x7fa6ed4446a5 in Baloo::WriteTransaction::removeDocument(unsigned long long) () from /lib64/libKF5BalooEngine.so.5 #16 0x55a2d1c5805e in Baloo::App::index(Baloo::Transaction*, QString const&, unsigned long long) () #17 0x55a2d1c5910c in Baloo::App::processNextFile() () #18 0x7fa6ec8d42b6 in QSingleShotTimer::timerEvent(QTimerEvent*) () from /lib64/libQt5Core.so.5 #19 0x7fa6ec8c7fc5 in QObject::event(QEvent*) () from /lib64/libQt5Core.so.5 #20 0x7fa6ec89d4e8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #21 0x7fa6ec8ed981 in QTimerInfoList::activateTimers() () from /lib64/libQt5Core.so.5 #22 0x7fa6ec8ee25c in timerSourceDispatch(_GSource*, int (*)(void*), void*) () from /lib64/libQt5Core.so.5 #23 0x7fa6eb518c7f in g_main_context_dispatch () from /lib64/libglib-2.0.so.0 #24 0x7fa6eb56f118 in g_main_context_iterate.constprop () from /lib64/libglib-2.0.so.0 #25 0x7fa6eb515f00 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #26 0x7fa6ec8ee5fa in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #27 0x7fa6ec89bf3a in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #28 0x7fa6ec8a4002 in QCoreApplication::exec() () from /lib64/libQt5Core.so.5 #29 0x55a2d1c4f079 in main () [Inferior 1 (process 5471) detached] The reporter indicates this bug may be a duplicate of or related to bug 421885. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 447900] Scaling Broken on Windows
https://bugs.kde.org/show_bug.cgi?id=447900 --- Comment #11 from Charlie --- To follow up on this, the nightly seems to set Windows High DPI override settings. See screeenshot - the Override checkbox is enabled but also greyed out. So that is also the way I fixed previous builds. So this does work which is great! Are there plans for KDiff3 to natively support high dpi on windows without this override? -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 447900] Scaling Broken on Windows
https://bugs.kde.org/show_bug.cgi?id=447900 --- Comment #10 from Charlie --- Created attachment 157225 --> https://bugs.kde.org/attachment.cgi?id=157225=edit High DPI Settings -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 447900] Scaling Broken on Windows
https://bugs.kde.org/show_bug.cgi?id=447900 --- Comment #8 from Charlie --- Thanks Michael! Happy to test when there is a new build. Sorry to ask a dumb question, but which commit is it (I'm looking at https://invent.kde.org/sdk/kdiff3/-/commits/master)? -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 447900] Scaling Broken on Windows
https://bugs.kde.org/show_bug.cgi?id=447900 --- Comment #4 from Charlie --- I just tried the latest installe (kdiff3-1.10.0-windows-cl-64.exe although the reported version is 0.97.0), and still see the issue. The problem with having windows override the hdpi setting is that when Kdiff3 opens up it is really really big and then it gets resized correctly. The whole process takes a about 1 second, but its kinda distracting. Would it be possible to fix the underlying issue as opposed to working around it? -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 447900] Scaling Broken on Windows
https://bugs.kde.org/show_bug.cgi?id=447900 Charlie changed: What|Removed |Added Ever confirmed|0 |1 Status|RESOLVED|REOPENED Resolution|FIXED |--- -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 461418] System Settings Crash on Appearance > Application Style
https://bugs.kde.org/show_bug.cgi?id=461418 --- Comment #4 from Charlie Baker --- (In reply to Antonio Rojas from comment #3) > It doesn't matter which theme you're using, the broken style causes the > crash just by being installed. Where do I uninstall the theme though? I don't know which theme is causing it or anything. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 461418] System Settings Crash on Appearance > Application Style
https://bugs.kde.org/show_bug.cgi?id=461418 --- Comment #2 from Charlie Baker --- Created attachment 153622 --> https://bugs.kde.org/attachment.cgi?id=153622=edit New crash information added by DrKonqi systemsettings (5.25.5) using Qt 5.15.6 It did it again even when using Breeze, so nothing to do with unsupported theme -- Backtrace (Reduced): #9 0x7f48ac70ab50 in QGtk2StylePlugin::create(QString const&) () at /usr/lib64/qt5/plugins/styles/libqgtk2style.so #10 0x7f4903a22919 in QStyleFactory::create(QString const&) () at /lib64/libQt5Widgets.so.5 #11 0x7f48c2f013c6 in PreviewItem::reload() () at /usr/lib64/qt5/plugins/plasma/kcms/systemsettings/kcm_style.so #12 0x7f4900b1a081 in QQmlObjectCreator::finalize(QQmlInstantiationInterrupt&) () at /lib64/libQt5Qml.so.5 #13 0x7f4900aaf1a2 in QQmlIncubatorPrivate::incubate(QQmlInstantiationInterrupt&) () at /lib64/libQt5Qml.so.5 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 461418] System Settings Crash on Appearance > Application Style
https://bugs.kde.org/show_bug.cgi?id=461418 Charlie Baker changed: What|Removed |Added CC||charl.cj.mo...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 461418] New: System Settings Crash on Appearance > Application Style
https://bugs.kde.org/show_bug.cgi?id=461418 Bug ID: 461418 Summary: System Settings Crash on Appearance > Application Style Classification: Applications Product: systemsettings Version: 5.25.5 Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: charl.cj.mo...@gmail.com Target Milestone: --- Application: systemsettings (5.25.5) Qt Version: 5.15.6 Frameworks Version: 5.99.0 Operating System: Linux 6.0.5-200.fc36.x86_64 x86_64 Windowing System: X11 Distribution: Fedora Linux 36 (KDE Plasma) DrKonqi: 5.25.5 [KCrashBackend] -- Information about the crash: System Settings crashed when Appearance > Application Style is selected. The crash can be reproduced every time. -- Backtrace: Application: System Settings (systemsettings), signal: Aborted [KCrash Handler] #4 0x7ff1bfe8ec0c in __pthread_kill_implementation () at /lib64/libc.so.6 #5 0x7ff1bfe3e986 in raise () at /lib64/libc.so.6 #6 0x7ff1bfe287f4 in abort () at /lib64/libc.so.6 #7 0x7ff1c06b14d5 in qt_message_output(QtMsgType, QMessageLogContext const&, QString const&) [clone .cold] () at /lib64/libQt5Core.so.5 #8 0x7ff1c06c5a08 in QMetaCallEvent::QMetaCallEvent(unsigned short, unsigned short, void (*)(QObject*, QMetaObject::Call, int, void**), QObject const*, int, int) [clone .cold] () at /lib64/libQt5Core.so.5 #9 0x7ff1901fdb50 in QGtk2StylePlugin::create(QString const&) () at /usr/lib64/qt5/plugins/styles/libqgtk2style.so #10 0x7ff1c1622919 in QStyleFactory::create(QString const&) () at /lib64/libQt5Widgets.so.5 #11 0x7ff1912723c6 in PreviewItem::reload() () at /usr/lib64/qt5/plugins/plasma/kcms/systemsettings/kcm_style.so #12 0x7ff1be71a081 in QQmlObjectCreator::finalize(QQmlInstantiationInterrupt&) () at /lib64/libQt5Qml.so.5 #13 0x7ff1be6af1a2 in QQmlIncubatorPrivate::incubate(QQmlInstantiationInterrupt&) () at /lib64/libQt5Qml.so.5 #14 0x7ff1be6af625 in QQmlEnginePrivate::incubate(QQmlIncubator&, QQmlContextData*) () at /lib64/libQt5Qml.so.5 #15 0x7ff1bd86774f in QQmlDelegateModelPrivate::object(QQmlListCompositor::Group, int, QQmlIncubator::IncubationMode) () at /lib64/libQt5QmlModels.so.5 #16 0x7ff1bed58584 in QQuickItemViewPrivate::createItem(int, QQmlIncubator::IncubationMode) () at /lib64/libQt5Quick.so.5 #17 0x7ff1bed4a355 in QQuickGridViewPrivate::addVisibleItems(double, double, double, double, bool) () at /lib64/libQt5Quick.so.5 #18 0x7ff1bed56ec2 in QQuickItemViewPrivate::refill(double, double) () at /lib64/libQt5Quick.so.5 #19 0x7ff1bed59b03 in QQuickItemViewPrivate::layout() () at /lib64/libQt5Quick.so.5 #20 0x7ff1beca8e5a in QQuickWindowPrivate::polishItems() () at /lib64/libQt5Quick.so.5 #21 0x7ff1bed35692 in QQuickRenderControl::polishItems() () at /lib64/libQt5Quick.so.5 #22 0x7ff1bf76e169 in QQuickWidgetPrivate::render(bool) () at /lib64/libQt5QuickWidgets.so.5 #23 0x7ff1bf76e3d6 in QQuickWidgetPrivate::renderSceneGraph() () at /lib64/libQt5QuickWidgets.so.5 #24 0x7ff1c08d2ad5 in QObject::event(QEvent*) () at /lib64/libQt5Core.so.5 #25 0x7ff1c15aed02 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib64/libQt5Widgets.so.5 #26 0x7ff1c08a81c8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /lib64/libQt5Core.so.5 #27 0x7ff1c08f83b1 in QTimerInfoList::activateTimers() () at /lib64/libQt5Core.so.5 #28 0x7ff1c08f8cd4 in idleTimerSourceDispatch(_GSource*, int (*)(void*), void*) () at /lib64/libQt5Core.so.5 #29 0x7ff1bf126faf in g_main_context_dispatch () at /lib64/libglib-2.0.so.0 #30 0x7ff1bf17c2c8 in g_main_context_iterate.constprop () at /lib64/libglib-2.0.so.0 #31 0x7ff1bf124940 in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #32 0x7ff1c08f902a in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #33 0x7ff1c08a6c1a in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #34 0x7ff1c08aece2 in QCoreApplication::exec() () at /lib64/libQt5Core.so.5 #35 0x557690f090c3 in main () [Inferior 1 (process 21324) detached] Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 435293] color history popup shouldn't appear centered
https://bugs.kde.org/show_bug.cgi?id=435293 Charlie Baker changed: What|Removed |Added CC||charl.cj.mo...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 459740] KWin Crashes when I launch LibreSprite
https://bugs.kde.org/show_bug.cgi?id=459740 --- Comment #8 from Charlie Baker --- The " QT_PLUGIN_PATH" isn't even listed in "env" -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 459740] KWin Crashes when I launch LibreSprite
https://bugs.kde.org/show_bug.cgi?id=459740 --- Comment #6 from Charlie Baker --- (In reply to Vlad Zahorodnii from comment #5) > It looks like Qt installation got corrupted? Qt can't load QtXCB platform > integration plugin. Make sure that QT_PLUGIN_PATH and other environment > variables are fine, also maybe try force re-installing qt5-base. Where is that path? and I tried to remove qt5-base, and it says it would break Plasma (which atm I am using, also there was no option for "--allowerasing") -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 459740] KWin Crashes when I launch LibreSprite
https://bugs.kde.org/show_bug.cgi?id=459740
--- Comment #4 from Charlie Baker ---
Gives this return:
```(base) [charl@Daisuke ~]$ coredumpctl dump kwin_x11
PID: 25595 (kwin_x11)
UID: 1000 (charl)
GID: 1000 (charl)
Signal: 6 (ABRT)
Timestamp: Fri 2022-09-16 18:44:25 BST (1 week 4 days ago)
Command Line: kwin_x11 -platform
dde-kwin-xcb:appFilePath=/usr/bin/kwin_no_scale
Executable: /usr/bin/kwin_x11
Control Group: /user.slice/user-1000.slice/session-8.scope
Unit: session-8.scope
Slice: user-1000.slice
Session: 8
Owner UID: 1000 (charl)
Boot ID: 341a13d75a6d4b30ae8d0615e78f32e5
Machine ID: d111a0edf10a44639a33cc372258ac5f
Hostname: Daisuke
Storage:
/var/lib/systemd/coredump/core.kwin_x11.1000.341a13d75a6d4b30ae8d0615e78f32e5.25595.166335026500.zst
(missing)
Message: Process 25595 (kwin_x11) of user 1000 dumped core.
Module linux-vdso.so.1 with build-id
ef533bb262f1a045f813981c3d60075160f0756a
Module libpcre2-8.so.0 with build-id
0d207ce0c9db9ba59d4a8264b95c5ebf3ddec190
Metadata for module libpcre2-8.so.0 owned by FDO found: {
"type" : "rpm",
"name" : "pcre2",
"version" : "10.40-1.fc36",
"architecture" : "x86_64",
"osCpe" : "cpe:/o:fedoraproject:fedora:36"
}
Module libbrotlicommon.so.1 with build-id
e2790c03a5c688b7e75e89676cdd2b5fcf247a6f
Metadata for module libbrotlicommon.so.1 owned by FDO found: {
"type" : "rpm",
"name" : "brotli",
"version" : "1.0.9-7.fc36",
"architecture" : "x86_64",
"osCpe" : "cpe:/o:fedoraproject:fedora:36"
}
Module libxml2.so.2 with build-id
aadf5879c68f117634a6bd13135e48749e846fc9
Metadata for module libxml2.so.2 owned by FDO found: {
"type" : "rpm",
"name" : "libxml2",
"version" : "2.9.14-1.fc36",
"architecture" : "x86_64",
"osCpe" : "cpe:/o:fedoraproject:fedora:36"
}
Module libusbmuxd-2.0.so.6 with build-id
b17561def18aa71a956649f6f81facc8ed4e669b
Stack trace of thread 25595:
#0 0x7fcb00720c4c __pthread_kill_implementation (libc.so.6
+ 0x8ec4c)
#1 0x7fcb006d09c6 raise (libc.so.6 + 0x3e9c6)
#2 0x7fcb006ba7f4 abort (libc.so.6 + 0x287f4)
#3 0x7fcb019224f5 _ZNK14QMessageLogger5fatalEPKcz
(libQt5Core.so.5 + 0xb14f5)
#4 0x7fcb01f5136b
_ZN22QGuiApplicationPrivate25createPlatformIntegrationEv (libQt5Gui.so.5 +
0x16336b)
#5 0x7fcb01f51818
_ZN22QGuiApplicationPrivate21createEventDispatcherEv (libQt5Gui.so.5 +
0x163818)
#6 0x7fcb01b1fb01 _ZN23QCoreApplicationPrivate4initEv
(libQt5Core.so.5 + 0x2aeb01)
#7 0x7fcb01f53bc3 _ZN22QGuiApplicationPrivate4initEv
(libQt5Gui.so.5 + 0x165bc3)
#8 0x7fcb00ea733d _ZN19QApplicationPrivate4initEv
(libQt5Widgets.so.5 + 0x1b433d)
#9 0x7fcb02b31b94
_ZN4KWin11ApplicationC1ENS0_13OperationModeERiPPc (libkwin.so.5 + 0x235b94)
#10 0x5575f87c7072 main (kwin_x11 + 0x34072)
#11 0x7fcb006bb550 __libc_start_call_main (libc.so.6 +
0x29550)
#12 0x7fcb006bb609 __libc_start_main@@GLIBC_2.34 (libc.so.6
+ 0x29609)
#13 0x5575f87c86a5 _start (kwin_x11 + 0x356a5)
ELF object binary architecture: AMD x86-64```
--
You are receiving this mail because:
You are watching all bug changes.
[kwin] [Bug 459740] KWin Crashes when I launch LibreSprite
https://bugs.kde.org/show_bug.cgi?id=459740 --- Comment #2 from Charlie Baker --- (In reply to David Edmundson from comment #1) > It doesn't crash here, I'm afraid we will need a crash log of kwin to > proceed. > > Please check coredumpctl kwin_wayland I'm running Plasma(X11) - is the command changed to `coredumpctl kwin_x11` ? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 459740] KWin Crashes when I launch LibreSprite
https://bugs.kde.org/show_bug.cgi?id=459740 Charlie Baker changed: What|Removed |Added CC||charl.cj.mo...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 459740] New: KWin Crashes when I launch LibreSprite
https://bugs.kde.org/show_bug.cgi?id=459740 Bug ID: 459740 Summary: KWin Crashes when I launch LibreSprite Classification: Plasma Product: kwin Version: 5.25.5 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: charl.cj.mo...@gmail.com Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** KWin crashes whenever I try launching LibreSprite - as a LibreSprite dev and talking with other devs, it isn't a LibreSprite issue - something is wrong with KWin - so basically when I launch LibreSprite (both from terminal and app launcher), all my open apps stay running, KWin crashes and gives the crash notification STEPS TO REPRODUCE 1. Compile LibreSprite 2. Run LibreSprite 3. Observe OBSERVED RESULT KWin crashes whenever LibreSprite is launched. EXPECTED RESULT LibreSprite to launch normally, with KWin not crashing. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 36 KDE Spin (available in About System) KDE Plasma Version: 5.25.5 KDE Frameworks Version: 5.98.0 Qt Version: 5.15.5 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 456789] Segmentation fault plasmashell Crashes on system Boot.
https://bugs.kde.org/show_bug.cgi?id=456789 --- Comment #1 from Charlie Ramirez Animation Studios MX --- Created attachment 150667 --> https://bugs.kde.org/attachment.cgi?id=150667=edit Dr Konqui Screen at boot -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 456789] New: Segmentation fault plasmashell Crashes on system Boot.
https://bugs.kde.org/show_bug.cgi?id=456789 Bug ID: 456789 Summary: Segmentation fault plasmashell Crashes on system Boot. Product: plasmashell Version: 5.24.5 Platform: Debian testing OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: Startup process Assignee: plasma-b...@kde.org Reporter: todo.ciencia.y.electron...@gmail.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 Created attachment 150666 --> https://bugs.kde.org/attachment.cgi?id=150666=edit Plasmashell Backtrace by DrKonqui SUMMARY Plasmashell Hangs during normal debian boot Launching Dr Konqi at the same time it starts the graphical environment. indicating that "Plasma unexpectedly quit" due to plasmashell PID: 1736 Signal: Segmentation fault (11) STEPS TO REPRODUCE 1. The problem started to occur suddenly after one of the Debian kernel updates around March 2022. 2. there is no clear way to observe the faulty component as it occurs during startup (after log in. During the black animated screen loading the Plasma desktop and the appearance of the desktop or windows from the previous session) 3. Reinstalling plasma through Apt and updating debian daily does not solve the problem, OBSERVED RESULT at boot time during desktop loading, the screen stays black for a few extra seconds after which the Dr Konqui screen appears stating that Plasma quit unexpectedly as the desktop background finishes loading. sometimes the error reporting window does not appear immediately instead an icon is displayed on the bar indicating that plasma failed and press if you want to report the failure [The desktop and plasma seem to work normally after this. until the equipment is turned off and starts up again]. # Suspend does not generate hang only on boot. EXPECTED RESULT The report wizard always returns that backtraces are not useful [See Attachment]. and requieres report manually. - because it only happens during boot I haven't been able to find a way to replicate it other than power off and on. [try to use gdb but it returns nothing] and coredumpctl is not located when using terminal. SOFTWARE/OS VERSIONS Operating System: Debian GNU/Linux KDE Plasma Version: 5.24.5 KDE Frameworks Version: 5.94.0 Qt Version: 5.15.4 Kernel Version: 5.18.0-2-amd64 (64-bit) Graphics Platform: X11 Processors: 8 × AMD Ryzen 5 3500U with Radeon Vega Mobile Gfx Memory: 13.6 GiB of RAM Graphics Processor: AMD Radeon Vega 8 Graphics ADDITIONAL INFORMATION -Debian 11 stable with Testing Repo and dual boot with Windows 11 . -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ki18n] [Bug 449452] Obsolete name for Mexico City Timezone
https://bugs.kde.org/show_bug.cgi?id=449452 --- Comment #2 from Charlie Ramirez Animation Studios MX --- (In reply to Christophe Giboudeaux from comment #1) > Current plasma versions depend on iso-codes, where the translation is > correct [1] > > [1] > https://salsa.debian.org/iso-codes-team/iso-codes/-/blob/main/iso_3166-2/es. > po#L14200 > > Which plasma-workspace version do you use? About 2 weeks after I started the thread, it was also updated in debian so now it also shows the correct name. however it was strange because before (this) update when it happened. -Default version packaged with debian 11 [Correct Name]. -Activate the Testing repositories and in that update the change to the previous name occurred. -2 weeks later it was corrected. [I had to change equipment a little less than 1 month ago, so I no longer have the version on which I opened the bug] -- You are receiving this mail because: You are watching all bug changes.
[juk] [Bug 453761] Juk Crash, if application is opened using media from unmounted partition [before mount]
https://bugs.kde.org/show_bug.cgi?id=453761 Charlie Ramirez Animation Studios MX changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=453763 -- You are receiving this mail because: You are watching all bug changes.
[juk] [Bug 453763] Juk Starts or Shows Volume 0% as a giant Negative Number tending to infinity
https://bugs.kde.org/show_bug.cgi?id=453763 Charlie Ramirez Animation Studios MX changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=453761 -- You are receiving this mail because: You are watching all bug changes.
[juk] [Bug 453763] Juk Starts or Shows Volume 0% as a giant Negative Number tending to infinity
https://bugs.kde.org/show_bug.cgi?id=453763 --- Comment #1 from Charlie Ramirez Animation Studios MX --- Created attachment 148817 --> https://bugs.kde.org/attachment.cgi?id=148817=edit Screenshot showing volume set to -2 147 483 648 percent in slide Bar the occurrence of the event seems to be somewhat random, since sometimes when changing the song the already adjusted volume value returns to the giant negative -- You are receiving this mail because: You are watching all bug changes.
[juk] [Bug 453763] New: Juk Starts or Shows Volume 0% as a giant Negative Number tending to infinity
https://bugs.kde.org/show_bug.cgi?id=453763 Bug ID: 453763 Summary: Juk Starts or Shows Volume 0% as a giant Negative Number tending to infinity Product: juk Version: 21.12.3 Platform: Debian testing OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: whee...@kde.org Reporter: todo.ciencia.y.electron...@gmail.com CC: mp...@kde.org Target Milestone: --- Created attachment 148813 --> https://bugs.kde.org/attachment.cgi?id=148813=edit Screenshot showing volume set to -2 147 483 648 percent SUMMARY *** Using the default installation of Debian 11 and default settings. When opening Juk on many occasions the volume is set as a giant negative number that needs to be raised manually with the slider. *** STEPS TO REPRODUCE 1. Open Juk normaly. 2. You should notice that the volume is muted; click or hover over the speaker icon, you will notice that the volume is set to negative (see attached). Sometimes the negative figure will also be displayed both at the bottom of the slider or just on hover 3. Increase the volume by sliding the bar (at the first touch with the click the number will return to zero and it will work normally if you try to increase the volume with the key shortcuts, only the negative number will be reduced, being too large does not produce changes) OBSERVED RESULT I don't know if the volume is usually set by default to 0 and has to be adjusted whenever juk is started, that is part of the problem, although it can be patch-corrected by simply clicking on the slider, the value should not drop to negatives, leaving keyboard shortcuts not working as a result EXPECTED RESULT The volume should remain at a "theoretical" zero or based on the last time it was used?. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Operating System: Debian GNU/Linux KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.90.0 Qt Version: 5.15.2 Kernel Version: 5.17.0-1-amd64 (64-bit) Graphics Platform: X11 Processors: 8 × AMD Ryzen 5 3500U with Radeon Vega Mobile Gfx Memory: 13.6 GiB of RAM Graphics Processor: AMD Radeon Vega 8 Graphics ADDITIONAL INFORMATION It is unknown if the bug could be related to the crash if juk is booted with media from an unmounted drive. https://bugs.kde.org/show_bug.cgi?id=453761 -- You are receiving this mail because: You are watching all bug changes.
[juk] [Bug 453761] Juk Crash, if application is opened using media from unmounted partition [before mount]
https://bugs.kde.org/show_bug.cgi?id=453761 --- Comment #1 from Charlie Ramirez Animation Studios MX --- Created attachment 148808 --> https://bugs.kde.org/attachment.cgi?id=148808=edit kde error Handler Screen after crash -- You are receiving this mail because: You are watching all bug changes.
[juk] [Bug 453761] New: Juk Crash, if application is opened using media from unmounted partition [before mount]
https://bugs.kde.org/show_bug.cgi?id=453761 Bug ID: 453761 Summary: Juk Crash, if application is opened using media from unmounted partition [before mount] Product: juk Version: 21.12.3 Platform: Debian testing OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: whee...@kde.org Reporter: todo.ciencia.y.electron...@gmail.com CC: mp...@kde.org Target Milestone: --- Created attachment 148807 --> https://bugs.kde.org/attachment.cgi?id=148807=edit KCrash Handler Generated Backtrace SUMMARY *** Using Juk Defaults in Debian 11 With Testing Repositories. Juk usually opens by default on startup [Function expected correct]. and remains in the background until the user needs it. -If Juke is configured to Read media or use a default music folder from a secondary Drive or unmounted partition, Juk will boot normally but will not show the playlist, If the source drive is mounted while juk is already open , at the time of scanning or pressing the play button the program will close suddenly, launching the error reporting wizard. If Juk is opened again (already with the media drive mounted) it will operate normally. And the playlist visible from the beginning *** -Inverse trace generated by the assistant is attached. But apparently not useful. STEPS TO REPRODUCE 1. Using a default installation of juk on debian 11 start it. 2. Open the Juk folder settings and configure a Media Folder as a single folder located on a secondary disk or Partition that is not mounted by default when booting debian, save changes and scan. [play some music, juk should work fine so far] 3. Reboot or shutdown Debian. (it doesn't matter if Juk is closed or stays in the background). Upon reboot, open an instance of juk [the partition or drive configured as source should not be mounted at this point yet]. 4. With juk open (as is), mount the drive with the media folder and hit the play button or try scanning the folder. [Juk should close and pop up a notification to generate a crash report]. OBSERVED RESULT The report assistant will only tell you that the generated backtrace is useless. or it lacks data to generate a report, or it must be done manually. giving the option to close or restart Juk. If Juk is rebooted (remember the media drive is already mounted now). juke will show the list of songs and work normally EXPECTED RESULT juk should not hang when mounting media and trying to play if media is not mounted before juk starts. SOFTWARE/OS VERSIONS Operating System: Debian GNU/Linux KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.90.0 Qt Version: 5.15.2 Kernel Version: 5.17.0-1-amd64 (64-bit) Graphics Platform: X11 Processors: 8 × AMD Ryzen 5 3500U with Radeon Vega Mobile Gfx Memory: 13.6 GiB of RAM Graphics Processor: AMD Radeon Vega 8 Graphics ADDITIONAL INFORMATION Probably unrelated, the media partition is on NTFS (Dualboot System -Windows). reason why it is not usually mounted by default on boot. -Inverse trace generated by the assistant is attached. -there is a secondary bug where juk in the same version, starts with the volume at 0% [But displayed as a volume number too large or tending to infinity, which must be manually raised in the frontend to return to zero or desired level and operate normally, I will open a separate Bug for this. ] -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 449452] New: Digital Clock on activity Bar Shows Incorrect (Obsolete name) for Mexico City Timezone
https://bugs.kde.org/show_bug.cgi?id=449452 Bug ID: 449452 Summary: Digital Clock on activity Bar Shows Incorrect (Obsolete name) for Mexico City Timezone Product: plasmashell Version: 5.23.5 Platform: Debian testing OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Digital Clock Assignee: plasma-b...@kde.org Reporter: todo.ciencia.y.electron...@gmail.com Target Milestone: 1.0 Created attachment 146121 --> https://bugs.kde.org/attachment.cgi?id=146121=edit Plasma shows Former Federal District name instead Mexico City SUMMARY ***Plasma refers to the city of Mexico, under the old name of the Federal District in various instances of the digital clock*** STEPS TO REPRODUCE --preferably with the system in Spanish language Mexico (ES_MX Locale) 1. Set and/or add aditional Timezone to Mexico City (CDT) [America/Mexico_City Central Time] timezone on the digital clock 2. click to open, or simply hover over the digital clock In both cases you will notice the Phrase Mexico D.F. on the clock and timezones 3. select customizable digital clock settings, Select to display city as time zone instead of CDT OBSERVED RESULT in all cases that plasmashell refers to the time zone or mexico city, it refers to it with the old Name of "Mexico D.F. (Federal District)". [See attachment] EXPECTED RESULT -Due to changes in the political and administrative organization of the country, since 2015, the federal district of Mexico was dissolved in 2016,making it the 32st state in the country, officially establishing as the the change of name of the locality and its respective ISO 3166 & ISO 3166-2:MX codes, as Mexico City for which the use of the Federal District as a geographic or political entity is considered incorrect, and since the year 2017 should be referred to as Mexico City only, allowing and spreading the preferential use of the abbreviation: (CDMX) "CiuDad de MéXico" or ISO format (less common): (CMX) in replacement of the abbreviation "DF - D.F." SOFTWARE/OS VERSIONS Linux/KDE Plasma: Debian 11 (stable with Testing Repos) x86_64 Linux 5.15.0-3-amd64 WM: KWin GTK Theme: Breeze [GTK2/3] Icon Theme: ePapirus-Dark KDE Plasma Version: 5.23.5 KDE Frameworks Version: 5.88.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION More info about Federal District Change: https://en.wikipedia.org/wiki/ISO_3166-2:MX |(in spanish better vers.) https://es.wikipedia.org/wiki/ISO_3166-2:MX https://www.excelsior.com.mx/comunidad/2015/04/29/1021330 https://foodandtravel.mx/hola-ciudad-de-mexico-adios-distrito-federal/ -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 447900] Scaling Broken on Windows
https://bugs.kde.org/show_bug.cgi?id=447900 --- Comment #2 from Charlie --- Created attachment 145096 --> https://bugs.kde.org/attachment.cgi?id=145096=edit Correct Scaling -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 447900] Scaling Broken on Windows
https://bugs.kde.org/show_bug.cgi?id=447900 --- Comment #1 from Charlie --- Created attachment 145095 --> https://bugs.kde.org/attachment.cgi?id=145095=edit Fix Scaling -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 447900] New: Scaling Broken on Windows
https://bugs.kde.org/show_bug.cgi?id=447900 Bug ID: 447900 Summary: Scaling Broken on Windows Product: kdiff3 Version: 1.9.4 Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: application Assignee: reeves...@gmail.com Reporter: c...@savagexi.com Target Milestone: --- Created attachment 145094 --> https://bugs.kde.org/attachment.cgi?id=145094=edit Incorrect Scaling Install latest version (note this issue has been true for all versions over the last year) of Kdiff3 on Windows on a machine with a high resolution monitor. For example, I am using a ThinkPad X1 Yoga gen 6 with a screen resolution of 3840x2400. The scaling factor is 300%. When you open the app the menus are squished together and the toolbar is illegible. See screenshot. To fix requires telling windows to take over scaling itself. This is done by right clicking the app in Windows explorer, selecting the compatibility tab and changing the high DPI settings. See screenshot. Reopen Kdiff3. Now it renders correctly. See screenshot. Would be nice if this worked automatically versus having to fix this manually. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 441121] gwenview crashes when opening .jpg in X11 Session (wayland not possible on graphics card)
https://bugs.kde.org/show_bug.cgi?id=441121 --- Comment #10 from Charlie Figura --- Created attachment 142865 --> https://bugs.kde.org/attachment.cgi?id=142865=edit New crash information added by DrKonqi gwenview (21.08.1) using Qt 5.15.2 Gwenview crashed when trying to open a jpg. The images in question were saved by Darktable from Canon Raw images, and ranged in size from 8.2 to 16.4 MiB. -- Backtrace (Reduced): #4 __pthread_kill_implementation (no_tid=0, signo=6, threadid=139626298358848) at pthread_kill.c:44 #5 __pthread_kill_internal (signo=6, threadid=139626298358848) at pthread_kill.c:80 #6 __GI___pthread_kill (threadid=139626298358848, signo=signo@entry=6) at pthread_kill.c:91 #7 0x7efd4d5d6476 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #8 0x7efd4d5bc7b7 in __GI_abort () at abort.c:79 -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 441121] gwenview crashes when opening .jpg in X11 Session (wayland not possible on graphics card)
https://bugs.kde.org/show_bug.cgi?id=441121 Charlie Figura changed: What|Removed |Added CC||cfigur...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 442161] kdenlive crashes using audio effects due Invalid or failed Parsing
https://bugs.kde.org/show_bug.cgi?id=442161 --- Comment #5 from Charlie Ramirez Animation Studios MX --- (In reply to emohr from comment #2) > Gracias por informar. Intente con Flatpak o AppImage oficial para ver si se > trata de un problema de empaque. -2 Error Logs Attached one for Flatpak and another for Appimage Tested using Flatpak The problem Persists, immediately the Sox Echo effect is added, the program closes abruptly, but the error codes displayed by the terminal differ from the snap version The App Image returns even more errors apparently and Quits abruptly for Segment Violation or Floating Comma. I ran app image 2 times; in the first one it closed as soon as it began to reproduce, in the second it did not happen until I added the Sox Echo and set some parameter with a value similar to the other (in this case both in 80) Although at the moment I have only been able to replicate the error by adding the effect in the project, if I use another video or the same video already rendered (new project), it does not seem to happen, although the following sentence when adding the effect continues to be repeated: [mp3 @ 0x7f356803ab40] Estimating duration from bitrate, this may be inaccurate [mp3 @ 0x7f3568059800] Estimating duration from bitrate, this may be inaccurate qml: TRIM AREA ENABLED: false QQmlContext: Cannot set context object on invalid context. QQmlComponent: Cannot create a component in an invalid context QQmlContext: Cannot set context object on invalid context. QQmlComponent: Cannot create a component in an invalid context qml: ENDING DRAG!! === REG FOCUS: false qml: ENDING DRAG!! qml: ENDING DRAG!! qml: ENDING DRAG!! qml: ENDING DRAG!! qml: [kdenlive/effect] qml: [kdenlive/effect] qml: Add effect: sox_echo XML parsing of "sox_echo" . found 4 parameters QLocale: Default value is QVariant(double, 0.5) parsed: "0.5" = = SET EFFECT PARAM: "gain-in" = 0.5 QLocale: Default value is QVariant(double, 1) parsed: "1" = = SET EFFECT PARAM: "gain-out" = 1 QLocale: Default value is QVariant(double, 150) parsed: "150" = = SET EFFECT PARAM: "delay" = 150 QLocale: Default value is QVariant(double, 0.8) parsed: "0.8" = = SET EFFECT PARAM: "decay" = 0.8 END parsing of "sox_echo" . Number of found parameters 4 // GOT CLIP STACK DATA CHANGE: QVector(307) // GOT CLIP STACK DATA CHANGE DONE: QModelIndex(0,0,0x7,TimelineItemModel(0x56133cf5fce0)) = QVector(307) qml: ENDING DRAG!! qml: ENDING DRAG!! qml: ENDING DRAG!! - / SHOW KEYFRAMES: true MUTEX LOCK setmodel MUTEX UNLOCK setmodel MUTEX LOCK loadEffects COUNT: 1 QLocale: Could not load double parameter "" QLocale: Could not load double parameter "" QLocale: Could not load double parameter "" QLocale: Could not load double parameter "" MUTEX UNLOCK loadEffects qml: ENDING DRAG!! qml: ENDING DRAG!! qml: ENDING DRAG!! === REG FOCUS: false -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 442161] kdenlive crashes using audio effects due Invalid or failed Parsing
https://bugs.kde.org/show_bug.cgi?id=442161 --- Comment #4 from Charlie Ramirez Animation Studios MX --- Created attachment 141938 --> https://bugs.kde.org/attachment.cgi?id=141938=edit Error log from kdenlive Appimage (running on Debian 11 terminal) log for Appimage Sep 26 2021 0627 CDT -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 442161] kdenlive crashes using audio effects due Invalid or failed Parsing
https://bugs.kde.org/show_bug.cgi?id=442161 --- Comment #3 from Charlie Ramirez Animation Studios MX --- Created attachment 141937 --> https://bugs.kde.org/attachment.cgi?id=141937=edit Error log from kdenlive FLATPAK (running on Debian 11 terminal) Log for flatpak 26 sep 2021 18:18:46 CDT -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 442161] kdenlive crashes using audio effects due Invalid or failed Parsing
https://bugs.kde.org/show_bug.cgi?id=442161 --- Comment #1 from Charlie Ramirez Animation Studios MX --- I almost forgot. The system is Debian 11 (stable). Clean install from ISO CD with Plasma as the only desktop. (all updated to this day) Software Versión de KDE Plasma: 5.20.5 Versión de KDE Frameworks: 5.78.0 Versión de Qt: 5.15.2 Versión del kernel: 5.10.0-8-amd64 Tipo de OS: 64 bits -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 442161] New: kdenlive crashes using audio effects due Invalid or failed Parsing
https://bugs.kde.org/show_bug.cgi?id=442161 Bug ID: 442161 Summary: kdenlive crashes using audio effects due Invalid or failed Parsing Product: kdenlive Version: 21.08.0 Platform: Snap OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: Effects & Transitions Assignee: vpi...@kde.org Reporter: todo.ciencia.y.electron...@gmail.com Target Milestone: --- Created attachment 141379 --> https://bugs.kde.org/attachment.cgi?id=141379=edit Error log from kdenlive (running on Debian 11 terminal) SUMMARY Snap version of kdenlive on Debian 11 (Clean installation of system and snap) closes abruptly when modifying parameters of audio effects (Discovered with effect "sox_Echo"). When run through terminal, you can get a log of various parsing errors from the splash screen startup. recreating the failure results in similar but final records that toggle between invalid / aborted parsing, invalid context, or double parameter STEPS TO REPRODUCE 1. start kdenlive from terminal (this will show the semi log) 2. create a project 1 video + audio 3. Add sox_echo effect to audio, set the delay parammeter to the minimum or in gradual decrements up to 80 [eventually the closer it gets to the minimum or immediately the kdenlive is placed it will close]. OBSERVED RESULT The terminal will return a series of registers where you can see various error messages by grouping together with some critical error messages, invalid syntax or parsing etc. until abrupt shutdown, or code aborted the project is recoverable when opening again, but as long as the modification of the effect is repeated, the failure will be repeated (it is recommended to open again with the terminal to register or notice changes in the error lines) EXPECTED RESULT Apparently there is some error in the syntax of the code from the start lines of the program, which lead to secondary failures in various components such as filters and effects and the title generator, -Among the errors, there seems to be one related to ALSA. (I don't know if it's the culprit or if it's a debian 11 bug) SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION I will attach a text document with the error messages returned by the method of running through the terminal (There is no difference between running from icon and terminal, the error is repeatable). -The system is clean (less than a week of new installation and kdenlive with less than 2 hours so I doubt it is an error in the system files) -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 424461] New: Crash while several tabs open and activley loading page on XDA website
https://bugs.kde.org/show_bug.cgi?id=424461 Bug ID: 424461 Summary: Crash while several tabs open and activley loading page on XDA website Product: konqueror Version: 5.0.97 Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: konq-b...@kde.org Reporter: phi...@hotmail.com Target Milestone: --- Application: konqueror (5.0.97) Qt Version: 5.13.2 Frameworks Version: 5.70.0 Operating System: Linux 5.6.18-200.fc31.x86_64+debug x86_64 Distribution: "Fedora release 31 (Thirty One)" -- Information about the crash: - What I was doing when the application crashed: Loading page on XDA-Developers Android Forums: www.xda-developers.com -- Backtrace: Application: Konqueror (konqueror), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fa65104f840 (LWP 886173))] Thread 13 (Thread 0x7fa5c3fff700 (LWP 887499)): #0 0x7fa653d56d45 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fa6551b06a0 in std::condition_variable::wait(std::unique_lock&) () at /lib64/libstdc++.so.6 #2 0x7fa62e00f784 in WTF::ParkingLot::parkConditionally(void const*, std::function, std::function, std::chrono::time_point > >) () at /lib64/libQt5WebKit.so.5 #3 0x7fa62d9ab081 in JSC::DFG::Worklist::runThread(JSC::DFG::ThreadData*) () at /lib64/libQt5WebKit.so.5 #4 0x7fa62e011ee9 in WTF::threadEntryPoint(void*) () at /lib64/libQt5WebKit.so.5 #5 0x7fa62e034c3f in WTF::wtfThreadEntryPoint(void*) () at /lib64/libQt5WebKit.so.5 #6 0x7fa653d504e2 in start_thread () at /lib64/libpthread.so.0 #7 0x7fa6574b46a3 in clone () at /lib64/libc.so.6 Thread 12 (Thread 0x7fa5c8bfe700 (LWP 887498)): #0 0x7fa653d56d45 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fa6551b06a0 in std::condition_variable::wait(std::unique_lock&) () at /lib64/libstdc++.so.6 #2 0x7fa62e00f784 in WTF::ParkingLot::parkConditionally(void const*, std::function, std::function, std::chrono::time_point > >) () at /lib64/libQt5WebKit.so.5 #3 0x7fa62d9ab081 in JSC::DFG::Worklist::runThread(JSC::DFG::ThreadData*) () at /lib64/libQt5WebKit.so.5 #4 0x7fa62e011ee9 in WTF::threadEntryPoint(void*) () at /lib64/libQt5WebKit.so.5 #5 0x7fa62e034c3f in WTF::wtfThreadEntryPoint(void*) () at /lib64/libQt5WebKit.so.5 #6 0x7fa653d504e2 in start_thread () at /lib64/libpthread.so.0 #7 0x7fa6574b46a3 in clone () at /lib64/libc.so.6 Thread 11 (Thread 0x7fa5c93ff700 (LWP 887497)): #0 0x7fa653d56d45 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fa6551b06a0 in std::condition_variable::wait(std::unique_lock&) () at /lib64/libstdc++.so.6 #2 0x7fa62e00f784 in WTF::ParkingLot::parkConditionally(void const*, std::function, std::function, std::chrono::time_point > >) () at /lib64/libQt5WebKit.so.5 #3 0x7fa62d9ab081 in JSC::DFG::Worklist::runThread(JSC::DFG::ThreadData*) () at /lib64/libQt5WebKit.so.5 #4 0x7fa62e011ee9 in WTF::threadEntryPoint(void*) () at /lib64/libQt5WebKit.so.5 #5 0x7fa62e034c3f in WTF::wtfThreadEntryPoint(void*) () at /lib64/libQt5WebKit.so.5 #6 0x7fa653d504e2 in start_thread () at /lib64/libpthread.so.0 #7 0x7fa6574b46a3 in clone () at /lib64/libc.so.6 Thread 10 (Thread 0x7fa5dabfd700 (LWP 886454)): #0 0x7fa653d56d45 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fa6551b06a0 in std::condition_variable::wait(std::unique_lock&) () at /lib64/libstdc++.so.6 #2 0x7fa62e00f784 in WTF::ParkingLot::parkConditionally(void const*, std::function, std::function, std::chrono::time_point > >) () at /lib64/libQt5WebKit.so.5 #3 0x7fa62e00e00c in WTF::ParallelHelperPool::waitForClientWithTask(WTF::Locker const&) () at /lib64/libQt5WebKit.so.5 #4 0x7fa62e00e0e2 in WTF::ParallelHelperPool::helperThreadBody() () at /lib64/libQt5WebKit.so.5 #5 0x7fa62e011ee9 in WTF::threadEntryPoint(void*) () at /lib64/libQt5WebKit.so.5 #6 0x7fa62e034c3f in WTF::wtfThreadEntryPoint(void*) () at /lib64/libQt5WebKit.so.5 #7 0x7fa653d504e2 in start_thread () at /lib64/libpthread.so.0 #8 0x7fa6574b46a3 in clone () at /lib64/libc.so.6 Thread 9 (Thread 0x7fa5db3fe700 (LWP 886453)): #0 0x7fa653d56d45 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fa6551b06a0 in std::condition_variable::wait(std::unique_lock&) () at /lib64/libstdc++.so.6 #2 0x7fa62e00f784 in WTF::ParkingLot::parkConditionally(void const*, std::function, std::function, std::chrono::time_point > >) () at /lib64/libQt5WebKit.so.5 #3 0x7fa62e00e00c in WTF::ParallelHelperPool::waitForClientWithTask(WTF::Locker const&) () at /lib64/libQt5WebKit.so.5 #4 0x7fa62e00e0e2 in
[systemsettings] [Bug 421805] New: App crash. When changing from 40-60hz. monitor rate. (secondary screen) Kubuntu
https://bugs.kde.org/show_bug.cgi?id=421805 Bug ID: 421805 Summary: App crash. When changing from 40-60hz. monitor rate. (secondary screen) Kubuntu Product: systemsettings Version: 5.18.4 Platform: Compiled Sources OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: todo.ciencia.y.electron...@gmail.com Target Milestone: --- Application: systemsettings5 (5.18.4) (Compiled from sources) Qt Version: 5.12.8 Frameworks Version: 5.68.0 Operating System: Linux 5.4.0-31-generic x86_64 Windowing system: X11 Distribution: Ubuntu 20.04 LTS -- Information about the crash: - What I was doing when the application crashed: The settings application closes abruptly when changing from 40 to 60hz. monitor refresh rate. On a secondary screen via VGA. on Kubuntu 20.04 Laptop. - Custom settings of the application: (Breeze)"Brisa Dark Theme" enabled. Secondary Screen [LCDTV] Set as principal. [Laptop Screen Disabled]. Scale at 125%. Kubuntu 20.04 in Spanish. Plastik Window Theme. The crash can be reproduced every time. -- Backtrace: Application: Preferencias del sistema (systemsettings5), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fecbd2d3800 (LWP 1555))] Thread 10 (Thread 0x7feca0a39700 (LWP 1570)): #0 0x7fecc11e696f in __GI___poll (fds=0x7fec880029e0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7fecbf4bc1ae in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fecbf4bc2e3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fecc1782583 in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fecc17294db in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fecc1561785 in QThread::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fecc08141a9 in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #7 0x7fecc15629d2 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fecbfda0609 in start_thread (arg=) at pthread_create.c:477 #9 0x7fecc11f3103 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 9 (Thread 0x7feca35ef700 (LWP 1567)): #0 0x7fecbf4bb6b8 in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7fecbf4bc0db in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fecbf4bc2e3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fecc1782583 in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fecc17294db in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fecc1561785 in QThread::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fecc08141a9 in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #7 0x7fecc15629d2 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fecbfda0609 in start_thread (arg=) at pthread_create.c:477 #9 0x7fecc11f3103 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 8 (Thread 0x7fecb18a9700 (LWP 1566)): #0 0x7fecc11e696f in __GI___poll (fds=0x7fec900025e0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7fecbf4bc1ae in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fecbf4bc2e3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fecc1782583 in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fecc17294db in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fecc1561785 in QThread::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fecc08141a9 in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #7 0x7fecc15629d2 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fecbfda0609 in start_thread (arg=) at pthread_create.c:477 #9 0x7fecc11f3103 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 7 (Thread 0x7fecb27fc700 (LWP 1564)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x55c08294001c) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x55c08293ffc8, cond=0x55c08293fff0) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x55c08293fff0, mutex=0x55c08293ffc8) at pthread_cond_wait.c:638 #3 0x7fecb8f6335b in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so #4 0x7fecb8f62f6b in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so #5 0x7fecbfda0609 in start_thread (arg=) at pthread_create.c:477 #6 0x7fecc11f3103 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95
[digikam] [Bug 182838] Facebook tool does not work any more
https://bugs.kde.org/show_bug.cgi?id=182838 --- Comment #31 from Charlie Gorichanaz --- (In reply to Maik Qualmann from comment #30) > Whether we will probably belong to the limited partners...??? Thank you very much Maik for the update. Please let me know if this is rejected for some reason and you need some contacts at Facebook. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 182838] Facebook tool does not work any more
https://bugs.kde.org/show_bug.cgi?id=182838 --- Comment #27 from Charlie Gorichanaz --- (In reply to Maik Qualmann from comment #26) > At the moment we have lost some interest in Facebook. This makes me sad, but I guess now I will not be waiting around for something that may never happen. I was very upset when the Adobe Photoshop Lightroom Facebook integration had a blip and I lost all my photos (https://votecharlie.com/blog/2017/05/years-of-photos-comments-gone-from-facebook.html), and was even more upset there was no way for me to simply use an app to help me upload photos that I would still retain full control over. Now that I switched to Linux, I thought I would give the open source tools a chance as well but found problems there, which are still not solved (this thread). That said, I am not solving them myself even though it is possible for anyone to help, so I therefore should also not complain. I at least wanted the record to show more than one person is interested in this. :-) -- You are receiving this mail because: You are watching all bug changes.
[Touchpad-KCM] [Bug 395722] touchpad settings are wrong after resuming from suspend
https://bugs.kde.org/show_bug.cgi?id=395722 Charlie changed: What|Removed |Added CC||taylorc...@gmail.com --- Comment #7 from Charlie --- I'm experiencing this bug too - it seems that the mouse settings are overriding the touchpad settings after a suspend, as ImreL has discovered. If I untick "Invert scroll direction" in mouse settings, then suddenly the touchpad follows suit after a reboot and the "active settings do not match saved settings" message appears in the touchpad settings. The same goes for changes in the mouse acceleration; this appears to override the touchpad acceleration. I make do by just keeping the settings the same, but ideally it should be otherwise. I'm on manjaro KDE, using libinput on X. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 395203] New: Unable to connect to Facebook due to app settings
https://bugs.kde.org/show_bug.cgi?id=395203 Bug ID: 395203 Summary: Unable to connect to Facebook due to app settings Product: digikam Version: 5.9.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: critical Priority: NOR Component: Export-Facebook Assignee: digikam-bugs-n...@kde.org Reporter: char...@gorichanaz.com Target Milestone: --- When I click "Export to Facebook", and then click "Change Account" (I have never added a Facebook account), I get a popup that says: > Please follow the instructions in the browser window. When done, copy the > Internet address from your browser into the textbox below and press "OK". And my browser opens a tab for the URL: https://www.facebook.com/dialog/oauth?client_id=400589753481372_uri=https%3A%2F%2Fwww.facebook.com%2Fconnect%2Flogin_success.html=user_photos%2Cpublish_actions%2Cuser_friends_type=token Facebook displays an error: > App Not Setup: This app is still in development mode, and you don't have > access to it. Switch to a registered test user or ask an app admin for > permissions. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 376069] Can not open pictures which path string contains chinese
https://bugs.kde.org/show_bug.cgi?id=376069 --- Comment #2 from Charlie Zhang <xiii_1...@163.com> --- (In reply to Christoph Feck from comment #1) > Does Dolphin show a preview of these files, if you enable image previews in > Dolphin? Yes, dolphin preview works fine. -- You are receiving this mail because: You are watching all bug changes.
[i18n] [Bug 376070] New: Wrong translation with 'Desktop Behavior'
https://bugs.kde.org/show_bug.cgi?id=376070 Bug ID: 376070 Summary: Wrong translation with 'Desktop Behavior' Product: i18n Version: unspecified Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: zh_CN Assignee: wen...@gmail.com Reporter: xiii_1...@163.com Target Milestone: --- 'Desktop Behavior' translated as '桌面 \n 行为' in ths control center. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 376069] New: Can not open pictures which path string contains chinese
https://bugs.kde.org/show_bug.cgi?id=376069 Bug ID: 376069 Summary: Can not open pictures which path string contains chinese Product: gwenview Version: 16.12.0 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: critical Priority: NOR Component: general Assignee: gwenview-bugs-n...@kde.org Reporter: xiii_1...@163.com CC: myr...@kde.org Target Milestone: --- I am using Archlinux. When I open a picture which contains Chinese charactor in the path(or filename), Gwenview show me a dialog said 'file does not exist'. The chinese charactors it shows me appearanced as a '�'. I have the right locale values and other application in kde works fine. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 123495] Can't load the file which path name includes Chinese
https://bugs.kde.org/show_bug.cgi?id=123495 Charlie Zhang <xiii_1...@163.com> changed: What|Removed |Added CC||xiii_1...@163.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 366173] plasma task manager "show only tasks from the current screen" shows the wrong list
https://bugs.kde.org/show_bug.cgi?id=366173 Charlie Waters <caw...@me.com> changed: What|Removed |Added CC||caw...@me.com --- Comment #3 from Charlie Waters <caw...@me.com> --- Same issue here on Arch Linux plasmashell 5.7.3, proprietary Nvidia drivers 367.35. Three monitors, all connected to a single Nvidia card. Left to right: DP-1, DVI-I-1, DVI-D-0. With "show only tasks from the current screen" enabled on all task managers, task manager on DP-1 shows tasks from DVI-D-0, and the task manager on DVI-D-0 shows tasks from DP-1. The task manager on DVI-I-1 is normal. This behavior has been very consistent for several weeks. I have tried different combinations of task managers and panels, but the behavior is always the same. My guess would be that under some conditions, the monitors are enumerated in reverse order. $ xrandr Screen 0: minimum 8 x 8, current 5760 x 1080, maximum 16384 x 16384 DVI-I-0 disconnected (normal left inverted right x axis y axis) DVI-I-1 connected primary 1920x1080+1920+0 (normal left inverted right x axis y axis) 553mm x 311mm 1920x1080 60.00*+ 1680x1050 59.95 1440x900 74.9859.89 1280x1024 75.0260.02 1280x960 60.00 1280x720 60.00 1152x864 75.00 1024x768 75.0370.0760.00 800x600 75.0072.1960.3256.25 640x480 75.0072.8159.94 HDMI-0 disconnected (normal left inverted right x axis y axis) DP-0 disconnected (normal left inverted right x axis y axis) DVI-D-0 connected 1920x1080+3840+0 (normal left inverted right x axis y axis) 553mm x 311mm 1920x1080 60.00*+ 1680x1050 59.95 1440x900 74.9859.89 1280x1024 75.0260.02 1280x960 60.00 1280x720 60.00 1152x864 75.00 1024x768 75.0370.0760.00 800x600 75.0072.1960.3256.25 640x480 75.0072.8159.94 DP-1 connected 1920x1080+0+0 (normal left inverted right x axis y axis) 553mm x 311mm 1920x1080 60.00*+ 59.9450.0060.0050.04 1680x1050 59.95 1440x900 74.9859.89 1280x1024 75.0260.02 1280x960 60.00 1280x720 60.0059.9450.00 1152x864 75.00 1024x768 75.0370.0760.00 800x600 75.0072.1960.3256.25 720x576 50.00 720x480 59.94 640x480 75.0072.8159.9459.93 480x576 50.00 480x480 59.94 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 359865] Krita Gemini not drawing at right place on screen
https://bugs.kde.org/show_bug.cgi?id=359865 --- Comment #2 from Charlie Tanner <charles.c.tan...@googlemail.com> --- Switching to Desktop 2.9 branch seems to have solved the problem, though it is a rather frustrating solution considering I paid for Gemini. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 359865] New: Krita Gemini not drawing at right place on screen
https://bugs.kde.org/show_bug.cgi?id=359865 Bug ID: 359865 Summary: Krita Gemini not drawing at right place on screen Product: krita Version: 2.9.11 Platform: unspecified OS: MS Windows Status: UNCONFIRMED Severity: grave Priority: NOR Component: krita gemini Assignee: krita-bugs-n...@kde.org Reporter: charles.c.tan...@googlemail.com When drawing on Krita Gemini, Krita doesn't draw where the pen is on the screen, but instead roughly halfway between the top left screen corner and where the pen is i.e. if I tap on the very centre of the screen, it draws roughly a quarter the way along the diagonal from the top left. The UI works perfectly fine with the pen. Drawing with my finger or mouse is perfectly fine. The issue is only present when drawing on the canvas with the pen. Reproducible: Always Steps to Reproduce: 1.Open Krita 2.Try drawing on canvas 3. Actual Results: Krita draws up and left of the pen. Expected Results: Krita draws where the pen makes contact. I have used Krita desktop before, and that does not exhibit the same problem, it's just Krita Gemini, as bought on Steam. I am using a Surface Pro 4 with Wintab drivers installed. -- You are receiving this mail because: You are watching all bug changes.
