[plasmashell] [Bug 435190] plasmashell crash on Wayland when opening Thunderbird blog entry
https://bugs.kde.org/show_bug.cgi?id=435190 --- Comment #3 from Alex --- Created attachment 137221 --> https://bugs.kde.org/attachment.cgi?id=137221&action=edit plasmashell output Output of plasmashell when reproducing this bug -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 435190] plasmashell crash on Wayland when opening Thunderbird blog entry
https://bugs.kde.org/show_bug.cgi?id=435190 soredake changed: What|Removed |Added CC||ndrzj1...@relay.firefox.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 434938] Blur Filter Layers break on seams in Wrap Around Mode
https://bugs.kde.org/show_bug.cgi?id=434938 Ahab Greybeard changed: What|Removed |Added CC||ahab.greybe...@hotmail.co.u ||k --- Comment #1 from Ahab Greybeard --- Created attachment 137222 --> https://bugs.kde.org/attachment.cgi?id=137222&action=edit gaps at borders I can confirm this for the Mar 30 5.0.0-prealpha (git 783e86c) appimage. It happens for a filter layer and a filter mask. When painting, there are obvious gaps at the border as show in the attachment 'gaps.png' If Image -> Trim to Image Size is done or if the filter visibility is turned off then on again, the gaps become discontinuities as shown in the attachment 'discontinuities.png'. The same effect is seen in the 4.3.0 and 4.4.0 appimages. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 433576] keyboard configurations with single layout are broken on Wayland
https://bugs.kde.org/show_bug.cgi?id=433576 soredake changed: What|Removed |Added CC||ndrzj1...@relay.firefox.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 435009] System Settings crashed in QtWayland::wl_registry::handle_global() for org_kde_kwin_blur_manager on Wayland when changing global theme
https://bugs.kde.org/show_bug.cgi?id=435009 --- Comment #4 from Vlad Zahorodnii --- This should be fixed by https://invent.kde.org/plasma/kwayland-server/-/merge_requests/156. Not sure that Neon was shipping kwin with that MR included. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 434938] Blur Filter Layers break on seams in Wrap Around Mode
https://bugs.kde.org/show_bug.cgi?id=434938 --- Comment #2 from Ahab Greybeard --- Created attachment 137223 --> https://bugs.kde.org/attachment.cgi?id=137223&action=edit border discontinuities -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 434938] Blur Filter Layers break on seams in Wrap Around Mode
https://bugs.kde.org/show_bug.cgi?id=434938 Ahab Greybeard changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 433829] Can't change between dvorak and qwerty
https://bugs.kde.org/show_bug.cgi?id=433829 Vlad Zahorodnii changed: What|Removed |Added Resolution|WORKSFORME |--- Status|RESOLVED|REPORTED --- Comment #5 from Vlad Zahorodnii --- I wonder if it's a dup of https://bugs.kde.org/show_bug.cgi?id=433576 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 433168] [Wayland] Drag & drop from Dolphin to WINE application doesn't work
https://bugs.kde.org/show_bug.cgi?id=433168 Vlad Zahorodnii changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #10 from Vlad Zahorodnii --- Setting bug status to reported. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 427688] killing Xwayland freezes entire system
https://bugs.kde.org/show_bug.cgi?id=427688 --- Comment #34 from Vlad Zahorodnii --- Hmm, I've never encountered that issue. Maybe somebody else can explain how to fix it. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 435119] Search doesn't work.
https://bugs.kde.org/show_bug.cgi?id=435119 tagwer...@innerjoin.org changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #8 from tagwer...@innerjoin.org --- (In reply to Mina from comment #6) > ... I used "~/Documents/TestBaloo" instead, because my Documents > folder is quite messy ... The only reason I suggested "Documents" is that not all distributions index all folders. As far as I can tell, everyone indexes "Documents" :-) > $ balooctl status > > It stays blank and I have to hit Ctrl + C to exit. Never met that! Doesn't sound healthy :-/ > $ balooctl purge > Stopping the File Indexer > > Not sure if you can see the output correctly, but it's just lots of dots and > "failed to stop" in the end. Have met that. More in the past, maybe less so recently... My gut feeling is the baloo index has got corrupted. It happens and in that case the best option is to start again from scratch. If you cannot do a "balooctl purge", do a "balooctl disable" (which might still fail to stop) and reboot. The "disable" should prevent baloo starting up again when you log back in. You should then be able to run a "balooctl monitor" in one window, a "balooctl purge" to delete the index and then a "balooctl enable" to start the indexing in a second window (it may be that you need a "balooctl enable" followed by a "balooctl enable" as it sometimes needs to be told twice) If you have no luck with "balooctl purge", the index file lives at: .local/share/baloo/index and you can stop baloo and delete it manually. > ... Yeah my neon is with me since 18.04 and I upgraded it to 20.04 There's a Bug 431664 about needing to reindex if you had been running a baloo 5.68 or earlier > Hope any of this makes sense. Thank you, yes :-) -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 435147] Video stabilization doesn't work.
https://bugs.kde.org/show_bug.cgi?id=435147 --- Comment #2 from kaushik.d...@gmail.com --- Created attachment 137224 --> https://bugs.kde.org/attachment.cgi?id=137224&action=edit Stabilization dialog in 20.08 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 435147] Video stabilization doesn't work.
https://bugs.kde.org/show_bug.cgi?id=435147 --- Comment #3 from kaushik.d...@gmail.com --- Created attachment 137225 --> https://bugs.kde.org/attachment.cgi?id=137225&action=edit Stabilization dialog in 20.12.3 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 435191] Loading the wrong keyboard layout
https://bugs.kde.org/show_bug.cgi?id=435191 Domenico Panella changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG --- Comment #4 from Domenico Panella --- I did this test: I created a new user and logged in with Wayland. I created the same keyboard layouts and it also worked after reboot and poweroff command. I logged in with X11 as my user and now it also worked. I don't know what is happened but at the moment it's working fine. I close this bug as "Not a bug" -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 435147] Video stabilization doesn't work.
https://bugs.kde.org/show_bug.cgi?id=435147 --- Comment #4 from kaushik.d...@gmail.com --- Created attachment 137226 --> https://bugs.kde.org/attachment.cgi?id=137226&action=edit *.mp4.mlt -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 435192] Certain System Monitor widget display styles crash Plasma Shell when selecting another display style
https://bugs.kde.org/show_bug.cgi?id=435192 David Redondo changed: What|Removed |Added CC||k...@david-redondo.de Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #1 from David Redondo --- Changing ApplciationTable to LineChart: #0 0x5a8ccb30 in () #1 0x701fe7e4 in QQuickDialogButtonBoxPrivate::getContentWidth() const (this=0x5a105aa0) at qquickdialogbuttonbox.cpp:325 #2 0x701f4238 in QQuickControlPrivate::updateImplicitContentWidth() (this=0x5a105aa0) at qquickcontrol.cpp:462 #3 0x701fe9d5 in QQuickDialogButtonBoxPrivate::itemImplicitWidthChanged(QQuickItem*) (this=0x5a105aa0, item=0x55938c70) at qquickdialogbuttonbox.cpp:202 #4 0x7766720d in QQuickItemPrivate::implicitWidthChanged() (this=) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qarraydata.h:236 #5 0x776603b6 in QQuickItem::setImplicitSize(double, double) (this=this@entry=0x55938c70, w=w@entry=0, h=h@entry=0) at items/qquickitem.cpp:6935 #6 0x7fffe04aa802 in QQuickLayoutPrivate::applySizeHints() const (this=) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qsize.h:315 #7 0x7fffe04aa84b in QQuickLayout::ensureLayoutItemsUpdated() const (this=) at qquicklayout.cpp:854 #8 0x7fffe04adcfe in QQuickGridLayoutBase::itemCount() const (this=) at qquicklinearlayout.cpp:432 #9 0x7fffe04a9a88 in QQuickLayout::deactivateRecur() (this=this@entry=0x55938c70) at qquicklayout.cpp:916 #10 0x7fffe04adc62 in QQuickGridLayoutBase::~QQuickGridLayoutBase() (this=0x55938c70, __in_chrg=) at qquicklinearlayout.cpp:313 #11 0x7fffe04b51d5 in QQuickLinearLayout::~QQuickLinearLayout() (this=0x55938c70, __in_chrg=) at ./qquicklinearlayout_p.h:228 #12 QQuickRowLayout::~QQuickRowLayout() (this=0x55938c70, __in_chrg=) at ./qquicklinearlayout_p.h:228 #13 QQmlPrivate::QQmlElement::~QQmlElement() (this=0x55938c70, __in_chrg=) at ../../../include/QtQml/../../src/qml/qml/qqmlprivate.h:144 #14 QQmlPrivate::QQmlElement::~QQmlElement() (this=0x55938c70, __in_chrg=) at ../../../include/QtQml/../../src/qml/qml/qqmlprivate.h:144 #15 0x75bdfcfe in QObjectPrivate::deleteChildren() (this=0x5a105aa0) at kernel/qobject.cpp:2104 #16 0x75bea726 in QObject::~QObject() (this=, __in_chrg=) at kernel/qobject.cpp:1082 #17 0x7766dc2a in QQuickItem::~QQuickItem() (this=0x5a1059e0, __in_chrg=) at items/qquickitem.cpp:2364 #18 0x7fffe0d04659 in () at /usr/lib/x86_64-linux-gnu/qt5/qml/QtQuick/Templates.2/libqtquicktemplates2plugin.so #19 0x75bdfcfe in QObjectPrivate::deleteChildren() (this=0x59f80090) at kernel/qobject.cpp:2104 #20 0x75bea726 in QObject::~QObject() (this=, __in_chrg=) at kernel/qobject.cpp:1082 #21 0x7fffe0d027d2 in () at /usr/lib/x86_64-linux-gnu/qt5/qml/QtQuick/Templates.2/libqtquicktemplates2plugin.so #22 0x75bdfcfe in QObjectPrivate::deleteChildren() (this=0x55ab3200) at kernel/qobject.cpp:2104 #23 0x75bea726 in QObject::~QObject() (this=, __in_chrg=) at kernel/qobject.cpp:1082 #24 0x7766dc2a in QQuickItem::~QQuickItem() (this=0x59710c20, __in_chrg=) at items/qquickitem.cpp:2364 #25 0x7fffe0116a49 in QQmlPrivate::QQmlElement::~QQmlElement() (this=0x59710c20, __in_chrg=) at /usr/include/x86_64-linux-gnu/qt5/QtQml/qqmlprivate.h:142 #26 QQmlPrivate::QQmlElement::~QQmlElement() (this=0x59710c20, __in_chrg=) at /usr/include/x86_64-linux-gnu/qt5/QtQml/qqmlprivate.h:144 #27 0x75be3013 in QObject::event(QEvent*) (this=this@entry=0x59710c20, e=e@entry=0x5ca07d40) at kernel/qobject.cpp:1301 #28 0x7766f7e9 in QQuickItem::event(QEvent*) (this=0x59710c20, ev=0x5ca07d40) at items/qquickitem.cpp:8202 #29 0x768b2dc3 in QApplicationPrivate::notify_helper(QObject*, QEvent*) (this=this@entry=0x556211d0, receiver=receiver@entry=0x59710c20, e=e@entry=0x5ca07d40) at kernel/qapplication.cpp:3632 #30 0x7688 in QApplication::notify(QObject*, QEvent*) (this=0x7fffdaa0, receiver=0x59710c20, e=0x5ca07d40) at kernel/qapplication.cpp:3156 #31 0x75bb56da in QCoreApplication::notifyInternal2(QObject*, QEvent*) (receiver=0x59710c20, event=0x5ca07d40) at ../../include/QtCore/5.15.2/QtCore/private/../../../../../src/corelib/thread/qthread_p.h:325 #32 0x75bb7fe1 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) (receiver=0x0, event_type=0, data=0x556161b0) at kernel/qcoreapplication.cpp:1817 #33 0x75c10987 in postEventSourceDispatch(GSource*, GSourceFunc, gpointer) (s=0x55736c60) at kernel/qeventdispatcher_glib.cpp:277 #34 0x73ead17d in g_main_context_dispatch () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #35 0x000
[kdenlive] [Bug 435147] Video stabilization doesn't work.
https://bugs.kde.org/show_bug.cgi?id=435147 --- Comment #5 from kaushik.d...@gmail.com --- Created attachment 137227 --> https://bugs.kde.org/attachment.cgi?id=137227&action=edit *.mp4.mlt.trf -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 435147] Video stabilization doesn't work.
https://bugs.kde.org/show_bug.cgi?id=435147 --- Comment #6 from kaushik.d...@gmail.com --- Hello Julius, thank you for your response. Here's the info you needed: 1. Appimage - kdenlive-20.12.3a-x86_64.appimage 2. I have tested this with several .mp4 videos and found the same problem. However, all these .mp4 videos could be successfully stabilized with versions 20.08. Additional details - When I check the 'stabilized' folder after a clip is stabilized, the stabilized clip still shows a progress bar at bottom and status shows 1 job in queue and the computer freezes. I have to either restart Kdenlive or my computer. This happened with all clips I tried to stabilize except one rare case when I was able to stabilize a clip. However even with this rare case it was a very slow process - after dragging the stabilized .mlt file on the Timeline I needed to wait for about 5-7 mins and only then the project monitor was able to play the clip. By the way, the vidstab dialog box looks slightly different in versions 20.08 vs 20.12.3. Just found this interesting and thought of sharing in case this helps (see attachment). 3. Yes I faced the same with the generator .mlt clip as well. While the stabilization process finally completed without having to restart Kdenlive but it was a very long process (took about 3 minutes to stabilize a 5 second generator clip, and then after dragging the stabilized .mlt file on the Timeline I needed to wait for about 5-7 mins and only then the project monitor was able to play the clip). 4. I have attached the destination files *.mlt and *.mlt.trf for the only one clip that I was able to successfully stabilize because on other occasions I had to restart Kdenlive / computer and therefore do not have the *.mlt.trf files. 5. Yes, I do. I have successfully stabilized clips in versions 20.08 and 20.04. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 429967] Gwenview and other apps on Wayland have "transparent" areas (i.e. not being painted)
https://bugs.kde.org/show_bug.cgi?id=429967 --- Comment #4 from Vlad Zahorodnii --- mmap() can fail with EINVAL in the following cases EINVAL We don't like addr, length, or offset (e.g., they are too large, or not aligned on a page boundary). EINVAL (since Linux 2.6.12) length was 0. EINVAL flags contained none of MAP_PRIVATE, MAP_SHARED, or MAP_SHARED_VALIDATE. The relevant code in qwaylandshmbackingstore.cpp uchar *data = (uchar *) mmap(nullptr, alloc, PROT_READ | PROT_WRITE, MAP_SHARED, fd, 0); so, it's most likely that the specified length is either 0 or it exceeds the limits. It's hard to say without being able to reproduce the bug. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 435208] New: Can't cancel the installing process in "Tasks" via "Break" button
https://bugs.kde.org/show_bug.cgi?id=435208 Bug ID: 435208 Summary: Can't cancel the installing process in "Tasks" via "Break" button Product: Discover Version: 5.19.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: discover Assignee: lei...@leinir.dk Reporter: mur...@gmail.com CC: aleix...@kde.org Target Milestone: --- SUMMARY The "Tasks" modal window have the "Break" button, but pressing it does nothing when the update is on "Installing" stage. STEPS TO REPRODUCE 1. Select some updates 2. Press "Update button" 3. Click on "Tasks", press the "Break" button. OBSERVED RESULT Nothing happens, process still wait something, seems even paused. Here is screenshot: https://i.imgur.com/CsnxwMJ.png EXPECTED RESULT Process must break or show me the reasons why it can't be cancelled at current stage. SOFTWARE/OS VERSIONS Operating System: Kubuntu 20.10 KDE Plasma Version: 5.19.5 KDE Frameworks Version: 5.74.0 Qt Version: 5.14.2 Kernel Version: 5.8.0-45-generic OS Type: 64-bit -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 414805] Crash in QScreen::handle() after QXcbIntegration::createPlatformOpenGLContext()
https://bugs.kde.org/show_bug.cgi?id=414805 --- Comment #19 from Szőts Ákos --- I attached Valgrind to running kwin_x11. It seems kwin crashes many more times than without it. It crashes on Alt+Tabs, closing windows, and minimising windows after returning from sleep (hopefully this is the reproducible case of the current ticket). I observed the following errors: ==18204== Syscall param writev(vector[...]) points to uninitialised byte(s) ==18204==at 0x64F21CD: __writev (writev.c:26) ==18204==by 0x64F21CD: writev (writev.c:24) ==18204==by 0x5B70AD2: UnknownInlinedFun (xcb_conn.c:277) ==18204==by 0x5B70AD2: _xcb_conn_wait.part.0 (xcb_conn.c:523) ==18204==by 0x5B70B8F: UnknownInlinedFun (xcb_out.c:463) ==18204==by 0x5B70B8F: _xcb_out_send (xcb_out.c:464) ==18204==by 0x5B70DE6: UnknownInlinedFun (xcb_out.c:488) ==18204==by 0x5B70DE6: _xcb_out_flush_to (xcb_out.c:477) ==18204==by 0x5B7242A: xcb_request_check (xcb_in.c:743) ==18204==by 0x112601: QtPrivate::QFunctorSlotObject, void>::impl(int, QtPrivate::QSlotObjectBase*, QObject*, void**, bool*) (main_x11.cpp:243) ==18204==by 0x5F26945: call (qobjectdefs_impl.h:398) ==18204==by 0x5F26945: void doActivate(QObject*, int, void**) (qobject.cpp:3886) ==18204==by 0x4BFF4C2: KSelectionOwner::Private::claimSucceeded() (kselectionowner.cpp:188) ==18204==by 0x4C047A0: UnknownInlinedFun (kselectionowner.cpp:222) ==18204==by 0x4C047A0: KSelectionOwner::filterEvent(void*) (kselectionowner.cpp:406) ==18204==by 0x5EED876: QAbstractEventDispatcher::filterNativeEvent(QByteArray const&, void*, long*) (qabstracteventdispatcher.cpp:495) ==18204==by 0xC3540E0: QXcbConnection::handleXcbEvent(xcb_generic_event_t*) (qxcbconnection.cpp:536) ==18204==by 0xC3555F5: QXcbConnection::processXcbEvents(QFlags) (qxcbconnection.cpp:1014) ==18204== Address 0xa1bfd7a is 4,538 bytes inside a block of size 21,168 alloc'd ==18204==at 0x4840B65: calloc (in /usr/lib64/valgrind/vgpreload_memcheck-amd64-linux.so) ==18204==by 0x5B73050: xcb_connect_to_fd (xcb_conn.c:346) ==18204==by 0x5B73C46: xcb_connect_to_display_with_auth_info (xcb_util.c:534) ==18204==by 0x7BA40E1: _XConnectXCB (xcb_disp.c:78) ==18204==by 0x7B94124: XOpenDisplay (OpenDis.c:129) ==18204==by 0xC379926: QXcbBasicConnection::QXcbBasicConnection(char const*) (qxcbconnection_basic.cpp:114) ==18204==by 0xC355B21: QXcbConnection::QXcbConnection(QXcbNativeInterface*, bool, unsigned int, char const*) (qxcbconnection.cpp:91) ==18204==by 0xC358992: QXcbIntegration::QXcbIntegration(QStringList const&, int&, char**) (qxcbintegration.cpp:197) ==18204==by 0x485E45E: create (qxcbmain.cpp:56) ==18204==by 0x485E45E: QXcbIntegrationPlugin::create(QString const&, QStringList const&, int&, char**) (qxcbmain.cpp:53) ==18204==by 0x55B908B: init_platform (qguiapplication.cpp:1223) ==18204==by 0x55B908B: QGuiApplicationPrivate::createPlatformIntegration() (qguiapplication.cpp:1481) ==18204==by 0x55BA48F: QGuiApplicationPrivate::createEventDispatcher() (qguiapplication.cpp:1498) ==18204==by 0x5EF6DB5: QCoreApplicationPrivate::init() (qcoreapplication.cpp:834) ==18204== Uninitialised value was created by a stack allocation ==18204==at 0x4BFF450: KSelectionOwner::Private::claimSucceeded() (kselectionowner.cpp:170) ==18204== Invalid read of size 16 ==18204==at 0x12A6CB01: ??? (in /memfd:sljit (deleted)) ==18204==by 0xD0A5537: ??? ==18204== Address 0xd0a555e is 62 bytes inside a block of size 76 alloc'd ==18204==at 0x483E77F: malloc (in /usr/lib64/valgrind/vgpreload_memcheck-amd64-linux.so) ==18204==by 0x5D1A490: QArrayData::allocate(unsigned long, unsigned long, unsigned long, QFlags) (qarraydata.cpp:218) ==18204==by 0x5D933F9: allocate (qarraydata.h:224) ==18204==by 0x5D933F9: QString::fromLatin1_helper(char const*, int) (qstring.cpp:5459) ==18204==by 0x671CE5D: KWin::GLPlatform::detect(KWin::OpenGLPlatformInterface) (qstring.h:701) ==18204==by 0x128B5AE1: KWin::GlxBackend::init() [clone .part.0] (glxbackend.cpp:196) ==18204==by 0x13181D88: KWin::SceneOpenGL::createScene(QObject*) (scene_opengl.cpp:449) ==18204==by 0x13190828: KWin::OpenGLFactory::create(QObject*) const (scene_opengl.cpp:2725) ==18204==by 0x4985E2E: KWin::Compositor::setupStart() [clone .part.0] (composite.cpp:238) ==18204==by 0x4988B59: KWin::X11Compositor::start() (composite.cpp:815) ==18204==by 0x5F1C350: QObject::event(QEvent*) (qobject.cpp:1314) ==18204==by 0x4F194FE: QApplicationPrivate::notify_helper(QObject*, QEvent*) (qapplication.cpp:3632) ==18204==by 0x5EF0329: QCoreApplication::notifyInternal2(QObject*, QEvent*) (qcoreapplication.cpp:1063) ==18204== Invalid read of size 16 ==18204==at 0x12A6C6D8: ??? (in /memfd:sljit (deleted)) ==18204==by 0xD0A5537: ??? ==18204== Address 0xd0a555e is 62 bytes inside a block of size 76 alloc'd ==18204==at 0x483E77F: malloc (in /usr/lib64/v
[Discover] [Bug 435208] Can't cancel the installing process in "Tasks" via "Break" button
https://bugs.kde.org/show_bug.cgi?id=435208 --- Comment #1 from Murz --- Same problem is when I click "Cancel" button on top-left corner. Also there are no process matched "apt" or "dpkg" in `ps aux | grep -E 'dpkg|apt'` output. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 435193] crop redo causes crash
https://bugs.kde.org/show_bug.cgi?id=435193 Ahab Greybeard changed: What|Removed |Added CC||ahab.greybe...@hotmail.co.u ||k --- Comment #2 from Ahab Greybeard --- With the 4.4.3 appimage, I could reproduce this just once and that was associated with the undo history moving back one step, as noted in the Description. After that, I never saw the undo history move back. I can induce a crash every time in 4.4.3 for the conditions as noted for https://bugs.kde.org/show_bug.cgi?id=433770 but this has been fixed for the nightly builds. @ Halcyoen Can you reproduce this in 4.4.3 with the undo history moving back or in the nightly builds? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 434715] After change animation speed Plasma Wayland Session + Nvidia just dies
https://bugs.kde.org/show_bug.cgi?id=434715 Vlad Zahorodnii changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=428089 --- Comment #3 from Vlad Zahorodnii --- Are you using the proprietary NVIDIA driver? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 428089] Restarting compositing breaks existing EGLStreams
https://bugs.kde.org/show_bug.cgi?id=428089 Vlad Zahorodnii changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=434715 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 434715] After change animation speed Plasma Wayland Session + Nvidia just dies
https://bugs.kde.org/show_bug.cgi?id=434715 Vlad Zahorodnii changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #4 from Vlad Zahorodnii --- Settings the NEEDSINFO status. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 435023] Drawing with the active lenovo pen on a lenovo laptop you can't draw at all
https://bugs.kde.org/show_bug.cgi?id=435023 Ahab Greybeard changed: What|Removed |Added Resolution|--- |NOT A BUG CC||ahab.greybe...@hotmail.co.u ||k Status|REPORTED|RESOLVED --- Comment #1 from Ahab Greybeard --- This is unlikely to be a bug in krita 4.4.2 (or in 4.4.3, the latest version) Please post a new topic in https://krita-artists.org/ which is a suitable forum for help and advice with pen/tablet settings, which is probably what is causing this. I'll set this to Resolved Not A Bug but the Status can be changed later if anything significant is observed. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 434715] After change animation speed Plasma Wayland Session + Nvidia just dies
https://bugs.kde.org/show_bug.cgi?id=434715 --- Comment #5 from Felipe Kinoshita --- Yes! -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 435209] New: Probably Dolphin kio-gdrive crash when unpausing file copy operation
https://bugs.kde.org/show_bug.cgi?id=435209 Bug ID: 435209 Summary: Probably Dolphin kio-gdrive crash when unpausing file copy operation Product: dolphin Version: 20.08.3 Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: prco...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- Application: dolphin (20.08.3) Qt Version: 5.14.2 Frameworks Version: 5.75.0 Operating System: Linux 5.10.22-100.fc32.x86_64 x86_64 Windowing system: X11 Distribution: "Fedora release 32 (Thirty Two)" -- Information about the crash: - What I was doing when the application crashed: Unpausing file transfer operation via kio-gdrive plugin, than crashing. Sometime repeates. The crash can be reproduced sometimes. -- Backtrace: Application: Dolphin (dolphin), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f4374d131c0 (LWP 19833))] Thread 5 (Thread 0x7f435d279700 (LWP 20834)): #0 0x7f437704a028 in pa_fdsem_before_poll () from /usr/lib64/pulseaudio/libpulsecommon-14.0.so #1 0x7f4377061ef7 in srbchannel_rwloop () from /usr/lib64/pulseaudio/libpulsecommon-14.0.so #2 0x7f4378147de3 in pa_mainloop_dispatch () from /lib64/libpulse.so.0 #3 0x7f4378148112 in pa_mainloop_iterate () from /lib64/libpulse.so.0 #4 0x7f43781481b0 in pa_mainloop_run () from /lib64/libpulse.so.0 #5 0x7f437815640d in thread () from /lib64/libpulse.so.0 #6 0x7f43770706ec in internal_thread_func () from /usr/lib64/pulseaudio/libpulsecommon-14.0.so #7 0x7f437819a432 in start_thread () from /lib64/libpthread.so.0 #8 0x7f437b7526d3 in clone () from /lib64/libc.so.6 Thread 4 (Thread 0x7f435e1f7700 (LWP 19840)): #0 0x7f437b74328c in read () from /lib64/libc.so.6 #1 0x7f437783b53f in g_wakeup_acknowledge () from /lib64/libglib-2.0.so.0 #2 0x7f43777f15ee in g_main_context_check () from /lib64/libglib-2.0.so.0 #3 0x7f43777f1a55 in g_main_context_iterate.constprop () from /lib64/libglib-2.0.so.0 #4 0x7f43777f1be3 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #5 0x7f4379879abb in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #6 0x7f437982c83b in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #7 0x7f4379698417 in QThread::exec() () from /lib64/libQt5Core.so.5 #8 0x7f4379699680 in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #9 0x7f437819a432 in start_thread () from /lib64/libpthread.so.0 #10 0x7f437b7526d3 in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7f4366f0e700 (LWP 19836)): #0 0x7f43777ef85c in g_source_ref () from /lib64/libglib-2.0.so.0 #1 0x7f43777ef928 in g_source_iter_next () from /lib64/libglib-2.0.so.0 #2 0x7f43777f0ee3 in g_main_context_prepare () from /lib64/libglib-2.0.so.0 #3 0x7f43777f19db in g_main_context_iterate.constprop () from /lib64/libglib-2.0.so.0 #4 0x7f43777f1be3 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #5 0x7f4379879abb in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #6 0x7f437982c83b in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #7 0x7f4379698417 in QThread::exec() () from /lib64/libQt5Core.so.5 #8 0x7f4379b0951b in QDBusConnectionManager::run() () from /lib64/libQt5DBus.so.5 #9 0x7f4379699680 in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #10 0x7f437819a432 in start_thread () from /lib64/libpthread.so.0 #11 0x7f437b7526d3 in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7f4367a72700 (LWP 19835)): #0 0x7f437b74786f in poll () from /lib64/libc.so.6 #1 0x7f43781c538a in _xcb_conn_wait () from /lib64/libxcb.so.1 #2 0x7f43781c771a in xcb_wait_for_event () from /lib64/libxcb.so.1 #3 0x7f4367beec68 in QXcbEventQueue::run() () from /lib64/libQt5XcbQpa.so.5 #4 0x7f4379699680 in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #5 0x7f437819a432 in start_thread () from /lib64/libpthread.so.0 #6 0x7f437b7526d3 in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7f4374d131c0 (LWP 19833)): [KCrash Handler] #4 0x7f437b68d7d5 in raise () from /lib64/libc.so.6 #5 0x7f437b676895 in abort () from /lib64/libc.so.6 #6 0x7f437b6d1627 in __libc_message () from /lib64/libc.so.6 #7 0x7f437b6d8b4c in malloc_printerr () from /lib64/libc.so.6 #8 0x7f437b6d8dfc in munmap_chunk () from /lib64/libc.so.6 #9 0x7f43796d1b77 in QHashData::free_helper(void (*)(QHashData::Node*)) () from /lib64/libQt5Core.so.5 #10 0x7f437b598196 in KFileItemModel::slotClear() () from /lib64/libdolphinprivate.so.5 #11 0x7f437b5fa5d5 in DolphinView::setUrl(QU
[frameworks-kholidays] [Bug 435210] New: Pakistani Holidays Missing from Calendar
https://bugs.kde.org/show_bug.cgi?id=435210 Bug ID: 435210 Summary: Pakistani Holidays Missing from Calendar Product: frameworks-kholidays Version: unspecified Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: cagajev...@tlhao86.com Target Milestone: --- SUMMARY There are no Holidays of Pakistan in the Calendars Holiday section. STEPS TO REPRODUCE 1. Open Calendar Settings 2. Go to Holidays Settings 3. No Pakistani Holidays found OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[keditbookmarks] [Bug 342533] Crash while dragging and dropping seleced bookmarks
https://bugs.kde.org/show_bug.cgi?id=342533 --- Comment #5 from Stefan Gies --- Created attachment 137228 --> https://bugs.kde.org/attachment.cgi?id=137228&action=edit New crash information added by DrKonqi keditbookmarks (20.12.3) using Qt 5.15.2 - What I was doing when the application crashed: Dragging and dropping imported bookmarks -- Backtrace (Reduced): #4 TreeItem::deleteChildren (this=0x0, first=-1, last=-1) at ./src/kbookmarkmodel/treeitem.cpp:73 #5 0x7fefbd7c4c0c in KBookmarkModel::removeBookmark (this=0x55f9e97627a0, bookmark=...) at ./src/kbookmarkmodel/model.cpp:456 #6 0x7fefbd7be594 in CreateCommand::undo (this=0x55f9e9b59020) at ./src/kbookmarkmodel/commands.cpp:159 #7 0x7fefbd7c122e in DeleteCommand::redo (this=0x55f9ea03a450) at ./src/kbookmarkmodel/commands.cpp:323 #8 0x7fefbcb07cda in QUndoCommand::redo() () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 -- You are receiving this mail because: You are watching all bug changes.
[keditbookmarks] [Bug 342533] Crash while dragging and dropping seleced bookmarks
https://bugs.kde.org/show_bug.cgi?id=342533 Stefan Gies changed: What|Removed |Added CC||sgies1...@t-online.de -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 412943] Use System Monitor Profile checkbox attributes wrong profile to screens, breaking color management
https://bugs.kde.org/show_bug.cgi?id=412943 --- Comment #13 from Tyson Tan --- Hi Tiar, My apologies, I have given up using multi-monitor altogether because of this bug. Now I use a single Cintiq on each working location, so unfortunately I cannot test or confirm about the situation. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 412943] Use System Monitor Profile checkbox attributes wrong profile to screens, breaking color management
https://bugs.kde.org/show_bug.cgi?id=412943 --- Comment #14 from Tyson Tan --- If there is one thing I can comment, I think Krita's current Color Management Display identification text is still inadequate. It only shows something like "DisplayPort-3 C 3840x2160". If I had two 4K display both connected to displayports, there is no way I can tell them apart. To help users assign ICC profiles accurately, I recommend you show users the Display's Vendor and Model on that page. -- You are receiving this mail because: You are watching all bug changes.
[picmi] [Bug 435211] New: Picmi wrongly calls a single black cell correct when there should be two
https://bugs.kde.org/show_bug.cgi?id=435211 Bug ID: 435211 Summary: Picmi wrongly calls a single black cell correct when there should be two Product: picmi Version: 2.0.0 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: ja...@gruber-linke.de Reporter: p...@bezitopo.org Target Milestone: --- SUMMARY There's a column with the numbers "1 1". xx*x_x correctly displays one 1 in blue and the other in black. xx*x*x correctly displays both 1s in blue. xx*xxx wrongly displays both 1s in blue. STEPS TO REPRODUCE 1. Play a game which has "1 1" in a row or column. 2. Mark all of them with an X except one, which mark with black. OBSERVED RESULT Both 1s turn blue. EXPECTED RESULT Either only one 1 should turn blue, or neither should. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Ubuntu Focal (available in About System) KDE Plasma Version: 4.5.18 KDE Frameworks Version: not sure what package that is Qt Version: 5.12.8 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 423963] Cannot spawn child process (unsupported clone flags) Qt
https://bugs.kde.org/show_bug.cgi?id=423963
Christoph Cullmann changed:
What|Removed |Added
CC||cullm...@kde.org
--- Comment #2 from Christoph Cullmann ---
Hi,
I have the same issue with Qt 6.1 (current branch state of today).
(and I have this since at least 6.0)
Interesting enough, it doesn't happen for all our QProcess::start calls :/
valgrind: m_syswrap/syswrap-main.c:1957 (vgPlain_client_syscall): Assertion '0
== (sci->flags & ~(SfMayBlock | SfPostOnFail | SfPollAfter))' failed.
host stacktrace:
==1115104==at 0x58041B2A: show_sched_status_wrk (m_libcassert.c:406)
==1115104==by 0x58041C47: report_and_quit (m_libcassert.c:477)
==1115104==by 0x58041DD7: vgPlain_assert_fail (m_libcassert.c:543)
==1115104==by 0x5809AB4F: vgPlain_client_syscall (syswrap-main.c:1980)
==1115104==by 0x5809617A: handle_syscall (scheduler.c:1208)
==1115104==by 0x58098177: vgPlain_scheduler (scheduler.c:1526)
==1115104==by 0x580E38D0: thread_wrapper (syswrap-linux.c:101)
==1115104==by 0x580E38D0: run_a_thread_NORETURN (syswrap-linux.c:154)
sched status:
running_tid=1
Thread 1: status = VgTs_Runnable syscall 56 (lwpid 1115104)
==1115104==at 0x83E2A9D: syscall (in /usr/lib/libc-2.33.so)
==1115104==by 0x7E48636: forkfd (in
/makefactory/products/master/release/linux64/a3_c_8918188/bin/libQt6Core.so.6)
==1115104==by 0x7E2F881: QProcessPrivate::startProcess() (in
/makefactory/products/master/release/linux64/a3_c_8918188/bin/libQt6Core.so.6)
==1115104==by 0x7E2A4B9:
QProcessPrivate::start(QFlags) (in
/makefactory/products/master/release/linux64/a3_c_8918188/bin/libQt6Core.so.6)
==1115104==by 0x15E54F9: main (in
/makefactory/products/master/release/linux64/a3_c_8918188/bin/a3c)
client stack range: [0x1FFEFE9000 0x1FFF000FFF] client SP: 0x1FFEFFE028
valgrind stack range: [0x10033B8000 0x10034B7FFF] top usage: 8328 of 1048576
valgrind version is valgrind-3.16.1, current Manjaro valgrind package.
Actually QProcess start code seems "normal", just like: (m_serverProcess ==
QProcess)
// try to startup the server, output its sever to stdout/err
m_serverProcess.setProcessChannelMode(QProcess::ForwardedChannels);
const QString program = arguments.takeFirst();
m_serverProcess.start(program, arguments, QProcess::ReadOnly);
if (!m_serverProcess.waitForStarted()) {
Ur::printf(Ur::Fatal, "Unable to start temporary server.");
}
Interesting enough, if I skip this process startup call (that happens in our
main shortly after the QApplication is created,
later calls that trigger more process starting work :/
I tried to avoid any special stuff we only do there, like the
m_serverProcess.setProcessChannelMode(QProcess::ForwardedChannels);
but that still happens.
--
You are receiving this mail because:
You are watching all bug changes.
[frameworks-kwindowsystem] [Bug 435212] New: Dead keys do not work properly in combination with control characters like shift, ctrl, alt (X11)
https://bugs.kde.org/show_bug.cgi?id=435212 Bug ID: 435212 Summary: Dead keys do not work properly in combination with control characters like shift, ctrl, alt (X11) Product: frameworks-kwindowsystem Version: 5.80.0 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: ed...@inbox.lv Target Milestone: --- SUMMARY I use Latvian (apostrophe) keyboard layout in KDE Plasma 5.21, it's very similar to standard Latin letters with addition of accented letters for Latvian language. In Latvian language to get accented keys like ā, ū, etc. I have to press so called "dead" key (apostrophe in my case), release it and then press a desired letter, for example "a", which produces "ā". This is working fine. However, when I press shift+apostrophe, I should get double quotes ", but instead this combination is interpreted as "dead" key anyway and I get nothing, if I press "a" after shift+apostrophe, I get "ā", which is wrong. Dead keys before KDE 5.21 worked fine, but starting with 5.21 they behave incorrectly. Additionally, I have tried to boot Fedora 34 Live ISO with KDE 5.21 and the issue is there as well, in addition to that I have verified that Ubuntu 18.04 Live ISO Gnome/Unity does not have this problem. STEPS TO REPRODUCE 1. Choose Latvian (apostrophe) keyboard layout 2. Press shift+apostrophe OBSERVED RESULT Nothing is printed, but if I press "a" afterwards, I get "ā". EXPECTED RESULT Double quote " character is printed. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Manjaro / KDE KDE Plasma Version: 5.21 KDE Frameworks Version: 5.80 Qt Version: 5.15.2 Session type: X11 ADDITIONAL INFORMATION Since KXKB is no longer available for bug reporting and I did not report this for correct component, please move it accordingly. It's not clear which component I have to choose. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 435213] New: Title clip length changes when updating title
https://bugs.kde.org/show_bug.cgi?id=435213 Bug ID: 435213 Summary: Title clip length changes when updating title Product: kdenlive Version: 20.12.3 Platform: Debian unstable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: roxane.pet...@gmail.com Target Milestone: --- SUMMARY So this a really weird (and minor) one, and i had not really noticed what exactly happened until today, but I had noticed my title clips were not all the same length in the bin. I now have noticed that every time i hit "update title" in the editor, the title clip shortens by one frame. STEPS TO REPRODUCE 1. create title clip (even empty works). In my case, it should be 5s long, but ends up being 4:23 (in 24fps). 2. double click on its thumbnail to edit it 3. the length of the clip automatically changes to 4:22 4. repeat 2 and it will shorten again and again OBSERVED RESULT Title clip has shorten length than is defined in the parameters EXPECTED RESULT Title clip stays length defined in the parameters. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Debian unstable (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION 20.12.3a appimage -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 435038] Krita document DPI affects Reference Images: saved image is loaded differently on load.
https://bugs.kde.org/show_bug.cgi?id=435038 Ahab Greybeard changed: What|Removed |Added CC||ahab.greybe...@hotmail.co.u ||k Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #1 from Ahab Greybeard --- I can reproduce this issue for the 4.4.3 appimage and the Mar 30 5.0.0-prealpha (git 783r86c) appimage. It only happens if the created document has a dpi of 1. The 5.0.0-prealpha has the ability to set fractional dpi values and it does not happen for a dpi value of 1.1 or higher, only for 1.0. The reference image appears at a very large size and with a very large offset from the image position. Examination of the .kra file maindoc.xml does not show any significant difference between reference inage size and transform values (for dpi = 1.1 vs dpi = 1.0) that could account for this. Setting to Confirmed -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 428789] panel splitting problem in the "Title Clip" window
https://bugs.kde.org/show_bug.cgi?id=428789 --- Comment #2 from Pierre Nerzic --- Hi, Actually, this bug did not show as hard in the 20.12.2 appimage. Maybe it depends on the width of the video and the width of the title window? I can see two "anchor points" of the separator, about 25% to the right when the parameters are hidden, and one to the left when the video is hidden. It looks like when the window is too narrow, those anchors are not behaving well, and the parameter panel and video appears or disappears weirdly. Ok to close the bug for now, but maybe it would be better to remove the anchor points. Have a nice day and stay safe -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 435056] Safe asserts both when undoing and redoing a selection mask after copying contents
https://bugs.kde.org/show_bug.cgi?id=435056 Ahab Greybeard changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 CC||ahab.greybe...@hotmail.co.u ||k --- Comment #1 from Ahab Greybeard --- I can confirm this for the Mar 30 5.0.0-prealpha (git 783e86c) appimage. The Copy action is needed. It doesnt happen if you do a brushstroke after the freehand (or any type of) selection. -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 435076] Input level monitoring can cause Bluetooth headsets with microphones to switch to undesirable "headset" profile rather than using superior "A2DP" profile
https://bugs.kde.org/show_bug.cgi?id=435076 --- Comment #4 from Gurenko Alex --- (In reply to David Redondo from comment #3) > That would really surprise me as we are just adding a monitor stream for > every stream that's already there. > > Does the same problem happen when using pavucontrol? Yes, I just tried and same behavior occur with pavucontrol, once you open it, headset profile is activated. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 435214] New: settings ui issue
https://bugs.kde.org/show_bug.cgi?id=435214 Bug ID: 435214 Summary: settings ui issue Product: systemsettings Version: 5.21.3 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: smurtaza...@outlook.com Target Milestone: --- Created attachment 137229 --> https://bugs.kde.org/attachment.cgi?id=137229&action=edit image Title over appearance is not there. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 435056] Safe asserts both when undoing and redoing a selection mask after copying contents
https://bugs.kde.org/show_bug.cgi?id=435056 Halla Rempt changed: What|Removed |Added CC||ha...@valdyas.org --- Comment #2 from Halla Rempt --- Strange... I must be doing something wrong, since I cannot reproduce this. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 434601] Assert on switching visibility
https://bugs.kde.org/show_bug.cgi?id=434601 --- Comment #3 from Ahab Greybeard --- With the Mar 30 5.0.0-prealpha (git 783e86c) appimage, I tried adding File layers, paint layers, moving layers, opening file layers, etc in various combinations but I don't get a crash or an assert in the log. -- You are receiving this mail because: You are watching all bug changes.
[Planet KDE] [Bug 359816] After opening notebook part of windows hide under task bar if they are maximized
https://bugs.kde.org/show_bug.cgi?id=359816 --- Comment #3 from Damian --- (In reply to Justin Zobel from comment #1) > Thank you for the bug report. > > As this report hasn't seen any changes in 5 years or more, we ask if you can > please confirm that the issue still persists. > > If this bug is no longer persisting or relevant please change the status to > resolved. I can not reproduce problem, because I do not have openSUSE now. Currently I use Fedora (with KDE) and problem do not appears. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 435204] Krita 4.4.4 wont's save file(happens at random)
https://bugs.kde.org/show_bug.cgi?id=435204 --- Comment #2 from stephen --- (In reply to Tiar from comment #1) > Can you please attach the content of Help -> Show Krita log for bug reports? > And please do tell how was your work (the one you lost progress in) called. Here's the log data ! --- WARNING: The Krita usage log file doesn't exist.File name and location: C:/Users/Yed/AppData/Local/krita.log Krita Version: 4.4.4-alpha (git 7d4dcb1) Qt Version (compiled): 5.12.9 Version (loaded): 5.12.9 OS Information Build ABI: x86_64-little_endian-llp64 Build CPU: x86_64 CPU: x86_64 Kernel Type: winnt Kernel Version: 10.0.18363 Pretty Productname: Windows 10 (10.0) Product Type: windows Product Version: 10 OpenGL Info Vendor: "Google Inc." Renderer: "ANGLE (NVIDIA GeForce GT 640M Direct3D11 vs_5_0 ps_5_0)" Version: "OpenGL ES 3.0 (ANGLE 2.1.0.57ea533f79a7)" Shading language: "OpenGL ES GLSL ES 3.00 (ANGLE 2.1.0.57ea533f79a7)" Requested format: QSurfaceFormat(version 3.0, options QFlags(DeprecatedFunctions), depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::DoubleBuffer, swapInterval 0, colorSpace QSurfaceFormat::DefaultColorSpace, profile QSurfaceFormat::CompatibilityProfile) Current format:QSurfaceFormat(version 3.0, options QFlags(), depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, stencilBufferSize 8, samples 0, swapBehavior QSurfaceFormat::DefaultSwapBehavior, swapInterval 0, colorSpace QSurfaceFormat::DefaultColorSpace, profile QSurfaceFormat::NoProfile) Version: 3.0 Supports deprecated functions false is OpenGL ES: true QPA OpenGL Detection Info supportsDesktopGL: true supportsAngleD3D11: true isQtPreferAngle: true Hardware Information Memory: 9 Gb Cores: 4 Swap: C:/Users/Yed/AppData/Local/Temp --- The work was called : A5_P03A_450ppi_new.kra It's the file for a comic page. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 435144] Brush size reverts back to its original if I make any change in brush settings
https://bugs.kde.org/show_bug.cgi?id=435144 Ahab Greybeard changed: What|Removed |Added CC||ahab.greybe...@hotmail.co.u ||k --- Comment #1 from Ahab Greybeard --- I don't see this happening in the Mar 30 5.0.0-prealpha (git 7783e86c) appimage with the Basic-2 Opacity brush preset. I tried making various change sand also saving as a new preset. The brush size stayed at whatever I'd changed it to. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 435120] Data protection: Removing or editing annotation metadata (author, date, time) should be possible
https://bugs.kde.org/show_bug.cgi?id=435120 --- Comment #19 from 2wxsy5823...@opayq.com --- (In reply to Rainer Klute from comment #18) > A controller who has to stick to the GDPR may only deploy software that > allows him to process personal data in a GDPR-compliant way. > setting the author before editing is a viable way to go > I haven’t found any option to “change the date before annotating” Are you able to find any software or method which allows you to remove or edit the annotation metadata? If no, does that mean you cannot process PDF files (or cannot do any annotation)? Also, if "a controller who has to stick to the GDPR may only deploy software that allows him to process personal data in a GDPR-compliant way", does that mean they cannot use closed-source software? How can they ensure that the closed-source software they are using have no backdoor and telemetry? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 433866] Krita GUI Main Window disappears after Krita is initiated and finishes 'Loading Main Window'. This condition arose after I did a Microsoft Windows Updates.
https://bugs.kde.org/show_bug.cgi?id=433866 --- Comment #4 from Alfred Borg --- Situation was resolved. Thanks. On Thu, Apr 1, 2021 at 6:33 AM Bug Janitor Service wrote: > https://bugs.kde.org/show_bug.cgi?id=433866 > > Bug Janitor Service changed: > >What|Removed |Added > > > Status|NEEDSINFO |RESOLVED > Resolution|WAITINGFORINFO |WORKSFORME > > --- Comment #3 from Bug Janitor Service --- > This bug has been in NEEDSINFO status with no change for at least > 30 days. The bug is now closed as RESOLVED > WORKSFORME > due to lack of needed information. > > For more information about our bug triaging procedures please read the > wiki located here: > https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging > > Thank you for helping us make KDE software even better for everyone! > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwindowsystem] [Bug 435212] Dead keys do not work properly in combination with control characters like shift, ctrl, alt (X11)
https://bugs.kde.org/show_bug.cgi?id=435212 --- Comment #1 from Eduardo --- Additional testing: Fedora 33 KDE, no issues with "dead" keys. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 435161] Baloo crashes with ASSERT in metadatamover.cpp
https://bugs.kde.org/show_bug.cgi?id=435161 --- Comment #3 from tagwer...@innerjoin.org --- Not sure whether this is related... It's a glitch I get "every so often". When I've missed capturing it, I've not found a way of reproducing it... cd ~/Documents mkdir temp echo "Hello Penguin" > temp/file1.txt balooshow -x temp/file1.txt gave: 144da0fc01 64513 1330592 temp/file1.txt [/home/test/.kde/share/config/kdeglobals] Mtime: 1617136526 2021-03-30T22:35:26 Ctime: 1617136526 2021-03-30T22:35:26 Cached properties: Line Count: 158 Internal Info Terms: 0 0.025 ... Mplain Mtext T5 T8 X20-158 activebackground activeblend activeforeground backgroundalternate backgroundnormal ... widgetstyle window wm File Name Terms: Fkdeglobals XAttr Terms: lineCount: 158 That is, the details of something else completely (a different file, indexed at a different time). "Balooctl monitor" did not show "file1.txt" being indexed. After a reboot I get the more expected: 144da0fc01 64513 1330592 temp/file1.txt [/home/test/Documents/temp/file1.txt] Mtime: 1617270546 2021-04-01T11:49:06 Ctime: 1617270546 2021-04-01T11:49:06 Cached properties: Line Count: 1 Internal Info Terms: Mplain Mtext T5 T8 X20-1 hello penguin File Name Terms: Ffile1 Ftxt XAttr Terms: lineCount: 1 I was hoping to be able to snapshot/clone the "confused" system, seemingly not this time though :-( It may be that if such a "confused" system is referencing a directory rather than a file then you might get such an assert Neon Unstable Plasma: 5.21.80 Frameworks: 5.81.0 Qt: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 435161] Baloo crashes with ASSERT in metadatamover.cpp
https://bugs.kde.org/show_bug.cgi?id=435161 --- Comment #4 from tagwer...@innerjoin.org --- Had to trim the list of terms in the previous post as the full list looked too much like spam. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 434180] Focus follows mouse on Wayland does not work, even between native Wayland apps (Focus under mouse works)
https://bugs.kde.org/show_bug.cgi?id=434180 k...@ashka.me changed: What|Removed |Added CC||k...@ashka.me -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 435109] Mouse pointer highlighter is distracting and could use a visual overhaul
https://bugs.kde.org/show_bug.cgi?id=435109 --- Comment #1 from postix --- I not necessarily meant to replace it, but to have an alternative, which is less distracting. The current one may have the advantage that by it's moving parts really catches the attention and the dark/bright circle makes it visible on both bright/dark backgrounds. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 435215] New: Tooltips are not affected by dark theme
https://bugs.kde.org/show_bug.cgi?id=435215 Bug ID: 435215 Summary: Tooltips are not affected by dark theme Product: kdevelop Version: 5.6.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: All editors Assignee: kdevelop-bugs-n...@kde.org Reporter: mato...@arcor.de Target Milestone: --- SUMMARY Using both a dark color theme and a dark text color theme, the tooltips appearing when hovering underlined text still use the default light color theme. STEPS TO REPRODUCE 1. Use breeze dark as color theme 2. Use breeze dark as text color theme 3. Have some code that gets underlined by code inspection 4. Hover that code OBSERVED RESULT See a white tooltip EXPECTED RESULT Tooltip has dark background SOFTWARE/OS VERSIONS Linux/KDE Plasma: Ubuntu 20.04 and Manjaro KDE Plasma Version: 5.18.5 and 5.21.3 KDE Frameworks Version: 5.68.0 and 5.80.0 Qt Version: 5.12.8 and 5.15.2 KDevelop Version: 5.5.0 and 5.6.2 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 422426] Implement Wayland Primary Selection Protocol bridge with XWayland
https://bugs.kde.org/show_bug.cgi?id=422426 Alex changed: What|Removed |Added CC||alex...@protonmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 435190] plasmashell crash on Wayland when opening Thunderbird blog entry
https://bugs.kde.org/show_bug.cgi?id=435190 --- Comment #4 from pyro4h...@gmail.com --- Glad I'm not alone, thanks Alex for confirming and providing a debug log. I have absolutely no idea if this is related, just looks to me like a double free. In Alex's log the IDs 199 and 250 are deleted twice just before the first "The Wayland connection broke" message [4107345.962] wl_display@1.delete_id(250) [4107358.380] wl_display@1.delete_id(199) [4107358.418] wl_callb...@199.done(13707024) [4107358.602] wl_callb...@250.done(8458) [4107359.103] wl_display@1.delete_id(250) [4107375.310] wl_display@1.delete_id(199) [4107375.361] wl_callb...@199.done(13707041) [4107831.124] wl_callb...@250.done(8458) [4107831.198] wl_buffer@201.release() [4107831.730] -> wl_surface@95.frame(new id wl_callback@199) [4107831.796] -> wl_surface@95.attach(wl_buffer@201, 0, 0) [4107831.870] -> wl_surface@95.damage(0, 0, 2147483647, 2147483647) [4107831.941] -> wl_surface@95.commit() [4107831.964] -> wl_disp...@1.sync(new id wl_callback@250) The Wayland connection broke. Did the Wayland compositor die? -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 435216] New: With the latest update my server is running at 100% and memory is growing 2MB per second
https://bugs.kde.org/show_bug.cgi?id=435216 Bug ID: 435216 Summary: With the latest update my server is running at 100% and memory is growing 2MB per second Product: Akonadi Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: major Priority: NOR Component: server Assignee: kdepim-b...@kde.org Reporter: a...@cryptomilk.org Target Milestone: --- SUMMARY With the latest update to version 20.12.3 on openSUSE Tumbleweed, akonadiserver started to run at 100% on one CPU core and my memory is growing ~2MB per second. I've tried heaptrack -p $(pidof akonadiserver) but it is directly crashing my akonadiserver. OBSERVED RESULT Server running at 100% and growing memory (2MB/s) EXPECTED RESULT Should use just a tiny bit of my CPU and not grow memory. SOFTWARE/OS VERSIONS Linux/KDE Plasma: openSUSE Tumbleweed with Plasma 5.21.3 (available in About System) KDE Plasma Version: 5.21.3 KDE Frameworks Version: 20.12.3 Qt Version: 5.15.2 ADDITIONAL INFORMATION I'm @asn:matrix.org or asn[m] on Freenode IRC. I would appreciate help how to debug this. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 421780] Most ways of scrolling a document not working (Qt 5.15)
https://bugs.kde.org/show_bug.cgi?id=421780 --- Comment #20 from David Hurka --- Thanks! No fails related to QScroller visible. But what’s with “parttest”? ctest didn’t run it, or cmake didn’t compile it? Maybe we can try to look at internal values of QScroller. You will need to install debugging symbols for (at least) Qt5 and Okular. On ubuntu, they are called: libqt5core5a-dbgsym, libqt5gui5-dbgsym, libqt5widgets5-dbgsym, okular-dbgsym. I don’t know how Gentoo works, possible that you don’t need them. Then run: > $ gdb okular > (gdb) set pagination off > (gdb) run > no open a document in Okular and reproduce the bug > ^C (hit Ctrl+C) > (gdb) breakpoint QScroller::scrollTo > (gdb) continue > now reproduce the bug > (gdb) print -pretty on -- *this->d_ptr I will look later at QScroller to see what these values mean. ;) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 430098] Alt + Resize or Move and window focus
https://bugs.kde.org/show_bug.cgi?id=430098 Aldoo changed: What|Removed |Added CC||aldo-pub...@laposte.net --- Comment #1 from Aldoo --- I would like to add that current behavior disrupts a very classical workflow: 1. you work on window1, maximized on your main screen (or just taking a lot of room on your only screen, if you are in a single monitor setup) 2. you want to switch to another task (window2), currently on your secondary screen (or maybe a small window on your main screen) 3. so you alt-grab window2 and move it to the most comfortable place (i.e. maximized on the main screen), most of the time reaching for the screen top edge so that window2 is maximized in the process. So you expect to have a readily usable full screen window for the new active task, but instead, the window of the task you want to switch to is hidden behind the window of your previous task. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 435179] face write to database with wrong user (''@'%') MariaDB backend
https://bugs.kde.org/show_bug.cgi?id=435179
--- Comment #18 from gessel ---
Sure, since it works with the user ''@'%' and working is better than secure,
the current state is :
Current database: digikam
+--+
| Grants for gessel@%
|
+--+
| GRANT ALL PRIVILEGES ON *.* TO `gessel`@`%` IDENTIFIED BY PASSWORD
'*' WITH GRANT OPTION |
+--+
1 row in set (0.004 sec)
Current database: digikam
+-+
| Grants for @% |
+-+
| GRANT USAGE ON *.* TO ``@`%`|
| GRANT ALL PRIVILEGES ON `digikam`.* TO ``@`%` WITH GRANT OPTION |
+-+
So to test:
MariaDB [digikam]> DROP USER ``@`%`;
MariaDB [digikam]> flush privileges;
MariaDB [digikam]> show grants for ''@'%';
ERROR 1141 (42000): There is no such grant defined for user '' on host '%'
And...
digikam.database: Creating new tag for name "TT" fullName "TT"
digikam.dbengine: Failure executing query:
"INSERT INTO Tags (pid, name) VALUES( ?, ?);"
Error messages: "QMYSQL3: Unable to execute statement" "The user specified as a
definer (''@'%') does not exist" "1449" 2
Bound values: (QVariant(int, 4), QVariant(QString, "Tony Thomas"))
digikam.dbengine: Error while executing DBAction [ "InsertTag" ] Statement [
"INSERT INTO Tags (pid, name) VALUES( :tagPID, :tagname);" ]
digikam.database: Attempt to create tag properties for tag id 0
digikam.general: Failed to get person tag
(as before, consistency is good.)
MariaDB [digikam]> GRANT TRIGGER ON digikam.* TO 'gessel'@'localhost';
Query OK, 0 rows affected (0.000 sec)
MariaDB [digikam]> flush privileges;
MariaDB [digikam]> show grants for 'gessel'@'localhost';
++
| Grants for gessel@localhost
|
++
| GRANT ALL PRIVILEGES ON *.* TO `gessel`@`localhost` IDENTIFIED BY PASSWORD
'*51A4B3BD9F7DFD67D84ED8C045C952264A901F4C' |
| GRANT TRIGGER ON `digikam`.* TO `gessel`@`localhost`
|
++
Initial test, no change, restart digikam and...
digikam.database: Creating new tag for name "TT" fullName "TT"
digikam.dbengine: Failure executing query:
"INSERT INTO Tags (pid, name) VALUES( ?, ?);"
Error messages: "QMYSQL3: Unable to execute statement" "The user specified as
a definer (''@'%') does not exist" "1449" 2
Bound values: (QVariant(int, 4), QVariant(QString, "Tony Thomas"))
digikam.dbengine: Error while executing DBAction [ "InsertTag" ] Statement [
"INSERT INTO Tags (pid, name) VALUES( :tagPID, :tagname);" ]
digikam.database: Attempt to create tag properties for tag id 0
digikam.general: Failed to get person tag
No improvements... so add a few more grants to extend the user class:
MariaDB [digikam]> GRANT TRIGGER ON digikam.* TO 'gessel'@'127.0.0.1';
MariaDB [digikam]> GRANT TRIGGER ON digikam.* TO 'gessel'@'%';
MariaDB [digikam]> flush privileges;
still no change:
digikam.database: Creating new tag for name "TT" fullName "TT"
digikam.dbengine: Failure executing query:
"INSERT INTO Tags (pid, name) VALUES( ?, ?);"
Error messages: "QMYSQL3: Unable to execute statement" "The user specified as
a definer (''@'%') does not exist" "1449" 2
Bound values: (QVariant(int, 4), QVariant(QString, "Tony Thomas"))
digikam.dbengine: Error while executing DBAction [ "InsertTag" ] Statement [
"INSERT INTO Tags (pid, name) VALUES( :tagPID, :tagname);" ]
digikam.database: Attempt to create tag properties for tag id 0
digikam.general: Failed to get person tag
Now add back user ''@'%' and see:
MariaDB [digikam]> CREATE USER ``@`%` IDENTIFIED BY '';
Query OK, 0 rows affected (0.004 sec)
MariaDB [digikam]> GRANT ALL ON digikam.* TO ''@'%' IDENTIFIED BY '' WITH
GRANT OPTION;
Query OK, 0 rows affected (0.000 sec)
MariaDB [digikam]> FLUSH PRIVILEGES;
Person tag successfully created.
--
You are receiving th
[Powerdevil] [Bug 435217] New: Send notification when the battery is charged to a certain level
https://bugs.kde.org/show_bug.cgi?id=435217 Bug ID: 435217 Summary: Send notification when the battery is charged to a certain level Product: Powerdevil Version: unspecified Platform: unspecified OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: n...@web.de Target Milestone: --- It is not good for batteries when they are fully charged. In order not to forget to remove the charger, it would be good if a notification is sent when the battery is charged to a certain level (like if the battery should be charged, but with the message that you should remove the charger). -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 421780] Most ways of scrolling a document not working (Qt 5.15)
https://bugs.kde.org/show_bug.cgi?id=421780 --- Comment #21 from abulhair.sapa...@gmail.com --- Apparently parttest seems to have been excluded by Gentoo (https://bugs.gentoo.org/641728), along with mainshelltest, chmgeneratortest, parttest, and annotationtoolbartest. Sure I'll try running okular with gdb now. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 421780] Most ways of scrolling a document not working (Qt 5.15)
https://bugs.kde.org/show_bug.cgi?id=421780 --- Comment #22 from David Hurka --- Mistake: Instead of this: >breakpoint QScroller::scrollTo it is called this: >break QScroller::scrollTo(QPointF const&, int) -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 421780] Most ways of scrolling a document not working (Qt 5.15)
https://bugs.kde.org/show_bug.cgi?id=421780 --- Comment #23 from abulhair.sapa...@gmail.com --- Created attachment 137231 --> https://bugs.kde.org/attachment.cgi?id=137231&action=edit gdb output For some reason there wasn't a symbol 'this' in the QScroller::scrollTo frame (maybe I didn't correctly compile with debug symbols), but I went one frame up to PageView::slotScrollDown (okular-20.12.3/part/pageview.cpp:4831) and did 'print -pretty on -- *d->scroller->d_ptr'. The output of this command is attached. The breakpoint fired when I tried to scroll down with the mouse wheel. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 421780] Most ways of scrolling a document not working (Qt 5.15)
https://bugs.kde.org/show_bug.cgi?id=421780 --- Comment #24 from abulhair.sapa...@gmail.com --- (In reply to David Hurka from comment #22) > Mistake: Instead of this: > > >breakpoint QScroller::scrollTo > it is called this: > > >break QScroller::scrollTo(QPointF const&, int) Ah this worked but the output is the same as before (aside from some differences in pointers in 'xSegments'). -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 435218] New: Double sharing tab in folder properties
https://bugs.kde.org/show_bug.cgi?id=435218 Bug ID: 435218 Summary: Double sharing tab in folder properties Product: dolphin Version: 20.04.2 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: panels: folders Assignee: dolphin-bugs-n...@kde.org Reporter: boscoro...@katamail.com CC: kfm-de...@kde.org Target Milestone: --- Created attachment 137232 --> https://bugs.kde.org/attachment.cgi?id=137232&action=edit Share tabs in folder properties SUMMARY When checking the properties of a folder there are 2 tabs named 'Share' one of which is empty. STEPS TO REPRODUCE 1. Open Dolphin then right click a folder or use ALT+Return 2. Select properties 3. Check the share tabs OBSERVED RESULT One of the 2 share tabs has no choices and it is totally empty EXPECTED RESULT There should be only one share tab in folder properties. SOFTWARE/OS VERSIONS Linux/KDE Plasma: OpenSUSE Leap 15.3 beta/ KDE Plasma Version: 5.18.6 KDE Frameworks Version: 5.76.0 Qt Version: 5.12.7 ADDITIONAL INFORMATION Operating System: openSUSE Leap 15.3 KDE Plasma Version: 5.18.6 KDE Frameworks Version: 5.76.0 Qt Version: 5.12.7 Kernel Version: 5.3.18-52-default OS Type: 64-bit Processors: 4 × Intel® Core™ i5 CPU M 520 @ 2.40GHz Memory: 3,7 GiB -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 435218] Double share tab in folder properties
https://bugs.kde.org/show_bug.cgi?id=435218 boscorosso changed: What|Removed |Added Summary|Double sharing tab in |Double share tab in folder |folder properties |properties -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 421780] Most ways of scrolling a document not working (Qt 5.15)
https://bugs.kde.org/show_bug.cgi?id=421780 --- Comment #25 from abulhair.sapa...@gmail.com --- Actually I think I may have inadvertently fixed my issue. I tried recompiling all of qtcore, qtwidgets, and okular with debug symbols as well as disabling all optimization and now it's scrolling correctly! I suspect it's one of the optimizations causing the bug. Give me some time to tinker and find exactly which one. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 429883] Faulty Fill pattern when importing for a Fill Layer
https://bugs.kde.org/show_bug.cgi?id=429883 Halla Rempt changed: What|Removed |Added Latest Commit||https://invent.kde.org/grap ||hics/krita/commit/741df3a86 ||41a072e676c48dfb0febb2b2858 ||ae00 Resolution|--- |FIXED Status|ASSIGNED|RESOLVED --- Comment #1 from Halla Rempt --- Git commit 741df3a8641a072e676c48dfb0febb2b2858ae00 by Halla Rempt. Committed on 01/04/2021 at 12:35. Pushed by rempt into branch 'master'. Set the name on the resource from the database Because many resources use the filename directly for the name, and the filename now is versioned, and we don't want the versioned filename used as the name. This fixes importing a resource and using it in a pattern fill layer. M +5-2libs/resources/KisResourceLocator.cpp https://invent.kde.org/graphics/krita/commit/741df3a8641a072e676c48dfb0febb2b2858ae00 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 435202] Newly imported images do not show in database
https://bugs.kde.org/show_bug.cgi?id=435202 --- Comment #3 from vaarti...@gmail.com --- Database is SQLite. It is hosted on my main system drive, which is an SSD. (C:\Users\vaart\OneDrive\Pictures\) My single Collection (huge) is hosted on a NAS (system hosting digiKam and NAS are both hard connected to router (non-wifi) Performance from NAS is reasonably quick under normal circumstances. DebugView log attached. Some notes:: I rebooted the system, and started debug and then digiKam off the fresh reboot. I did not have any other programs running. Find New Items task started upon opening digiKam, and it was nearly 10 minutes before it actually showed status above 0%. I let it run until completed, which took approximately 20 minutes to complete. I did open up the settings dialog during this process to get the answers for where the database was hosted, in case you see that in the debug log. Once there were no active processes, I attached a memory card and imported a single raw photo into an album.(Z:/Photos/2021/Raw/Astro/) Find new items scan started. My photo finally appeared in the album after 6 minutes. The find new times progress remained at 0% even after my photo appeared in the album, and remained at 0% for about 12 minutes until disappearing. I didn't notice the progress change, I just saw the process status disappear. I hope this information helps. Thanks for helping me figure this out. I am new to digiKam. I tried to ask this in the users list, but I got no response. On Wed, Mar 31, 2021 at 9:24 PM wrote: > https://bugs.kde.org/show_bug.cgi?id=435202 > > caulier.gil...@gmail.com changed: > >What|Removed |Added > > > CC||caulier.gil...@gmail.com > > --- Comment #1 from caulier.gil...@gmail.com --- > Which kind of database type did you use ? > > Sqlite ? Mysql interanm ? Mysql or MariaDb server ? > > Where is hosted your database ? Which settings do you use exactly ? > > Can you provide a Debuview trace while digiKam is running ? Look details in > contribute page for details : > > https://www.digikam.org/contribute/ > > Gilles Caulier > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 435191] Loading the wrong keyboard layout
https://bugs.kde.org/show_bug.cgi?id=435191 --- Comment #5 from Andrey --- Could you please check if the last used layout restores for you on Wayland when "Restore last session" is set? -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 435198] Discover crashes while calculating available updates after selecting updates notification in system tray
https://bugs.kde.org/show_bug.cgi?id=435198 Dan Leinir Turthra Jensen changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED CC||ad...@leinir.dk --- Comment #1 from Dan Leinir Turthra Jensen --- Thank you for reporting it - it's a duplicate, but the extra backtrace gave some more context to the investigation, which is always useful :) *** This bug has been marked as a duplicate of bug 433807 *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knewstuff] [Bug 433807] crashes after clicking on the button in the notification
https://bugs.kde.org/show_bug.cgi?id=433807 Dan Leinir Turthra Jensen changed: What|Removed |Added CC||dequ...@mykolab.com --- Comment #3 from Dan Leinir Turthra Jensen --- *** Bug 435198 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[picmi] [Bug 435211] Picmi wrongly calls a single black cell correct when there should be two
https://bugs.kde.org/show_bug.cgi?id=435211 Jakob Gruber changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #1 from Jakob Gruber --- I can repro, this is a bug. (Not sure when I'll get around to fixing it, patches welcome.) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 435202] Newly imported images do not show in database
https://bugs.kde.org/show_bug.cgi?id=435202 --- Comment #4 from caulier.gil...@gmail.com --- Please post the full debugview trace for a better investigation... -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 405891] Show "Downloading" instead of "Installing" while Discover downloads updates and replace the download speed with the percentage of the installation proccess while the updates ar
https://bugs.kde.org/show_bug.cgi?id=405891 Alex changed: What|Removed |Added CC||alex...@protonmail.com -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 405891] Show "Downloading" instead of "Installing" while Discover downloads updates and replace the download speed with the percentage of the installation proccess while the updates ar
https://bugs.kde.org/show_bug.cgi?id=405891 --- Comment #1 from Alex --- Now that Neon has offline updates, this is more noticeable. Discover says its installing updates, when its really just downloading them. Also, the progress bar only fills to 50%, I assume the other 50% is for the installation which never happens during that session. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 435202] Newly imported images do not show in database
https://bugs.kde.org/show_bug.cgi?id=435202 --- Comment #5 from vaarti...@gmail.com --- I attached the debug capture log to my last response... what more do you need? I don't understand. On Thu, Apr 1, 2021 at 9:18 AM wrote: > https://bugs.kde.org/show_bug.cgi?id=435202 > > --- Comment #4 from caulier.gil...@gmail.com --- > Please post the full debugview trace for a better investigation... > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knewstuff] [Bug 434325] Discover intermittently crashes in KNSCore::Engine::addProvider() when opening the Settings view
https://bugs.kde.org/show_bug.cgi?id=434325 Dan Leinir Turthra Jensen changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Dan Leinir Turthra Jensen --- Thanks for the report! While you describe arriving at the issue differently to the one of which i'm marking this down as a duplicate, the backtrace is the same, which tells us it's the same base cause - thank you for checking first, even if you didn't find the other report, it's very much appreciated :) *** This bug has been marked as a duplicate of bug 433807 *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knewstuff] [Bug 433807] crashes after clicking on the button in the notification
https://bugs.kde.org/show_bug.cgi?id=433807 --- Comment #4 from Dan Leinir Turthra Jensen --- *** Bug 434325 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 435191] Loading the wrong keyboard layout
https://bugs.kde.org/show_bug.cgi?id=435191 Domenico Panella changed: What|Removed |Added Resolution|NOT A BUG |--- Status|RESOLVED|REOPENED Ever confirmed|0 |1 --- Comment #6 from Domenico Panella --- (In reply to Andrey from comment #5) > Could you please check if the last used layout restores for you on Wayland > when "Restore last session" is set? I checked that, on Wayland it restore fine while on X11 not restore last layout setted. Moreover, i set "Start new session" with these layout: English (us) (top) Italian (it). I expected the English keyboard layout set while the italian is set instead. Anyway, on X11 it not works properly as Wayland. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 435191] Loading the wrong keyboard layout
https://bugs.kde.org/show_bug.cgi?id=435191 --- Comment #7 from Domenico Panella --- According you, where is the problem? i see plasma-desktop/applets/keyboardlayout (is it plasmoid?) , plasma-workspace/components/keyboardlayout or anything else ? I could check that if you guide me. -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 433258] Network system monitor doesn't work for network bridges
https://bugs.kde.org/show_bug.cgi?id=433258 miklos changed: What|Removed |Added CC||mtm...@gmail.com --- Comment #2 from miklos --- It doesn't measure anything even if you don't have a bridge. 5.19 worked fine, 5.20 is broken. Tried with Deian Bullseye, and Fedora 33. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 435202] Newly imported images do not show in database
https://bugs.kde.org/show_bug.cgi?id=435202 --- Comment #6 from caulier.gil...@gmail.com --- Oups, i do not the the file attachments... Sorry. I do not see a dysfunction in traces... Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 435192] Certain System Monitor widget display styles crash Plasma Shell when selecting another display style
https://bugs.kde.org/show_bug.cgi?id=435192 --- Comment #2 from Marco Martin --- looking at the code seems to be an upstream qt bug. What seems to happen is that in the destructor of that dialog, void QQuickContainerPrivate::cleanup() gets called, and *after* that, QQuickDialogButtonBoxPrivate::getContentWidth() gets called (QQuickDialogButtonBoxPrivate is a QQuickContainerPrivate instance) trying to call contentModel->count() where contentModel was deleted in QQuickContainerPrivate::cleanup() -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 420623] "Counter" generated resource cannot be archived with project
https://bugs.kde.org/show_bug.cgi?id=420623 Julius Künzel changed: What|Removed |Added Latest Commit||https://invent.kde.org/mult ||imedia/kdenlive/commit/0329 ||427786a3e804c60bc23b2b20995 ||06eb4a9fc Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #1 from Julius Künzel --- Git commit 0329427786a3e804c60bc23b2b2099506eb4a9fc by Julius Künzel. Committed on 01/04/2021 at 13:55. Pushed by jlskuz into branch 'release/21.04'. Fix archiving for generator mlt clips M +1-1src/project/dialogs/projectsettings.cpp https://invent.kde.org/multimedia/kdenlive/commit/0329427786a3e804c60bc23b2b2099506eb4a9fc -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 420623] "Counter" generated resource cannot be archived with project
https://bugs.kde.org/show_bug.cgi?id=420623 Julius Künzel changed: What|Removed |Added CC||jk.kde...@smartlab.uber.spa ||ce --- Comment #2 from Julius Künzel --- Thanks for your report! You're patch seems to be almost the best solution, but I decided to solve it slightly different, because we have the same problem with all generators. However your work made it much easier for my to find the problem and fix it! P.S.: If you suggest code changes/patches it would be easier for the team to review if you open a merge request on https://invent.kde.org/multimedia/kdenlive -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 435192] Certain System Monitor widget display styles crash Plasma Shell when selecting another display style
https://bugs.kde.org/show_bug.cgi?id=435192 Marco Martin changed: What|Removed |Added CC||byteena...@outlook.com --- Comment #3 from Marco Martin --- *** Bug 435053 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 435053] System Monitor crashes in KSysGuard::SensorFace>::~QQmlElement()
https://bugs.kde.org/show_bug.cgi?id=435053 Marco Martin changed: What|Removed |Added Status|REPORTED|RESOLVED CC||notm...@gmail.com Resolution|--- |DUPLICATE --- Comment #1 from Marco Martin --- *** This bug has been marked as a duplicate of bug 435192 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 435192] Certain System Monitor widget display styles crash Plasmashell in KSysGuard::SensorFace>::~QQmlElement() when selecting another display style
https://bugs.kde.org/show_bug.cgi?id=435192 Nate Graham changed: What|Removed |Added CC||n...@kde.org Summary|Certain System Monitor |Certain System Monitor |widget display styles crash |widget display styles crash |Plasma Shell when selecting |Plasmashell in |another display style |KSysGuard::SensorFace>::~QQ ||mlElement() when selecting ||another display style -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 435042] kwin_wayland segfaults while recording via pipewire if mouse hovers over (close) button of window
https://bugs.kde.org/show_bug.cgi?id=435042 smit changed: What|Removed |Added CC||smit1...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdenetwork-filesharing] [Bug 427772] Installing kdenetwork-filesharing results in two "Share" tabs in Dolphin
https://bugs.kde.org/show_bug.cgi?id=427772 Nate Graham changed: What|Removed |Added CC||boscoro...@katamail.com --- Comment #11 from Nate Graham --- *** Bug 435218 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 435218] Double share tab in folder properties
https://bugs.kde.org/show_bug.cgi?id=435218 Nate Graham changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED CC||n...@kde.org --- Comment #1 from Nate Graham --- *** This bug has been marked as a duplicate of bug 427772 *** -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 435076] Input level monitoring can cause Bluetooth headsets with microphones to switch to undesirable "headset" profile rather than using superior "A2DP" profile
https://bugs.kde.org/show_bug.cgi?id=435076 Nate Graham changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |UPSTREAM --- Comment #5 from Nate Graham --- Fascinating. That suggests that the problem is somewhere in PulseAudio itself. Can you please file a bug report for the PulseAudio folks at https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/? Thanks! -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 426962] Dolphin crashes in KFileItemModel::slotClear() / DolphinView::setUrl() when navigating remote folders
https://bugs.kde.org/show_bug.cgi?id=426962 Nate Graham changed: What|Removed |Added CC||prco...@gmail.com --- Comment #7 from Nate Graham --- *** Bug 435209 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 435209] Probably Dolphin kio-gdrive crash when unpausing file copy operation
https://bugs.kde.org/show_bug.cgi?id=435209 Nate Graham changed: What|Removed |Added Status|REPORTED|RESOLVED CC||n...@kde.org Resolution|--- |DUPLICATE --- Comment #1 from Nate Graham --- *** This bug has been marked as a duplicate of bug 426962 *** -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 426962] Dolphin crashes in KFileItemModel::slotClear() / DolphinView::setUrl() when navigating remote folders
https://bugs.kde.org/show_bug.cgi?id=426962 Nate Graham changed: What|Removed |Added CC||jens-bugs.kde.org@spamfreem ||ail.de --- Comment #8 from Nate Graham --- *** Bug 433526 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 433526] Crash after adding filetype when changing partitions
https://bugs.kde.org/show_bug.cgi?id=433526 Nate Graham changed: What|Removed |Added CC||n...@kde.org Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Nate Graham --- *** This bug has been marked as a duplicate of bug 426962 *** -- You are receiving this mail because: You are watching all bug changes.
