[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&action=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&action=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.
[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&action=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&action=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 /lib/x86_64-linux-gnu/libQt5Core.s
[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&action=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&action=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.
[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&action=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&action=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&action=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&action=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&action=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&action=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&action=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.
[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&action=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&action=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&action=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.
[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 Thread
