[ark] [Bug 458523] New: ARK 21.12.3 refuse the password of RAR file
https://bugs.kde.org/show_bug.cgi?id=458523 Bug ID: 458523 Summary: ARK 21.12.3 refuse the password of RAR file Product: ark Version: 21.12.3 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: general Assignee: elvis.angelac...@kde.org Reporter: adriano.ceni@gmail.com CC: aa...@kde.org, rthoms...@gmail.com Target Milestone: --- Created attachment 151711 --> https://bugs.kde.org/attachment.cgi?id=151711=edit screen shot Hi, I have a problem with ARK Version 21.12.3 that preinstalled on Kubuntu 22.04. when I try open a RAR file with password ARK refuse the password. I opened the RAR file in my phone and the app accept the password. so what is the problem in ARK 21.12.3 ? I had use ARK on Kubuntu 20.04 and it worked perfect! thank you all. Operating System: Kubuntu 22.04 KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 Kernel Version: 5.15.0-46-generic (64-bit) -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 447064] crash while rendering
https://bugs.kde.org/show_bug.cgi?id=447064 --- Comment #8 from ad --- Sorry Farid, for not monitoring the thread. For some time I'm not working with videos now, so this made me negligent. Yes, you can close the thread. If in the future I pick video editing up again, I'll see what happens. Thanks by the way for Kdenlive! Greetings, ad T = 06 54 24 00 46 E = nudna...@zonnet.nl A = Dorpsstraat 96, 6252 NE Eckelrade Op 26-8-2022 om 21:04 schreef farid: > https://bugs.kde.org/show_bug.cgi?id=447064 > > farid changed: > > What|Removed |Added > > Resolution|--- |WAITINGFORINFO > CC||snd.no...@gmail.com > Status|REPORTED|NEEDSINFO > > --- Comment #7 from farid --- > So this is fixed? We can close it? > -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 447064] crash while rendering
https://bugs.kde.org/show_bug.cgi?id=447064 --- Comment #6 from ad --- Created attachment 144710 --> https://bugs.kde.org/attachment.cgi?id=144710=edit second version of craching file Hi emohr, here the newly rendered file (including log) - after applying the changes you suggested (no effects at all in this file). Thanks again. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 447064] crash while rendering
https://bugs.kde.org/show_bug.cgi?id=447064 --- Comment #3 from ad --- Thanks for replying! Uploaded the file (with subtitle-file). -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 447064] crash while rendering
https://bugs.kde.org/show_bug.cgi?id=447064 --- Comment #2 from ad --- Created attachment 144681 --> https://bugs.kde.org/attachment.cgi?id=144681=edit File that crashes, including subtitle. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 447064] New: crash while rendering
https://bugs.kde.org/show_bug.cgi?id=447064 Bug ID: 447064 Summary: crash while rendering Product: kdenlive Version: 21.12.0 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: crash Priority: NOR Component: Video Display & Export Assignee: j...@kdenlive.org Reporter: nudna...@zonnet.nl Target Milestone: --- Sorry for not providing you with the information following the correct procedues (I'm no dev). Here's my crash info - using Kdenlive: 21.12.0 in Windows 11: [h264 @ 167a2540] QP 52 out of range [h264 @ 167a2540] decode_slice_header error [h264 @ 167a5780] QP 52 out of range [h264 @ 167a5780] decode_slice_header error [h264 @ 167a5780] no frame! [h264 @ 167a6080] Reference 2 >= 2 [h264 @ 167a6080] error while decoding MB 69 3, bytestream 6151 [h264 @ 167a7780] QP 52 out of range [h264 @ 167a7780] decode_slice_header error [h264 @ 167a7c00] Found reference and non-reference fields in the same frame, which is not implemented. Update your FFmpeg version to the newest one from Git. If the problem still occurs, it means that your file has a feature which has not been implemented. [h264 @ 167a7c00] If you want to help, upload a sample of this file to https://streams.videolan.org/upload/ and contact the ffmpeg-devel mailing list. (ffmpeg-de...@ffmpeg.org) [h264 @ 167a7c00] decode_slice_header error Current Frame: 102, percentage: 0 [h264 @ 167a2540] mmco: unref short failure [h264 @ 167a2540] QP 52 out of range [h264 @ 167a2540] decode_slice_header error [h264 @ 167a5300] Missing reference picture, default is 6 [h264 @ 167a5300] Missing reference picture, default is 6 [h264 @ 167a4e40] QP 52 out of range [h264 @ 167a4e40] decode_slice_header error [h264 @ 167a5780] Missing reference picture, default is 6 [h264 @ 167a5780] Missing reference picture, default is 6 [h264 @ 167a5780] Reference 3 >= 2 [h264 @ 167a5780] error while decoding MB 0 1, bytestream 4772 [h264 @ 167a6080] Found reference and non-reference fields in the same frame, which is not implemented. Update your FFmpeg version to the newest one from Git. If the problem still occurs, it means that your file has a feature which has not been implemented. [h264 @ 167a6080] If you want to help, upload a sample of this file to https://streams.videolan.org/upload/ and contact the ffmpeg-devel mailing list. (ffmpeg-de...@ffmpeg.org) [h264 @ 167a6080] decode_slice_header error [h264 @ 167a7780] reference picture missing during reorder [h264 @ 167a7780] Missing reference picture, default is 6 [h264 @ 167a4e40] mmco: unref short failure [h264 @ 167a5780] illegal short term buffer state detected [h264 @ 167a5780] Missing reference picture, default is 65567 [h264 @ 167a5780] Missing reference picture, default is 65567 [h264 @ 167a6080] Missing reference picture, default is 65567 [h264 @ 167a6080] Missing reference picture, default is 65567 [h264 @ 167a7780] Missing reference picture, default is 65567 [h264 @ 167a7780] Missing reference picture, default is 65567 [h264 @ 167a6540] Missing reference picture, default is 65567 [h264 @ 167a6540] Missing reference picture, default is 65567 [h264 @ 167a7c00] Missing reference picture, default is 65567 [h264 @ 167a7780] mmco: unref short failure [swscaler @ 24bdfd00] Warning: data is not aligned! This can lead to a speed loss Current Frame: 103, percentage: 0 [mp4 @ 029a5700] Timestamps are unset in a packet for stream 1. This is deprecated and will stop working in the future. Fix your code to set the timestamps properly [mp4 @ 029a5700] Encoder did not produce proper pts, making some up. [mp4 @ 029a5700] Application provided invalid, non monotonically increasing dts to muxer in stream 1: 28798976 >= 28798976 Hope you can help. Kdenlive is a really nice tool! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 442433] Chromium-based (electron) web browsers hang when rendering fullscreen
https://bugs.kde.org/show_bug.cgi?id=442433 Ad changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 442433] Chromium-based (electron) web browsers hang when rendering fullscreen
https://bugs.kde.org/show_bug.cgi?id=442433 --- Comment #2 from Ad --- As I can see! Thanks for your quick reply, feel free to close (if the attempt I am about to make fails). -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwindowsystem] [Bug 442433] New: Chromium-based (electron) web browsers hang when rendering fullscreen
https://bugs.kde.org/show_bug.cgi?id=442433 Bug ID: 442433 Summary: Chromium-based (electron) web browsers hang when rendering fullscreen Product: frameworks-kwindowsystem Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: mrnyctico...@gmail.com Target Milestone: --- SUMMARY I am not quite sure it's a bug rather than a problem with my configuration, but for a couple of weeks (the problem didn't appear before) any chromium-based web browser run through Wayland with `--enable-features=UseOzonePlatform --ozone-platform=wayland` -- the usual way of forcing an electron application to render to the Wayland client -- completely freezes when setting a running video stream to fullscreen. The only escape hatch is Alt-F4 out of it. STEPS TO REPRODUCE 1. From a tty, launch a Wayland session: `dbus-run-session startplasma-wayland` 2. Run microsoft-edge-beta (rpm source: 94.0.992.19-1) or brave-browser (rpm source: 1.29.80-1) with the flags `--enable-features=UseOzonePlatform --ozone-platform=wayland` 3. Point the browser to an embedded video, click the player widget to set it to fullscreen. OBSERVED RESULT The browser completely hangs. (Wasn't happening a couple of weeks ago) EXPECTED RESULT The browser runs the video fine. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20210910 KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.85.0 Qt Version: 5.15.2 Kernel Version: 5.14.1-1-default (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i7-6700HQ CPU @ 2.60GHz Memory: 15.5 Gio of RAM Graphics Processor: Mesa Intel® HD Graphics 530 -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 440175] New: VSCode suddently crashing despite low workload
https://bugs.kde.org/show_bug.cgi?id=440175
Bug ID: 440175
Summary: VSCode suddently crashing despite low workload
Product: Akonadi
Version: unspecified
Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: server
Assignee: kdepim-b...@kde.org
Reporter: mrnyctico...@gmail.com
Target Milestone: ---
Application: akonadiserver (5.17.3 (21.04.3))
Qt Version: 5.15.2
Frameworks Version: 5.84.0
Operating System: Linux 5.13.2-1-default x86_64
Windowing System: Wayland
Drkonqi Version: 5.22.3
Distribution: "openSUSE Tumbleweed"
-- Information about the crash:
I was simply refactoring Python code with only a couple of extensions on when
this happened.
The crash can be reproduced sometimes.
-- Backtrace:
Application: Akonadi Server (akonadiserver), signal: Segmentation fault
[KCrash Handler]
#4 std::default_delete::operator() (__ptr=0x91,
this=) at /usr/include/c++/11/bits/unique_ptr.h:79
#5 std::unique_ptr >::~unique_ptr
(this=, this=) at
/usr/include/c++/11/bits/unique_ptr.h:361
#6 __gnu_cxx::new_allocator >
>::destroy > > (__p=,
this=) at /usr/include/c++/11/ext/new_allocator.h:168
#7
std::allocator_traits > >
>::destroy > > (__p=,
__a=...) at /usr/include/c++/11/bits/alloc_traits.h:531
#8 std::vector >,
std::allocator > > >::_M_erase
(__position=std::unique_ptr = {get() =
0x562c886e2a60}, this=) at
/usr/include/c++/11/bits/vector.tcc:177
#9 std::vector >,
std::allocator > > >::erase
(__position=std::unique_ptr = {get() =
0x562c886e2a60}, this=) at
/usr/include/c++/11/bits/stl_vector.h:1431
#10 Akonadi::Server::AkonadiServer::connectionDisconnected (this=) at
/usr/src/debug/akonadi-server-21.04.3-2.2.x86_64/src/server/akonadi.cpp:234
#11 0x7f5c0a2a4f5e in QObject::event (this=0x7fff6f100500,
e=0x7f5bd402ef70) at kernel/qobject.cpp:1314
#12 0x7f5c0a27893f in doNotify (event=0x7f5bd402ef70,
receiver=0x7fff6f100500) at kernel/qcoreapplication.cpp:1154
#13 QCoreApplication::notify (event=, receiver=,
this=) at kernel/qcoreapplication.cpp:1140
#14 QCoreApplication::notifyInternal2 (receiver=0x7fff6f100500,
event=0x7f5bd402ef70) at kernel/qcoreapplication.cpp:1064
#15 0x7f5c0a27b9b7 in QCoreApplicationPrivate::sendPostedEvents
(receiver=0x0, event_type=0, data=0x562c886d4e20) at
kernel/qcoreapplication.cpp:1821
#16 0x7f5c0a2d07d3 in postEventSourceDispatch (s=0x562c886dcc10) at
kernel/qeventdispatcher_glib.cpp:277
#17 0x7f5c084b380f in g_main_context_dispatch () from
/lib64/libglib-2.0.so.0
#18 0x7f5c084b3b98 in ?? () from /lib64/libglib-2.0.so.0
#19 0x7f5c084b3c4f in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#20 0x7f5c0a2cfe54 in QEventDispatcherGlib::processEvents
(this=0x562c886da0c0, flags=...) at kernel/qeventdispatcher_glib.cpp:423
#21 0x7f5c0a27736b in QEventLoop::exec (this=this@entry=0x7fff6f100340,
flags=..., flags@entry=...) at
../../include/QtCore/../../src/corelib/global/qflags.h:69
#22 0x7f5c0a27f650 in QCoreApplication::exec () at
../../include/QtCore/../../src/corelib/global/qflags.h:121
#23 0x562c87b3f3d9 in AkApplicationBase::exec (this=0x7fff6f1004d0) at
/usr/src/debug/akonadi-server-21.04.3-2.2.x86_64/src/shared/akapplication.cpp:107
#24 main (argc=, argv=) at
/usr/src/debug/akonadi-server-21.04.3-2.2.x86_64/src/server/main.cpp:65
[Inferior 1 (process 1691) detached]
Possible duplicates by query: bug 440159, bug 440137, bug 440136, bug 440125,
bug 440067.
Reported using DrKonqi
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 439408] Dirty shadows around certain panes, bars & application menus
https://bugs.kde.org/show_bug.cgi?id=439408 --- Comment #11 from Ad --- (In reply to Ad from comment #10) > Good catch David Edmundson, removing ~/.cache/*.kcache and restarting > plasmashell fixed it for me. > > Le mar. 6 juil. 2021 à 18:09, Alois Wohlschlager > a écrit : > > > > https://bugs.kde.org/show_bug.cgi?id=439408 > > > > --- Comment #9 from Alois Wohlschlager --- > > > Can you confirm if this is "resolved" by removing ~/.cache/*.kcache and > > > restarting plasmashell > > > > In fact, just restarting plasmashell seemed to be enough. > > > > -- > > You are receiving this mail because: > > You reported the bug. In fact the problem happens again on every new fresh sessions even after removing the cache. I would not even consider it a temporary fix. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 439408] Dirty shadows around certain panes, bars & application menus
https://bugs.kde.org/show_bug.cgi?id=439408 --- Comment #10 from Ad --- Good catch David Edmundson, removing ~/.cache/*.kcache and restarting plasmashell fixed it for me. Le mar. 6 juil. 2021 à 18:09, Alois Wohlschlager a écrit : > > https://bugs.kde.org/show_bug.cgi?id=439408 > > --- Comment #9 from Alois Wohlschlager --- > > Can you confirm if this is "resolved" by removing ~/.cache/*.kcache and > > restarting plasmashell > > In fact, just restarting plasmashell seemed to be enough. > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 439408] New: Dirty shadows around certain panes, bars & application menus
https://bugs.kde.org/show_bug.cgi?id=439408 Bug ID: 439408 Summary: Dirty shadows around certain panes, bars & application menus Product: plasmashell Version: 5.22.2 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: mrnyctico...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 139805 --> https://bugs.kde.org/attachment.cgi?id=139805=edit screenshots SUMMARY Most default widgets (default bottom bar + menu) render with dirty, empty-boxed "shadows", giving Plasma a sketchy look. STEPS TO REPRODUCE 1. Create a new user and open a Plasma Wayland session from it. OBSERVED RESULT See the attached files. The first is from my current session. The second is from a new user's session. EXPECTED RESULT Clean shadows or no shadow, not the blurry, sketchy middle-ground shown here. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20210629 KDE Plasma Version: 5.22.2 KDE Frameworks Version: 5.83.0 Qt Version: 5.15.2 Kernel Version: 5.12.13-1-default (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i7-6700HQ CPU @ 2.60GHz Memory: 15.5 Gio of RAM Graphics Processor: Mesa DRI Intel® HD Graphics 530 -- You are receiving this mail because: You are watching all bug changes.
[baloo-widgets] [Bug 437974] New: baloo_file crashes upon login
https://bugs.kde.org/show_bug.cgi?id=437974 Bug ID: 437974 Summary: baloo_file crashes upon login Product: baloo-widgets Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: stefan.bru...@rwth-aachen.de Reporter: mrnyctico...@gmail.com CC: baloo-bugs-n...@kde.org Target Milestone: --- Created attachment 138932 --> https://bugs.kde.org/attachment.cgi?id=138932=edit error logs made using symbols tools SUMMARY Baloo instantly crashed right after login. STEPS TO REPRODUCE 1. Install openSUSE Tumbleweed, snapshot 20210527. 2. Reboot. From tty1, log in to a ordinary user session and then do: - $ env QT_QPA_PLATFORM=wayland dbus-launch startplasma-wayland - 3. Baloo will crash while the workspace is loading. SYSTEM INFOS Operating System: openSUSE Tumbleweed 20210527 KDE Plasma Version: 5.21.5 KDE Frameworks Version: 5.82.0 Qt Version: 5.15.2 Kernel Version: 5.12.4-2-default OS Type: 64-bit Graphics Platform: Wayland Processors: 8 × Intel® Core™ i7-6700HQ CPU @ 2.60GHz Memory: 15.5 Gio of RAM Graphics Processor: Mesa DRI Intel® HD Graphics 530 -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 435556] Neither spectacle nor any screenshot utility is able to use "rectangular" / partial screen mode.
https://bugs.kde.org/show_bug.cgi?id=435556 --- Comment #4 from Ad --- (In reply to Nate Graham from comment #3) > It's going to be released on June 3rd, just 5 weeks away. See > https://community.kde.org/Schedules/Plasma_5 Right, that's good, and I rejoice that this trick might help people through 5 full weeks of pain. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 435556] Neither spectacle nor any screenshot utility is able to use "rectangular" / partial screen mode.
https://bugs.kde.org/show_bug.cgi?id=435556 --- Comment #2 from Ad --- (In reply to Nate Graham from comment #1) > Fixed in Plasma 5.22 already, thankfully. > > *** This bug has been marked as a duplicate of bug 432260 *** 5.22 is a long way down the road as far as I can tell. Also I wanted to emphasis that the only thing that actually works is the convoluted ``` DISPLAY=0 QT_QPA_PLATFORM=wayland spectacle ``` -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 435556] New: Neither spectacle nor any screenshot utility is able to use "rectangular" / partial screen mode.
https://bugs.kde.org/show_bug.cgi?id=435556 Bug ID: 435556 Summary: Neither spectacle nor any screenshot utility is able to use "rectangular" / partial screen mode. Product: Spectacle Version: 21.03.80 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: m...@baloneygeek.com Reporter: mrnyctico...@gmail.com CC: k...@david-redondo.de Target Milestone: --- I am using openSUSE Tumbleweed snapshot 20210406 on x64. I've tried to launch spectacle 20.12.3-1.2 with various launch parameters: - QTA_QPA_PLATFORM=wayland spectacle - QTA_QPA_PLATFORM=xcb spectacle - GDK_BACKEND=x11 spectacle - GDK_BACKEND=wayland spectacle but none allows me to use spectacle's rectangular snapshot feature. All other snaphot features work, however. No matter how I launch it, spectacle with crash upon using the rectangular snapshot with this message: ``` Error calling KWin DBus interface: "org.kde.kwin.Screenshot.Error.ScreenMissing" "Screen not found" ``` -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 426814] Application Dashboard "steals" keybindings triggered from pressing the Meta key
https://bugs.kde.org/show_bug.cgi?id=426814 --- Comment #1 from Ad --- typo: have the *default* active pane . . . -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 426814] New: Application Dashboard "steals" keybindings triggered from pressing the Meta key
https://bugs.kde.org/show_bug.cgi?id=426814 Bug ID: 426814 Summary: Application Dashboard "steals" keybindings triggered from pressing the Meta key Product: kdeplasma-addons Version: 5.18.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Application Dashboard Assignee: h...@kde.org Reporter: mrnyctico...@gmail.com CC: plasma-b...@kde.org Target Milestone: --- SUMMARY In some circumstances the Application Dashboard widget / plasmoid "steals" keybindings from Application Menu after Application Menu is set to replace Application Launcher as main launcher. STEPS TO REPRODUCE 1. Have the fault active pane contain (both enabled) the default Application Launcher + Application Dashboard, with Application Launcher's keybinding set to Alt-F1 and Application Dashboard's keybinding set to Meta + . 2. Right-click on the default Application Launcher, and from the "Pick alternative" menu, select "Application Menu" (also known as "Kicker") 3. Press the Meta key (alone). OBSERVED RESULT Pressing the Meta key opens Application Dashboard. EXPECTED RESULT Pressing the Meta key opens Application Menu. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 32 KDE SiG, Plasma 5.18.5 KDE Plasma Version: KDE Frameworks Version: 5.70.0 Qt Version: 5.14.2 -- You are receiving this mail because: You are watching all bug changes.
