[kde] [Bug 459942] New: The second side menu is not removed
https://bugs.kde.org/show_bug.cgi?id=459942 Bug ID: 459942 Summary: The second side menu is not removed Classification: I don't know Product: kde Version: unspecified Platform: Archlinux OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: vitaly.hawan...@yandex.ru Target Milestone: --- STEPS TO REPRODUCE 1. Run Settings 2. Go to the "Appearance" tab 3. Right click on sound widget 4. "Set up sound devices" OBSERVED RESULT https://media.discordapp.net/attachments/718825766179045389/1026528186055540786/unknown.png?width=851&height=457 EXPECTED RESULT https://media.discordapp.net/attachments/718825766179045389/1026528264249942016/unknown.png?width=854&height=457 SOFTWARE/OS VERSIONS KDE Plasma 5.25.5 KDE Frameworks Version: 5.98.0 Qt Version: 5.15.6 Kernel: linux 5.15.71-1-lts (64-bit) On wayland -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 459942] The second side menu in settings not removing when i open sound settings from sound widget
https://bugs.kde.org/show_bug.cgi?id=459942 Vitaly changed: What|Removed |Added Summary|The second side menu is not |The second side menu in |removed |settings not removing when ||i open sound settings from ||sound widget -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 408928] Keyboard layout OSD doesn't work on X
https://bugs.kde.org/show_bug.cgi?id=408928 Vitaly changed: What|Removed |Added CC||vch...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 220582] Desktop Grid plug-in crashes when moving pinned window [QHash::findNode, QHash
https://bugs.kde.org/show_bug.cgi?id=220582 vitaly changed: What|Removed |Added CC||vitalka...@ukr.net -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwindowsystem] [Bug 423674] New: kwin-x11 crashing all the time
https://bugs.kde.org/show_bug.cgi?id=423674 Bug ID: 423674 Summary: kwin-x11 crashing all the time Product: frameworks-kwindowsystem Version: 5.71.0 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: vitalka...@ukr.net Target Milestone: --- SUMMARY kwin-x11 crashing all the time and all opened windows are moving up on screen and control buttons are disapearing STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwindowsystem] [Bug 423674] kwin-x11 crashing all the time
https://bugs.kde.org/show_bug.cgi?id=423674 --- Comment #2 from vitaly --- (In reply to David Edmundson from comment #1) > Crashes need a backtrace. > > See the sad face icon in the system tray. Alredy meny times) -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwindowsystem] [Bug 423674] kwin-x11 crashing all the time
https://bugs.kde.org/show_bug.cgi?id=423674 --- Comment #4 from vitaly --- Application: KWin (kwin_x11), signal: Aborted [KCrash Handler] #4 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51 #5 0x7f474a298801 in __GI_abort () at abort.c:79 #6 0x7f471a539eb2 in ?? () from /usr/lib/x86_64-linux-gnu/dri/vmwgfx_dri.so #7 0x7f471a53d670 in ?? () from /usr/lib/x86_64-linux-gnu/dri/vmwgfx_dri.so #8 0x7f471a50b947 in ?? () from /usr/lib/x86_64-linux-gnu/dri/vmwgfx_dri.so #9 0x7f471a6cf724 in ?? () from /usr/lib/x86_64-linux-gnu/dri/vmwgfx_dri.so #10 0x7f471a5e8e18 in ?? () from /usr/lib/x86_64-linux-gnu/dri/vmwgfx_dri.so #11 0x7f471a5d43b3 in ?? () from /usr/lib/x86_64-linux-gnu/dri/vmwgfx_dri.so #12 0x7f471a1502a6 in ?? () from /usr/lib/x86_64-linux-gnu/dri/vmwgfx_dri.so #13 0x7f471a14b10a in ?? () from /usr/lib/x86_64-linux-gnu/dri/vmwgfx_dri.so #14 0x7f47249569d8 in ?? () from /usr/lib/x86_64-linux-gnu/libGLX_mesa.so.0 #15 0x7f473c8d3a53 in ?? () from /usr/lib/x86_64-linux-gnu/libGLX.so.0 #16 0x7f473c8d4edb in ?? () from /usr/lib/x86_64-linux-gnu/libGLX.so.0 #17 0x7f4724bc0bbb in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/xcbglintegrations/libqxcb-glx-integration.so #18 0x7f474b4e9207 in QOpenGLContext::doneCurrent() () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 #19 0x7f474a03ba80 in KWin::EffectQuickView::EffectQuickView(QObject*, KWin::EffectQuickView::ExportMode) () from /usr/lib/x86_64-linux-gnu/libkwineffects.so.12 #20 0x7f472c2dd07e in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/org.kde.kdecoration2/kwin5_aurorae.so #21 0x7f474d826fbe in KWin::Decoration::DecorationBridge::createDecoration(KWin::AbstractClient*) () from /usr/lib/x86_64-linux-gnu/libkwin.so.5 #22 0x7f474d95c9fc in KWin::X11Client::createDecoration(QRect const&) () from /usr/lib/x86_64-linux-gnu/libkwin.so.5 #23 0x7f474d958a01 in KWin::X11Client::updateDecoration(bool, bool) () from /usr/lib/x86_64-linux-gnu/libkwin.so.5 #24 0x7f474d95f292 in KWin::X11Client::manage(unsigned int, bool) () from /usr/lib/x86_64-linux-gnu/libkwin.so.5 #25 0x7f474d944267 in KWin::Workspace::createClient(unsigned int, bool) () from /usr/lib/x86_64-linux-gnu/libkwin.so.5 #26 0x7f474d852a7f in KWin::Workspace::workspaceEvent(xcb_generic_event_t*) () from /usr/lib/x86_64-linux-gnu/libkwin.so.5 #27 0x7f474aea74df in QAbstractEventDispatcher::filterNativeEvent(QByteArray const&, void*, long*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #28 0x7f47363dfbac in QXcbConnection::handleXcbEvent(xcb_generic_event_t*) () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #29 0x7f47363e06d6 in QXcbConnection::processXcbEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #30 0x7f473640532c in ?? () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #31 0x7f474aea8d2a in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #32 0x7f474aeb24a0 in QCoreApplication::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #33 0x55d25f5703db in ?? () #34 0x7f474a279b97 in __libc_start_main (main=0x55d25f570010, argc=3, argv=0x7fffc47bec08, init=, fini=, rtld_fini=, stack_end=0x7fffc47bebf8) at ../csu/libc-start.c:310 #35 0x55d25f57096a in _start () -- You are receiving this mail because: You are watching all bug changes.
[qca] [Bug 422734] New: QCA freezes on receiving a list of certificates (OS Windows Qt-5.15.0 MSVC2019)
https://bugs.kde.org/show_bug.cgi?id=422734 Bug ID: 422734 Summary: QCA freezes on receiving a list of certificates (OS Windows Qt-5.15.0 MSVC2019) Product: qca Version: Git Platform: Compiled Sources OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dr...@land.ru Reporter: the...@gmail.com CC: aa...@kde.org, br...@frogmouth.net, jus...@karneges.com Target Milestone: --- Running the cipherunittest test freezes. STEPS TO REPRODUCE 1. compile qca library in QtCreator 2. run cipherunittest OBSERVED RESULT cipherunittest freezes EXPECTED RESULT cipherunittest should pass SOFTWARE/OS VERSIONS Windows: 10 Qt Version: 5.15.0 msvc64_2019 ADDITIONAL INFORMATION Psi-im has the same behavior when it receives a list of certificates. The library was built in the environment of MSVC2019 x64 with official Qt libraries version 5.15.0 in the Windows operating system. The same behavior is observed when running a test built using mingw32 cross-compilation (MXE). When I'm pressing a pause button on program hangs the QtCreator shows this line https://github.com/KDE/qca/blob/ae5dec259faf60bec8cf1559d20876e6a5960f7a/src/support/syncthread.cpp#L183 and ok value is -52. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 414848] New: Problem with additing Slide-Show Clip to project in MS Win
https://bugs.kde.org/show_bug.cgi?id=414848 Bug ID: 414848 Summary: Problem with additing Slide-Show Clip to project in MS Win Product: kdenlive Version: 18.12.1 Platform: MS Windows OS: MS Windows Status: REPORTED Severity: normal Priority: NOR Component: Effects & Transitions Assignee: vpi...@kde.org Reporter: vvfi...@mail.ru Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Problem with additing Slide-Show Clip to project. Error Window writes me "Clip is invalid and will removed from project". And some strange line: c:/dir1/dir2/dir3\.all.jpg 2. In Ubuntu it works normaly. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 414850] New: I can only drug files to Project's Tree. It isn't work selections from folders.
https://bugs.kde.org/show_bug.cgi?id=414850 Bug ID: 414850 Summary: I can only drug files to Project's Tree. It isn't work selections from folders. Product: kdenlive Version: 18.12.1 Platform: MS Windows OS: MS Windows Status: REPORTED Severity: normal Priority: NOR Component: Effects & Transitions Assignee: vpi...@kde.org Reporter: vvfi...@mail.ru Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1.Press button "Add clip to project" 2. Select any folder (Docs, Video) 3. It's display only KDENLIVE's folders (Bin,Etc, Lib...) 4. I can only drug files to Project's Tree to work. Ubuntu version hasn't this problem. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 421597] New: Crash when new window opening cancelled
https://bugs.kde.org/show_bug.cgi?id=421597 Bug ID: 421597 Summary: Crash when new window opening cancelled Product: konqueror Version: 5.0.97 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: konq-b...@kde.org Reporter: vch...@gmail.com Target Milestone: --- Application: konqueror (5.0.97) Qt Version: 5.12.4 Frameworks Version: 5.62.0 Operating System: Linux 5.3.0-51-generic x86_64 Distribution: Ubuntu 19.10 -- Information about the crash: - What I was doing when the application crashed: Right click on a link on any web page, select "Open link in a new window" in popup menu. In the information message box appeared with question "Open ?" select "Cancel" button. Konqueror will crash immediately. The crash can be reproduced every time. -- Backtrace: Application: Konqueror (konqueror), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f8f8e0cc680 (LWP 28824))] Thread 18 (Thread 0x7f8f0a7fc700 (LWP 30533)): #0 0x7f8f909ae6e0 in futex_abstimed_wait_cancelable (private=, abstime=0x7f8f0a7fbb30, clockid=, expected=0, futex_word=0x7f8f0a7fbc78) at ../sysdeps/unix/sysv/linux/futex-internal.h:208 #1 0x7f8f909ae6e0 in __pthread_cond_wait_common (abstime=0x7f8f0a7fbb30, clockid=, mutex=0x7f8f0a7fbc28, cond=0x7f8f0a7fbc50) at pthread_cond_wait.c:520 #2 0x7f8f909ae6e0 in __pthread_cond_timedwait (cond=0x7f8f0a7fbc50, mutex=0x7f8f0a7fbc28, abstime=0x7f8f0a7fbb30) at pthread_cond_wait.c:656 #3 0x7f8f7395d10b in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7f8f7395dab2 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7f8f7395dba6 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7f8f7391f705 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7f8f73921c6b in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #8 0x7f8f73922258 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #9 0x7f8f7395fc75 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #10 0x7f8f909a7669 in start_thread (arg=) at pthread_create.c:479 #11 0x7f8f940ea323 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 17 (Thread 0x7f8f097fa700 (LWP 28923)): #0 0x7f8f909ae6e0 in futex_abstimed_wait_cancelable (private=, abstime=0x7f8f097f9b30, clockid=, expected=0, futex_word=0x7f8f097f9c78) at ../sysdeps/unix/sysv/linux/futex-internal.h:208 #1 0x7f8f909ae6e0 in __pthread_cond_wait_common (abstime=0x7f8f097f9b30, clockid=, mutex=0x7f8f097f9c28, cond=0x7f8f097f9c50) at pthread_cond_wait.c:520 #2 0x7f8f909ae6e0 in __pthread_cond_timedwait (cond=0x7f8f097f9c50, mutex=0x7f8f097f9c28, abstime=0x7f8f097f9b30) at pthread_cond_wait.c:656 #3 0x7f8f7395d10b in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7f8f7395dab2 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7f8f7395dba6 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7f8f7391f705 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7f8f73921f96 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #8 0x7f8f73922258 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #9 0x7f8f7395fc75 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #10 0x7f8f909a7669 in start_thread (arg=) at pthread_create.c:479 #11 0x7f8f940ea323 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 16 (Thread 0x7f8f0b7fe700 (LWP 28919)): #0 0x7f8f909ae2c6 in futex_wait_cancelable (private=, expected=0, futex_word=0x7f8f0b7fdc88) at ../sysdeps/unix/sysv/linux/futex-internal.h:80 #1 0x7f8f909ae2c6 in __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x7f8f0b7fdc38, cond=0x7f8f0b7fdc60) at pthread_cond_wait.c:508 #2 0x7f8f909ae2c6 in __pthread_cond_wait (cond=0x7f8f0b7fdc60, mutex=0x7f8f0b7fdc38) at pthread_cond_wait.c:638 #3 0x7f8f7395d03d in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7f8f7395dac0 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7f8f7395db63 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7f8f7391f718 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7f8f73921c6b in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #8 0x7f8f739222b8 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #9 0x7f8f7395fc75 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #10 0x7f8f909a7669 in start_thread (arg=) at pthread_create.c:479 #11 0x7f8f940ea323 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 15 (Thread 0x7f8f227fc700 (LWP 288
[systemsettings] [Bug 414043] New: Notification sounds volume setting is broken
https://bugs.kde.org/show_bug.cgi?id=414043 Bug ID: 414043 Summary: Notification sounds volume setting is broken Product: systemsettings Version: 5.17.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: vito.korot...@gmail.com Target Milestone: --- SUMMARY Notification Sounds (volume change, Spectacle shutter) disappear when changing their volume in Sound KCM, and the volume slider starts to work incorrectly. STEPS TO REPRODUCE 1. Go to sound settings, apps. 2. To try to change the volume level of your notifications. OBSERVED RESULT The inability to change the volume of notifications and complete disappearance of their sounds. https://youtu.be/iIpF2SkhgKs SOFTWARE/OS VERSIONS openSUSE Tumbleweed and KDE Neon User Edition with KDE Plasma 5.17.2 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 401113] New: When you try to install Skype, the installation does not occur. Writes a message to disable the lock Snap.
https://bugs.kde.org/show_bug.cgi?id=401113 Bug ID: 401113 Summary: When you try to install Skype, the installation does not occur. Writes a message to disable the lock Snap. Product: Discover Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: discover Assignee: aleix...@kde.org Reporter: v...@live.ru Target Milestone: --- Created attachment 116355 --> https://bugs.kde.org/attachment.cgi?id=116355&action=edit screenshot SUMMARY STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: MacOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 401113] When you try to install Skype, the installation does not occur. Writes a message to disable the lock Snap.
https://bugs.kde.org/show_bug.cgi?id=401113 --- Comment #2 from Vitaly --- Операционная система: KDE neon 5.14 Версия KDE Plasma: 5.14.3 Версия Qt: 5.11.2 Версия KDE Frameworks: 5.52.0 Версия ядра: 4.15.0-42-generic Архитектура: 64-битная Процессоры: 2 × Intel® Celeron® CPU 887 @ 1.50GHz Память: 3,8 ГиБ ОЗУ -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 401113] When you try to install Skype, the installation does not occur. Writes a message to disable the lock Snap.
https://bugs.kde.org/show_bug.cgi?id=401113 --- Comment #3 from Vitaly --- Came out of the situation as follows: downloaded on the official website deb package skype and installed it -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 401113] When you try to install Skype, the installation does not occur. Writes a message to disable the lock Snap.
https://bugs.kde.org/show_bug.cgi?id=401113 --- Comment #5 from Vitaly --- Thanks! Спасибо! Вообще мне очень нравится KDE neon! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 496352] New: Plasma reported a crash after changing accent color to a custom value
https://bugs.kde.org/show_bug.cgi?id=496352 Bug ID: 496352 Summary: Plasma reported a crash after changing accent color to a custom value Classification: Plasma Product: plasmashell 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: vitaly.koro...@gmail.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 Application: plasmashell (5.27.5) Qt Version: 5.15.8 Frameworks Version: 5.103.0 Operating System: Linux 6.1.0-27-arm64 aarch64 Windowing System: Wayland Distribution: Debian GNU/Linux 12 (bookworm) DrKonqi: 5.27.5 [CoredumpBackend] -- Information about the crash: Changed accent color to a custom value. The color did get applied and works as expected, but crash was triggered. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault PID: 69050 (plasmashell) UID: 1000 (user) GID: 1000 (user) Signal: 11 (SEGV) Timestamp: Sat 2024-11-16 08:46:10 PST (39s ago) Command Line: /usr/bin/plasmashell --no-respawn Executable: /usr/bin/plasmashell Control Group: /user.slice/user-1000.slice/user@1000.service/session.slice/plasma-plasmashell.service Unit: user@1000.service User Unit: plasma-plasmashell.service Slice: user-1000.slice Owner UID: 1000 (user) Boot ID: ca6e8ccd9bb94437856b651e6a504969 Machine ID: 495e9f50449b4d7ba9eb7b97d53d2a97 Hostname: debian Storage: /var/lib/systemd/coredump/core.plasmashell.1000.ca6e8ccd9bb94437856b651e6a504969.69050.173177557000.zst (present) Size on Disk: 29.0M Message: Process 69050 (plasmashell) of user 1000 dumped core. Module libsystemd.so.0 from deb systemd-252.31-1~deb12u1.arm64 Module libudev.so.1 from deb systemd-252.31-1~deb12u1.arm64 Stack trace of thread 69050: #0 0x99c362c8 pthread_sigmask (libc.so.6 + 0x862c8) #1 0x99bea92c sigprocmask (libc.so.6 + 0x3a92c) #2 0x9c47438c _ZN6KCrash15setCrashHandlerEPFviE (libKF5Crash.so.5 + 0x438c) #3 0x9c475064 _ZN6KCrash19defaultCrashHandlerEi (libKF5Crash.so.5 + 0x5064) #4 0x9cb987bc n/a (linux-vdso.so.1 + 0x7bc) #5 0x9cb987bc n/a (linux-vdso.so.1 + 0x7bc) #6 0x9ae3654c _ZN19KCoreConfigSkeleton4loadEv (libKF5ConfigCore.so.5 + 0x4654c) #7 0xf9e24510 n/a (n/a + 0x0) ELF object binary architecture: AARCH64 [New LWP 69050] [New LWP 69062] [New LWP 69063] [New LWP 69228] [New LWP 70084] [New LWP 69105] [New LWP 70090] [New LWP 70178] [New LWP 69070] [New LWP 70070] [New LWP 70088] [New LWP 70104] [New LWP 70180] [New LWP 70071] [New LWP 69773] [New LWP 69767] [New LWP 69741] [New LWP 69262] [New LWP 69152] [New LWP 69148] [New LWP 70179] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/aarch64-linux-gnu/libthread_db.so.1". Core was generated by `/usr/bin/plasmashell --no-respawn'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x99c362c8 in pthread_sigmask () from /lib/aarch64-linux-gnu/libc.so.6 [Current thread is 1 (Thread 0x9ca56c20 (LWP 69050))] [Current thread is 1 (Thread 0x9ca56c20 (LWP 69050))] Thread 21 (Thread 0x1a79ef00 (LWP 70179)): #0 0x99c2b6f4 in ?? () from /lib/aarch64-linux-gnu/libc.so.6 #1 0x99c2e230 in pthread_cond_wait () from /lib/aarch64-linux-gnu/libc.so.6 #2 0x9a054e34 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from /lib/aarch64-linux-gnu/libQt5Core.so.5 #3 0x9bf9c2f0 in ?? () from /lib/aarch64-linux-gnu/libQt5Quick.so.5 #4 0x9bf9e5d0 in ?? () from /lib/aarch64-linux-gnu/libQt5Quick.so.5 #5 0x9a04dfe0 in ?? () from /lib/aarch64-linux-gnu/libQt5Core.so.5 #6 0x99c2ee90 in ?? () from /lib/aarch64-linux-gnu/libc.so.6 #7 0x99c97b1c in ?? () from /lib/aarch64-linux-gnu/libc.so.6 Thread 20 (Thread 0x74b9ef00 (LWP 69148)): #0 0x99c8da58 in poll () from /lib/aarch64-linux-gnu/libc.so.6 #1 0x987f7958 in ?? () from /lib/aarch64-linux-gnu/libglib-2.0.so.0 #2 0x987f7a84 in g_main_context_iteration () from /lib/aarch64-linux-gnu/libglib-2.0.so.0 #3 0x9a299ac8 in QEventDispatcherGlib::processEvents(QFlags) () from /lib/aarch64-linux-gnu/libQt5Core.so.5 #4 0x9a238278 in QEventLoop::exec(QFlags) () from /lib/aarch64-linux-gnu/libQt5Core.so.5 #5 0x9a04cad4 in QThread::exec() () from /lib/aarch64-linux-gnu/libQt5Core.so.5 #6 0x9beeb6d8 in ?? () from /lib/aa
[valgrind] [Bug 469783] New: ARM32: Process terminating with default action of signal 11 (SIGSEGV): _dl_discover_osversion (in /lib/ld-linux-armhf.so.3)
https://bugs.kde.org/show_bug.cgi?id=469783 Bug ID: 469783 Summary: ARM32: Process terminating with default action of signal 11 (SIGSEGV): _dl_discover_osversion (in /lib/ld-linux-armhf.so.3) Classification: Developer tools Product: valgrind Version: 3.17.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: memcheck Assignee: jsew...@acm.org Reporter: v...@altlinux.org Target Milestone: --- On ARM32 (ALT Linux) any tool of valgrind (even `none`) reports SIGSEGV and crashes target binary (which is perfectly working otherwise): ``` # valgrind --tool=none ls ==2125518== Nulgrind, the minimal Valgrind tool ==2125518== Copyright (C) 2002-2017, and GNU GPL'd, by Nicholas Nethercote. ==2125518== Using Valgrind-3.17.0 and LibVEX; rerun with -h for copyright info ==2125518== Command: ls ==2125518== ==2125518== ==2125518== Process terminating with default action of signal 11 (SIGSEGV) ==2125518== Access not within mapped region at address 0xFEB7FFAC ==2125518==at 0x4012068: _dl_discover_osversion (in /lib/ld-linux-armhf.so.3) ==2125518== If you believe this happened as a result of a stack ==2125518== overflow in your program's main thread (unlikely but ==2125518== possible), you can try to increase the size of the ==2125518== main thread stack using the --main-stacksize= flag. ==2125518== The main thread stack size used in this run was 8388608. ==2125518== Segmentation fault ``` When run under another user reported function is different: ``` $ valgrind --tool=none ls ==2127882== Nulgrind, the minimal Valgrind tool ==2127882== Copyright (C) 2002-2017, and GNU GPL'd, by Nicholas Nethercote. ==2127882== Using Valgrind-3.17.0 and LibVEX; rerun with -h for copyright info ==2127882== Command: ls ==2127882== ==2127882== ==2127882== Process terminating with default action of signal 11 (SIGSEGV): dumping core ==2127882== Access not within mapped region at address 0xFE8D325C ==2127882==at 0x40134B8: handle_preload_list (in /lib/ld-linux-armhf.so.3) ==2127882== If you believe this happened as a result of a stack ==2127882== overflow in your program's main thread (unlikely but ==2127882== possible), you can try to increase the size of the ==2127882== main thread stack using the --main-stacksize= flag. ==2127882== The main thread stack size used in this run was 8388608. ==2127882== Segmentation fault ``` ``` /# ls bin boot dev etc home lib media mnt opt proc root run sbin selinux srv sys tmp usr var ``` -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 469783] ARM32: Process terminating with default action of signal 11 (SIGSEGV): _dl_discover_osversion (in /lib/ld-linux-armhf.so.3)
https://bugs.kde.org/show_bug.cgi?id=469783 Vitaly Chikunov changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=452575 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 452575] Valgrind crashes with segmentation fault and a lot invalid writes on Raspberry Pi 4B
https://bugs.kde.org/show_bug.cgi?id=452575 Vitaly Chikunov changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=469783 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 469783] ARM32: Process terminating with default action of signal 11 (SIGSEGV): _dl_discover_osversion (in /lib/ld-linux-armhf.so.3)
https://bugs.kde.org/show_bug.cgi?id=469783 --- Comment #1 from Vitaly Chikunov --- Stack traces with debuginfo installed: ``` ==2137208== Process terminating with default action of signal 11 (SIGSEGV) ==2137208== Access not within mapped region at address 0xFEAD6FAC ==2137208==at 0x4012068: _dl_discover_osversion (dl-sysdep.c:260) ==2137208==by 0x40144BB: dl_main (rtld.c:1768) ==2137208==by 0x4011E43: _dl_sysdep_start (dl-sysdep.c:142) ==2137208==by 0x4013271: _dl_start (rtld.c:507) ==2137208==by 0x401266F: ??? (in /lib/ld-linux-armhf.so.3) ``` ``` ==2137268== Process terminating with default action of signal 11 (SIGSEGV): dumping core ==2137268== Access not within mapped region at address 0xFE90E25C ==2137268==at 0x40134B8: handle_preload_list (rtld.c:894) ==2137268==by 0x401579D: dl_main (rtld.c:1891) ==2137268==by 0x4011E43: _dl_sysdep_start (dl-sysdep.c:142) ==2137268==by 0x4013271: _dl_start (rtld.c:507) ==2137268==by 0x401266F: ??? (in /lib/ld-linux-armhf.so.3) ``` -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 482358] New: Feature Request: Add --track-fds=error
https://bugs.kde.org/show_bug.cgi?id=482358 Bug ID: 482358 Summary: Feature Request: Add --track-fds=error Classification: Developer tools Product: valgrind Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: jsew...@acm.org Reporter: v...@altlinux.org Target Milestone: --- Now --track-fds=yes is only informational message (and it's even suppressed with -q), but sometimes (for using valgrind in CI testing) it's useful to consider it's an error if fd is leaked. Please add --track-fds=error which would output (not suppressible) error message and exit with --error-exitcode if fd leak is occurred. Thanks, -- You are receiving this mail because: You are watching all bug changes.
[Merkuro] [Bug 456233] "Invalid dates provided" for any/all inputs -> cannot create/edit events
https://bugs.kde.org/show_bug.cgi?id=456233 Vitaly Sulimov changed: What|Removed |Added CC||v.suli...@fastmail.fm --- Comment #3 from Vitaly Sulimov --- Same for me. Kde Neon, Merkuro Calendar version 24.05.0 As a workaround, I can modify the dates and times of the event I'm creating and switch focus between those fields. After that, the validation error goes away. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 469783] ARM32: Process terminating with default action of signal 11 (SIGSEGV): _dl_discover_osversion (in /lib/ld-linux-armhf.so.3)
https://bugs.kde.org/show_bug.cgi?id=469783 --- Comment #2 from Vitaly Chikunov --- This is still true for valgrind-3.22.0: ``` builder@armv7l:~/RPM/BUILD/valgrind-3.22.0$ ./vg-in-place /bin/true ==228878== Memcheck, a memory error detector ==228878== Copyright (C) 2002-2022, and GNU GPL'd, by Julian Seward et al. ==228878== Using Valgrind-3.22.0 and LibVEX; rerun with -h for copyright info ==228878== Command: /bin/true ==228878== ==228878== Invalid write of size 4 ==228878==at 0x10568: ??? (in /bin/true) ==228878==by 0xFEC454E3: ??? ==228878== Address 0xfec454b4 is on thread 1's stack ==228878== 24 bytes below stack pointer ==228878== ==228878== Invalid write of size 4 ==228878==at 0x18D72: ??? (in /bin/true) ==228878== Address 0xfec453d4 is on thread 1's stack ==228878== 224 bytes below stack pointer ==228878== ==228878== Invalid write of size 4 ==228878==at 0x1876A: ??? (in /bin/true) ==228878== Address 0xfec45434 is on thread 1's stack ==228878== 104 bytes below stack pointer ==228878== ==228878== Invalid write of size 4 ==228878==at 0x107F0: ??? (in /bin/true) ==228878== Address 0xfec4545c is on thread 1's stack ==228878== 64 bytes below stack pointer ==228878== ==228878== Invalid write of size 4 ==228878==at 0x17FDE: ??? (in /bin/true) ==228878== Address 0xfec45458 is on thread 1's stack ==228878== 24 bytes below stack pointer ==228878== ==228878== Invalid write of size 4 ==228878==at 0x18D0E: ??? (in /bin/true) ==228878== Address 0xfec45460 is on thread 1's stack ==228878== 16 bytes below stack pointer ==228878== ==228878== Invalid write of size 4 ==228878==at 0x1854E: ??? (in /bin/true) ==228878== Address 0xfec45458 is on thread 1's stack ==228878== 24 bytes below stack pointer ==228878== ==228878== Syscall param set_robust_list(head) points to uninitialised byte(s) ==228878==at 0x10A16: ??? (in /bin/true) ==228878==by 0x185B1: ??? (in /bin/true) ==228878== Address 0x474 is in the brk data segment 0x400-0x4000873 ==228878== ==228878== Invalid write of size 4 ==228878==at 0x19652: ??? (in /bin/true) ==228878== Address 0xfec45490 is on thread 1's stack ==228878== 32 bytes below stack pointer ==228878== ==228878== Invalid write of size 4 ==228878==at 0x21ADE: ??? (in /bin/true) ==228878== Address 0xfec45488 is on thread 1's stack ==228878== 16 bytes below stack pointer ==228878== ==228878== Invalid write of size 4 ==228878==at 0x19722: ??? (in /bin/true) ==228878== Address 0xfec454a0 is on thread 1's stack ==228878== 16 bytes below stack pointer ==228878== ==228878== Invalid write of size 4 ==228878==at 0x18EA0: ??? (in /bin/true) ==228878== Address 0xfec4543c is on thread 1's stack ==228878== 80 bytes below stack pointer ==228878== ==228878== Invalid write of size 4 ==228878==at 0x2991A: ??? (in /bin/true) ==228878== Address 0xfec44450 is not stack'd, malloc'd or (recently) free'd ==228878== ==228878== ==228878== Process terminating with default action of signal 11 (SIGSEGV): dumping core ==228878== Access not within mapped region at address 0xFEC44450 ==228878==at 0x2991A: ??? (in /bin/true) ==228878== If you believe this happened as a result of a stack ==228878== overflow in your program's main thread (unlikely but ==228878== possible), you can try to increase the size of the ==228878== main thread stack using the --main-stacksize= flag. ==228878== The main thread stack size used in this run was 8388608. ==228878== ==228878== HEAP SUMMARY: ==228878== in use at exit: 0 bytes in 0 blocks ==228878== total heap usage: 0 allocs, 0 frees, 0 bytes allocated ==228878== ==228878== All heap blocks were freed -- no leaks are possible ==228878== ==228878== Use --track-origins=yes to see where uninitialised values come from ==228878== For lists of detected and suppressed errors, rerun with: -s ==228878== ERROR SUMMARY: 13 errors from 13 contexts (suppressed: 0 from 0) Segmentation fault ``` -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 469783] ARM32: Process terminating with default action of signal 11 (SIGSEGV): _dl_discover_osversion (in /lib/ld-linux-armhf.so.3)
https://bugs.kde.org/show_bug.cgi?id=469783
--- Comment #4 from Vitaly Chikunov ---
It's still crashes with tool none:
```
builder@armv7l:~/RPM/BUILD/valgrind-3.22.0$ ./vg-in-place --tool=none /bin/true
==1347567== Nulgrind, the minimal Valgrind tool
==1347567== Copyright (C) 2002-2017, and GNU GPL'd, by Nicholas Nethercote.
==1347567== Using Valgrind-3.22.0 and LibVEX; rerun with -h for copyright info
==1347567== Command: /bin/true
==1347567==
==1347567==
==1347567== Process terminating with default action of signal 11 (SIGSEGV):
dumping core
==1347567== Access not within mapped region at address 0xFEF1C4A0
==1347567==at 0x2991A: ??? (in /bin/true)
==1347567== If you believe this happened as a result of a stack
==1347567== overflow in your program's main thread (unlikely but
==1347567== possible), you can try to increase the size of the
==1347567== main thread stack using the --main-stacksize= flag.
==1347567== The main thread stack size used in this run was 8388608.
==1347567==
Segmentation fault
```
With suppressor from Debian:
```
builder@armv7l:~/RPM/BUILD/valgrind-3.22.0$ ./vg-in-place
--suppressions=armhf-stackclash.supp /bin/true
==1355694== Memcheck, a memory error detector
==1355694== Copyright (C) 2002-2022, and GNU GPL'd, by Julian Seward et al.
==1355694== Using Valgrind-3.22.0 and LibVEX; rerun with -h for copyright info
==1355694== Command: /bin/true
==1355694==
==1355694== Syscall param set_robust_list(head) points to uninitialised byte(s)
==1355694==at 0x10A16: ??? (in /bin/true)
==1355694==by 0x185B1: ??? (in /bin/true)
==1355694== Address 0x474 is in the brk data segment 0x400-0x4000873
==1355694==
==1355694==
==1355694== Process terminating with default action of signal 11 (SIGSEGV):
dumping core
==1355694== Access not within mapped region at address 0xFEF00450
==1355694==at 0x2991A: ??? (in /bin/true)
==1355694== If you believe this happened as a result of a stack
==1355694== overflow in your program's main thread (unlikely but
==1355694== possible), you can try to increase the size of the
==1355694== main thread stack using the --main-stacksize= flag.
==1355694== The main thread stack size used in this run was 8388608.
==1355694==
==1355694== HEAP SUMMARY:
==1355694== in use at exit: 0 bytes in 0 blocks
==1355694== total heap usage: 0 allocs, 0 frees, 0 bytes allocated
==1355694==
==1355694== All heap blocks were freed -- no leaks are possible
==1355694==
==1355694== Use --track-origins=yes to see where uninitialised values come from
==1355694== For lists of detected and suppressed errors, rerun with: -s
==1355694== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 12 from 12)
Segmentation fault
builder@armv7l:~/RPM/BUILD/valgrind-3.22.0$ cat armhf-stackclash.supp
# On armhf, stack-clash-protector is implemented by writing out of stack
# bounds. https://bugzilla.redhat.com/show_bug.cgi?id=1522678
{
stack-clash-protection-armhf
Memcheck:Addr4
obj:*
}
```
--
You are receiving this mail because:
You are watching all bug changes.
[krusader] [Bug 487558] New: Provide appImage
https://bugs.kde.org/show_bug.cgi?id=487558 Bug ID: 487558 Summary: Provide appImage Classification: Applications Product: krusader Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: krusader-bugs-n...@kde.org Reporter: zdanevich.vit...@ya.ru CC: krusader-bugs-n...@kde.org Target Milestone: --- On my Gentoo Linux I see that it needs a BIG list of dependencies, I am afraid to install it. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 445678] New: GTK toolbar icons looks like push buttons
https://bugs.kde.org/show_bug.cgi?id=445678 Bug ID: 445678 Summary: GTK toolbar icons looks like push buttons Product: Breeze Version: 5.23.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: gtk theme Assignee: uhh...@gmail.com Reporter: vit...@easycoding.org CC: plasma-b...@kde.org Target Milestone: --- SUMMARY GTK toolbar icons looks like push buttons. They are no longer flat after upgrading from 5.22 to 5.23. STEPS TO REPRODUCE 1. Upgrade to Fedora 35 with KDE Plasma 5.23.x. 2. Run any GTK applications with toolbars. Eg. FileZilla or Virt Manager. OBSERVED RESULT FileZilla: https://i.imgur.com/xuOHOxn.png Virt Manager: https://i.imgur.com/kFIVRd5.png EXPECTED RESULT How they should like: FileZilla: https://i.imgur.com/I9qSiY1.png Virt Manager: https://i.imgur.com/LSDrhYq.png SOFTWARE/OS VERSIONS Operating System: Fedora Linux 35 KDE Plasma Version: 5.23.2 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.2 Kernel Version: 5.14.17-301.fc35.x86_64 (64-bit) Graphics Platform: X11 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 443626] GTK toolbar buttons have outline
https://bugs.kde.org/show_bug.cgi?id=443626 --- Comment #7 from Vitaly Zaitsev --- OBSERVED RESULT FileZilla: https://i.imgur.com/xuOHOxn.png Virt Manager: https://i.imgur.com/kFIVRd5.png EXPECTED RESULT How they should like: FileZilla: https://i.imgur.com/I9qSiY1.png Virt Manager: https://i.imgur.com/LSDrhYq.png -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 445383] New: Build failure on Fedora 35
https://bugs.kde.org/show_bug.cgi?id=445383 Bug ID: 445383 Summary: Build failure on Fedora 35 Product: krita Version: 4.4.8 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: vit...@easycoding.org Target Milestone: --- SUMMARY Krita 4.4.8 build failure on Fedora 35. STEPS TO REPRODUCE 1. Run packaged build on Fedora 35 or Rawhide. 2. 3. OBSERVED RESULT FAILED: plugins/extensions/pykrita/sip/krita/sipkritapart0.cpp /builddir/build/BUILD/krita-4.4.8/redhat-linux-build/plugins/extensions/pykrita/sip/krita/sipkritapart0.cpp cd /builddir/build/BUILD/krita-4.4.8/redhat-linux-build/plugins/extensions/pykrita/sip && /usr/bin/cmake -E echo && /usr/bin/cmake -E touch /builddir/build/BUILD/krita-4.4.8/redhat-linux-build/plugins/extensions/pykrita/sip/./krita/sipkritapart0.cpp && /usr/bin/sip -t ALL -t WS_X11 -t Qt_5_15_0 -g -o -x PyKDE_QVector -n PyQt5.sip -j 1 -c /builddir/build/BUILD/krita-4.4.8/redhat-linux-build/plugins/extensions/pykrita/sip/./krita -I /usr/share/sip -I /usr/lib64/python3.10/site-packages/PyQt5/bindings -I /builddir/build/BUILD/krita-4.4.8/plugins/extensions/pykrita/sip/krita /builddir/build/BUILD/krita-4.4.8/plugins/extensions/pykrita/sip/krita/kritamod.sip sip: /usr/lib64/python3.10/site-packages/PyQt5/bindings/QtCore/QtCoremod.sip:23: syntax error EXPECTED RESULT Successful build. SOFTWARE/OS VERSIONS Operating System: Fedora Linux 35 KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.2 Kernel Version: 5.14.16-301.fc35.x86_64 (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-8550U CPU @ 1.80GHz Memory: 15.4 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 445383] Build failure on Fedora 35
https://bugs.kde.org/show_bug.cgi?id=445383 --- Comment #2 from Vitaly Zaitsev --- Krita need to be ported to the new sip version. Debian downstream bug report: https://bugs.kde.org/show_bug.cgi?id=445383 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 445383] Build failure on Fedora 35
https://bugs.kde.org/show_bug.cgi?id=445383 Vitaly Zaitsev changed: What|Removed |Added Resolution|--- |DOWNSTREAM Status|REPORTED|RESOLVED --- Comment #3 from Vitaly Zaitsev --- Downstream fix: https://src.fedoraproject.org/rpms/sip/pull-request/15 Can be closed. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 438874] Disk & Devices applet doesn't show USB removable devices after connecting the device for 2nd time
https://bugs.kde.org/show_bug.cgi?id=438874 Vitaly Zaitsev changed: What|Removed |Added CC||vit...@easycoding.org --- Comment #20 from Vitaly Zaitsev --- Can confirm this issue on Fedora 34. Very annoying. Operating System: Fedora 34 KDE Plasma Version: 5.22.4 KDE Frameworks Version: 5.83.0 Qt Version: 5.15.2 Kernel Version: 5.13.6-200.fc34.x86_64 (64-bit) Graphics Platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-solid] [Bug 438478] Device notifier shows SD card being inserted only once
https://bugs.kde.org/show_bug.cgi?id=438478 Vitaly Zaitsev changed: What|Removed |Added CC||vit...@easycoding.org -- You are receiving this mail because: You are watching all bug changes.
[ghostwriter] [Bug 461321] New: CVE-2022-39209 ghostwriter: cmark-gfm: Unbounded resource exhaustion may lead to denial of service.
https://bugs.kde.org/show_bug.cgi?id=461321 Bug ID: 461321 Summary: CVE-2022-39209 ghostwriter: cmark-gfm: Unbounded resource exhaustion may lead to denial of service. Classification: Applications Product: ghostwriter Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: megan.con...@kdemail.net Reporter: vit...@easycoding.org Target Milestone: --- SUMMARY In cmark-gfm versions prior to 0.29.0.gfm.6 a polynomial time complexity issue in cmark-gfm's autolink extension may lead to unbounded resource exhaustion and subsequent denial of service. More information: https://github.com/github/cmark-gfm/security/advisories/GHSA-cgh3-p57x-9q7q Upstream fix: https://github.com/github/cmark-gfm/commit/9d57d8a23142b316282bdfc954cb0ecda40a8655 -- You are receiving this mail because: You are watching all bug changes.
[ghostwriter] [Bug 461321] CVE-2022-39209 ghostwriter: cmark-gfm: Unbounded resource exhaustion may lead to denial of service.
https://bugs.kde.org/show_bug.cgi?id=461321 --- Comment #1 from Vitaly Zaitsev --- Fedora downstream bug report: https://bugzilla.redhat.com/show_bug.cgi?id=2128046 Fixed version: 0.29.0.gfm.6 or higher. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 464281] New: 1px gaps in Konsole with fractional scaling
https://bugs.kde.org/show_bug.cgi?id=464281 Bug ID: 464281 Summary: 1px gaps in Konsole with fractional scaling Classification: Applications Product: konsole Version: 22.12.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: vit...@easycoding.org Target Milestone: --- SUMMARY Konsole since version 22.12.1 has 1px gaps when fractional scaling 150% is used. Version 22.08.3 works fine. STEPS TO REPRODUCE 1. Switch to X11 session. 2. Enable 150% scaling in settings. 3. Open Konsole and start Midnight Commander there. OBSERVED RESULT https://i.imgur.com/5fylnPI.png EXPECTED RESULT It should be rendered without gaps. SOFTWARE/OS VERSIONS Operating System: Fedora Linux 37 KDE Plasma Version: 5.26.5 KDE Frameworks Version: 5.101.0 Qt Version: 5.15.8 Kernel Version: 6.1.5-200.fc37.x86_64 (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-8550U CPU @ 1.80GHz Memory: 15.4 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 464282] New: Broken panel icons with fractional scaling
https://bugs.kde.org/show_bug.cgi?id=464282 Bug ID: 464282 Summary: Broken panel icons with fractional scaling Classification: Applications Product: krusader Version: 2.8.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: krusader-bugs-n...@kde.org Reporter: vit...@easycoding.org CC: krusader-bugs-n...@kde.org Target Milestone: --- SUMMARY All icons of folders or files are broken if fractional scaling 150% is used. Version 2.7.2 works fine. STEPS TO REPRODUCE 1. Switch to X11 session. 2. Set 150% scaling in display settings. 3. Start Krusader. OBSERVED RESULT https://i.imgur.com/rrwr4mS.png EXPECTED RESULT All icons should be displayed correctly. SOFTWARE/OS VERSIONS Operating System: Fedora Linux 37 KDE Plasma Version: 5.26.5 KDE Frameworks Version: 5.101.0 Qt Version: 5.15.8 Kernel Version: 6.1.5-200.fc37.x86_64 (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-8550U CPU @ 1.80GHz Memory: 15.4 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 464282] Broken panel icons with fractional scaling
https://bugs.kde.org/show_bug.cgi?id=464282 Vitaly Zaitsev changed: What|Removed |Added Platform|Other |Fedora RPMs -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 464281] 1px gaps in Konsole with fractional scaling
https://bugs.kde.org/show_bug.cgi?id=464281 Vitaly Zaitsev changed: What|Removed |Added Platform|Other |Fedora RPMs -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 409392] NetworkManager widget freezes on VPN connection issues, freezing/blocking Plasma
https://bugs.kde.org/show_bug.cgi?id=409392 Vitaly Zaitsev changed: What|Removed |Added CC||vit...@easycoding.org --- Comment #17 from Vitaly Zaitsev --- Can be easily reproduced with a router: remove WAN cable from the router and wait for 5 seconds. KDE Plasma will freeze for 30 seconds. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 420872] Incorrect scaling of mouse cursor on 150%
https://bugs.kde.org/show_bug.cgi?id=420872 Vitaly Zaitsev changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED Status|NEEDSINFO |RESOLVED --- Comment #13 from Vitaly Zaitsev --- Already fixed in 5.20+. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 438009] New: Open File Manager context menu entry no longer working
https://bugs.kde.org/show_bug.cgi?id=438009 Bug ID: 438009 Summary: Open File Manager context menu entry no longer working Product: konsole Version: 21.04.1 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: vit...@easycoding.org Target Milestone: --- SUMMARY Open File Manager context menu entry no longer working. STEPS TO REPRODUCE 1. Open Konsole. 2. Press right mouse button and select the "Open File Manager" context menu entry. OBSERVED RESULT Unknown mime-type association dialog for the "octet/stream" will be shown. EXPECTED RESULT Dolphin should be opened with current directory. SOFTWARE/OS VERSIONS Operating System: Fedora 34 KDE Frameworks Version: 5.82.0 Qt Version: 5.15.2 Kernel Version: 5.12.8-300.fc34.x86_64 OS Type: 64-bit Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-8550U CPU @ 1.80GHz Memory: 15.4 GiB of RAM ADDITIONAL INFORMATION Konsole version 21.04.1. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 438009] Open File Manager context menu entry no longer working
https://bugs.kde.org/show_bug.cgi?id=438009 --- Comment #2 from Vitaly Zaitsev --- > Works for me. What is the path that you're asking Dolphin to open? You can use home directory: cd ~ RMB -> Open File Manager -> Unknown mime-type association dialog for the "octet/stream" will be shown. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 438009] Open File Manager context menu entry no longer working
https://bugs.kde.org/show_bug.cgi?id=438009 --- Comment #4 from Vitaly Zaitsev --- > That works fine for me. What does `file --mime-type ~` say for you? $ file --mime-type ~ /home/vitaly: inode/directory -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 438009] Open File Manager context menu entry no longer working
https://bugs.kde.org/show_bug.cgi?id=438009 --- Comment #6 from Vitaly Zaitsev --- Video: https://xvitaly.fedorapeople.org/bug-reports/2021-06-04_15-06-48.mp4 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 438009] Open File Manager context menu entry no longer working
https://bugs.kde.org/show_bug.cgi?id=438009 --- Comment #7 from Vitaly Zaitsev --- I have the same issue also with some text files. Visit /usr/lib/rpm/macros.d/ on Fedora and click on any *.macros files, for example macros.qt5. Unknown mime-type association dialog for the "octet/stream" will be shown. $ file --mime-type macros.qt5 macros.qt5: text/plain -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 438009] Open File Manager context menu entry no longer working
https://bugs.kde.org/show_bug.cgi?id=438009 --- Comment #8 from Vitaly Zaitsev --- > I'll dig deeper, Nate's probably right that's it's a mimetype issue. Definitely not. "xdg-open ~" works absolutely fine. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 438009] Open File Manager context menu entry no longer working
https://bugs.kde.org/show_bug.cgi?id=438009 --- Comment #13 from Vitaly Zaitsev --- > export QT_LOGGING_RULES="*konsole*=true" $ export QT_LOGGING_RULES="*konsole*=true" $ konsole org.kde.konsole: The font to use in the terminal can not be matched exactly on your system. org.kde.konsole: Selected: "Monospace,11.5,-1,2,50,0,0,0,0,0" org.kde.konsole: System : "DejaVu Sans Mono,11.25,-1,2,50,0,0,0,0,0" -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 438009] Open File Manager context menu entry no longer working
https://bugs.kde.org/show_bug.cgi?id=438009 --- Comment #15 from Vitaly Zaitsev --- > And you tried to open a text file from Konsole? Yes. Tried both ~ and macros.qt5: $ kde-open5 ~ $ kde-open5 /usr/lib/rpm/macros.d/macros.qt5 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 438009] Open File Manager context menu entry no longer working
https://bugs.kde.org/show_bug.cgi?id=438009 --- Comment #19 from Vitaly Zaitsev --- I can confirm that kf5-kio-5.82.0-3.fc34 fixes issue. Many thanks. -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 130266] [testcase] Incorrect textarea height calculation, incorrect clientHeight/offsetHeight/scrollHeight values
https://bugs.kde.org/show_bug.cgi?id=130266 --- Comment #11 from Vitaly Harisov --- I have no KDE/conqueror now and can't check this issue. > 21 марта 2021 г., в 03:25, Justin Zobel написал(а): > > https://bugs.kde.org/show_bug.cgi?id=130266 > > --- Comment #10 from Justin Zobel --- > Thank you for the bug report. > > As this report hasn't seen any changes in 10 years or more, we ask if you can > please confirm that the issue still persists. > > If this bug is no longer persisting or relevant please change the status to > resolved. > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 461760] New: Non-maximized windows hang after maximization
https://bugs.kde.org/show_bug.cgi?id=461760 Bug ID: 461760 Summary: Non-maximized windows hang after maximization Classification: Plasma Product: kwin Version: 5.26.2 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: vit...@easycoding.org Target Milestone: --- SUMMARY All windows started as non-maximized, hang after maximization. Can be reproduced with any maximized window: Firefox, Konsole, Dolphin, etc. STEPS TO REPRODUCE 1. Run any app in non-maximized window. 2. Press Maximize button. OBSERVED RESULT The window hang until restored to its initial state. EXPECTED RESULT It should not hang. SOFTWARE/OS VERSIONS Operating System: Fedora Linux 37 KDE Plasma Version: 5.26.2 KDE Frameworks Version: 5.99.0 Qt Version: 5.15.6 Kernel Version: 6.0.7-301.fc37.x86_64 (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-8550U CPU @ 1.80GHz Memory: 15.4 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 ADDITIONAL INFORMATION Video proof of this bug: https://xvitaly.fedorapeople.org/bug-reports/plasma-window-hang.mkv -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 407829] New: kdiff3 1.8.1 crash during scroll when comparing directories
https://bugs.kde.org/show_bug.cgi?id=407829 Bug ID: 407829 Summary: kdiff3 1.8.1 crash during scroll when comparing directories Product: kdiff3 Version: 1.8.x Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: application Assignee: reeves...@gmail.com Reporter: yermolc...@gmail.com Target Milestone: --- SUMMARY kdiff3 1.8.1 release crash when I scroll to beginning or end of file list comparing any two directories. STEPS TO REPRODUCE I) 1. kdiff3 dir1 dir2 2. Scroll using mouse wheel or keyboard over list of files or II) 1. kdiff3 dir1 dir2 2. Select first file in the list 3. Press up arrow key OBSERVED RESULT Segmentation fault. EXPECTED RESULT Just stop scrolling at the end of list. SOFTWARE/OS VERSIONS Linux/KDE Plasma: OpenSUSE Leap 15.1 KDE Plasma Version: 5.14.4-lp151.1.1 KDE Frameworks Version: 5.55.0-lp151.1.1 Qt Version: 5.9.7-lp151.3.1 ADDITIONAL INFORMATION I) Thread 1 (Thread 0x7f8025b09440 (LWP 5719)): [KCrash Handler] #6 0x7f802342fba0 in QAbstractSlider::value() const () from /usr/lib64/libQt5Widgets.so.5 #7 0x56133b8be87b in ?? () #8 0x7f8023379be8 in QWidget::event(QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #9 0x7f802333b3dc in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #10 0x7f80233446c7 in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #11 0x7f80225918d8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib64/libQt5Core.so.5 II) Thread 1 (Thread 0x7f314c839440 (LWP 19115)): [KCrash Handler] #6 0x7f314a15fba0 in QAbstractSlider::value() const () from /usr/lib64/libQt5Widgets.so.5 #7 0x56475209185b in KDiff3App::scrollDiffTextWindow(int, int) () #8 0x7f314a0aa417 in QWidget::event(QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #9 0x7f314a06b3dc in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #10 0x7f314a0741e2 in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #11 0x7f31492c18d8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib64/libQt5Core.so.5 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 405263] New: Broken pseudo-graphics in Konsole on HiDPI displays after KF5 update to 5.55
https://bugs.kde.org/show_bug.cgi?id=405263 Bug ID: 405263 Summary: Broken pseudo-graphics in Konsole on HiDPI displays after KF5 update to 5.55 Product: konsole Version: 18.12.2 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: font Assignee: konsole-de...@kde.org Reporter: vit...@easycoding.org Target Milestone: --- Broken pseudo-graphics in Konsole on HiDPI displays after KF5 update to version 5.55. STEPS TO REPRODUCE 1. Run Konsole with scale factor 1.5. 2. Start Midnight Commander in it. 3. OBSERVED RESULT Broken pseudo-graphics: https://i.imgur.com/ZQ7923z.png EXPECTED RESULT Working pseudo-graphics. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 29 KDE Plasma Version: 5.14.5 KDE Frameworks Version: 5.55.0 Qt Version: 5.11.3 Kernel version: 4.20.13-200.fc29.x86_64 ADDITIONAL INFORMATION Downgrading KF5 to version 5.54 resolve this issue. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 420872] New: Incorrect scaling of mouse cursor on 150%
https://bugs.kde.org/show_bug.cgi?id=420872 Bug ID: 420872 Summary: Incorrect scaling of mouse cursor on 150% Product: kwin Version: 5.18.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: decorations Assignee: kwin-bugs-n...@kde.org Reporter: vit...@easycoding.org Target Milestone: --- SUMMARY Incorrect scaling of mouse pointer on 150% on mouse over window title, on desktop widget and some window controls, like checkboxes. Screenshots: https://imgur.com/a/OziChRx Regression in 5.18.x. On 5.17.5 everything works fine. STEPS TO REPRODUCE 1. Set screen scaling to 150%. 2. Navigate mouse pointer to window title or desktop widget. 3. OBSERVED RESULT Very small mouse pointer. EXPECTED RESULT Scaled mouse pointer. SOFTWARE/OS VERSIONS Operating System: Fedora 32 KDE Plasma Version: 5.18.3 KDE Frameworks Version: 5.68.0 Qt Version: 5.13.2 Kernel Version: 5.6.7-300.fc32.x86_64 OS Type: 64-bit Processors: 8 × Intel® Core™ i7-8550U CPU @ 1.80GHz Memory: 15.4 GiB of RAM ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 350521] [RFE] [OpenVPN] kdeplasma-applets-plasma-nm does not support OTP Tokens for OpenVPN connections
https://bugs.kde.org/show_bug.cgi?id=350521 Vitaly Dub changed: What|Removed |Added CC||forceus...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 386741] New: Provide binary build and instructions about how to build on macOS
https://bugs.kde.org/show_bug.cgi?id=386741 Bug ID: 386741 Summary: Provide binary build and instructions about how to build on macOS Product: kdenlive Version: unspecified Platform: Compiled Sources OS: OS X Status: UNCONFIRMED Severity: normal Priority: NOR Component: Installation Assignee: vpi...@kde.org Reporter: zdanevich.vit...@ya.ru Target Milestone: --- Created attachment 108783 --> https://bugs.kde.org/attachment.cgi?id=108783&action=edit Screenshot of https://kdenlive.org/download/ Better - formula for Brew, when users can install with `brew install kdenlive` -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 499614] Fail to open merge from command line
https://bugs.kde.org/show_bug.cgi?id=499614 VITALY Buka changed: What|Removed |Added CC||vitalyb...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 499614] New: Fail to open merge from command line
https://bugs.kde.org/show_bug.cgi?id=499614 Bug ID: 499614 Summary: Fail to open merge from command line Classification: Applications Product: kdiff3 Version: 1.11.5 Platform: Debian unstable OS: Other Status: REPORTED Severity: major Priority: NOR Component: application Assignee: reeves...@gmail.com Reporter: vitalyb...@gmail.com Target Milestone: --- f6aca74944482c1bf5f2df653945a2fb5d2bf660 has strange side effect. I bisected locally and revert ontop 1.11.5 fix my issue. Any 1.11.* (on Debian) fail to do from command line: I didn't try 1.12 because of dependency issues. `kdiff3 a b c -o d` Doing the same from UI works fine, but command line invocation always fail with "File open error - KDIFF3" dialog - b Opening b failed. Unknown error. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 451817] Render fails instantly 21.12.3 on Linux Mint kdenlive-21.12.3-x86_64.AppImage
https://bugs.kde.org/show_bug.cgi?id=451817 Vitaly "_Vi" Shukela changed: What|Removed |Added CC||vi0...@gmail.com --- Comment #3 from Vitaly "_Vi" Shukela --- Still reproducible for kdenlive-22.04.0-1-x86_x64.AppImage: Rendering of /home/vi/Videos/untitled.mp4 crashed /tmp/.mount_kdenlihBl3HV/usr/bin/melt: symbol lookup error: /tmp/.mount_kdenlihBl3HV/usr/lib/ladspa/alias_1407.so: undefined symbol: libintl_bindtextdomain -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 451817] Render fails instantly 21.12.3 on Linux Mint kdenlive-21.12.3-x86_64.AppImage
https://bugs.kde.org/show_bug.cgi?id=451817 --- Comment #4 from Vitaly "_Vi" Shukela --- Workaroud: save render script (mlt) from GUI, install "melt" package in distro, then render the video from CLI using /usr/bin/melt outside AppImage. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 451817] Render fails instantly 21.12.3 on Linux Mint kdenlive-21.12.3-x86_64.AppImage
https://bugs.kde.org/show_bug.cgi?id=451817 --- Comment #8 from Vitaly "_Vi" Shukela --- @emohr Tried kdenlive-master-208-linux-64-gcc.AppImage: rendering now works out of the box: `/tmp/.mount_kdenliNUbyI1/usr/bin/melt` is working. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 416139] Crash on startup running Kdenlive without pulseaudio
https://bugs.kde.org/show_bug.cgi?id=416139 Vitaly "_Vi" Shukela changed: What|Removed |Added CC||vi0...@gmail.com --- Comment #5 from Vitaly "_Vi" Shukela --- kdenlive-master-208-linux-64-gcc.AppImage or /opt/kdenlive-22.04.0-1-x86_x64.AppImage crash when I try to start after "chmod -x /usr/bin/pulseaudio". Sometimes it shows "Could not initialize preview" before crashing, sometimes main window only briefly blinks. I see in dmesg: [1367303.177761] SDLHotplugALSA[3978]: segfault at 0 ip 7fa010cdc5fe sp 7f9fd49f6c10 error 4 in libSDL2-2.0.so.0[7fa010c1f000+12a000] [1367303.177803] Code: 68 67 fa ff 48 85 db 75 e3 48 83 c4 78 31 c0 5b 5d 41 5c 41 5d 41 5e 41 5f c3 66 90 48 c7 44 24 68 00 00 00 00 4c 8b 44 24 60 <49> 8b 38 48 85 ff 0f 84 df 04 00 00 48 c7 44 24 18 00 00 00 00 45 [1368115.019694] AppRun.wrapped[6297]: segfault at 0 ip 7fdb859c31e0 sp 7ffe4564ffd8 error 4 in libmlt++-7.so.7[7fdb859a6000+29000] [1368115.019719] Code: 54 24 08 48 89 34 24 ff d0 48 8b 54 24 08 48 8b 34 24 48 83 c4 18 48 89 c7 e9 cc 89 ff ff 66 66 2e 0f 1f 84 00 00 00 00 00 90 <48> 8b 07 48 8d 0d d6 f8 ff ff 48 8b 40 10 48 39 c8 75 0d 48 8b 7f With /usr/bin/pulseaudio enabled it starts successfully from one user account but crashes from another one (before even displaying a message about preview pane being unavailable). Typically the crash happens after second instance of the following console messages: ALSA lib /home/appimage/Craft/BC/linux-64-gcc/build/libs/libasound2/work/alsa-lib-1.2.5.1/src/conf.c:4499:(snd_config_update_r) Cannot access file /home/appimage/Craft/BC/linux-64-gcc/share/alsa/alsa.conf (it crashes instead of outputting "no alsa devices available") Workaround: explicitly and manually start PulseAudio for that user: `pulseaudio --daemonize=false --exit-idle-time=-1 --disallow-exit=true`. Kdenlive then starts properly. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 454236] New: Crash when using a clip that was changed on the filesystem.
https://bugs.kde.org/show_bug.cgi?id=454236 Bug ID: 454236 Summary: Crash when using a clip that was changed on the filesystem. Product: kdenlive Version: git-master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Video Display & Export Assignee: j...@kdenlive.org Reporter: vi0...@gmail.com Target Milestone: --- Encounted a crash: ... ::: REGISTERING CLIP TO BIN: :: REGISTRATION 35 ptr count 8 qml: loaded clip: 3143 , ID: 35 , index: 0 , TYPE: Video qml: loaded clip with Astream: -1 terminate called after throwing an instance of 'std::out_of_range' what(): _Map_base::at [1]+ Aborted /opt/kdenlive-master-208-linux-64-gcc.AppImage when re-adding a video clip from bin to timeline where the clip was repeatedly changed on filesystem. The video got replaced by one-second video, then back to original length. I saw the clip's segment shrink to 1 second in the timeline, but after deleting and attempting to re-add it Kdenlive crashed. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 454236] Crash when using a clip that was changed on the filesystem.
https://bugs.kde.org/show_bug.cgi?id=454236 --- Comment #1 from Vitaly "_Vi" Shukela --- After Kdenlive restart it offered to recover session. Repeating the actions in the recovered session worked properly. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 339605] vgpreload_helgrind-arm-linux.so is not linked to libc.so and can't find sched_yield, pthread_self and so on
https://bugs.kde.org/show_bug.cgi?id=339605 --- Comment #6 from Vitaly "_Vi" Shukela --- > Is your application linked with libpthread and does it run correctly on its > own? I don't remember which application it was, but probably it worked correctly (apart from bugs to be debugged using valgrind), and according to my previous comment it also worked in Valgrind (but other tool). It was 8 years ago, so many things both in Android, Valgrind and toolchains for building apps could have changed. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 339605] vgpreload_helgrind-arm-linux.so is not linked to libc.so and can't find sched_yield, pthread_self and so on
https://bugs.kde.org/show_bug.cgi?id=339605 --- Comment #8 from Vitaly "_Vi" Shukela --- If there will be more similar problems, I'll probably open another issue. -- You are receiving this mail because: You are watching all bug changes.
