[kdenlive] [Bug 385780] Speed Effect is not saved after editing
https://bugs.kde.org/show_bug.cgi?id=385780 --- Comment #16 from Marcus --- I tested the kdenlive-19.03.70-bd12c4f-x86_64.appimage As i just see, the speed effect remains on group move, but disappears on project close , project reopen. Steps to reproduce it: 1. create new project 2. add ONE video clip into bin 3. add a color clip 4. place the video clip into time line 5. put the color clip behind the video clip 6. add speed effect to video clip, set it to 200% 7. replay the clip section, check the double speed. 8. save project 9. close kdenlive 10. start kdenlive, reload the project 10. check the clip in timeline / context menu / speed : the speed effect on the clip is gone. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 385780] Speed Effect is not saved after editing
https://bugs.kde.org/show_bug.cgi?id=385780 --- Comment #14 from Marcus --- Created attachment 117458 --> https://bugs.kde.org/attachment.cgi?id=117458=edit Screenshot ofkdenlive-19.03.70-bd12c4f-x86_64.appimage I tested the kdenlive-19.03.70-bd12c4f-x86_64.appimage In the given version, there is no (more) speed effect available. See the screen shot. The former effect that was set with the older kdenlive version is not being represented in the current program. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 385780] Speed Effect is not saved after editing
https://bugs.kde.org/show_bug.cgi?id=385780 --- Comment #12 from Marcus --- I am using kde-apps/kdenlive-18.12.0 on gentoo linux (default/linux/amd64/17.0/desktop) and just tested the current version. The bug still persists and can be recreated by following Comment 4. Here I would note that this bug is not specific to the windows binary. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 401280] Unpaired automatically
https://bugs.kde.org/show_bug.cgi?id=401280 --- Comment #6 from Marcus Sundman --- Pressing "refresh" doesn't unpair anymore for me after deleting settings from both phone and computer. It still disconnects all the time (despite disabling all powersave options for the app on the phone), having to run the app manually to reconnect, but maybe that's another bug? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 370023] plasmashell crash when attempting to use search bar
https://bugs.kde.org/show_bug.cgi?id=370023 --- Comment #4 from Marcus Harrison --- Fine by me, tried reproducing it and can't. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 400854] kwin crash when restarting IntelliJ application
https://bugs.kde.org/show_bug.cgi?id=400854 --- Comment #7 from Marcus Better --- I cannot reproduce it consistently, so not sure in which scenarios it happens. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 401317] New: Replace the search system with KFind
https://bugs.kde.org/show_bug.cgi?id=401317 Bug ID: 401317 Summary: Replace the search system with KFind Product: dolphin Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: search Assignee: dolphin-bugs-n...@kde.org Reporter: bio...@gmail.com Target Milestone: --- The current search system used by Dolphin is far from being optimal. I wouldn't want to sound rough but the search system, when works, it shows just partial results, sometimes it doesn't work at all so that I ended up replacing search with filter, which is a good compromise most of times. At the same time we have KFind (which is great), it supports all sort of advanced search options, always finds every possible result and, most important, I never seen it crashing. I was wandering, did anyone contemplate the the idea to truly integrate it into Dolphin? (I mean not like it is now: use other search tools or similar) but to get the result from KFind when someone searches using the input text element from Dolphin (starting from the current directory). -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 401280] Unpaired automatically
https://bugs.kde.org/show_bug.cgi?id=401280 Marcus Sundman changed: What|Removed |Added CC||sund...@iki.fi --- Comment #2 from Marcus Sundman --- I did those things separately, without success, but deleting the config from both phone and computer at the same time seems to have helped now. At least the list refresh doesn't unpair them now. Let's see how it goes. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 401056] akonadiserver mamory leak
https://bugs.kde.org/show_bug.cgi?id=401056 Marcus Harrison changed: What|Removed |Added CC||mar...@harrisonland.co.uk --- Comment #1 from Marcus Harrison --- I'm seeing the same behaviour in KDE Neon packages. Plasma: 5.14.3 Frameworks: 5.52.0 Qt: 5.11.2 Akonadi server: 5.9.3 -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 401280] New: Unpaired automatically
https://bugs.kde.org/show_bug.cgi?id=401280 Bug ID: 401280 Summary: Unpaired automatically Product: kdeconnect Version: 1.3.3 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: common Assignee: albertv...@gmail.com Reporter: sund...@iki.fi Target Milestone: --- SUMMARY KDE Connect used to work just fine, but lately my phones are constantly getting unpaired. To not be connected is one thing, and I've resolved that by disabling all battery saving for kdeconnect, but this auto-unpairing is driving me nuts. This happens with different versions of android on different phones. STEPS TO REPRODUCE 1. Open KDE connect on both the phone and computer. 2. Pair them. 3. Hit "Refresh" on the KDE Connect System Settings Module. OBSERVED RESULT My phone gets upaired, and vanishes from the list. Hitting "Refresh" again makes it reappear on the list, but now in an unpaired state. EXPECTED RESULT No changes. SOFTWARE/OS VERSIONS Linux/KDE Plasma: (k)ubuntu 18.10. KDE Plasma Version: 5.14.3-0ubuntu1~ubuntu18.10~ppa1 KDE Frameworks Version: 4:17.08.3-0ubuntu2 Qt Version: 4:4.8.7+dfsg-7ubuntu1 ADDITIONAL INFORMATION It doesn't happen only when I refresh the list, as described above, but also from time to time randomly without doing anything in particular. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 368438] KDE Connect does not communicate while running in background on phone
https://bugs.kde.org/show_bug.cgi?id=368438 Marcus Sundman changed: What|Removed |Added CC||sund...@iki.fi --- Comment #23 from Marcus Sundman --- This used to work just fine, but lately my phones are constantly getting unpaired. To not be connected is one thing, and I've resolved that by disabling all battery saving for kdeconnect, but this auto-unpairing is driving me nuts. This happens with different versions of android on different phones. Steps to reproduce: 1. Open KDE connect on both the phone and computer. 2. Pair them. 3. Hit "Refresh" on the computer. Result: The phone and computer get unpaired, and need to be paired again. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 401151] docx files opened as archives in remote folders
https://bugs.kde.org/show_bug.cgi?id=401151 --- Comment #2 from Marcus --- I don't have all those opportunities to test remote protocols. In the case of FTP, it works correctly (I used this https://dlptest.com/ftp-test/), it open with LibreOffice (though I cannot read it from that server). I also noted the icon is different when I copy a file to google drive the icon becomes the one of archives (yellow). When a docx file is moved/copied to another location, it changes back to the violet document icon. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 401152] New: In multi monitor configuration PC start with screen OFF
https://bugs.kde.org/show_bug.cgi?id=401152 Bug ID: 401152 Summary: In multi monitor configuration PC start with screen OFF Product: kwin Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: bio...@gmail.com Target Milestone: --- Created attachment 116376 --> https://bugs.kde.org/attachment.cgi?id=116376=edit Screen configuration I have the PC connected to a Samsung TV through an audio amplifier. Usually I do not use the TV so it is disabled in monitor settings (attachment: SAMSUNG). My monitor (attachment: VE248) is set as the main screen. OBSERVED RESULT When the computer starts it start with the screen ON: I can see the mouse on a dark background and it moves correctly. In a few seconds it turns OFF, no matter I move the mouse or randomly press on keyboard, it stays OFF. The turn my monitor ON I have to power ON the amplifier, then it turns ON. After that I can turn the amplifier OFF again, everything keeps working as expected. EXPECTED RESULT The screen should stay ON independently on the amplifier when it is enabled in Screen settings. SOFTWARE/OS VERSIONS OS: Kubuntu 18.10 KDE Plasma Version: 5.14.3 KDE Frameworks Version: 5.52.0 Qt Version: 5.11.1 ADDITIONAL INFORMATION PC is connected from an AMD GPU through HDMI to the monitor. PC is connected from the integrated Intel HDMI output to a Yamaha audio amplifier (5.1 Home cinema) which is connected through HDMI to a Samsung TV. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 401151] New: docx files opened as archives in remote folders
https://bugs.kde.org/show_bug.cgi?id=401151 Bug ID: 401151 Summary: docx files opened as archives in remote folders Product: systemsettings Version: unspecified Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: kcm_filetypes Assignee: fa...@kde.org Reporter: bio...@gmail.com Target Milestone: --- Created attachment 116375 --> https://bugs.kde.org/attachment.cgi?id=116375=edit File association setted It is impossible to set remote files .docx to open with libreoffice. They will always open with Ark. This happen (for me) only on the google drive folder, when moved locally everithing works as expected. STEPS TO REPRODUCE 1. Setup Google drive directory 2. Open Dolphin and go to "gdrive:account/" 3. Copy a .docx file in some folder 4. Open the file with Dolphin (as usual, by double clicking) Ark will open 5. Set the file to be opened with LibreOffice (see the attachment) 6. Go to number 3 OBSERVED RESULT Locally it works as expected EXPECTED RESULT The association of docx -> LibreOffice should be remembered SOFTWARE/OS VERSIONS Kubuntu 18.10 updated KDE Plasma Version: 5.14.3 KDE Frameworks Version: 5.52.0 Qt Version: 5.11.1 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 396921] Speed Effect - Breaks when Cut with Razor Tool
https://bugs.kde.org/show_bug.cgi?id=396921 Marcus Sundman changed: What|Removed |Added CC||sund...@iki.fi -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 369585] Timeline corruption due to speed effect
https://bugs.kde.org/show_bug.cgi?id=369585 Marcus Sundman changed: What|Removed |Added CC||sund...@iki.fi -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 369585] Timeline corruption due to speed effect
https://bugs.kde.org/show_bug.cgi?id=369585 Marcus Sundman changed: What|Removed |Added CC||enzo.gianvitto...@gmail.com --- Comment #27 from Marcus Sundman --- *** Bug 401037 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 401037] Speed effects get lost and mess up other effects when the clips are adjusted in the timeline
https://bugs.kde.org/show_bug.cgi?id=401037 Marcus Sundman changed: What|Removed |Added CC||sund...@iki.fi Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #1 from Marcus Sundman --- *** This bug has been marked as a duplicate of bug 369585 *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 400854] kwin crash when restarting IntelliJ application
https://bugs.kde.org/show_bug.cgi?id=400854 --- Comment #4 from Marcus Better --- No, I have a plain Debian install. No fancy scripts that I know of. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 400854] New: kwin crash when restarting IntelliJ application
https://bugs.kde.org/show_bug.cgi?id=400854 Bug ID: 400854 Summary: kwin crash when restarting IntelliJ application Product: kwin Version: 5.13.5 Platform: Debian testing OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: mar...@better.se Target Milestone: --- Application: kwin_x11 (5.13.5) Qt Version: 5.11.2 Frameworks Version: 5.49.0 Operating System: Linux 4.19.1-better x86_64 Distribution: Debian GNU/Linux testing (buster) -- Information about the crash: - What I was doing when the application crashed: Was restarting the IntelliJ IDEA application (the feature that restarts the IDE after a plugin update). -- Backtrace: Application: Kwin (kwin_x11), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f1e200bb940 (LWP 2574))] Thread 5 (Thread 0x7f1e1d1b1700 (LWP 4321)): #0 0x7f1e28ad6e6c in futex_wait_cancelable (private=, expected=0, futex_word=0x55e668c385a0) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x55e668c38550, cond=0x55e668c38578) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x55e668c38578, mutex=0x55e668c38550) at pthread_cond_wait.c:655 #3 0x7f1d87950e2b in cnd_wait (mtx=0x55e668c38550, cond=0x55e668c38578) at ../../../include/c11/threads_posix.h:155 #4 util_queue_thread_func (input=input@entry=0x55e668d596e0) at ../../../src/util/u_queue.c:255 #5 0x7f1d87950b57 in impl_thrd_routine (p=) at ../../../include/c11/threads_posix.h:87 #6 0x7f1e28ad0f2a in start_thread (arg=0x7f1e1d1b1700) at pthread_create.c:463 #7 0x7f1e2b2b9edf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 4 (Thread 0x7f1e0f3fe700 (LWP 2702)): #0 0x7f1e28ad6e6c in futex_wait_cancelable (private=, expected=0, futex_word=0x7f1e298c4fb8 ) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x7f1e298c4f68 , cond=0x7f1e298c4f90 ) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x7f1e298c4f90 , mutex=0x7f1e298c4f68 ) at pthread_cond_wait.c:655 #3 0x7f1e297cde2a in QTWTF::TCMalloc_PageHeap::scavengerThread (this=0x7f1e298b6ec0 ) at ../3rdparty/javascriptcore/JavaScriptCore/wtf/FastMalloc.cpp:2359 #4 0x7f1e297cde49 in QTWTF::TCMalloc_PageHeap::runScavengerThread (context=) at ../3rdparty/javascriptcore/JavaScriptCore/wtf/FastMalloc.cpp:1464 #5 0x7f1e28ad0f2a in start_thread (arg=0x7f1e0f3fe700) at pthread_create.c:463 #6 0x7f1e2b2b9edf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7f1e0700 (LWP 2699)): #0 0x7f1e2b2af836 in __GI_ppoll (fds=fds@entry=0x7f1e08000d28, nfds=nfds@entry=1, timeout=, timeout@entry=0x0, sigmask=sigmask@entry=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:39 #1 0x7f1e29ea1d11 in ppoll (__ss=, __timeout=, __nfds=, __fds=) at /usr/include/x86_64-linux-gnu/bits/poll2.h:77 #2 qt_ppoll (timeout_ts=0x0, nfds=1, fds=0x7f1e08000d28) at kernel/qcore_unix.cpp:132 #3 qt_safe_poll (fds=0x7f1e08000d28, nfds=nfds@entry=1, timeout_ts=timeout_ts@entry=0x0) at kernel/qcore_unix.cpp:153 #4 0x7f1e29ea3189 in QEventDispatcherUNIX::processEvents(QFlags) () at ../../include/QtCore/../../src/corelib/tools/qarraydata.h:209 #5 0x7f1e29e52d0b in QEventLoop::exec(QFlags) () at ../../include/QtCore/../../src/corelib/global/qflags.h:140 #6 0x7f1e29ca20c6 in QThread::exec() () at ../../include/QtCore/../../src/corelib/global/qflags.h:120 #7 0x7f1e28300355 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #8 0x7f1e29cabc97 in QThreadPrivate::start(void*) () at thread/qthread_unix.cpp:367 #9 0x7f1e28ad0f2a in start_thread (arg=0x7f1e0700) at pthread_create.c:463 #10 0x7f1e2b2b9edf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7f1e1e66e700 (LWP 2608)): #0 0x7f1e29c9ee7f in QMutex::unlock (this=this@entry=0x55e6689056b0) at /usr/include/c++/8/bits/atomic_base.h:742 #1 0x7f1e29ea301c in QMutexLocker::unlock (this=) at ../../include/QtCore/../../src/corelib/thread/qmutex.h:240 #2 QMutexLocker::~QMutexLocker (this=, __in_chrg=) at ../../include/QtCore/../../src/corelib/thread/qmutex.h:213 #3 QThreadData::canWaitLocked (this=0x55e668905680) at ../../include/QtCore/5.11.2/QtCore/private/../../../../../src/corelib/thread/qthread_p.h:254 #4 QEventDispatcherUNIX::processEvents(QFlags) () at kernel/qeventdispatcher_unix.cpp:472 #5 0x7f1e29e52d0b in QEventLoop::exec(QFlags) () at ../../include/QtCore/../../src/corelib/global/qflags.h:140 #6 0x7f1e29ca20c6 in QThread::exec() () at ../../include/QtCore/../../src/corelib/global/qflags.h:120 #7 0x7f1e27ddd545 in ?? () from
[frameworks-solid] [Bug 387454] MTP doesn't work in KDE with Linux 4.14
https://bugs.kde.org/show_bug.cgi?id=387454 --- Comment #40 from Marcus Meissner --- i released libmtp 1.1.16 with this fix included in its generated udev rules -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 392500] Session crashes when an external monitor is connected
https://bugs.kde.org/show_bug.cgi?id=392500 Marcus changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #4 from Marcus --- I'm closing this issue as I switched back to plasma and no more shows up in newer versions. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 357991] Unable to rotate video negative amount when not using standard locale for numbers
https://bugs.kde.org/show_bug.cgi?id=357991 Marcus Sundman changed: What|Removed |Added Attachment #115635|0 |1 is obsolete|| --- Comment #10 from Marcus Sundman --- Created attachment 115636 --> https://bugs.kde.org/attachment.cgi?id=115636=edit Negative rotate does NOT work Negative rotation does not work (unless I set LC_NUMERIC to C). This issue most likely won't affect windows, since I think it doesn't have any LC_NUMERIC environment variable at all. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 357991] Unable to rotate video negative amount when not using standard locale for numbers
https://bugs.kde.org/show_bug.cgi?id=357991 --- Comment #8 from Marcus Sundman --- Yes, this problem still exists in 18.08.2. Adding the "Rotate (keyframable)" effect and entering a positive rotation works, but a negative rotation does not work. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-solid] [Bug 387454] MTP doesn't work in KDE with Linux 4.14
https://bugs.kde.org/show_bug.cgi?id=387454 Marcus Meissner changed: What|Removed |Added CC||mar...@jet.franken.de -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 398061] Missing auto-detect button in digiKam
https://bugs.kde.org/show_bug.cgi?id=398061 --- Comment #5 from Marcus Meissner --- i did not do any windows builds for/with libgphoto2/gphoto2, so i cannot help here -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 397564] New: Latte dock shows empty preview of grouped applications
https://bugs.kde.org/show_bug.cgi?id=397564 Bug ID: 397564 Summary: Latte dock shows empty preview of grouped applications Product: latte-dock Version: 0.8.0 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: application Assignee: mvourla...@gmail.com Reporter: marcus.behrendt...@gmail.com Target Milestone: --- Created attachment 114468 --> https://bugs.kde.org/attachment.cgi?id=114468=edit Screenshot As said in the title, latte dock shows no preview when hovering an application icon if more than one instance of that application is running. This occurs on all my machines (Arch Linux). Normal task manager works as expected. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 396341] The "close" tooltip for the window decoration's close button appears at random
https://bugs.kde.org/show_bug.cgi?id=396341 --- Comment #2 from Marcus Harrison --- I don't know what commands you used to get all that information but here's what I could gather: Plasma: 5.13.2 Frameworks: 5.47.0 Qt: 5.11.0 Kernel: 4.13.0-45-generic Video: Intel HD Graphics 520 Kernel driver: i915 Mesa 3D: 18.0.5 Xorg: 1.19.6 Screen: 1920x1080 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 396341] New: The "close" tooltip for the window decoration's close button appears at random
https://bugs.kde.org/show_bug.cgi?id=396341 Bug ID: 396341 Summary: The "close" tooltip for the window decoration's close button appears at random Product: kwin Version: 5.13.2 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: mar...@harrisonland.co.uk Target Milestone: --- The "Close" tooltip used for the window decoration's close button will appear frequently when not hovering over the close button, and when hovering over Qt application widgets which don't have their own tooltip. I can't reproduce this behaviour under X. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 396282] New: Segmentation fault on loading mail in Wayland
https://bugs.kde.org/show_bug.cgi?id=396282 Bug ID: 396282 Summary: Segmentation fault on loading mail in Wayland Product: kmail2 Version: 5.8.2 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: misc Assignee: kdepim-b...@kde.org Reporter: mar...@harrisonland.co.uk Target Milestone: --- On first opening KMail on Wayland, the window and widgets load, then it crashes before the E-mail view widget loads. KDE's crash wizard won't spawn but I've run KMail from gdb to retrieve this backtrace: #0 0x7fffde284e42 in gl::GLSurfaceGLXQt::Initialize(gl::GLSurfaceFormat) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #1 0x7fffde26f0e8 in gl::init::CreateOffscreenGLSurfaceWithFormat(gfx::Size const&, gl::GLSurfaceFormat) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #2 0x7fffe02b5a8d in gl::init::CreateOffscreenGLSurface(gfx::Size const&) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #3 0x7fffe232a927 in gpu::GpuChannelManager::GetDefaultOffscreenSurface() () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7fffe232d8f0 in gpu::GLES2CommandBufferStub::Initialize(gpu::CommandBufferStub*, GPUCreateCommandBufferConfig const&, std::unique_ptr >) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7fffe2328e16 in gpu::GpuChannel::OnCreateCommandBuffer(GPUCreateCommandBufferConfig const&, int, base::SharedMemoryHandle, gpu::ContextResult*, gpu::Capabilities*) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7fffe2326adf in bool IPC::MessageT, std::tuple >::Dispatch(IPC::Message const*, gpu::GpuChannel*, gpu::GpuChannel*, void*, void (gpu::GpuChannel::*)(GPUCreateCommandBufferConfig const&, int, base::SharedMemoryHandle, gpu::ContextResult*, gpu::Capabilities*)) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7fffe2328022 in gpu::GpuChannel::OnControlMessageReceived(IPC::Message const&) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #8 0x7fffe2329bbd in gpu::GpuChannel::HandleMessageHelper(IPC::Message const&) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #9 0x7fffdf7f68d9 in base::debug::TaskAnnotator::RunTask(char const*, base::PendingTask*) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #10 0x7fffdf817da0 in base::MessageLoop::RunTask(base::PendingTask*) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #11 0x7fffdf8187fd in base::MessageLoop::DeferOrRunPendingTask(base::PendingTask) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #12 0x7fffdf818ae7 in base::MessageLoop::DoWork() [clone .part.156] [clone .constprop.178] () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #13 0x7fffdf814679 in base::MessagePumpDefault::Run(base::MessagePump::Delegate*) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #14 0x7fffdf83abcf in base::RunLoop::Run() () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #15 0x7fffdf85c71f in base::Thread::ThreadMain() () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #16 0x7fffdf857d80 in base::(anonymous namespace)::ThreadFunc(void*) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #17 0x7fffea8946ba in start_thread (arg=0x7fff6d7fa700) at pthread_create.c:333 #18 0x74fe841d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 395388] Software Center Discover Crashed
https://bugs.kde.org/show_bug.cgi?id=395388 Marcus Harrison changed: What|Removed |Added CC||mar...@harrisonland.co.uk -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 395388] Software Center Discover Crashed
https://bugs.kde.org/show_bug.cgi?id=395388 --- Comment #4 from Marcus Harrison --- Created attachment 113813 --> https://bugs.kde.org/attachment.cgi?id=113813=edit New crash information added by DrKonqi plasma-discover (5.13.2) using Qt 5.11.0 - What I was doing when the application crashed: Opened Discover from having searched for and selected an application in KRunner. -- Backtrace (Reduced): #8 0x7f4d041cfcfc in qobject_cast (object=) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h:504 #9 QQmlDelegateModelItem::dataForObject (object=object@entry=0x5229de0) at types/qqmldelegatemodel.cpp:1986 #10 0x7f4d041d6de7 in QQmlDelegateModelPrivate::release (this=0x4ee26a0, object=0x5229de0) at types/qqmldelegatemodel.cpp:543 #11 0x7f4d041d6e6d in QQmlDelegateModel::release (this=, item=) at types/qqmldelegatemodel.cpp:567 #12 0x7f4d041caed9 in QQmlInstantiatorPrivate::clear (this=this@entry=0x4edc960) at types/qqmlinstantiator.cpp:83 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 395538] (Version 5.8.1) KMail wizards are missing
https://bugs.kde.org/show_bug.cgi?id=395538 Marcus Harrison changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 395538] (Version 5.8.1) KMail wizards are missing
https://bugs.kde.org/show_bug.cgi?id=395538 --- Comment #2 from Marcus Harrison --- Oh my goodness I've been trying to solve this for such a long time and never found that. Sorry for the noise. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 395538] New: (Version 5.8.1) KMail wizards are missing
https://bugs.kde.org/show_bug.cgi?id=395538 Bug ID: 395538 Summary: (Version 5.8.1) KMail wizards are missing Product: kmail2 Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: misc Assignee: kdepim-b...@kde.org Reporter: mar...@harrisonland.co.uk Target Milestone: --- On KDE Neon, with kdepim-addons installed, the anti-spam/anti-virus wizards do not appear in the Tools menu of KMail. Package status: $ apt-cache policy kdepim-addons spamassassin bogofilter kdepim-addons: Installed: 18.04.1-0neon+16.04+xenial+build39 Candidate: 18.04.1-0neon+16.04+xenial+build39 Version table: *** 18.04.1-0neon+16.04+xenial+build39 500 500 http://archive.neon.kde.org/user xenial/main amd64 Packages 100 /var/lib/dpkg/status 18.04.0-0neon+16.04+xenial+build38 500 500 http://archive.neon.kde.org/user xenial/main amd64 Packages 17.12.3-0neon+16.04+xenial+build36 500 500 http://archive.neon.kde.org/user xenial/main amd64 Packages 17.12.2-0neon+16.04+xenial+build34 500 500 http://archive.neon.kde.org/user xenial/main amd64 Packages spamassassin: Installed: 3.4.1-3 Candidate: 3.4.1-3 Version table: *** 3.4.1-3 500 500 http://es.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 500 http://es.archive.ubuntu.com/ubuntu xenial/main i386 Packages 500 http://gb.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 500 http://gb.archive.ubuntu.com/ubuntu xenial/main i386 Packages 100 /var/lib/dpkg/status bogofilter: Installed: 1.2.4+dfsg1-4build1 Candidate: 1.2.4+dfsg1-4build1 Version table: *** 1.2.4+dfsg1-4build1 500 500 http://es.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages 500 http://es.archive.ubuntu.com/ubuntu xenial/universe i386 Packages 500 http://gb.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages 500 http://gb.archive.ubuntu.com/ubuntu xenial/universe i386 Packages 100 /var/lib/dpkg/status -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 387733] kdevelop crashes on deactivating the activity containing it
https://bugs.kde.org/show_bug.cgi?id=387733 --- Comment #3 from Marcus Harrison --- Created attachment 113397 --> https://bugs.kde.org/attachment.cgi?id=113397=edit New crash information added by DrKonqi kdevelop (5.2.3) using Qt 5.11.0 - What I was doing when the application crashed: Same steps, deactivated an activity that KDevelop was running on and received this crash notification. -- Backtrace (Reduced): #6 QWidget::~QWidget (this=0xf5d180, __in_chrg=) at kernel/qwidget.cpp:1611 #7 0x7fba72e23e79 in QWidget::~QWidget (this=0xf5d180, __in_chrg=) at kernel/qwidget.cpp:1727 #8 0x7fba7204dc00 in QObject::event (this=this@entry=0xf5d180, e=e@entry=0x2766db0) at kernel/qobject.cpp:1242 #9 0x7fba72e28b73 in QWidget::event (this=0xf5d180, event=0x2766db0) at kernel/qwidget.cpp:9343 #10 0x7fba72de929c in QApplicationPrivate::notify_helper (this=, receiver=0xf5d180, e=0x2766db0) at kernel/qapplication.cpp:3713 -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 387733] kdevelop crashes on deactivating the activity containing it
https://bugs.kde.org/show_bug.cgi?id=387733 Marcus Harrison changed: What|Removed |Added CC||mar...@harrisonland.co.uk -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 395305] New: Parser produces errors when keywords are used as function names
https://bugs.kde.org/show_bug.cgi?id=395305 Bug ID: 395305 Summary: Parser produces errors when keywords are used as function names Product: kdevelop Version: 5.2.3 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Language Support: PHP Assignee: kdevelop-bugs-n...@kde.org Reporter: mar...@harrisonland.co.uk Target Milestone: --- In the Laravel PHP framework, some classes[1] use function names that are also type keywords (e.g. public function string(...)). On these files, the parser errors, producing: Expected symbol "identifier" (current token: "string" ...) This causes other features of KDevelop to stop working, including use declarations which use the class, API autocompletion and so on. - [1] https://github.com/laravel/framework/blob/0200dc58ca805e86a366a5779870856b16f8/src/Illuminate/Database/Schema/Blueprint.php#L586 -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 395044] New: Networking system settings module crash on applying new settings when switching to different settings view
https://bugs.kde.org/show_bug.cgi?id=395044 Bug ID: 395044 Summary: Networking system settings module crash on applying new settings when switching to different settings view Product: kde Version: unspecified Platform: unspecified OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: mar...@harrisonland.co.uk Target Milestone: --- Application: kcmshell5 (5.12.5) Qt Version: 5.10.0 Frameworks Version: 5.46.0 Operating System: Linux 4.13.0-43-generic x86_64 Distribution: KDE neon User Edition 5.12 -- Information about the crash: - What I was doing when the application crashed: - Opened the Networking system settings module from the Plasma widget - Made modifications to a network - Clicked to change to a different network - On the pop-up asking to save my changes, I chose to save changes The crash happened before the other network's settings panel displayed and after the dialogue window closed. -- Backtrace: Application: System Settings Module (kcmshell5), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fa4d0f148c0 (LWP 21891))] Thread 3 (Thread 0x7fa4ac405700 (LWP 21897)): #0 0x7fa4d08f027d in read () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fa4c86d76f0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fa4c8693e74 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fa4c8694330 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fa4c869449c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7fa4cdd785db in QEventDispatcherGlib::processEvents (this=0x7fa4a40008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #6 0x7fa4cdd1f65a in QEventLoop::exec (this=this@entry=0x7fa4ac404ce0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #7 0x7fa4cdb3f554 in QThread::exec (this=this@entry=0xb83010) at thread/qthread.cpp:522 #8 0x7fa4cc648a35 in QQmlThreadPrivate::run (this=0xb83010) at qml/ftw/qqmlthread.cpp:147 #9 0x7fa4cdb446eb in QThreadPrivate::start (arg=0xb83010) at thread/qthread_unix.cpp:376 #10 0x7fa4ca5836ba in start_thread (arg=0x7fa4ac405700) at pthread_create.c:333 #11 0x7fa4d090041d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 2 (Thread 0x7fa4b48aa700 (LWP 21893)): #0 0x7fa4d08f027d in read () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fa4c86d76f0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fa4c8693e74 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fa4c8694330 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fa4c869449c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7fa4cdd785db in QEventDispatcherGlib::processEvents (this=0x7fa4b8c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #6 0x7fa4cdd1f65a in QEventLoop::exec (this=this@entry=0x7fa4b48a9cd0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #7 0x7fa4cdb3f554 in QThread::exec (this=) at thread/qthread.cpp:522 #8 0x7fa4ce19b2c5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #9 0x7fa4cdb446eb in QThreadPrivate::start (arg=0x7fa4ce40fd60) at thread/qthread_unix.cpp:376 #10 0x7fa4ca5836ba in start_thread (arg=0x7fa4b48aa700) at pthread_create.c:333 #11 0x7fa4d090041d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 1 (Thread 0x7fa4d0f148c0 (LWP 21891)): [KCrash Handler] #6 0x7fa4cdd4deb2 in QObjectPrivate::isSignalConnected (checkDeclarative=false, signal_index=35, this=) at kernel/qobject_p.h:260 #7 QMetaObject::activate (sender=0x1023c20, signalOffset=, local_signal_index=, argv=argv@entry=0x7fff9cfe4830) at kernel/qobject.cpp:3647 #8 0x7fa4cc59c705 in QQmlVMEMetaObject::activate (this=this@entry=0x106eec0, object=, index=index@entry=52, args=args@entry=0x7fff9cfe4830) at qml/qqmlvmemetaobject.cpp:1243 #9 0x7fa4cc59e9a4 in QQmlVMEMetaObject::metaCall (this=0x106eec0, o=, c=QMetaObject::InvokeMetaMethod, _id=52, a=0x7fff9cfe4830) at qml/qqmlvmemetaobject.cpp:921 #10 0x7fa4cc5fabf9 in QQmlObjectOrGadget::metacall (this=this@entry=0x7fff9cfe4ba0, type=type@entry=QMetaObject::InvokeMetaMethod, index=index@entry=52, argv=) at qml/qqmlpropertycache.cpp:1732 #11 0x7fa4cc5775bd in CallMethod (object=..., index=, returnType=, argCount=, argTypes=, engine=engine@entry=0xa5a320, callArgs=0x7fa4ab3c63b8, callType=QMetaObject::InvokeMetaMethod) at jsruntime/qv4qobjectwrapper.cpp:1158 #12 0x7fa4cc578c8d in CallPrecise (object=..., data=..., engine=engine@entry=0xa5a320, callArgs=callArgs@entry=0x7fa4ab3c63b8,
[systemsettings] [Bug 394578] System settings clicking with the mouse
https://bugs.kde.org/show_bug.cgi?id=394578 --- Comment #2 from Marcus Larborg <m.larb...@protonmail.com> --- Hi Scott I´m not 100% sure, but I think I was in "Application Style" and clicked "Window Decorations". My memory faded when I was following the bug report guide. I will try to reproduce it next time I´m on that computer. Med vänlig hälsning Marcus Larborg Sent with ProtonMail Secure Email. ‐‐‐ Original Message ‐‐‐ On 23 May 2018 1:45 PM, Scott Harvey <bugzilla_nore...@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=394578 > > Scott Harvey sc...@spharvey.me changed: > > What |Removed |Added > > > > > CC||sc...@spharvey.me > > > --- Comment #1 from Scott harveysc...@spharvey.me --- > > Do you remember which settings module you were in when the application > crashed? > > System Settings is a whole bunch of individual modules; there could be a > > problem with a certain one. > > > -- > > You are receiving this mail because: > > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 394578] New: System settings clicking with the mouse
https://bugs.kde.org/show_bug.cgi?id=394578 Bug ID: 394578 Summary: System settings clicking with the mouse Product: systemsettings Version: 5.12.5 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: m.larb...@protonmail.com Target Milestone: --- Application: systemsettings5 (5.12.5) Qt Version: 5.10.0 Frameworks Version: 5.46.0 Operating System: Linux 4.13.0-41-generic x86_64 Distribution: KDE neon User Edition 5.12 -- Information about the crash: - What I was doing when the application crashed: I was clicking around with the mouse, when it suddenly crashed. The crash can be reproduced sometimes. -- Backtrace: Application: Systeminställningar (systemsettings5), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f99e2c56900 (LWP 22927))] Thread 7 (Thread 0x7f99a6e02700 (LWP 23182)): #0 __GI___tls_get_addr (ti=0x7f99df49b690) at dl-tls.c:834 #1 0x7f99dee5f576 in get_thread_data () at thread/qthread_unix.cpp:193 #2 QThreadData::current (createIfNecessary=createIfNecessary@entry=true) at thread/qthread_unix.cpp:248 #3 0x7f99df0944ba in postEventSourcePrepare (s=0x7f99880011b0, timeout=0x7f99a6e01ad4) at kernel/qeventdispatcher_glib.cpp:252 #4 0x7f99d85fe91d in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f99d85ff2bb in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7f99d85ff49c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #7 0x7f99df0945cb in QEventDispatcherGlib::processEvents (this=0x7f99880030e0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #8 0x7f99df03b64a in QEventLoop::exec (this=this@entry=0x7f99a6e01ca0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #9 0x7f99dee5b554 in QThread::exec (this=this@entry=0x354d9f0) at thread/qthread.cpp:522 #10 0x7f99dc995a35 in QQmlThreadPrivate::run (this=0x354d9f0) at qml/ftw/qqmlthread.cpp:147 #11 0x7f99dee606eb in QThreadPrivate::start (arg=0x354d9f0) at thread/qthread_unix.cpp:376 #12 0x7f99dabe66ba in start_thread (arg=0x7f99a6e02700) at pthread_create.c:333 #13 0x7f99de76d41d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 6 (Thread 0x7f99a8605700 (LWP 23181)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f99dee6167b in QWaitConditionPrivate::wait (time=18446744073709551615, this=0x3343810) at thread/qwaitcondition_unix.cpp:143 #2 QWaitCondition::wait (this=this@entry=0x3159c58, mutex=mutex@entry=0x3159c50, time=time@entry=18446744073709551615) at thread/qwaitcondition_unix.cpp:215 #3 0x7f99dce728fd in QSGRenderThreadEventQueue::takeEvent (wait=true, this=0x3159c48) at scenegraph/qsgthreadedrenderloop.cpp:245 #4 QSGRenderThread::processEventsAndWaitForMore (this=this@entry=0x3159bd0) at scenegraph/qsgthreadedrenderloop.cpp:709 #5 0x7f99dce731f5 in QSGRenderThread::run (this=0x3159bd0) at scenegraph/qsgthreadedrenderloop.cpp:738 #6 0x7f99dee606eb in QThreadPrivate::start (arg=0x3159bd0) at thread/qthread_unix.cpp:376 #7 0x7f99dabe66ba in start_thread (arg=0x7f99a8605700) at pthread_create.c:333 #8 0x7f99de76d41d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 5 (Thread 0x7f99a7e04700 (LWP 23179)): #0 0x7f99de76174d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f99d85ff38c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f99d85ff49c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f99df0945cb in QEventDispatcherGlib::processEvents (this=0x7f999018b8f0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f99df03b64a in QEventLoop::exec (this=this@entry=0x7f99a7e03ca0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #5 0x7f99dee5b554 in QThread::exec (this=this@entry=0x31adbb0) at thread/qthread.cpp:522 #6 0x7f99dc995a35 in QQmlThreadPrivate::run (this=0x31adbb0) at qml/ftw/qqmlthread.cpp:147 #7 0x7f99dee606eb in QThreadPrivate::start (arg=0x31adbb0) at thread/qthread_unix.cpp:376 #8 0x7f99dabe66ba in start_thread (arg=0x7f99a7e04700) at pthread_create.c:333 #9 0x7f99de76d41d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 4 (Thread 0x7f99b1343700 (LWP 22933)): #0 0x7f99de76174d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f99d85ff38c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f99d85ff49c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f99df0945cb in QEventDispatcherGlib::processEvents (this=0x7f99ac0008c0, flags=...) at
[telepathy] [Bug 368395] Error: Handler no longer available
https://bugs.kde.org/show_bug.cgi?id=368395 Marcus Harrison <mar...@harrisonland.co.uk> changed: What|Removed |Added CC||mar...@harrisonland.co.uk --- Comment #6 from Marcus Harrison <mar...@harrisonland.co.uk> --- (In reply to Mostafa from comment #5) > (In reply to Mostafa from comment #4) > > I have the same issue with ktp-text-ui 15.12.3 running on KDE Neon and the > > following: > > > > KDE Frameworks 5.37.0 > > Qt 5.9.1 (built against 5.9.1) > > The xcb windowing system > > If I open the contact from KRunner the chat window opens normally. I was about to submit exactly the same bug. KDE Frameworks 5.45.0 Qt 5.10.0 (built against 5.10.0) Chat Application version 15.12.3 -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 272618] Vertical scrollbar makes horizontal scrollbar show at minimum width
https://bugs.kde.org/show_bug.cgi?id=272618 --- Comment #3 from Marcus Harrison <mar...@harrisonland.co.uk> --- Not really? The minimum width is now much smaller, so a horizontal scrollbar appears at minimum width regardless of whether there's enough songs to scroll vertically. This could also vary based on the Playlist Layout selected. Using Amarok 2.8.0. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 385780] Speed Effect is not saved after editing
https://bugs.kde.org/show_bug.cgi?id=385780 --- Comment #9 from Marcus <liquidni...@gmx.net> --- I could go ahead and try testing the new version. 1. I found on the website the page for the new beta version: https://files.kde.org/kdenlive/unstable/kdenlive-18.04-beta2.AppImage.mirrorlist Is that the version you mentioned ? 2. I use gentoo, and there is a kde overlay which provides a Version kdenlive-18.04.49. , see http://gpo.zugaina.org/kde-apps/kdenlive Does this version contain the branch ? If not is it another version on any branch I could install with portage ? 3. If not - where can I read what to do with these AppImage files ? -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 392769] Installation of classic Snaps stops immediately
https://bugs.kde.org/show_bug.cgi?id=392769 --- Comment #3 from Marcus Harrison <mar...@harrisonland.co.uk> --- Sorry, I meant to say that obs-studio installs fine in Discover, and that this only affects classic snaps. I'll test this as soon as I can (I'll try building Discover and, failing that, I'll let you know as soon as a binary version is available for KDE Neon). Thanks. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 392769] New: Installation of classic Snaps stops immediately
https://bugs.kde.org/show_bug.cgi?id=392769 Bug ID: 392769 Summary: Installation of classic Snaps stops immediately Product: Discover Version: 5.12.3 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Snap Backend Assignee: aleix...@kde.org Reporter: mar...@harrisonland.co.uk Target Milestone: --- Discover is able to install Snaps using current confinement but not Snaps using classic confinement. The snaps tested were OBS Studio (current) and Skype (classic/legacy). On the command line, `snap` installs `obs-studio` immediately, while with the `skype` snap it halts to print a warning message about legacy confinement before forcing the user to type the command again with the `--classic` flag. I believe the correct behaviour for Discover should be somewhere between showing a dialogue box that warns the user of the lack of sandboxing with classic snaps, and not showing classic snaps at all. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 392707] New: Enabling Identities / [Identity settings] / Advanced / Attach my vCard to message causes errors in PGP signatures
https://bugs.kde.org/show_bug.cgi?id=392707 Bug ID: 392707 Summary: Enabling Identities / [Identity settings] / Advanced / Attach my vCard to message causes errors in PGP signatures Product: kmail2 Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: crypto Assignee: kdepim-b...@kde.org Reporter: mar...@harrisonland.co.uk Target Milestone: --- When an identity is configured to attach a vCard on sending automatically, the E-mails sent result in invalid signature errors both in KMail and in other E-mail clients (I tested K-9 Mail on Android). Steps to reproduce: 1. Ensure you already have a valid GPG key set up in Kleopatra for signing E-mails with your chosen identity. 2. Set up a vCard for your sending identity. 3. Tick the box to automatically attach that vCard to sent E-mails. 4. Compose a new message to an E-mail address you control. 5. Confirm that the E-mail will be signed and send. Expected result: The message is signed, the signature passes validation and the vCard is attached. Actual result: The message is signed and the cVard is attached but the signature fails validity checks. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 392500] Session crashes when an external monitor is connected
https://bugs.kde.org/show_bug.cgi?id=392500 --- Comment #2 from Marcus <bio...@gmail.com> --- It is on X11 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 392500] New: Session crashes when an external monitor is connected
https://bugs.kde.org/show_bug.cgi?id=392500 Bug ID: 392500 Summary: Session crashes when an external monitor is connected Product: kwin Version: 5.12.4 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: core Assignee: kwin-bugs-n...@kde.org Reporter: bio...@gmail.com Target Milestone: --- This bug happened starting from Plasma 5.12.3 (or maybe .2). I remember perfectly that it worked on the initial version of Plasma 5.12. What happens: With an external monitor the screen will suddently become black and the system will go to the login screen (which is correctly visualized). Now I use the live version of KDE Neon. When I start the system without the external monitor HDMI attached, it correctly loads. As soon as I attach the HDMI the screen becomes black and then loops between the initial white KDE logo on a black background and a total black screen. I use the live distro KDE Neon as downloaded from the website, without any modification. My GPU is: AMD HD 7950, CPU: Intel i5 3570k. The problem is 100% reproducible so I can provide logs if you tell me the command to input in the terminal. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 392154] New: Atadenoise frame count is broken
https://bugs.kde.org/show_bug.cgi?id=392154 Bug ID: 392154 Summary: Atadenoise frame count is broken Product: kdenlive Version: unspecified Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Effects & Transitions Assignee: vpi...@kde.org Reporter: sund...@iki.fi Target Milestone: --- In the Atadenoise filter the av.s frame count parameter can only be 5. If set to anything else the result is not denoised properly. Sometimes the beginning of the video gets included twice. Steps to reproduce: 1. Add the Atadenoise filter to a noisy clip. 2. Set Atadenoise's av.s value to, say, 6. 3. Render. Expected results: 6 frame averaging denoising. Actual results: No denoising. Possibly starting with a duplicate section of the beginning of the clip. Kdenlive: 18.03.70 MLT: 6.7.0 Kubuntu: 18.04 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 387650] unsharp is broken
https://bugs.kde.org/show_bug.cgi?id=387650 --- Comment #4 from Marcus Sundman <sund...@iki.fi> --- The segfault stack dump is using kdenlive 18.03.70 and mlt 6.7.0 where these problems still occurs. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 387650] unsharp is broken
https://bugs.kde.org/show_bug.cgi?id=387650 Marcus Sundman <sund...@iki.fi> changed: What|Removed |Added CC||sund...@iki.fi --- Comment #3 from Marcus Sundman <sund...@iki.fi> --- Created attachment 111534 --> https://bugs.kde.org/attachment.cgi?id=111534=edit segfault stack dump -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 391722] Hqdn3d doesn't work at all
https://bugs.kde.org/show_bug.cgi?id=391722 --- Comment #2 from Marcus Sundman <sund...@iki.fi> --- Same problem with kdenlive 18.03.70 and mlt 6.7.0. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 391722] Hqdn3d doesn't work at all
https://bugs.kde.org/show_bug.cgi?id=391722 --- Comment #1 from Marcus Sundman <sund...@iki.fi> --- I also tried adjusting the values directly in the .kdenlive project file, but upon reloading it into kdenlive the values were still just 0s. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 391722] New: Hqdn3d doesn't work at all
https://bugs.kde.org/show_bug.cgi?id=391722 Bug ID: 391722 Summary: Hqdn3d doesn't work at all Product: kdenlive Version: unspecified Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Effects & Transitions Assignee: vpi...@kde.org Reporter: sund...@iki.fi Target Milestone: --- The Hqdn3d doesn't work at all. Steps to reproduce: 1. Add the Hqdn3d filter to a video. 2. Try to adjust some values. Actual results: All values will stay at 0. Expected results: The values should be adjustable. Version: - kdenlive 17.12.2 from the kdenlive ppa - mlt 6.5.0 - running on kubuntu 17.10 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 391722] Hqdn3d doesn't work at all
https://bugs.kde.org/show_bug.cgi?id=391722 Marcus Sundman <sund...@iki.fi> changed: What|Removed |Added CC||sund...@iki.fi -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 390648] New: Snap packages always appear as installed
https://bugs.kde.org/show_bug.cgi?id=390648 Bug ID: 390648 Summary: Snap packages always appear as installed Product: Discover Version: 5.12.1 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Snap Backend Assignee: aleix...@kde.org Reporter: mar...@harrisonland.co.uk Target Milestone: --- On KDE Neon with the Snap backend installed, packages available as Snaps always appear as installed, even when they are not installed. They show the options to Remove the package from the listing view, or from the description view, the option to Remove or Open. The Open button does nothing. The Remove button prompts for authentication, then shows the error, "snap [package-name] is not installed". -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 390115] On wayland, keyboard input that causes Firefox focus passes key presses to Firefox
https://bugs.kde.org/show_bug.cgi?id=390115 --- Comment #4 from Marcus Harrison <mar...@harrisonland.co.uk> --- Here's the output, hopefully it helps. Cheers. KWin-Unterstützungsinformationen: Benutzen Sie die folgenden Informationen, wenn Sie nach Unterstützung fragen, z. B. auf http://forum.kde.org. Sie enthalten Informationen über die momentan laufende Instanz, welche Optionen verwendet werden, welcher OpenGL-Treiber verwendet wird und welche Effekte laufen. Bitte geben Sie die unten stehenden Informationen bei einem Pastebin-Dienst wie http://paste.kde.org ein, anstatt sie direkt in die Hilfediskussionen zu schreiben. == Version === KWin version: 5.12.0 Qt Version: 5.9.3 Qt compile version: 5.9.3 XCB compile version: 1.11.1 Operation Mode: Xwayland Build Options = KWIN_BUILD_DECORATIONS: yes KWIN_BUILD_TABBOX: yes KWIN_BUILD_ACTIVITIES: yes HAVE_INPUT: yes HAVE_DRM: yes HAVE_GBM: yes HAVE_X11_XCB: yes HAVE_EPOXY_GLX: yes HAVE_WAYLAND_EGL: yes X11 === Vendor: The X.Org Foundation Vendor Release: 11804000 Protocol Version/Revision: 11/0 SHAPE: yes; Version: 0x11 RANDR: yes; Version: 0x14 DAMAGE: yes; Version: 0x11 Composite: yes; Version: 0x4 RENDER: yes; Version: 0xb XFIXES: yes; Version: 0x50 SYNC: yes; Version: 0x31 GLX: yes; Version: 0x0 Decoration == Plugin: org.kde.breeze Theme: Blur: 0 onAllDesktopsAvailable: false alphaChannelSupported: true closeOnDoubleClickOnMenu: false decorationButtonsLeft: 5, 3, 4 decorationButtonsRight: borderSize: 0 gridUnit: 12 font: Oxygen-Sans,11,-1,5,50,0,0,0,0,0,Sans-Book smallSpacing: 3 largeSpacing: 12 Platform == Name: DRM Active: true Atomic Mode Setting: true Options === focusPolicy: 0 nextFocusPrefersMouse: false clickRaise: true autoRaise: false autoRaiseInterval: 0 delayFocusInterval: 0 shadeHover: false shadeHoverInterval: 250 separateScreenFocus: false placement: 4 focusPolicyIsReasonable: true borderSnapZone: 10 windowSnapZone: 10 centerSnapZone: 0 snapOnlyWhenOverlapping: false rollOverDesktops: true focusStealingPreventionLevel: 1 legacyFullscreenSupport: false operationTitlebarDblClick: 5000 operationMaxButtonLeftClick: 5000 operationMaxButtonMiddleClick: 5015 operationMaxButtonRightClick: 5014 commandActiveTitlebar1: 0 commandActiveTitlebar2: 30 commandActiveTitlebar3: 2 commandInactiveTitlebar1: 4 commandInactiveTitlebar2: 30 commandInactiveTitlebar3: 2 commandWindow1: 7 commandWindow2: 8 commandWindow3: 8 commandWindowWheel: 31 commandAll1: 10 commandAll2: 3 commandAll3: 14 keyCmdAllModKey: 16777251 showGeometryTip: false condensedTitle: false electricBorderMaximize: true electricBorderTiling: true electricBorderCornerRatio: 0.25 borderlessMaximizedWindows: false killPingTimeout: 5000 hideUtilityWindowsForInactive: true inactiveTabsSkipTaskbar: false autogroupSimilarWindows: false autogroupInForeground: true compositingMode: 1 useCompositing: true compositingInitialized: true hiddenPreviews: 1 glSmoothScale: 0 xrenderSmoothScale: false maxFpsInterval: 1666 refreshRate: 0 vBlankTime: 600 glStrictBinding: false glStrictBindingFollowsDriver: true glCoreProfile: true glPreferBufferSwap: 101 glPlatformInterface: 2 windowsBlockCompositing: true Screen Edges desktopSwitching: false desktopSwitchingMovingClients: false cursorPushBackDistance: 1x1 timeThreshold: 0 reActivateThreshold: 350 actionTopLeft: 0 actionTop: 0 actionTopRight: 0 actionRight: 0 actionBottomRight: 0 actionBottom: 0 actionBottomLeft: 0 actionLeft: 0 Screens === Multi-Head: no Active screen follows mouse: no Number of Screens: 1 Screen 0: - Name: MEI eDP-1-VVX13F009G10 Geometry: 0,0,1920x1080 Scale: 1 Refresh Rate: 60.011 Compositing === Compositing is active Compositing Type: OpenGL OpenGL vendor string: Intel Open Source Technology Center OpenGL renderer string: Mesa DRI Intel(R) HD Graphics 520 (Skylake GT2) OpenGL version string: 4.5 (Core Profile) Mesa 17.2.4 OpenGL platform interface: EGL OpenGL shading language version string: 4.50 Driver: Intel GPU class: Unknown OpenGL version: 4.5 GLSL version: 4.50 Mesa version: 17.2.4 Linux kernel version: 4.13 Direct rendering: Requires strict binding: no GLSL shaders: yes Texture NPOT support: yes Virtual Machine: no OpenGL 2 Shaders are used Painting blocks for vertical retrace: no Loaded Effects: --- zoom kwin4_effect_logout kwin4_effect_windowaperture kwin4_effect_dialogparent kwin4_effect_translucency kwin4_effect_login kwin4_effect_morphingpopups kwin4_effect_frozenapp kwin4_effect_fade slidingpopups slideback slide screenshot minimizeanimation desktopgrid colorpicker presentwindows highlightwindow blur contrast startupfeedback screenedge kscreen Currently Active Effects: - blur contrast Effect Settings: zoom: zoomFactor: 1.2 mousePointer: 0 mouseTracking: 0 enableFocusTracking: false followFocus: true focusDelay: 350 moveFactor: 20 targetZ
[kwin] [Bug 390115] On wayland, keyboard input that causes Firefox focus passes key presses to Firefox
https://bugs.kde.org/show_bug.cgi?id=390115 --- Comment #2 from Marcus Harrison <mar...@harrisonland.co.uk> --- Sorry, how would I go about finding the version number? Thanks. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 390115] New: On wayland, keyboard input that causes Firefox focus passes key presses to Firefox
https://bugs.kde.org/show_bug.cgi?id=390115 Bug ID: 390115 Summary: On wayland, keyboard input that causes Firefox focus passes key presses to Firefox Product: kwin Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: mar...@harrisonland.co.uk Target Milestone: --- Sorry for the poorly-worded summary. This only appears when running plasma-wayland. If a keyboard press causes a previously-focused window to become unfocused, and makes Firefox the newly-focused window, the key-press is passed to Firefox as a duplicate. To reproduce: Example 1 1. Make Firefox the selected window. Focus a textarea HTML widget. 2. Open plasma's default Application Launcher. 3. Hit "Enter" to open any selected item. Expected behaviour: No key press is passed to Firefox and the selected item is opened. Actual behaviour: The "Enter" keypress is passed to Firefox, creating a newline in the text area. If Firefox has a HTML anchor element selected, it is activated, potentially switching pages. Forms can be unintentionally submitted, etc. Example 2 1. Make Firefox the focused window. 2. Open a new application window, e.g. Kwrite or Konsole. 3. Use Alt+F4 to close the new window and make Firefox the focused window again. Expected behaviour: No key press is passed to Firefox and the previously-opened window is closed. Actual behaviour: The window is closed and the Firefox application menu (file, edit etc.) is focused. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 390115] On wayland, keyboard input that causes Firefox focus passes key presses to Firefox
https://bugs.kde.org/show_bug.cgi?id=390115 Marcus Harrison <mar...@harrisonland.co.uk> changed: What|Removed |Added Platform|Other |Neon Packages Version|unspecified |5.12.0 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 389001] plasma-discover crashes after installing flatpak backend
https://bugs.kde.org/show_bug.cgi?id=389001 Marcus Harrison <mar...@harrisonland.co.uk> changed: What|Removed |Added CC||mar...@harrisonland.co.uk --- Comment #3 from Marcus Harrison <mar...@harrisonland.co.uk> --- Hello, I just ran into the same issue with the same solution. Is the plasma-discover upgrade path broken somehow? I've been upgrading my packages pretty blindly when they become available. Cheers. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 385780] Speed Effect is not saved after editing
https://bugs.kde.org/show_bug.cgi?id=385780 --- Comment #7 from Marcus <liquidni...@gmx.net> --- The bug is also inkde-apps/kdenlive- , from the "kde" overlay, used in gentoo.This version of the ebuild downloads the most recent source and installs it. If the developers fix this bug, I could test it using the kde overlay again. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 385780] Speed Effect is not saved after editing
https://bugs.kde.org/show_bug.cgi?id=385780 --- Comment #6 from Marcus <liquidni...@gmx.net> --- I see on Linux mint, which uses kdenlive-15.12.3, that this bug is already in that old version. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 385780] Speed Effect is not saved after editing
https://bugs.kde.org/show_bug.cgi?id=385780 --- Comment #5 from Marcus <liquidni...@gmx.net> --- As I just tested, that version of kdenlive is affected by this bug: kde-apps/kdenlive-17.08.3 == gentoo-stable@2018-02-04 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 385780] Speed Effect is not saved after editing
https://bugs.kde.org/show_bug.cgi?id=385780 --- Comment #4 from Marcus <liquidni...@gmx.net> --- I found steps to reproduce it: 1. create new project 2. add ONE video clip into bin 3. add a color clip 4. place the video clip into time line 5. put the color clip behind the video clip 6. add speed effect to video clip, set it to 200% 7. replay the clip section, check the double speed. 8. save project 9. do a GROUP MOVE of both clips, to the right (also to left) 10. check the replay, speed is gone ! 11. Save, reopen - the speed effect on the clip is gone ! -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 385542] Clips with Speed effect reset when moved back with other clips
https://bugs.kde.org/show_bug.cgi?id=385542 Marcus <liquidni...@gmx.net> changed: What|Removed |Added CC||liquidni...@gmx.net --- Comment #1 from Marcus <liquidni...@gmx.net> --- Might be similar to bug 385780 - I am affected by this bug, too. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 385780] Speed Effect is not saved after editing
https://bugs.kde.org/show_bug.cgi?id=385780 --- Comment #3 from Marcus <liquidni...@gmx.net> --- This might be similiar to bug 385542 . Additional issue 1: When you copy a speed effect from one clip to another, the program forgets it. Additional issue 2: When you copy a color rotation effect from lane1 (with setting) to lane2, the program forgets the setting at lane2. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 385780] Speed Effect is not saved after editing
https://bugs.kde.org/show_bug.cgi?id=385780 Marcus <liquidni...@gmx.net> changed: What|Removed |Added CC||liquidni...@gmx.net --- Comment #2 from Marcus <liquidni...@gmx.net> --- I see a similar issue on Gentoo64bit, media-libs/mlt-6.4.1-r6 kde-apps/kdenlive-17.12.1 Here I have a project with about 400 video files, about 500 time clips and >100 Speed settings. SOME operations like shifting clips in the time line , or lane-shifting, or something else kills lots of speed settings previously applied to lots of clips in the time line. I see me adding speed effects the 4th time over and over to the same clips :-( -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kdewebkit] [Bug 389053] New: Graphical glitches with Webkit renderers on Wayland
https://bugs.kde.org/show_bug.cgi?id=389053 Bug ID: 389053 Summary: Graphical glitches with Webkit renderers on Wayland Product: frameworks-kdewebkit Version: 5.42.0 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kdelibs-b...@kde.org Reporter: mar...@harrisonland.co.uk Target Milestone: --- This applies to the E-mail view in Kontact, the new System Settings layout and the Discover view. Sorry if this bug is mis-filed. When using these applications on Wayland using the KDE Slimbook, they will often distort the display outside of the application. This includes drawing the application view outside of the application's window or drawing it on top of applications that overlap them in the window manager. This does not affect Xorg sessions. When those applications listed above are closed, the distortion ends. I am using mesa on intel graphics and this happens every time. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 388142] digikam crash when clicing on map tool
https://bugs.kde.org/show_bug.cgi?id=388142 --- Comment #7 from Marcus Gama <marcus.g...@gmail.com> --- About the GDB, this is what I got: Thread 1 "digikam" received signal SIGSEGV, Segmentation fault. 0x7fffee951baa in Marble::GeoSceneLayer::backend() const () from /usr/lib64/libmarblewidget-qt5.so.27 I made some tests and I figured out what happened. The problem was the other repo. According the backtrace above, the digikam was compiled with the libmarblewidget-qt5.so.27, provided by KDE Apps 17.04. The new repo provides KDE Apps 17.12, with libmarblewidget-qt5.so.28. This broke the system. I removed the new Marble and installed the old one and the problem was solved. Maik, thank you for your help. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 388142] digikam crash when clicing on map tool
https://bugs.kde.org/show_bug.cgi?id=388142 --- Comment #5 from Marcus Gama <marcus.g...@gmail.com> --- This is my components info (in Portuguese): digikam version 5.7.0 CPU cores: 8 Eigen: 3.2.9 Exiv2: 0.26 Exiv2 can write to Jp2: Sim Exiv2 can write to Jpeg: Sim Exiv2 can write to Pgf: Sim Exiv2 can write to Png: Sim Exiv2 can write to Tiff: Sim Exiv2 supports XMP metadata: Sim KF5: 5.32.0 LensFun: 0.3.2-0 LibCImg: 130 LibJPEG: 80 LibJasper: 1.900.14 LibLCMS: 2080 LibLqr support: Sim LibPGF: 7.15.32 LibPNG: 1.6.8 LibRaw: 0.18.2 LibTIFF: 4.0.8 Marble: 0.27.1 Parallelized demosaicing: Sim Qt: 5.10.0 Infraestrutura do banco de dados: QSQLITE LibGphoto2: 2.5.13 LibKipi: 5.2.0 LibOpenCV: 3.3.1 LibQtAV: 1.12.0 Plugins do Kipi: 5.7.0 Suporte ao AkonadiContact: Sim Suporte ao Baloo: Sim Suporte ao calendário: sim Suporte para galerias HTML: sim Suporte para leitores multimédia: Sim Suporte para o D-Bus: Sim Suporte à panorâmica: sim I'm not sure if this issue can be result of the other repository mentioned (http://download.opensuse.org/repositories/KDE:/Applications/KDE_Frameworks5_openSUSE_Leap_42.3/). This repository installed the latest Kde applications (17.12). The Marble works fine (stand alone at least). I already tried to remove the digikamrc but the crash persists. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 388142] digikam crash when clicing on map tool
https://bugs.kde.org/show_bug.cgi?id=388142 --- Comment #3 from Marcus Gama <marcus.g...@gmail.com> --- Sorry, the right repo for digikam 5.7 is: http://download.opensuse.org/repositories/KDE:/Extra/openSUSE_Leap_42.3/ -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 388142] digikam crash when clicing on map tool
https://bugs.kde.org/show_bug.cgi?id=388142 --- Comment #2 from Marcus Gama <marcus.g...@gmail.com> --- I updated to digikam 5.7 using the repository: http://download.opensuse.org/repositories/KDE:/Applications/KDE_Frameworks5_openSUSE_Leap_42.3/ I'm using the Marble 2.2.20 (KDE version) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 388142] New: digikam crash when clicing on map tool
https://bugs.kde.org/show_bug.cgi?id=388142 Bug ID: 388142 Summary: digikam crash when clicing on map tool Product: digikam Version: 5.7.0 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: Geolocation Assignee: digikam-bugs-n...@kde.org Reporter: marcus.g...@gmail.com Target Milestone: --- I'm using openSUSE 42.3 with digikam 5.7. Any time I click on map tool, digikam crash. I installed debug package but, for unknown reason, I cannot generate a useful backtrace. The only content that I got is: Application: digiKam (digikam), signal: Segmentation fault >From drkonqi: pa_write() failed while trying to wake up the mainloop: Descritor de arquivo inválido Invalid write to eventfd: Descritor de arquivo inválido Code should not be reached at pulsecore/fdsem.c:199, function pa_fdsem_post(). Aborting. KCrash: Application 'digikam' crashing... KCrash: Attempting to start /usr/lib64/libexec/drkonqi from kdeinit sock_file=/run/user/1000/kdeinit5__0 Unable to start Dr. Konqi Re-raising signal for core dump handling. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 387650] unsharp is broken
https://bugs.kde.org/show_bug.cgi?id=387650 --- Comment #1 from Marcus Sundman <sund...@iki.fi> --- When it crashes it writes this to the console: [filt @ 0x7faea3a2cb40] luma or chroma matrix size too big [filter avfilter.unsharp] Cannot init filter: Invalid argument Segmentation fault -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 387650] New: unsharp is broken
https://bugs.kde.org/show_bug.cgi?id=387650 Bug ID: 387650 Summary: unsharp is broken Product: kdenlive Version: 17.08.2 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: Effects & Transitions Assignee: vpi...@kde.org Reporter: sund...@iki.fi Target Milestone: --- The unsharp filter is completely broken. First of all, there are 2 of all parameters (e.g., av.luma_msize_x AND av.lx). Second, if you try to set av.lx big (like 17) the whole program crashes. Third, often the effect won't show up in the project monitor until you tweak them back and forth a few times. Fourth, the effect won't get applied during render, not even if it shows up in the project monitor. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 387451] KWin crash on using default window-switcher
https://bugs.kde.org/show_bug.cgi?id=387451 Marcus Harrison <mar...@harrisonland.co.uk> changed: What|Removed |Added Resolution|UPSTREAM|FIXED --- Comment #2 from Marcus Harrison <mar...@harrisonland.co.uk> --- Thanks. Where would I go about that? Simply searching results in hits for submitting Catalyst/DirectX/Windows bugs... -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 387451] New: KWin crash on using default window-switcher
https://bugs.kde.org/show_bug.cgi?id=387451 Bug ID: 387451 Summary: KWin crash on using default window-switcher Product: kwin Version: unspecified Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: tabbox Assignee: kwin-bugs-n...@kde.org Reporter: mar...@harrisonland.co.uk Target Milestone: --- Application: kwin_x11 (5.10.5) Qt Version: 5.9.1 Frameworks Version: 5.38.0 Operating System: Linux 4.13.0-17-generic x86_64 Distribution: Ubuntu 17.10 -- Information about the crash: - What I was doing when the application crashed: Alt-tabbing through windows when compositing effects are enabled. The crash can be reproduced sometimes. -- Backtrace: Application: KWin (kwin_x11), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f37f0a02980 (LWP 10676))] Thread 15 (Thread 0x7f3705066700 (LWP 10717)): #0 0x7f37e95b0072 in futex_wait_cancelable (private=, expected=0, futex_word=0x558c4d8c13dc) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7f37e95b0072 in __pthread_cond_wait_common (abstime=0x0, mutex=0x558c4d8c1388, cond=0x558c4d8c13b0) at pthread_cond_wait.c:502 #2 0x7f37e95b0072 in __pthread_cond_wait (cond=0x558c4d8c13b0, mutex=0x558c4d8c1388) at pthread_cond_wait.c:655 #3 0x7f37cca75b8b in () at /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #4 0x7f37cca75aa7 in () at /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #5 0x7f37e95a97fc in start_thread (arg=0x7f3705066700) at pthread_create.c:465 #6 0x7f37f038bb0f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 14 (Thread 0x7f3707fff700 (LWP 10716)): #0 0x7f37f037f9fb in __GI_ppoll (fds=0x7f378800c098, nfds=1, timeout=, sigmask=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:39 #1 0x7f37ed98e151 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7f37ed98f86e in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7f37ed937e3a in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f37ed7573ca in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f37ed75c29d in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f37e95a97fc in start_thread (arg=0x7f3707fff700) at pthread_create.c:465 #7 0x7f37f038bb0f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 13 (Thread 0x7f37961a2700 (LWP 10702)): #0 0x7f37e95b0072 in futex_wait_cancelable (private=, expected=0, futex_word=0x558c4db3fab8) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7f37e95b0072 in __pthread_cond_wait_common (abstime=0x0, mutex=0x558c4db3fa68, cond=0x558c4db3fa90) at pthread_cond_wait.c:502 #2 0x7f37e95b0072 in __pthread_cond_wait (cond=0x558c4db3fa90, mutex=0x558c4db3fa68) at pthread_cond_wait.c:655 #3 0x7f37cca75b8b in () at /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #4 0x7f37cca75aa7 in () at /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #5 0x7f37e95a97fc in start_thread (arg=0x7f37961a2700) at pthread_create.c:465 #6 0x7f37f038bb0f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 12 (Thread 0x7f37959a1700 (LWP 10691)): #0 0x7f37e95b0072 in futex_wait_cancelable (private=, expected=0, futex_word=0x7f37ecbd1fb8) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7f37e95b0072 in __pthread_cond_wait_common (abstime=0x0, mutex=0x7f37ecbd1f68, cond=0x7f37ecbd1f90) at pthread_cond_wait.c:502 #2 0x7f37e95b0072 in __pthread_cond_wait (cond=0x7f37ecbd1f90, mutex=0x7f37ecbd1f68) at pthread_cond_wait.c:655 #3 0x7f37ec8ddbd4 in () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #4 0x7f37ec8ddc19 in () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #5 0x7f37e95a97fc in start_thread (arg=0x7f37959a1700) at pthread_create.c:465 #6 0x7f37f038bb0f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 11 (Thread 0x7f379f5ef700 (LWP 10687)): #0 0x7f37f037f9fb in __GI_ppoll (fds=0x7f3798000d18, nfds=1, timeout=, sigmask=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:39 #1 0x7f37ed98e151 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7f37ed98f86e in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7f37ed937e3a in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f37ed7573ca in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f37e80b0f45 in () at /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #6 0x7f37ed75c29d in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f37e95a97fc in
[amarok] [Bug 387309] New: Amarok fails to copy tracks to a removable drive collection
https://bugs.kde.org/show_bug.cgi?id=387309 Bug ID: 387309 Summary: Amarok fails to copy tracks to a removable drive collection Product: amarok Version: 2.8.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Collections/USB mass storage and MSC Assignee: amarok-bugs-d...@kde.org Reporter: mar...@harrisonland.co.uk CC: bart.cerne...@kde.org Target Milestone: 2.9 On KDE Neon, an unlabelled FAT32 USB stick is mounted in a directory formatted as /media/[user]/neon user [mmdd]-[hh]:[mm]/ where the date is shown as an 8 digit number and the time is shown as a colon-separated number. It is picked up by Amarok. Attempting to use the "Copy/Move to Collection" functions to copy music from my local collection to the removable drive collection brings up the dialogue asking if I would like to copy unmodified, or transcode. Selecting either option closes the dialogue without copying the tracks and no progress is shown in the progress meter at the bottom of the collections window. Changing the label on the fat32 partition to an alphanumerical value caused it to be mounted in /media/[username]/[alphanumerical value]/, after which using the "Copy/Move to Collection" functions worked correctly. -- You are receiving this mail because: You are watching all bug changes.
[kipiplugins] [Bug 385315] kipiplugins sendimage not available in digikam and gwenview
https://bugs.kde.org/show_bug.cgi?id=385315 Marcus <wellend...@posteo.de> changed: What|Removed |Added Version|5.8.0 |5.7.0 -- You are receiving this mail because: You are watching all bug changes.
[kipiplugins] [Bug 385315] New: kipiplugins sendimage not available in digikam and gwenview
https://bugs.kde.org/show_bug.cgi?id=385315 Bug ID: 385315 Summary: kipiplugins sendimage not available in digikam and gwenview Product: kipiplugins Version: 5.8.0 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: imaging-bugs-n...@kde.org Reporter: wellend...@posteo.de Target Milestone: --- I am using Manjaro stable with installed digikam and kipiplugins both version 5.7.0-1 libkipi 5.2.0 (17.08.1) and gwenview 17.08.1 KDE Frameworks 5.38.0 Qt 5.9.1 (compiled with 5.9.1) In Digikam and Gwenview I cant find the sendimage plugin to send an email attached picture anymore. There is no entry in the menues or context menues. I remember in Digikam it was in the tools menu before, in earlier versions in the export menu of the menubar, but neither there nor in the context menu is any entry for it. All other menues I looked through and didn't find anything related. In Digikam settings > plugins there is no email or sendimage plugin listed, like I saw before. There are 15 other plugins listed, I have only one choosen which appears in the menubar Then I opened Gwenview, not sure if there was a menue entry for sending pictures with email before. However, I don't find one now. I checked which files got installed with the kipi plugins in the /usr folder: kipiplugin_sendimages.desktop kipiplugin_sendimages.so kipiplugin_sendimagesui.rc plus a lot of kipiplugin_sendimages.mo files. Shouldn't be there an entry for using the plugin? Thank you for your attention! -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 381743] cpfind doesn.t work: couldn't parse panos tool script: 'pano_base.pto
https://bugs.kde.org/show_bug.cgi?id=381743 --- Comment #14 from Marcus <wellend...@posteo.de> --- Sorry, that was on Manjaro, I don't know about Arch. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 381743] cpfind doesn.t work: couldn't parse panos tool script: 'pano_base.pto
https://bugs.kde.org/show_bug.cgi?id=381743 --- Comment #13 from Marcus <wellend...@posteo.de> --- Just to confirm: After an update to 5.7.0 on Arch the autooptimizer detection is working. Thank you! -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 383959] New: memory leak when connecting to chip
https://bugs.kde.org/show_bug.cgi?id=383959 Bug ID: 383959 Summary: memory leak when connecting to chip Product: plasma-nm Version: 5.10.4 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: applet Assignee: jgrul...@redhat.com Reporter: furlo...@gmail.com Target Milestone: --- When connecting a chip board via USB (similar to RaspPI -> https://getchip.com/), plasma-nm continues to try connecting to it, and gets stuck on acquiring network address. It never gets a network address (and I don't want it to, I just want to power it, or e.g. flash it) , however the plasma-nm applet becomes non-responsive. In this case, plasmashell is consuming all the memory and eventually all the swap on the machine, and eventually plasmashell gets killed by the OOM. Each time I plug in one of these devices it shows up as a new wired connection, so I cannot get plasma-nm to remember the device settings and disable the connection. The USB dmesg output is as follows: [121719.097187] usb 3-7.2: new high-speed USB device number 13 using xhci_hcd [121719.185904] usb 3-7.2: New USB device found, idVendor=0525, idProduct=a4aa [121719.185907] usb 3-7.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [121719.185907] usb 3-7.2: Product: CDC Composite Gadget [121719.185908] usb 3-7.2: Manufacturer: Linux 4.4.13-ntc-mlc with musb-hdrc [121719.196430] cdc_ether 3-7.2:1.0 usb0: register 'cdc_ether' at usb-:00:14.0-7.2, CDC Ethernet Device, fa:f6:32:41:11:a5 [121719.196731] cdc_acm 3-7.2:1.2: ttyACM0: USB ACM device -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 383826] New: akregator chrashes on opening first feed on first startup
https://bugs.kde.org/show_bug.cgi?id=383826 Bug ID: 383826 Summary: akregator chrashes on opening first feed on first startup Product: akregator Version: 5.5.3 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: mar...@jet.franken.de Target Milestone: --- Application: akregator (5.5.3) Qt Version: 5.9.1 Frameworks Version: 5.36.0 Operating System: Linux 4.12.7-1-default x86_64 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: After freshly booting, opening Akregator and then selecting the first feed will crash akregator immediately. Starting it a second will make it work, but then the feeds are not fetching. The crash can be reproduced every time. -- Backtrace: Application: Akregator (akregator), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f0f1e9e2e00 (LWP 2576))] Thread 22 (Thread 0x7f0ee5732700 (LWP 4185)): #0 0x7f0f14d8c90c in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f0f0a4ee7b2 in base::ConditionVariable::TimedWait(base::TimeDelta const&) () from /usr/lib64/libQt5WebEngineCore.so.5 #2 0x7f0f0a4c49c9 in base::PosixDynamicThreadPool::WaitForTask() () from /usr/lib64/libQt5WebEngineCore.so.5 #3 0x7f0f0a4c4f2b in base::(anonymous namespace)::WorkerThread::ThreadMain() () from /usr/lib64/libQt5WebEngineCore.so.5 #4 0x7f0f0a4bd80b in base::(anonymous namespace)::ThreadFunc(void*) () from /usr/lib64/libQt5WebEngineCore.so.5 #5 0x7f0f14d864d7 in start_thread () from /lib64/libpthread.so.0 #6 0x7f0f1a853b2f in clone () from /lib64/libc.so.6 Thread 21 (Thread 0x7f0ec7546700 (LWP 3031)): #0 0x7f0f14d8c5dd in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f0f076f88e4 in ?? () from /usr/lib64/libQt5Script.so.5 #2 0x7f0f076f8929 in ?? () from /usr/lib64/libQt5Script.so.5 #3 0x7f0f14d864d7 in start_thread () from /lib64/libpthread.so.0 #4 0x7f0f1a853b2f in clone () from /lib64/libc.so.6 Thread 20 (Thread 0x7f0ec86c3700 (LWP 3009)): #0 0x7f0f14d8c5dd in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f0f0a4bfec5 in base::SequencedWorkerPool::Inner::ThreadLoop(base::SequencedWorkerPool::Worker*) () from /usr/lib64/libQt5WebEngineCore.so.5 #2 0x7f0f0a4c03a7 in base::SequencedWorkerPool::Worker::Run() () from /usr/lib64/libQt5WebEngineCore.so.5 #3 0x7f0f0a4c1141 in base::SimpleThread::ThreadMain() () from /usr/lib64/libQt5WebEngineCore.so.5 #4 0x7f0f0a4bd80b in base::(anonymous namespace)::ThreadFunc(void*) () from /usr/lib64/libQt5WebEngineCore.so.5 #5 0x7f0f14d864d7 in start_thread () from /lib64/libpthread.so.0 #6 0x7f0f1a853b2f in clone () from /lib64/libc.so.6 Thread 19 (Thread 0x7f0ece28f700 (LWP 3008)): #0 0x7f0f1a84a18d in poll () from /lib64/libc.so.6 #1 0x7f0f12f78d19 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f0f12f78e2c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7f0f1b1686ab in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #4 0x7f0f1b11135a in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #5 0x7f0f1af4131a in QThread::exec() () from /usr/lib64/libQt5Core.so.5 #6 0x7f0f1af45d2e in ?? () from /usr/lib64/libQt5Core.so.5 #7 0x7f0f14d864d7 in start_thread () from /lib64/libpthread.so.0 #8 0x7f0f1a853b2f in clone () from /lib64/libc.so.6 Thread 18 (Thread 0x7f0ecf726700 (LWP 2984)): #0 0x7f0f14d8c5dd in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f0f0a4bfec5 in base::SequencedWorkerPool::Inner::ThreadLoop(base::SequencedWorkerPool::Worker*) () from /usr/lib64/libQt5WebEngineCore.so.5 #2 0x7f0f0a4c03a7 in base::SequencedWorkerPool::Worker::Run() () from /usr/lib64/libQt5WebEngineCore.so.5 #3 0x7f0f0a4c1141 in base::SimpleThread::ThreadMain() () from /usr/lib64/libQt5WebEngineCore.so.5 #4 0x7f0f0a4bd80b in base::(anonymous namespace)::ThreadFunc(void*) () from /usr/lib64/libQt5WebEngineCore.so.5 #5 0x7f0f14d864d7 in start_thread () from /lib64/libpthread.so.0 #6 0x7f0f1a853b2f in clone () from /lib64/libc.so.6 Thread 17 (Thread 0x7f0edff27700 (LWP 2983)): #0 0x7f0f1a84a18d in poll () from /lib64/libc.so.6 #1 0x7f0f040a0881 in ?? () from /usr/lib64/libpulse.so.0 #2 0x7f0f04092240 in pa_mainloop_poll () from /usr/lib64/libpulse.so.0 #3 0x7f0f040928d0 in pa_mainloop_iterate () from /usr/lib64/libpulse.so.0 #4 0x7f0f04092960 in pa_mainloop_run () from /usr/lib64/libpulse.so.0 #5 0x7f0f040a07c9 in ?? () from
[Akonadi] [Bug 338658] GMail, Novell Groupwise, other IMAP: "Multiple merge candidates, aborting"
https://bugs.kde.org/show_bug.cgi?id=338658 Marcus <wellend...@posteo.de> changed: What|Removed |Added CC||wellend...@posteo.de -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 381743] cpfind doesn.t work: couldn't parse panos tool script: 'pano_base.pto
https://bugs.kde.org/show_bug.cgi?id=381743 --- Comment #12 from Marcus <wellend...@posteo.de> --- Great! Looking forward to get the new version. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 381163] katepart shows stripes in selected text when source code highlighting is enabled and thus text is colored
https://bugs.kde.org/show_bug.cgi?id=381163 Marcus Behrendt <marcus.behrendt...@gmail.com> changed: What|Removed |Added CC||marcus.behrendt...@gmail.co ||m -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 381163] katepart shows stripes in selected text when source code highlighting is enabled and thus text is colored
https://bugs.kde.org/show_bug.cgi?id=381163 --- Comment #2 from Marcus Behrendt <marcus.behrendt...@gmail.com> --- Any thoughts on this? -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 381163] katepart shows stripes in selected text when source code highlighting is enabled and thus text is colored
https://bugs.kde.org/show_bug.cgi?id=381163 Marcus Behrendt <marcus.behrendt...@gmail.com> changed: What|Removed |Added Version|17.04.2 |17.04.3 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 381163] katepart shows stripes in selected text when source code highlighting is enabled and thus text is colored
https://bugs.kde.org/show_bug.cgi?id=381163 Marcus Behrendt <marcus.behrendt...@gmail.com> changed: What|Removed |Added CC||dhaum...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 381743] cpfind doesn.t work: couldn't parse panos tool script: 'pano_base.pto
https://bugs.kde.org/show_bug.cgi?id=381743 --- Comment #10 from Marcus <wellend...@posteo.de> --- Dear Gilles, thank you for your question. As far as I have researched the problem it could be a bug because it doesn't work with hugin 2017 or a packaging problem downstream, because it should be packaged with an earlier version of hugin. In the beginning I just saw, that the panorama stitching doesn't work for me. But my understanding now is, that it depends on your definition. Actually I posted at the Manjaro forum after I found out, that there have been similar problems with earlier versions and it might be a wrong packaging. Please let me know if you would say this is a packaging problem downstream and I will forward that to the Manjaro team. Thank you very much! -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 381743] cpfind doesn.t work: couldn't parse panos tool script: 'pano_base.pto
https://bugs.kde.org/show_bug.cgi?id=381743 --- Comment #8 from Marcus <wellend...@posteo.de> --- Is that maybe a reason, the automatic testing searches here: digikam.general: Testing "/usr/bin/autooptimiser/autooptimiser" ... (autooptimiser inside a folder "autooptimiser") And manually adding the path: digikam.general: Testing "/usr/bin//autooptimiser" ... (two slashes: bin// ) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 381743] cpfind doesn.t work: couldn't parse panos tool script: 'pano_base.pto
https://bugs.kde.org/show_bug.cgi?id=381743 --- Comment #7 from Marcus <wellend...@posteo.de> --- I was writing autooptimizer but it should be autooptimiser! Checking the help file I get this: $ autooptimiser --help autooptimiser: optimize image positions autooptimiser version 2017.0.0.eac5e8cc546e Usage: autooptimiser [options] input.pto To read a project from stdio, specify - as input file. ... Which seems to be ok. ls -l /usr/bin/autooptimiser: -rwxr-xr-x 1 root root 133272 15. Jul 14:57 /usr/bin/autooptimiser -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 381743] cpfind doesn.t work: couldn't parse panos tool script: 'pano_base.pto
https://bugs.kde.org/show_bug.cgi?id=381743
--- Comment #6 from Marcus <wellend...@posteo.de> ---
I did some further research and found here another bug
https://bugs.kde.org/show_bug.cgi?id=280736 which is maybe related to this.
Manjaro provides hugin 2017.0.0-1.
As far as I understood the panoramagui tests which version auf autooptimizer is
installed through a parsing autooptimizer --help. The above mentioned bugs
reporter writes about cpfind:
> I assume it's executing 'cpfind --help' and trying to parse the first line,
> however kubuntu's hugin version does not have version number on the first
> line, but 'ThreadQueue created'.
That would explain that even choosing autooptimizer doesn't work for me.
But I don't know how to check the parsing process.
Starting digikam from the console I get this output when opening the
panoramagui:
digikam.general: Testing "/usr/bin/autooptimiser/autooptimiser" ...
digikam.general: Testing "autooptimiser" ...
digikam.general: "autooptimiser" help header line:
""
digikam.general: Testing "cpclean" ...
digikam.general: "cpclean" help header line:
"cpclean version 2017.0.0.eac5e8cc546e"
digikam.general: Found "cpclean" version: "2017.0.0"
digikam.general: Testing "cpfind" ...
digikam.general: "cpfind" help header line:
"Hugin's cpfind 2017.0.0.eac5e8cc546e"
digikam.general: Found "cpfind" version: "2017.0.0"
digikam.general: Testing "enblend" ...
digikam.general: "enblend" help header line:
"enblend 4.2"
digikam.general: Found "enblend" version: "4.2"
digikam.general: Testing "make" ...
digikam.general: "make" help header line:
"GNU Make 4.2.1"
digikam.general: Found "make" version: "4.2.1"
digikam.general: Testing "nona" ...
digikam.general: "nona" help header line:
"nona version 2017.0.0.eac5e8cc546e"
digikam.general: Found "nona" version: "2017.0.0"
digikam.general: Testing "pano_modify" ...
digikam.general: "pano_modify" help header line:
"pano_modify version 2017.0.0.eac5e8cc546e"
digikam.general: Found "pano_modify" version: "2017.0.0"
digikam.general: Testing "pto2mk" ...
digikam.general: Testing "hugin_executor" ...
digikam.general: Found "hugin_executor"
digikam.general: Starting Main Thread
digikam.general: Testing "autooptimiser" ...
digikam.general: "autooptimiser" help header line:
""
digikam.general: Testing "/usr/bin/autooptimiser/autooptimiser" ...
digikam.general: Testing "autooptimiser" ...
digikam.general: "autooptimiser" help header line:
""
digikam.general: Testing "/usr/bin/autooptimiser/autooptimiser" ...
digikam.general: Testing "autooptimiser" ...
digikam.general: "autooptimiser" help header line:
""
digikam.general: All Binaries Found : false
digikam.general: Testing "/usr/bin/autooptimiser/autooptimiser" ...
digikam.general: All Binaries Found : false
digikam.general: Hugin >= 2015.0 : false
digikam.general: Testing "pto2mk" ...
digikam.general: Testing "autooptimiser" ...
digikam.general: "autooptimiser" help header line:
""
digikam.general: All Binaries Found : false
digikam.general: Testing "/usr/bin/autooptimiser/autooptimiser" ...
digikam.general: All Binaries Found : false
If I manually choose autooptimizer I get this output:
kf5.kio.widgets: No node found for item that was just removed:
QUrl("file:///usr/bin/gdb")
digikam.general: Testing "/usr/bin//autooptimiser" ...
digikam.general: "autooptimiser" help header line:
""
digikam.general: All Binaries Found : false
--
You are receiving this mail because:
You are watching all bug changes.
[neon] [Bug 382453] New: Errors while processing libkf5followupreminder and libkf5libkleo5
https://bugs.kde.org/show_bug.cgi?id=382453 Bug ID: 382453 Summary: Errors while processing libkf5followupreminder and libkf5libkleo5 Product: neon Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Packages User Edition Assignee: neon-b...@kde.org Reporter: mar...@harrisonland.co.uk CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- My system is in a state where attempting to run any apt operation results in the following output: $ sudo apt upgrade Reading package lists... Done Building dependency tree Reading state information... Done You might want to run ‘apt-get -f install’ to correct these. The following packages have unmet dependencies. libkf5followupreminder5 : Depends: kf5-kdepim-apps-libs-data (= 4:17.04.2-0neon+16.04+xenial+build5) but it is not installed libkf5libkleo5 : Depends: libkf5libkleo-data (= 4:17.04.2-0neon+16.04+xenial+build29) but it is not installed Depends: libqgpgme7 (>= 1.8.0) but it is not installed E: Unmet dependencies. Try using -f. Running apt install -f (with a clean cache) results in the following output: $ sudo apt install -f Reading package lists... Done Building dependency tree Reading state information... Done Correcting dependencies...Starting pkgProblemResolver with broken count: 0 Starting 2 pkgProblemResolver with broken count: 0 Done Done Starting pkgProblemResolver with broken count: 0 Starting 2 pkgProblemResolver with broken count: 0 Done The following additional packages will be installed: kf5-kdepim-apps-libs-data libkf5followupreminder5 libkf5libkleo-data libkf5libkleo5 libqgpgme7 The following NEW packages will be installed kf5-kdepim-apps-libs-data libkf5libkleo-data libqgpgme7 The following packages will be upgraded: libkf5followupreminder5 libkf5libkleo5 2 to upgrade, 3 to newly install, 0 to remove and 0 not to upgrade. 89 not fully installed or removed. Need to get 668 kB of archives. After this operation, 2,239 kB of additional disk space will be used. Do you want to continue? [Y/n] Get:1 http://archive.neon.kde.org/user xenial/main amd64 libqgpgme7 amd64 1.8.0-neon0+16.04+xenial+build3 [198 kB] Get:2 http://archive.neon.kde.org/user xenial/main amd64 libkf5followupreminder5 amd64 4:17.04.3-0neon+16.04+xenial+build6 [12.4 kB] Get:3 http://archive.neon.kde.org/user xenial/main amd64 kf5-kdepim-apps-libs-data all 4:17.04.3-0neon+16.04+xenial+build6 [21.5 kB] Get:4 http://archive.neon.kde.org/user xenial/main amd64 libkf5libkleo5 amd64 4:17.04.3-0neon+16.04+xenial+build30 [289 kB] Get:5 http://archive.neon.kde.org/user xenial/main amd64 libkf5libkleo-data all 4:17.04.3-0neon+16.04+xenial+build30 [147 kB] Fetched 668 kB in 5s (121 kB/s) Selecting previously unselected package libqgpgme7:amd64. (Reading database ... 307646 files and directories currently installed.) Preparing to unpack .../libqgpgme7_1.8.0-neon0+16.04+xenial+build3_amd64.deb ... Unpacking libqgpgme7:amd64 (1.8.0-neon0+16.04+xenial+build3) ... Selecting previously unselected package libkf5followupreminder5:amd64. Preparing to unpack .../libkf5followupreminder5_4%3a17.04.3-0neon+16.04+xenial+build6_amd64.deb ... dpkg: error processing archive /var/cache/apt/archives/libkf5followupreminder5_4%3a17.04.3-0neon+16.04+xenial+build6_amd64.deb (--unpack): triggers ci file contains unknown directive '
[digikam] [Bug 381743] cpfind doesn.t work: couldn't parse panos tool script: 'pano_base.pto
https://bugs.kde.org/show_bug.cgi?id=381743 --- Comment #4 from Marcus <wellend...@posteo.de> --- This is on Manjaro stable. I parallel installed opensuse stable, where everything works fine with digikam 5.2. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 381743] cpfind doesn.t work: couldn't parse panos tool script: 'pano_base.pto
https://bugs.kde.org/show_bug.cgi?id=381743 --- Comment #3 from Marcus <wellend...@posteo.de> --- This is running on Manjaro stable. I installed a stable opensuse, digikam 5.2, where it works. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 381743] cpfind doesn.t work: couldn't parse panos tool script: 'pano_base.pto
https://bugs.kde.org/show_bug.cgi?id=381743 --- Comment #2 from Marcus <wellend...@posteo.de> --- In this window can click "find" and it opens /usr/bin where is installed autooptimiser. But clicking the program it returns to this screen, still not display the version and showing "find", not "change (Ändern)" Similar problem if I press "find" to find pto2mk. Actually pto2mk is not installed later than Hugin 2014, hugin should instead search for hugin_executor, not for pto2mk actually. Manually adding hugin_executor doesn't work. -- You are receiving this mail because: You are watching all bug changes.
