[Plasma Vault] [Bug 453468] Opening plasma vault fails with error code 127
https://bugs.kde.org/show_bug.cgi?id=453468 --- Comment #2 from Peter Stolz --- Hi Ömer, If I use command: cryfs --version I get this: cryfs: symbol lookup error: cryfs: undefined symbol: _ZN6spdlog5sinks15basic_file_sinkISt5mutexEC1ERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEb Version of my cryfs: 0.11.2-1.2-x86_64 from vendor openSUSE Peter -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 453468] New: Opening plasma vault fails with error code 127
https://bugs.kde.org/show_bug.cgi?id=453468 Bug ID: 453468 Summary: Opening plasma vault fails with error code 127 Product: Plasma Vault Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: general Assignee: ivan.cu...@kde.org Reporter: p.stol...@gmail.com Target Milestone: --- Created attachment 148607 --> https://bugs.kde.org/attachment.cgi?id=148607=edit Screenshot with error message (try to open vault) STEPS TO REPRODUCE 1. Use openSUSE Tumbleweed 20220504 / bug introduced with this snapshot 2. Opening plasma vault OBSERVED RESULT Vault is not opening and fails with error code 127 EXPECTED RESULT Opening vault works fine SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20220504 KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.93.0 Qt Version: 5.15.2 Kernel Version: 5.17.4-1-default (64-bit) Graphics Platform: X11 Processors: 6 × Intel® Core™ i5-9400 CPU @ 2.90GHz Memory: 31.2 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 630 Vault Version: 5.24.4-1.1-x86_64 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 417507] Kate ignores new mode/filetypes
https://bugs.kde.org/show_bug.cgi?id=417507 Stolz changed: What|Removed |Added CC||st...@gsmlandia.com --- Comment #4 from Stolz --- Kate version 20.12.3 still affected -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 430311] Intensive color selection broken as of 270d6ea3
https://bugs.kde.org/show_bug.cgi?id=430311 Stolz changed: What|Removed |Added CC||j...@gsmlandia.com -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 430267] No option to display bold font as intense color
https://bugs.kde.org/show_bug.cgi?id=430267 Stolz changed: What|Removed |Added CC||j...@gsmlandia.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 421488] Plasma crashes after login
https://bugs.kde.org/show_bug.cgi?id=421488 Peter Stolz changed: What|Removed |Added CC||p.stol...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 421466] Plasma crashs after login
https://bugs.kde.org/show_bug.cgi?id=421466 --- Comment #1 from Peter Stolz --- If I login and switch between the kde start options "plasma", "plasma (full wayland)" and "plasma (wayland)" kde sometimes starts. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 421466] New: Plasma crashs after login
https://bugs.kde.org/show_bug.cgi?id=421466 Bug ID: 421466 Summary: Plasma crashs after login Product: plasmashell Version: 5.18.5 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: p.stol...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.18.5) Qt Version: 5.14.1 Frameworks Version: 5.70.0 Operating System: Linux 5.6.11-1-default x86_64 Windowing system: X11 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: I installed new opensuse tumbleweed snapshot with kde update to 5.70.0 After the first reboot plasma crashed. I see short the desktop with taskbars then I see a black screen. After each boot now plasma crashes and my system is dead. . The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7ff87df00800 (LWP 2339))] Thread 11 (Thread 0x7ff84e750700 (LWP 2577)): #0 0x7ff87e9df09d in () at /usr/lib64/libglib-2.0.so.0 #1 0x7ff87e9e0ab5 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7ff87e9e234f in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #3 0x7ff87e9e2982 in () at /usr/lib64/libglib-2.0.so.0 #4 0x7ff87e9e2aff in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #5 0x7ff88048ebeb in QEventDispatcherGlib::processEvents(QFlags) (this=0x7ff84b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #6 0x7ff880436b7b in QEventLoop::exec(QFlags) (this=this@entry=0x7ff84e74fd60, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:136 #7 0x7ff8802615ce in QThread::exec() (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:118 #8 0x7ff84ec95e68 in KCupsConnection::run() () at /usr/lib64/libkcupslib.so #9 0x7ff880262698 in QThreadPrivate::start(void*) (arg=0x55f0a6245d80) at thread/qthread_unix.cpp:342 #10 0x7ff87f6deefa in start_thread () at /lib64/libpthread.so.0 #11 0x7ff87fef03bf in clone () at /lib64/libc.so.6 Thread 10 (Thread 0x7ff85ad40700 (LWP 2551)): #0 0x7ff87fee14fc in read () at /lib64/libc.so.6 #1 0x7ff87ea2a37f in () at /usr/lib64/libglib-2.0.so.0 #2 0x7ff87e9e2537 in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #3 0x7ff87e9e2982 in () at /usr/lib64/libglib-2.0.so.0 #4 0x7ff87e9e2aff in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #5 0x7ff88048ebeb in QEventDispatcherGlib::processEvents(QFlags) (this=0x7ff848000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #6 0x7ff880436b7b in QEventLoop::exec(QFlags) (this=this@entry=0x7ff85ad3fd60, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:136 #7 0x7ff8802615ce in QThread::exec() (this=this@entry=0x55f0a2aa2e00) at ../../include/QtCore/../../src/corelib/global/qflags.h:118 #8 0x7ff881eb40e6 in QQuickPixmapReader::run() (this=0x55f0a2aa2e00) at /usr/src/debug/libqt5-qtdeclarative-5.14.1-1.3.x86_64/src/quick/util/qquickpixmapcache.cpp:987 #9 0x7ff880262698 in QThreadPrivate::start(void*) (arg=0x55f0a2aa2e00) at thread/qthread_unix.cpp:342 #10 0x7ff87f6deefa in start_thread () at /lib64/libpthread.so.0 #11 0x7ff87fef03bf in clone () at /lib64/libc.so.6 Thread 9 (Thread 0x7ff85bd2d700 (LWP 2545)): #0 0x7ff87fee5acf in poll () at /lib64/libc.so.6 #1 0x7ff87e9e29de in () at /usr/lib64/libglib-2.0.so.0 #2 0x7ff87e9e2aff in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7ff88048ebeb in QEventDispatcherGlib::processEvents(QFlags) (this=0x7ff85b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7ff880436b7b in QEventLoop::exec(QFlags) (this=this@entry=0x7ff85bd2cda0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:136 #5 0x7ff8802615ce in QThread::exec() (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:118 #6 0x7ff880262698 in QThreadPrivate::start(void*) (arg=0x55f0a25bf790) at thread/qthread_unix.cpp:342 #7 0x7ff87f6deefa in start_thread () at /lib64/libpthread.so.0 #8 0x7ff87fef03bf in clone () at /lib64/libc.so.6 Thread 8 (Thread 0x7ff869a7f700 (LWP 2505)): #0 0x7ff87f6e5795 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7ff86b7c181b in () at /usr/lib64/dri/i965_dri.so #2 0x7ff86b7c1697 in () at /usr/lib64/dri/i965_dri.so #3 0x7ff87f6deefa in start_thread () at /lib64/libpthread.so.0 #4 0x7ff87fef03bf in clone () at /lib64/libc.so.6 Thread 7 (Thread 0x7ff86a280700 (LWP 2504)): #0 0x7ff87f6e5795 in
[dolphin] [Bug 410800] Device in Bookmark will show docker mount point when docker container opened
https://bugs.kde.org/show_bug.cgi?id=410800 Stolz changed: What|Removed |Added CC||j...@gsmlandia.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 415014] Plasma5 crashes at startup
https://bugs.kde.org/show_bug.cgi?id=415014 Peter Stolz changed: What|Removed |Added CC||p.stol...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 415014] New: Plasma5 crashes at startup
https://bugs.kde.org/show_bug.cgi?id=415014 Bug ID: 415014 Summary: Plasma5 crashes at startup Product: plasmashell Version: 5.17.3 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: generic-crash Assignee: plasma-b...@kde.org Reporter: p.stol...@gmail.com Target Milestone: 1.0 Created attachment 124424 --> https://bugs.kde.org/attachment.cgi?id=124424=edit KDE Error Report File SUMMARY Plasma5 crashes at startup STEPS TO REPRODUCE 1. I login with my credentials at login screen 2. Plasma5 starts and crashes 3. I get a dark screen with only a mouse cursor and plasma is unusable OBSERVED RESULT Plasma 5 crashes at startup and I can not use my Laptop EXPECTED RESULT Plasma 5 starts up fine and I can use my Laptop SOFTWARE/OS VERSIONS Linux/KDE Plasma: openSUSE Tumbleweed 20191207 KDE-Plasma-Version: 5.17.3 KDE-Frameworks-Version: 5.64.0 QT-Version: 5.13.1 Kernel-Version: 5.3.12-1-default 64 Bit OS ADDITIONAL INFORMATION Hardware Processor: 8 x Intel Core i5-8265U CPU @ 1.60Ghz Memory: 15,4 Gib RAM -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 380019] Kdenlive crashes when using "Fade from black" on an image
https://bugs.kde.org/show_bug.cgi?id=380019 Stolz changed: What|Removed |Added CC|j...@gsmlandia.com | -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktexteditor] [Bug 386151] Error using Tools->Scripts->Emmet
https://bugs.kde.org/show_bug.cgi?id=386151 --- Comment #1 from Stolz <st...@gsmlandia.com> --- Same problem here. This post on the forums has some more information https://forum.kde.org/viewtopic.php?f=25=142536 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktexteditor] [Bug 386151] Error using Tools->Scripts->Emmet
https://bugs.kde.org/show_bug.cgi?id=386151 Stolz <st...@gsmlandia.com> changed: What|Removed |Added CC||st...@gsmlandia.com -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 375713] New: Kdenlive crashes if GPU processing (Movit library) is enabled
https://bugs.kde.org/show_bug.cgi?id=375713 Bug ID: 375713 Summary: Kdenlive crashes if GPU processing (Movit library) is enabled Product: kdenlive Version: 16.12.1 Platform: Gentoo Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Video Display & Export Assignee: j...@kdenlive.org Reporter: j...@gsmlandia.com Target Milestone: --- Application: kdenlive (16.12.1) Qt Version: 5.7.1 Frameworks Version: 5.30.0 Operating System: Linux 4.9.5-gentoo x86_64 Distribution (Platform): Gentoo Packages -- Information about the crash: - What I was doing when the application crashed: Trying to play timeline from the project monitor - Custom settings of the application: It only happens when "Use GPU processing (Movit library)" option is enabled in the playback settings. If I don't enable that option playback works (but very choppy) The crash can be reproduced every time. -- Backtrace: Application: Kdenlive (kdenlive), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f219cd2b780 (LWP 22834))] Thread 17 (Thread 0x7f211639c700 (LWP 31750)): #0 0x7f2194cf63a8 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f218166cdc4 in ?? () from /usr/lib64/opengl/nvidia/lib/libGLX_nvidia.so.0 #2 0x7f217afd5cd4 in ?? () from /usr/lib64/libnvidia-glcore.so.378.09 #3 0x7f218166c0ac in ?? () from /usr/lib64/opengl/nvidia/lib/libGLX_nvidia.so.0 #4 0x7f2194cf0444 in start_thread () from /lib64/libpthread.so.0 #5 0x7f219685fabd in clone () from /lib64/libc.so.6 Thread 16 (Thread 0x7f2146ffd700 (LWP 31749)): [KCrash Handler] #6 0x7f21967ab1e8 in raise () from /lib64/libc.so.6 #7 0x7f21967ac63a in abort () from /lib64/libc.so.6 #8 0x7f21794656a9 in movit::abort_gl_error(unsigned int, char const*, int) () from /usr/lib64/libmovit.so.5 #9 0x7f21796eae40 in GlslManager::render_frame_rgba (this=, chain=chain@entry=0x7f213835df20, frame=frame@entry=0x7f213826b6b0, width=width@entry=3840, height=height@entry=2160, image=image@entry=0x7f2146ffcb70) at filter_glsl_manager.cpp:443 #10 0x7f21796ebcc9 in movit_render (chain=0x7f213835df20, frame=0x7f213826b6b0, format=0x3b984ac, output_format=mlt_image_rgb24a, width=3840, height=2160, image=0x7f2146ffcb70) at filter_movit_convert.cpp:454 #11 0x7f21796edc81 in convert_image (frame=0x7f213826b6b0, image=0x7f2146ffcb70, format=, output_format=mlt_image_rgb24a) at filter_movit_convert.cpp:573 #12 0x7f219bf10193 in mlt_frame_get_image (self=self@entry=0x7f213826b6b0, buffer=buffer@entry=0x7f2146ffcb70, format=format@entry=0x3b984ac, width=width@entry=0x7f2146ffcb58, height=height@entry=0x7f2146ffcb5c, writable=writable@entry=0) at mlt_frame.c:591 #13 0x7f2171744b5d in filter_get_image (this=this@entry=0x7f213826b6b0, image=image@entry=0x7f2146ffcb70, format=format@entry=0x3b984ac, width=width@entry=0x7f2146ffcb58, height=height@entry=0x7f2146ffcb5c, writable=writable@entry=0) at filter_frei0r.c:32 #14 0x7f219bf10140 in mlt_frame_get_image (self=self@entry=0x7f213826b6b0, buffer=buffer@entry=0x7f2146ffcb70, format=format@entry=0x3b984ac, width=width@entry=0x7f2146ffcb58, height=height@entry=0x7f2146ffcb5c, writable=writable@entry=0) at mlt_frame.c:585 #15 0x7f219bf23eb3 in get_image_b (b_frame=b_frame@entry=0x7f213826b6b0, image=image@entry=0x7f2146ffcb70, format=format@entry=0x3b984ac, width=width@entry=0x7f2146ffcb58, height=height@entry=0x7f2146ffcb5c, writable=writable@entry=0) at mlt_transition.c:366 #16 0x7f219bf10140 in mlt_frame_get_image (self=self@entry=0x7f213826b6b0, buffer=buffer@entry=0x7f2146ffcb70, format=format@entry=0x3b984ac, width=width@entry=0x7f2146ffcb58, height=height@entry=0x7f2146ffcb5c, writable=writable@entry=0) at mlt_frame.c:585 #17 0x7f21710e30f5 in get_image (a_frame=a_frame@entry=0x7f213833cb50, image=image@entry=0x7f2146ffce18, format=format@entry=0x3b984ac, width=width@entry=0x7f2146ffce04, height=height@entry=0x7f2146ffce08, writable=writable@entry=0) at transition_qtblend.cpp:146 #18 0x7f219bf10140 in mlt_frame_get_image (self=self@entry=0x7f213833cb50, buffer=buffer@entry=0x7f2146ffce18, format=format@entry=0x3b984ac, width=width@entry=0x7f2146ffce04, height=height@entry=0x7f2146ffce08, writable=writable@entry=0) at mlt_frame.c:585 #19 0x7f219bf24a6e in producer_get_image (self=self@entry=0x7f2138250c30, buffer=buffer@entry=0x7f2146ffce18, format=format@entry=0x3b984ac, width=width@entry=0x7f2146ffce04, height=height@entry=0x7f2146ffce08, writable=writable@entry=0) at mlt_tractor.c:370 #20 0x7f219bf10140 in mlt_frame_get_image (self=self@entry=0x7f2138250c30, buffer=buffer@entry=0x7f2146ffce18, format=format@entry=0x3b984ac, width=width@entry=0x7f2146ffce04, height=height@entry=0x7f2146ffce08,
[plasmashell] [Bug 374138] Start shell script with desktop icon
https://bugs.kde.org/show_bug.cgi?id=374138 --- Comment #1 from Peter Stolz <p.stol...@gmail.com> --- It seems to be caused by Bug 366793 Regression in Konsole's handling of command line parameters -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 374138] New: Start shell script with desktop icon
https://bugs.kde.org/show_bug.cgi?id=374138 Bug ID: 374138 Summary: Start shell script with desktop icon Product: plasmashell Version: 5.8.3 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Desktop Containment Assignee: se...@kde.org Reporter: p.stol...@gmail.com Target Milestone: 1.0 Created attachment 102986 --> https://bugs.kde.org/attachment.cgi?id=102986=edit Screeshot with desktop icon configuration It is not possible to start a shell script with a desktop icon: No terminal is starting and no user interacts (password input) are possible. In earlier KDE Version like 5.4 this works (see attachment) Peter -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 362733] New: Kate does not preserve original group owner when saving a file
https://bugs.kde.org/show_bug.cgi?id=362733 Bug ID: 362733 Summary: Kate does not preserve original group owner when saving a file Product: kate Version: unspecified Platform: Gentoo Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: application Assignee: kwrite-bugs-n...@kde.org Reporter: j...@gsmlandia.com Whenever a save a file whose group is not the default for the user Kate changes the group of the file to the default one $ groups javi users nginx $ touch sample.txt $ sudo chown javi:nginx sample.txt $ ls -l sample.txt -rw-r--r-- 1 javi nginx 0 may 6 14:31 sample.txt $ kate sample.txt # Make some changes to the file and then save it $ ls -l sample.txt -rw-r--r-- 1 javi users 2 may 6 14:32 sample.txt Reproducible: Always Steps to Reproduce: 1. Create a file whose group is not the default for the current user 2. Open the file with Kate 3. Make some changes to the file and save it Actual Results: The group of the file is changed Expected Results: The file should preserve the original group ownership Kate Version 15.12.3 using KDE Frameworks 5.21.0 Qt 5.5.1 (built against 5.5.1) Compiled from the official Gentoo repository -- You are receiving this mail because: You are watching all bug changes.
