[digikam] [Bug 113914] Image permissions are restricted after saving.
https://bugs.kde.org/show_bug.cgi?id=113914 caulier.gil...@gmail.com changed: What|Removed |Added Version Fixed In||7.5.0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 168461] info in Properties panel not updated after moving to other image
https://bugs.kde.org/show_bug.cgi?id=168461 caulier.gil...@gmail.com changed: What|Removed |Added Version Fixed In||7.5.0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 155407] "Save as" diaglog is quite small in the image editor
https://bugs.kde.org/show_bug.cgi?id=155407 caulier.gil...@gmail.com changed: What|Removed |Added Version Fixed In||7.5.0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 181930] slider for resizing does not work, i.e.shows either 1 or some extremely high number
https://bugs.kde.org/show_bug.cgi?id=181930 caulier.gil...@gmail.com changed: What|Removed |Added Version Fixed In||7.5.0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 97777] images pixelated after edit and save
https://bugs.kde.org/show_bug.cgi?id=9 caulier.gil...@gmail.com changed: What|Removed |Added Version Fixed In||7.5.0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 154526] big screen size lead to small picture in main window and editor
https://bugs.kde.org/show_bug.cgi?id=154526 caulier.gil...@gmail.com changed: What|Removed |Added Version Fixed In||7.5.0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 126165] meta-bug for digikam editor tool release (digikam devels only)
https://bugs.kde.org/show_bug.cgi?id=126165 caulier.gil...@gmail.com changed: What|Removed |Added Version Fixed In||7.5.0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 98457] imageeditorf: bind 'home' and 'end' to goto first/last image
https://bugs.kde.org/show_bug.cgi?id=98457 caulier.gil...@gmail.com changed: What|Removed |Added Version Fixed In||7.5.0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 114069] digikam save-as empty filename field
https://bugs.kde.org/show_bug.cgi?id=114069 caulier.gil...@gmail.com changed: What|Removed |Added Version Fixed In||7.5.0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 111695] single click to open image editor is really annoying when tagging
https://bugs.kde.org/show_bug.cgi?id=111695 caulier.gil...@gmail.com changed: What|Removed |Added Version Fixed In||7.5.0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 91006] wish: save width of left pane on exit
https://bugs.kde.org/show_bug.cgi?id=91006 caulier.gil...@gmail.com changed: What|Removed |Added Version Fixed In||7.5.0 Resolution|DUPLICATE |FIXED CC||caulier.gil...@gmail.com --- Comment #2 from caulier.gil...@gmail.com --- Fixed with https://bugs.kde.org/show_bug.cgi?id=91005 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 103351] multiple instances of image editor
https://bugs.kde.org/show_bug.cgi?id=103351 caulier.gil...@gmail.com changed: What|Removed |Added CC||caulier.gil...@gmail.com Version Fixed In||7.5.0 Resolution|DUPLICATE |FIXED --- Comment #2 from caulier.gil...@gmail.com --- Fixed with https://bugs.kde.org/show_bug.cgi?id=135048 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 120714] wish: Database understanding image 'mutations'
https://bugs.kde.org/show_bug.cgi?id=120714 caulier.gil...@gmail.com changed: What|Removed |Added Resolution|DUPLICATE |FIXED Version Fixed In||7.5.0 --- Comment #2 from caulier.gil...@gmail.com --- Fixed with https://bugs.kde.org/show_bug.cgi?id=103350 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 136060] Doesn't save existing comments when "save image comments as embedded text" has been activated
https://bugs.kde.org/show_bug.cgi?id=136060 caulier.gil...@gmail.com changed: What|Removed |Added Resolution|DUPLICATE |FIXED Version Fixed In||7.5.0 CC||caulier.gil...@gmail.com --- Comment #6 from caulier.gil...@gmail.com --- Fixed with https://bugs.kde.org/show_bug.cgi?id=130017 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 139075] Opening a new image from main digikam then saving changes to first image results in editor overwriting new image
https://bugs.kde.org/show_bug.cgi?id=139075 caulier.gil...@gmail.com changed: What|Removed |Added Resolution|DUPLICATE |FIXED Version Fixed In||7.5.0 CC||caulier.gil...@gmail.com --- Comment #2 from caulier.gil...@gmail.com --- Fixed with https://bugs.kde.org/show_bug.cgi?id=138620 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 160873] Feature request multicore support
https://bugs.kde.org/show_bug.cgi?id=160873 caulier.gil...@gmail.com changed: What|Removed |Added Resolution|DUPLICATE |FIXED Version Fixed In||7.5.0 --- Comment #7 from caulier.gil...@gmail.com --- Fixed with https://bugs.kde.org/show_bug.cgi?id=289204 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 187657] Showoff the most common actions
https://bugs.kde.org/show_bug.cgi?id=187657 caulier.gil...@gmail.com changed: What|Removed |Added Version Fixed In||7.5.0 Resolution|DUPLICATE |FIXED --- Comment #2 from caulier.gil...@gmail.com --- Fixed with https://bugs.kde.org/show_bug.cgi?id=174070 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 263061] Add new tool to search for watermark in collections
https://bugs.kde.org/show_bug.cgi?id=263061 caulier.gil...@gmail.com changed: What|Removed |Added Version Fixed In||7.5.0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 263061] Add new tool to search for watermark in collections
https://bugs.kde.org/show_bug.cgi?id=263061 caulier.gil...@gmail.com changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED --- Comment #2 from caulier.gil...@gmail.com --- digiKam has already options in Advanced search to find item with Creator/Author/Headline from IPTC/XMP metadata. If you tags images with this king of information, digiKam will help your to search about. There is no plan to search images with a visual watermark overlay. Best Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[marble] [Bug 448108] free(): invalid pointer
https://bugs.kde.org/show_bug.cgi?id=448108 --- Comment #2 from Laurent Bonnaud --- Running marble with valgrind gives the following (among many other) error: ==94== Invalid free() / delete / delete[] / realloc() ==94==at 0x484684F: operator delete(void*) (vg_replace_malloc.c:802) ==94==by 0x66DC4E2: QObject::event(QEvent*) (qobject.cpp:1301) ==94==by 0x4FBC0CC: KXmlGuiWindow::event(QEvent*) (kxmlguiwindow.cpp:219) ==94==by 0x57C46B2: QApplicationPrivate::notify_helper(QObject*, QEvent*) (qapplication.cpp:3632) ==94==by 0x66AF169: QCoreApplication::notifyInternal2(QObject*, QEvent*) (qcoreapplication.cpp:1063) ==94==by 0x66B2256: QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) (qcoreapplication.cpp:1817) ==94==by 0x6708EF6: postEventSourceDispatch(_GSource*, int (*)(void*), void*) (qeventdispatcher_glib.cpp:277) ==94==by 0x80108BA: UnknownInlinedFun (gmain.c:3337) ==94==by 0x80108BA: g_main_context_dispatch (gmain.c:4055) ==94==by 0x8063F07: g_main_context_iterate.constprop.0 (gmain.c:4131) ==94==by 0x800E002: g_main_context_iteration (gmain.c:4196) ==94==by 0x6708547: QEventDispatcherGlib::processEvents(QFlags) (qeventdispatcher_glib.cpp:423) ==94==by 0x66ADA9A: QEventLoop::exec(QFlags) (qeventloop.cpp:232) ==94== Address 0x1ffefff8c0 is on thread 1's stack -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 437193] Starting Digikam with defined search
https://bugs.kde.org/show_bug.cgi?id=437193 caulier.gil...@gmail.com changed: What|Removed |Added Version Fixed In||7.5.0 Resolution|--- |FIXED Status|REPORTED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 440582] Detecting black & white image
https://bugs.kde.org/show_bug.cgi?id=440582 caulier.gil...@gmail.com changed: What|Removed |Added Component|Searches|Maintenance-Quality CC||caulier.gil...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[marble] [Bug 448108] free(): invalid pointer
https://bugs.kde.org/show_bug.cgi?id=448108 --- Comment #1 from Laurent Bonnaud --- I also observe a similar behavior with the Ubuntu package: Package: marble Status: install ok installed Priority: optional Section: misc Installed-Size: 1112 Maintainer: Kubuntu Developers Architecture: amd64 Version: 4:21.12.1-0ubuntu1~ubuntu21.10~ppa1 Replaces: marble-data (<< 4:17.08.1) Depends: marble-data (>= 4:21.12.1-0ubuntu1~ubuntu21.10~ppa1), marble-plugins (= 4:21.12.1-0ubuntu1~ubuntu21.10~ppa1), kio, libc6 (>= 2.34), libgcc-s1 (>= 3.0), libkf5configcore5 (>= 4.98.0), libkf5configgui5 (>= 4.97.0), libkf5configwidgets5 (>= 4.96.0), libkf5coreaddons5 (>= 5.7.0~), libkf5crash5 (>= 5.7.0~), libkf5i18n5 (>= 5.7.0~), libkf5kiowidgets5 (>= 5.7.0~), libkf5parts5 (>= 5.7.0~), libkf5widgetsaddons5 (>= 4.96.0), libkf5xmlgui5 (>= 4.98.0), libmarblewidget-qt5-28 (= 4:21.12.1-0ubuntu1~ubuntu21.10~ppa1), libqt5core5a (>= 5.15.1), libqt5dbus5 (>= 5.7.0~), libqt5gui5 (>= 5.7.0) | libqt5gui5-gles (>= 5.7.0), libqt5network5 (>= 5.7.0~), libqt5printsupport5 (>= 5.7.0~), libqt5widgets5 (>= 5.7.0~), libqt5xml5 (>= 5.7.0~), libstdc++6 (>= 4.1.1) Suggests: gosmore, monav-routing-daemon, routino Breaks: marble-data (<< 4:17.08.1) Description: globe and map widget Marble is a generic geographical map widget and framework for KDE applications. The Marble widget shows the earth as a sphere but does not require hardware acceleration. A minimal set of geographical data is included, so it can be used without an internet connection. . This package is part of the KDE education module. Homepage: https://marble.kde.org/ Original-Maintainer: Debian Qt/KDE Maintainers -- You are receiving this mail because: You are watching all bug changes.
[marble] [Bug 448108] New: free(): invalid pointer
https://bugs.kde.org/show_bug.cgi?id=448108 Bug ID: 448108 Summary: free(): invalid pointer Product: marble Version: 21.12.1 Platform: Flatpak OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: marble-b...@kde.org Reporter: l.bonn...@laposte.net Target Milestone: --- SUMMARY marble free()s an invalid pointer on exit STEPS TO REPRODUCE 1. flatpak run org.kde.marble 2. quit marble OBSERVED RESULT $ flatpak run org.kde.marble Start: MarblePart::readSettings() Updating Settings ... kf.xmlgui: Shortcut for action "" "Hide &All Panels" set with QAction::setShortcut()! Use KActionCollection::setDefaultShortcut(s) instead. free(): invalid pointer Sometimes I also get a crash: $ flatpak run org.kde.marble Start: MarblePart::readSettings() Updating Settings ... kf.xmlgui: Shortcut for action "" "Hide &All Panels" set with QAction::setShortcut()! Use KActionCollection::setDefaultShortcut(s) instead. free(): invalid pointer KCrash: crashing... crashRecursionCounter = 2 KCrash: Application Name = marble path = /app/bin pid = 2 KCrash: Arguments: /app/bin/marble EXPECTED RESULT no invalid free and no crash SOFTWARE/OS VERSIONS $ flatpak info org.kde.marble//stable Marble - Virtual Globe ID: org.kde.marble Ref: app/org.kde.marble/x86_64/stable Arch: x86_64 Branch: stable Version: 21.12.1 License: LGPL-2.1-or-later Origin: flathub Collection: org.flathub.Stable Installation: system Installed: 237.3 MB Runtime: org.kde.Platform/x86_64/5.15-21.08 Sdk: org.kde.Sdk/x86_64/5.15-21.08 Commit: e5df76dd61ee708f4b8b7a838331fa6dcba0fa99d0ca635057fa12710d3ed2d1 Parent: 562104dc0f72eeeda48d4fc3216436bb77dbde998076e4cfbd1881a0b11e52c9 Subject: Update to 21.12.1 (0a4b16e6) Date: 2022-01-06 20:08:40 + -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 399506] Integrations with FS and Internet browser
https://bugs.kde.org/show_bug.cgi?id=399506 caulier.gil...@gmail.com changed: What|Removed |Added Component|Searches|Usability-Menus Version Fixed In||7.5.0 Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #3 from caulier.gil...@gmail.com --- Fixed with Bug 380065 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 448107] New: Pointer for the Edit Shapes tool is a small rectangle of broken lines
https://bugs.kde.org/show_bug.cgi?id=448107 Bug ID: 448107 Summary: Pointer for the Edit Shapes tool is a small rectangle of broken lines Product: krita Version: 5.0.2 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: Tools/Vector Assignee: krita-bugs-n...@kde.org Reporter: chris.k.d.w...@gmail.com Target Milestone: --- SUMMARY When the Edit Shapes tool is selected, its pointer becomes a small rectangle of broken lines. This is the problem. When the mouse is moved over a line segment, the pointer becomes a hand with pointed finger which is OK. STEPS TO REPRODUCE 1. In a vector layer, create a vector object such as a rectangle or bezier curved object. 2. Select the object and then select the Edit Shapes tool. 3. The pointer shape displayed when the mouse is on the canvas is a small rectangle of broken lines. OBSERVED RESULT Pointer shape displayed when the mouse is on the canvas is a small rectangle of broken lines. EXPECTED RESULT Pointer shape should be some proper shape instead of a pseudo-random bitmap. SOFTWARE/OS VERSIONS Windows: 10 macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION Note, this bug was also present in recent 4.4.X versions of Krita. WARNING: The system information file doesn't exist.File name and location: C:/Users/chris/AppData/Local/krita-sysinfo.log Krita Version: 5.0.2 Qt Version (compiled): 5.12.12 Version (loaded): 5.12.12 OS Information Build ABI: x86_64-little_endian-llp64 Build CPU: x86_64 CPU: x86_64 Kernel Type: winnt Kernel Version: 10.0.19044 Pretty Productname: Windows 10 (10.0) Product Type: windows Product Version: 10 OpenGL Info Vendor: "Google Inc." Renderer: "ANGLE (NVIDIA GeForce MX250 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 supportsBufferMapping: true supportsBufferInvalidation: false Extensions: "GL_CHROMIUM_sync_query" "GL_ANGLE_program_cache_control" "GL_NV_pixel_buffer_object" "GL_EXT_disjoint_timer_query" "GL_ANGLE_request_extension" "GL_ANGLE_multiview" "GL_OES_surfaceless_context" "GL_EXT_map_buffer_range" "GL_OES_standard_derivatives" "GL_OES_EGL_image" "GL_ANGLE_texture_usage" "GL_KHR_debug" "GL_OES_packed_depth_stencil" "GL_OES_rgb8_rgba8" "GL_EXT_shader_texture_lod" "GL_ANGLE_texture_compression_dxt5" "GL_OES_texture_half_float_linear" "GL_OES_mapbuffer" "GL_ANGLE_instanced_arrays" "GL_NV_pack_subimage" "GL_OES_texture_float" "GL_EXT_debug_marker" "GL_CHROMIUM_bind_generates_resource" "GL_OES_get_program_binary" "GL_CHROMIUM_bind_uniform_location" "GL_EXT_texture_rg" "GL_ANGLE_client_arrays" "GL_OES_EGL_image_external_essl3" "GL_OES_compressed_ETC1_RGB8_texture" "GL_OES_vertex_array_object" "GL_ANGLE_framebuffer_multisample" "GL_ANGLE_translated_shader_source" "GL_CHROMIUM_copy_compressed_texture" "GL_OES_depth32" "GL_EXT_draw_buffers" "GL_EXT_color_buffer_half_float" "GL_ANGLE_robust_client_memory" "GL_OES_element_index_uint" "GL_ANGLE_framebuffer_blit" "GL_EXT_blend_minmax" "GL_ANGLE_texture_compression_dxt3" "GL_EXT_texture_compression_dxt1" "GL_EXT_texture_compression_s3tc_srgb" "GL_EXT_texture_filter_anisotropic" "GL_OES_EGL_image_external" "GL_OES_texture_float_linear" "GL_CHROMIUM_copy_texture" "GL_EXT_discard_framebuffer" "GL_OES_texture_npot" "GL_EXT_frag_depth" "GL_EXT_occlusion_query_boolean" "GL_EXT_sRGB" "GL_EXT_texture_format_BGRA" "GL_EXT_texture_norm16" "GL_EXT_color_buffer_float" "GL_ANGLE_lossy_etc_decode" "GL_CHROMIUM_col
[digikam] [Bug 431563] While closing digikam ist crashed
https://bugs.kde.org/show_bug.cgi?id=431563 --- Comment #4 from caulier.gil...@gmail.com --- Noon, We need a fresh feedback for this file, else we will close it as well. Thanks in advance Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 408788] Empty Search result -> reset -> nonempty search result
https://bugs.kde.org/show_bug.cgi?id=408788 --- Comment #6 from caulier.gil...@gmail.com --- Maik, what do you think about the proposal in comment #4 ? It can be a solution to prevent a confusion when user want to create a new search and edit an existing one. Gilles -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 431774] Search does not work for specific tag and folder
https://bugs.kde.org/show_bug.cgi?id=431774 caulier.gil...@gmail.com changed: What|Removed |Added CC||caulier.gil...@gmail.com --- Comment #2 from caulier.gil...@gmail.com --- Hi M*sh and happy new year, Did you read the previous comment from Maik in this thread ? Can you reproduce the problem with last digiKam 7.4.0 ? Best regards Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 448106] KOrganizer crashes on startup
https://bugs.kde.org/show_bug.cgi?id=448106 --- Comment #1 from Peter Huyoff --- After restarting the service, google groupware runs without flaws! -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 438960] Add support for searching images created in a time interval
https://bugs.kde.org/show_bug.cgi?id=438960 caulier.gil...@gmail.com changed: What|Removed |Added Summary|Searching images created in |Add support for searching |a time interval doesn't |images created in a time |work|interval CC||caulier.gil...@gmail.com Version|7.2.0 |7.5.0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 372440] Search for panoramic shots (search by aspect ratio *range*)
https://bugs.kde.org/show_bug.cgi?id=372440 caulier.gil...@gmail.com changed: What|Removed |Added Version|7.0.0 |7.4.0 Ever confirmed|0 |1 Status|REPORTED|CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 448106] New: KOrganizer crashes on startup
https://bugs.kde.org/show_bug.cgi?id=448106
Bug ID: 448106
Summary: KOrganizer crashes on startup
Product: kde
Version: unspecified
Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: general
Assignee: unassigned-b...@kde.org
Reporter: peter.huy...@gmx.de
Target Milestone: ---
Application: akonadi_google_resource (5.19.0 (21.12.0))
Qt Version: 5.15.2
Frameworks Version: 5.89.0
Operating System: Linux 5.15.12-1-default x86_64
Windowing System: X11
Distribution: "openSUSE Tumbleweed"
DrKonqi: 5.23.4 [KCrashBackend]
-- Information about the crash:
- What I was doing when the application crashed:
KOrganizer crashes everytime, when KDE comes up after booting. It looks, like
it's related to one of the last three updates on tumleweed.
The crash can be reproduced every time.
-- Backtrace:
Application: Google Groupware (peter.huy...@gmail.com)
(akonadi_google_resource), signal: Aborted
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = }
[KCrash Handler]
#6 __pthread_kill_implementation (threadid=,
signo=signo@entry=6, no_tid=no_tid@entry=0) at pthread_kill.c:44
#7 0x7f052e2f82d3 in __pthread_kill_internal (signo=6, threadid=) at pthread_kill.c:78
#8 0x7f052e2a8356 in __GI_raise (sig=sig@entry=6) at
../sysdeps/posix/raise.c:26
#9 0x7f052e2917d3 in __GI_abort () at abort.c:79
#10 0x7f052e770fe7 in qt_message_fatal (message=...,
context=...) at global/qlogging.cpp:1914
#11 QMessageLogger::fatal(char const*, ...) const
(this=this@entry=0x7ffe2bcaac38, msg=msg@entry=0x7f052ea72028 "ASSERT failure
in %s: \"%s\", file %s, line %d") at global/qlogging.cpp:893
#12 0x7f052e7704ca in qt_assert_x(char const*, char const*, char const*,
int) (where=where@entry=0x7f05303375d0 "Akonadi::ResourceBase::retrieveItem()",
what=what@entry=0x7f0530337500 "The base implementation of retrieveItem() must
never be reached. You must implement either retrieveItem() or
retrieveItems(Akonadi::Item::List, QSet) overload to handle item
retrieval requ"..., file=file@entry=0x7f05303374b0
"/home/abuild/rpmbuild/BUILD/akonadi-21.12.0/src/agentbase/resourcebase.cpp",
line=line@entry=1457) at global/qglobal.cpp:3366
#13 0x7f0530303e6e in Akonadi::ResourceBase::retrieveItem(Akonadi::Item
const&, QSet const&) (this=this@entry=0x7ffe2bcab310,
item=, parts=...) at
/usr/src/debug/akonadi-server-21.12.0-1.1.x86_64/src/agentbase/resourcebase.cpp:1452
#14 0x7f053031d732 in
Akonadi::ResourceBasePrivate::slotPrepareItemRetrievalResult(KJob*)
(this=, job=) at
/usr/src/debug/akonadi-server-21.12.0-1.1.x86_64/src/agentbase/resourcebase.cpp:1035
#15 0x7f052e9c7393 in QtPrivate::QSlotObjectBase::call(QObject*, void**)
(a=0x7ffe2bcaadb0, r=0x559644834730, this=0x55964492dc40) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#16 doActivate(QObject*, int, void**) (sender=0x55964493e330,
signal_index=6, argv=0x7ffe2bcaadb0) at kernel/qobject.cpp:3886
#17 0x7f052e9c085f in QMetaObject::activate(QObject*, QMetaObject const*,
int, void**) (sender=sender@entry=0x55964493e330, m=,
local_signal_index=local_signal_index@entry=3, argv=argv@entry=0x7ffe2bcaadb0)
at kernel/qobject.cpp:3946
#18 0x7f052fd86ffc in KJob::result(KJob*, KJob::QPrivateSignal)
(this=this@entry=0x55964493e330, _t1=, _t1@entry=0x55964493e330,
_t2=...) at
/usr/src/debug/kcoreaddons-5.89.0-1.2.x86_64/build/src/lib/KF5CoreAddons_autogen/include/moc_kjob.cpp:633
#19 0x7f052fd8b39b in KJob::finishJob(bool) (this=0x55964493e330,
emitResult=) at
/usr/src/debug/kcoreaddons-5.89.0-1.2.x86_64/src/lib/jobs/kjob.cpp:98
#20 0x7f052e9bd33e in QObject::event(QEvent*) (this=0x55964493e330,
e=0x55964493feb0) at kernel/qobject.cpp:1314
#21 0x7f052f5d3a7f in QApplicationPrivate::notify_helper(QObject*, QEvent*)
(this=, receiver=0x55964493e330, e=0x55964493feb0) at
kernel/qapplication.cpp:3632
#22 0x7f052e990d2a in QCoreApplication::notifyInternal2(QObject*, QEvent*)
(receiver=0x55964493e330, event=0x55964493feb0) at
kernel/qcoreapplication.cpp:1064
#23 0x7f052e993d77 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) (receiver=0x0, event_type=0, data=0x559644787250) at
kernel/qcoreapplication.cpp:1821
#24 0x7f052e9e8b83 in postEventSourceDispatch(GSource*, GSourceFunc,
gpointer) (s=s@entry=0x55964485c4e0) at kernel/qeventdispatcher_glib.cpp:277
#25 0x7f052c91dd9f in g_main_dispatch (context=0x7f0520005000) at
../glib/gmain.c:3381
#26 g_main_context_dispatch (context=0x7f0520005000) at ../glib/gmain.c:4099
#27 0x7f052c91e128 in g_main_context_iterate
(context=context@entry=0x7f0520005000, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at ../glib/gmain.c:4175
#28 0x7f052c91e1df in g_main_context_iteration (context=0x7f0520005000,
may_block=1) at ../glib/gmain.c:4240
#29 0x7f052e9
[digikam] [Bug 396305] Being able to find which files which doesn't already have author, copyright, and locations tags
https://bugs.kde.org/show_bug.cgi?id=396305 caulier.gil...@gmail.com changed: What|Removed |Added CC||caulier.gil...@gmail.com Status|REPORTED|RESOLVED Severity|normal |wishlist Version Fixed In||7.5.0 Resolution|--- |FIXED --- Comment #1 from caulier.gil...@gmail.com --- Tested with 7.5.0 in advanced search. We have now these options: - "Caption, Comment, Title/Empty Text" section ==> return item without text in : Creator | Caption | Author | Headline | Title. - "Geographic position/Item has no GPS info" section ==> return not geo-located. Sounds like this fill the wishes from this file. Closed Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 448105] New: Open just one instance of gwenview
https://bugs.kde.org/show_bug.cgi?id=448105 Bug ID: 448105 Summary: Open just one instance of gwenview Product: gwenview Version: 21.12.0 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: gwenview-bugs-n...@kde.org Reporter: kde-b...@spaetzle.info Target Milestone: --- SUMMARY *** If gwenview is already open and I click another image, that one is opened in a new instance of gwenview. I would expect it to be opened in the already running gwenview-instance. *** STEPS TO REPRODUCE 1. Open gwenview 2. Click an image OBSERVED RESULT Two gwenview instances (windows) are open. EXPECTED RESULT Open the image which was clicked to open in the already existing window. SOFTWARE/OS VERSIONS KDE Plasma Version: 5.23.4 KDE Frameworks Version: 5.89.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 448099] two (out of three) docks not showing up after reboot
https://bugs.kde.org/show_bug.cgi?id=448099 --- Comment #3 from Michail Vourlakos --- (In reply to kde-bugs from comment #2) > (In reply to Michail Vourlakos from comment #1) > > If you restart Latte are they showing correctly? > > I just killed (SIGTERM) latte-dock and restarted it from the terminal. Same > behaviour - the main dock shows perfectly fine, the other two don't show up. send me your layout file please to test it? -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 448099] two (out of three) docks not showing up after reboot
https://bugs.kde.org/show_bug.cgi?id=448099 --- Comment #2 from kde-b...@spaetzle.info --- (In reply to Michail Vourlakos from comment #1) > If you restart Latte are they showing correctly? I just killed (SIGTERM) latte-dock and restarted it from the terminal. Same behaviour - the main dock shows perfectly fine, the other two don't show up. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 398721] No results if an album (directory) is selected
https://bugs.kde.org/show_bug.cgi?id=398721 --- Comment #11 from caulier.gil...@gmail.com --- Hi Pierre and happy new year, We need a fresh feedback using last digiKam 7.4.0 on you computer Thanks in advance Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 448104] New: System settings crashes on opening Power menu
https://bugs.kde.org/show_bug.cgi?id=448104
Bug ID: 448104
Summary: System settings crashes on opening Power menu
Product: systemsettings
Version: 5.23.4
Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: general
Assignee: plasma-b...@kde.org
Reporter: hornets...@gmail.com
Target Milestone: ---
Application: systemsettings5 (5.23.4)
Qt Version: 5.15.2
Frameworks Version: 5.89.0
Operating System: Linux 5.15.12-1-default x86_64
Windowing System: X11
Distribution: "openSUSE Tumbleweed"
DrKonqi: 5.23.4 [KCrashBackend]
-- Information about the crash:
- What I was doing when the application crashed:
Attempting to open Settings>System Settings>Power Management menu.
Immediately faults with "System Settings closed unexpectedly" message.
The crash can be reproduced every time.
-- Backtrace:
Application: System Settings (systemsettings5), signal: Segmentation fault
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = }
[KCrash Handler]
#6 0x7fb212cfc506 in QComboBox::clear (this=0x556f74ade1b0) at
widgets/qcombobox.cpp:3049
#7 0x7fb1ff6f3714 in operator() (__closure=0x556f787011d0,
watcher=) at
/usr/src/debug/powerdevil5-5.23.4-1.2.x86_64/daemon/actions/bundled/powerprofileconfig.cpp:83
#8 0x7fb211f76393 in QtPrivate::QSlotObjectBase::call (a=0x7ffeb0de9440,
r=0x7fb200011460, this=0x556f787011c0) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#9 doActivate (sender=0x556f783e5750, signal_index=3,
argv=0x7ffeb0de9440) at kernel/qobject.cpp:3886
#10 0x7fb211f6f85f in QMetaObject::activate (sender=,
m=m@entry=0x7fb210aa25e0 ,
local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffeb0de9440)
at kernel/qobject.cpp:3946
#11 0x7fb210a8307f in QDBusPendingCallWatcher::finished (this=, _t1=) at .moc/moc_qdbuspendingcall.cpp:158
#12 0x7fb211f6c33e in QObject::event (this=0x556f783e5750,
e=0x556f79d12af0) at kernel/qobject.cpp:1314
#13 0x7fb212bf1a7f in QApplicationPrivate::notify_helper (this=, receiver=0x556f783e5750, e=0x556f79d12af0) at
kernel/qapplication.cpp:3632
#14 0x7fb211f3fd2a in QCoreApplication::notifyInternal2
(receiver=0x556f783e5750, event=0x556f79d12af0) at
kernel/qcoreapplication.cpp:1064
#15 0x7fb211f42d77 in QCoreApplicationPrivate::sendPostedEvents
(receiver=0x0, event_type=0, data=0x556f74830480) at
kernel/qcoreapplication.cpp:1821
#16 0x7fb211f97b83 in postEventSourceDispatch (s=s@entry=0x556f749336c0) at
kernel/qeventdispatcher_glib.cpp:277
#17 0x7fb20fa92d9f in g_main_dispatch (context=0x7fb208005000) at
../glib/gmain.c:3381
#18 g_main_context_dispatch (context=0x7fb208005000) at ../glib/gmain.c:4099
#19 0x7fb20fa93128 in g_main_context_iterate
(context=context@entry=0x7fb208005000, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at ../glib/gmain.c:4175
#20 0x7fb20fa931df in g_main_context_iteration (context=0x7fb208005000,
may_block=1) at ../glib/gmain.c:4240
#21 0x7fb211f97204 in QEventDispatcherGlib::processEvents
(this=0x556f7493cf90, flags=...) at kernel/qeventdispatcher_glib.cpp:423
#22 0x7fb211f3e72b in QEventLoop::exec (this=this@entry=0x7ffeb0de9830,
flags=..., flags@entry=...) at
../../include/QtCore/../../src/corelib/global/qflags.h:69
#23 0x7fb211f46a10 in QCoreApplication::exec () at
../../include/QtCore/../../src/corelib/global/qflags.h:121
#24 0x7fb21249319c in QGuiApplication::exec () at
kernel/qguiapplication.cpp:1867
#25 0x7fb212bf19f5 in QApplication::exec () at kernel/qapplication.cpp:2824
#26 0x556f73cb610b in main (argc=, argv=) at
/usr/src/debug/systemsettings5-5.23.4-1.2.x86_64/app/main.cpp:208
[Inferior 1 (process 26586) detached]
Possible duplicates by query: bug 447910, bug 447904, bug 447759, bug 447676,
bug 447282.
Reported using DrKonqi
--
You are receiving this mail because:
You are watching all bug changes.
[digikam] [Bug 297771] Add support for Nikon camera shotting modes in Advanced settings
https://bugs.kde.org/show_bug.cgi?id=297771 caulier.gil...@gmail.com changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED Version|2.5.0 |7.5.0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 297771] Add support for Nikon camera shotting modes in Advanced settings
https://bugs.kde.org/show_bug.cgi?id=297771 caulier.gil...@gmail.com changed: What|Removed |Added Severity|normal |wishlist Summary|Advanced settings from |Add support for Nikon |Nikon camera not accessible |camera shotting modes in |for search queries |Advanced settings -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 436975] Advanced search - right panel is disabled
https://bugs.kde.org/show_bug.cgi?id=436975 caulier.gil...@gmail.com changed: What|Removed |Added Version|7.3.0 |7.5.0 Ever confirmed|0 |1 Status|REPORTED|CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 448103] New: Can't select linear ramp stops other than the first
https://bugs.kde.org/show_bug.cgi?id=448103 Bug ID: 448103 Summary: Can't select linear ramp stops other than the first Product: krita Version: 5.0.2 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: Tools/Vector Assignee: krita-bugs-n...@kde.org Reporter: chris.k.d.w...@gmail.com Target Milestone: --- SUMMARY When setting or editing colors in a linear ramp fill of a vector object, only the first (shown on left) stop can be selected STEPS TO REPRODUCE 1. Create a vector layer and then a vector object (a rectangle object for example) in the layer. 2. Choose the select tool, select the vector object just created, select the gradient fill option. 3. The left hand stop is active by default and its color can easily be edited. 4. Trying to change to the right hand stop either by pressing the > (or <) button (or the tear drop) does NOT change the current stop to the right hand stop. (A blue outline does briefly appear around the tear drop for the other stop, but it immediately moves back to the left hand stop.) 5. The currently editable remains as the left stop. OBSERVED RESULT Can not select any stop other than the left stop in a linear ramp for editing the linear ramp fill of a vector object in a vector layer. EXPECTED RESULT Should be able to select any stop of a linear ramp so its color can be adjusted. SOFTWARE/OS VERSIONS Windows: 10 macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION WARNING: The system information file doesn't exist.File name and location: C:/Users/chris/AppData/Local/krita-sysinfo.log Krita Version: 5.0.2 Qt Version (compiled): 5.12.12 Version (loaded): 5.12.12 OS Information Build ABI: x86_64-little_endian-llp64 Build CPU: x86_64 CPU: x86_64 Kernel Type: winnt Kernel Version: 10.0.19044 Pretty Productname: Windows 10 (10.0) Product Type: windows Product Version: 10 OpenGL Info Vendor: "Google Inc." Renderer: "ANGLE (NVIDIA GeForce MX250 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 supportsBufferMapping: true supportsBufferInvalidation: false Extensions: "GL_EXT_texture_filter_anisotropic" "GL_OES_EGL_image_external" "GL_OES_compressed_ETC1_RGB8_texture" "GL_EXT_color_buffer_float" "GL_EXT_map_buffer_range" "GL_OES_depth32" "GL_OES_texture_half_float_linear" "GL_ANGLE_client_arrays" "GL_ANGLE_framebuffer_multisample" "GL_ANGLE_framebuffer_blit" "GL_CHROMIUM_color_buffer_float_rgba" "GL_ANGLE_translated_shader_source" "GL_CHROMIUM_color_buffer_float_rgb" "GL_EXT_sRGB" "GL_ANGLE_request_extension" "GL_ANGLE_texture_compression_dxt5" "GL_ANGLE_pack_reverse_row_order" "GL_OES_packed_depth_stencil" "GL_NV_pixel_buffer_object" "GL_OES_texture_npot" "GL_ANGLE_texture_compression_dxt3" "" "GL_EXT_texture_compression_dxt1" "GL_OES_surfaceless_context" "GL_OES_mapbuffer" "GL_EXT_frag_depth" "GL_OES_rgb8_rgba8" "GL_EXT_draw_buffers" "GL_EXT_texture_norm16" "GL_ANGLE_texture_usage" "GL_OES_texture_float" "GL_ANGLE_instanced_arrays" "GL_ANGLE_lossy_etc_decode" "GL_OES_texture_float_linear" "GL_KHR_debug" "GL_EXT_unpack_subimage" "GL_ANGLE_depth_texture" "GL_ANGLE_robust_client_memory" "GL_EXT_occlusion_query_boolean" "GL_EXT_color_buffer_half_float" "GL_ANGLE_multiview" "GL_EXT_discard_framebuffer" "GL_NV_fence" "GL_EXT_texture_rg" "GL_OES_vertex_array_object" "GL_EXT_shader_texture_lod" "GL_OES_element_index_uint" "GL_EXT_disjoint_timer_query" "GL_CHROMIUM_sync_query" "GL_EXT_robustness" "GL_EXT_debug_marker" "GL_EXT_texture_storage" "GL
[rust-qt-binding-generator] [Bug 448087] rust-qt-binding-generator: Undefined Behaviour: One can obtain a mutable reference to a Rust struct from an immutable reference.
https://bugs.kde.org/show_bug.cgi?id=448087 --- Comment #3 from Andreas Grois --- Sorry, this is not really relevant to the bug, but I just have to correct myself here. I was too tired yesterday to realize that also the &mut self -> &self situation can cause issues. Actually #406178 describes such a call stack. With Rust's aliasing rules the compiler can assume that the call to C++ (which does not take any references into the memory pointed to by &mut self) is independent of &mut self, so it need not guarantee that the memory referenced by &mut self is in a consistent (or up-to-date) state when it triggers the signal. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 442342] Cursor brush outline not visible on first pen proximity after opening document
https://bugs.kde.org/show_bug.cgi?id=442342 --- Comment #3 from Dmitry Kazakov --- I can confirm both problems. The first time the stylus tip enters the document directly (without hovering the GUI elements), the outline is not visible. If one flips the stylus the same problem happens for the second stylus tip. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 425886] DigiKam Crashes immediately after hitting the search button for Images, both on regular and advanced search tool
https://bugs.kde.org/show_bug.cgi?id=425886 caulier.gil...@gmail.com changed: What|Removed |Added Component|Searches-Advanced |Plugin-DImg-TIFF -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 425886] DigiKam Crashes immediately after hitting the search button for Images, both on regular and advanced search tool
https://bugs.kde.org/show_bug.cgi?id=425886 caulier.gil...@gmail.com changed: What|Removed |Added Severity|normal |crash --- Comment #17 from caulier.gil...@gmail.com --- Hi Kim and happy new year, Can you try to reproduce the problem with digiKam 7.5.0 pre-release for Windows available at this url : https://files.kde.org/digikam/ Thanks in advance Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 448102] New: Crash of kwin after sleep
https://bugs.kde.org/show_bug.cgi?id=448102
Bug ID: 448102
Summary: Crash of kwin after sleep
Product: kwin
Version: 5.23.4
Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: general
Assignee: kwin-bugs-n...@kde.org
Reporter: jerem.gir...@gmail.com
Target Milestone: ---
Application: kwin_x11 (5.23.4)
Qt Version: 5.15.2
Frameworks Version: 5.89.0
Operating System: Linux 5.15.12-1-default x86_64
Windowing System: X11
Distribution: "openSUSE Tumbleweed"
DrKonqi: 5.23.4 [KCrashBackend]
-- Information about the crash:
- Unusual behavior I noticed:
I have two screen (1 displayport + 1 hdmi)
After resume computer from sleep, kwin crash.
So, I have no wallpaper and no panel of the left screen (displayport).
The crash can be reproduced every time.
-- Backtrace:
Application: KWin (kwin_x11), signal: Segmentation fault
Content of s_kcrashErrorMessage: {_M_t = { >> = {_M_t = { >> = { >> = {, true>> = {_M_head_impl = {}}, },
> = {_M_head_impl = }, }, }}, }}
[KCrash Handler]
#6 0x7f853d3df953 in KWin::Workspace::clientArea(KWin::clientAreaOption,
KWin::AbstractOutput const*, KWin::VirtualDesktop const*) const
(this=0x55921134c330, opt=KWin::PlacementArea, output=,
desktop=) at
/usr/src/debug/kwin5-5.23.4-1.3.x86_64/src/workspace.cpp:2298
#7 0x7f853d2991a5 in
KWin::WorkspaceWrapper::clientArea(KWin::WorkspaceWrapper::ClientAreaOption,
int, int) const (this=0x559211494ef0, desktop=,
screen=, option=) at
/usr/src/debug/kwin5-5.23.4-1.3.x86_64/src/scripting/workspace_wrapper.cpp:270
#8 KWin::WorkspaceWrapper::qt_static_metacall(QObject*, QMetaObject::Call,
int, void**) (_o=_o@entry=0x559211494ef0,
_c=_c@entry=QMetaObject::InvokeMetaMethod, _id=_id@entry=85,
_a=_a@entry=0x7ffecbd2d8d0) at
/usr/src/debug/kwin5-5.23.4-1.3.x86_64/build/src/kwin_autogen/7KDSW62DQT/moc_workspace_wrapper.cpp:649
#9 0x7f853d29a92b in
KWin::WorkspaceWrapper::qt_metacall(QMetaObject::Call, int, void**)
(this=this@entry=0x559211494ef0, _c=_c@entry=QMetaObject::InvokeMetaMethod,
_id=85, _a=_a@entry=0x7ffecbd2d8d0) at
/usr/src/debug/kwin5-5.23.4-1.3.x86_64/build/src/kwin_autogen/7KDSW62DQT/moc_workspace_wrapper.cpp:919
#10 0x7f853d29a951 in
KWin::DeclarativeScriptWorkspaceWrapper::qt_metacall(QMetaObject::Call, int,
void**) (this=0x559211494ef0, _c=QMetaObject::InvokeMetaMethod, _id=, _a=0x7ffecbd2d8d0) at
/usr/src/debug/kwin5-5.23.4-1.3.x86_64/build/src/kwin_autogen/7KDSW62DQT/moc_workspace_wrapper.cpp:1300
#11 0x7f853a7ceead in QQmlObjectOrGadget::metacall(QMetaObject::Call, int,
void**) const (this=this@entry=0x7ffecbd2db60,
type=type@entry=QMetaObject::InvokeMetaMethod, index=,
index@entry=90, argv=) at
/usr/src/debug/libqt5-qtdeclarative-5.15.2+kde36-1.3.x86_64/src/qml/qml/qqmlobjectorgadget.cpp:51
#12 0x7f853a6ae000 in CallMethod (callType=, callArgs=0x2,
engine=, argTypes=, argCount=,
returnType=, index=, object=...) at
/usr/include/qt5/QtCore/qvarlengtharray.h:190
#13 CallPrecise(QQmlObjectOrGadget const&, QQmlPropertyData const&,
QV4::ExecutionEngine*, QV4::CallData*, QMetaObject::Call) (object=...,
data=, engine=engine@entry=0x559211490220,
callArgs=callArgs@entry=0x7f85183baa20,
callType=callType@entry=QMetaObject::InvokeMetaMethod) at
/usr/src/debug/libqt5-qtdeclarative-5.15.2+kde36-1.3.x86_64/src/qml/jsruntime/qv4qobjectwrapper.cpp:1569
#14 0x7f853a6afdeb in CallOverloaded (callType=,
propertyCache=, callArgs=, engine=, data=, object=) at
/usr/src/debug/libqt5-qtdeclarative-5.15.2+kde36-1.3.x86_64/src/qml/jsruntime/qv4qobjectwrapper.cpp:1645
#15 QV4::QObjectMethod::callInternal(QV4::Value const*, QV4::Value const*, int)
const (this=, thisObject=, argv=,
argc=) at
/usr/src/debug/libqt5-qtdeclarative-5.15.2+kde36-1.3.x86_64/src/qml/jsruntime/qv4qobjectwrapper.cpp:2133
#16 0x7f853a6de27a in QV4::FunctionObject::call(QV4::Value const*,
QV4::Value const*, int) const (argc=3, argv=0x7f85183ba9d8,
thisObject=0x7f85183ba9c0, this=0x7ffecbd2dc98) at
/usr/src/debug/libqt5-qtdeclarative-5.15.2+kde36-1.3.x86_64/src/qml/jsruntime/qv4functionobject_p.h:202
#17 QV4::Runtime::CallPropertyLookup::call(QV4::ExecutionEngine*, QV4::Value
const&, unsigned int, QV4::Value*, int) (engine=0x559211490220, base=...,
index=, argv=0x7f85183ba9d8, argc=3) at
/usr/src/debug/libqt5-qtdeclarative-5.15.2+kde36-1.3.x86_64/src/qml/jsruntime/qv4runtime.cpp:1460
#18 0x7f85200038b1 in ()
#19 0x in ()
[Inferior 1 (process 32257) detached]
Possible duplicates by query: bug 444927, bug 443166, bug 441577, bug 414317,
bug 409838.
Reported using DrKonqi
--
You are receiving this mail because:
You are watching all bug changes.
[digikam] [Bug 444578] [Feature Request] find duplicate choose best image to keep (size, pixel ...)
https://bugs.kde.org/show_bug.cgi?id=444578 caulier.gil...@gmail.com changed: What|Removed |Added Severity|normal |wishlist CC||caulier.gil...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 437912] Similarity-Duplicates digiKam closes unexpectedly.
https://bugs.kde.org/show_bug.cgi?id=437912 caulier.gil...@gmail.com changed: What|Removed |Added CC||caulier.gil...@gmail.com --- Comment #4 from caulier.gil...@gmail.com --- Hi hannesj and happy new year, Can you try to reproduce the problem with digiKam 7.5.0 pre-release for Windows available at this url : https://files.kde.org/digikam/ Thanks in advance Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 430858] Digikam 7.1.0 crash Assert d in similaritydbaccess.cpp line 105
https://bugs.kde.org/show_bug.cgi?id=430858 --- Comment #7 from caulier.gil...@gmail.com --- Ian, Please review the last comment from me and Maik about this entry. We needs a fresh feedback, else we will close the file as well... Best regards Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 248037] Making a new database
https://bugs.kde.org/show_bug.cgi?id=248037 caulier.gil...@gmail.com changed: What|Removed |Added Version Fixed In||7.5.0 Resolution|DUPLICATE |FIXED --- Comment #3 from caulier.gil...@gmail.com --- Fixed with https://bugs.kde.org/show_bug.cgi?id=218256 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 438784] Panning and zooming bug in Krita
https://bugs.kde.org/show_bug.cgi?id=438784 Zack Keller changed: What|Removed |Added CC||zeek-...@outlook.com --- Comment #14 from Zack Keller --- Still present in 5.0.2. Modifier keys just spaz out when I pan, rotate and zoom quickly. Can reproduce it on my main rig (Win10 / Huion WH1409 v2) and my Surface Book 2 (Win10 / Wacom Bamboo Ink). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 448101] New: Plasma becomes unresponsive after scrolling in 'Years' tab of calendar
https://bugs.kde.org/show_bug.cgi?id=448101 Bug ID: 448101 Summary: Plasma becomes unresponsive after scrolling in 'Years' tab of calendar Product: plasmashell Version: master Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Calendar Assignee: plasma-b...@kde.org Reporter: bugsefor...@gmx.com Target Milestone: 1.0 STEPS TO REPRODUCE 1. click on digital clock 2. click on 'Years' tab 3. hover over any year and scroll down/up a few times OBSERVED RESULT Plasma becomes unresponsive for a while (nothing happens when I click on anything in the panel) and sometimes it crashes after clicks on panel during the unresponsiveness. EXPECTED RESULT Plasma remains responsive SOFTWARE/OS VERSIONS Operating System: KDE neon Unstable Edition KDE Plasma Version: 5.23.80 KDE Frameworks Version: 5.90.0 Qt Version: 5.15.3 Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 444335] Sticky keys does not work under Wayland
https://bugs.kde.org/show_bug.cgi?id=444335 Robert Kratky changed: What|Removed |Added CC||kra...@rob.cz --- Comment #2 from Robert Kratky --- Can confirm on: Operating System: Fedora Linux 35 KDE Plasma Version: 5.23.5 KDE Frameworks Version: 5.89.0 Qt Version: 5.15.2 Kernel Version: 5.15.12-200.fc35.x86_64 (64-bit) Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 447732] Rescale upon login causes widgets to move from their usual position
https://bugs.kde.org/show_bug.cgi?id=447732 --- Comment #3 from Lyubomir --- Created attachment 145215 --> https://bugs.kde.org/attachment.cgi?id=145215&action=edit KDE widgets posiiton and notification Not sure if it isn't the notifications fault here - steps are: 1. Splash loading screen shows after clicking login into the SDDM display manager 2. During the splash screen showing there is a rescale and it becomes bigger and more blurry 3. Then it fades away to desktop - at this moment the widgets are at their correct position 4. Then the notifications show up on the left part of the screen for a while, then move to their correct position to the right. It is that moment when they move to the correct position in the right when the widgets "make place" for the notification. But please note that if i then go and move the widgets back to the very corner of the screen, where they should be, further notifications don't move the widgets but display over them. So if it is the notifications - then it's only the first ones right after login that are moving from the left of the screen to the right. Or it's simply because of the rescale during the splash screen - but if so then why after it fades to desktop the widgets are initially in their correct position? -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 448028] sometimes vertical line or rectangle at the beginning of a line - input and/or output
https://bugs.kde.org/show_bug.cgi?id=448028 --- Comment #4 from Alexander Semke --- (In reply to Helmut B from comment #2) > Created attachment 145212 [details] > attachment-14139-0.html Danke, Helmut. This looks like an issue with the libspectre library rendering the EPS output. This library is causing problems in multiple places and we're trying to remove it now completely and use PDF instead. Until this change is finalized in Cantor, you can switch off the LaTeX-typesetting in the application settings. With this you get the output of Maxima in plain text format which also looks very reasonable for very many use-cases. I also see you're working with "LaTeX entries" to enter text. If these entries are also causing issues for you, you can switch to text and/or markdown entries maybe. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 448100] When I cut a video and replace a file I miss a frame and gap audio
https://bugs.kde.org/show_bug.cgi?id=448100 --- Comment #1 from Javier Celis --- Created attachment 145214 --> https://bugs.kde.org/attachment.cgi?id=145214&action=edit Project_files_MLT_Source_Resize_ZIP_EXE_PACK In the 1080 project is possible see a gap because this is a 1 second video, but in larger projects, this is not visible adjust magnetic or gap, perhaps is interesting cretae a gap tag for timeline por adjust and near overlap. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 448098] Trying to drag tabs in Chrome to reorder them suddenly always produces a new window
https://bugs.kde.org/show_bug.cgi?id=448098 Patrick Silva changed: What|Removed |Added Resolution|--- |DOWNSTREAM Status|REPORTED|RESOLVED CC||bugsefor...@gmx.com --- Comment #1 from Patrick Silva --- chromium bug https://bugs.chromium.org/p/chromium/issues/detail?id=1279532 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 448100] New: When I cut a video and replace a file I miss a frame and gap audio
https://bugs.kde.org/show_bug.cgi?id=448100 Bug ID: 448100 Summary: When I cut a video and replace a file I miss a frame and gap audio Product: kdenlive Version: unspecified Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: minor Priority: NOR Component: Effects & Transitions Assignee: vpi...@kde.org Reporter: javcel...@gmail.com Target Milestone: --- SUMMARY When I cut a video and replace a file I miss a frame and gap audio. I have this issue, but this is not an expected behaviour and with non reframe video rate (frame numeration) it doesn´t happend. STEPS TO REPRODUCE 1. I have a mp4 file h264 and I make a subsample video_size=-1:360 with ffmpeg and try -r 15000/1001 (framerate), for use h264_qsv hardware accel. 2. With this file I create a kdenlivve project with a timepoint to cut this file, and put this in two tracks, render and it's OK 3. I replace the mp4 file for the original FHD 29.97fps file, render and I have a gap. OBSERVED RESULT I have a gap when I replace a file with changed framerate EXPECTED RESULT Cut a video and replace make the cut in a unique time previous and before in each track with audio-video continum. If I was Create an unique point and the time is the same previous and before I don´t expect the gap after replace and this issue works OK whithout framerate change in my pseudo proxy file -r 15000/1001 SOFTWARE/OS VERSIONS Windows: Windows10_21H2 KDE Frameworks Version: 5.88.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION MLT: 7.3.0 -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 438127] latte crashes occasionally at login of dual-monitor setup
https://bugs.kde.org/show_bug.cgi?id=438127 Michail Vourlakos changed: What|Removed |Added Status|REOPENED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #19 from Michail Vourlakos --- needs info with proper crash report -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 447667] [touchscreen] - must tap on an app in dock twice to start it
https://bugs.kde.org/show_bug.cgi?id=447667 --- Comment #1 from Michail Vourlakos --- does this also occur with plasma panel and plasma taskmanager? -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 447668] [touchscreen] - cannot show hidden docks and panels on wayland
https://bugs.kde.org/show_bug.cgi?id=447668 --- Comment #1 from Michail Vourlakos --- If you disable option, Behavior(advanced) -> "Activate KWin edge after hiding" is it fixed? -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 447929] hide background feature randomly doesn't work until dock restart
https://bugs.kde.org/show_bug.cgi?id=447929 Michail Vourlakos changed: What|Removed |Added Summary|Hide background feature |hide background feature |randomly doesn't work until |randomly doesn't work until |dock restart|dock restart -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 448099] two (out of three) docks not showing up after reboot
https://bugs.kde.org/show_bug.cgi?id=448099 Michail Vourlakos changed: What|Removed |Added Summary|Two (out of three) docks|two (out of three) docks |not showing up after reboot |not showing up after reboot -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 448096] [wayland] - minimizing and reopening windows causes window to be open on multiple virtual desktops at once
https://bugs.kde.org/show_bug.cgi?id=448096 --- Comment #1 from Michail Vourlakos --- I remember that there was a relevant wayland fix for upcoming plasma 5.24 that will also fix latte taskmanager behavior... nonetheless that patch should also be applied to latte internal wm:waylandinterface functions -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 448096] [wayland] - minimizing and reopening windows causes window to be open on multiple virtual desktops at once
https://bugs.kde.org/show_bug.cgi?id=448096 Michail Vourlakos changed: What|Removed |Added Summary|Minimizing and reopening|[wayland] - minimizing and |windows in Wayland session |reopening windows causes |causes window to be open on |window to be open on |multiple virtual desktops |multiple virtual desktops |at once |at once -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 448061] [feature] - merge lists of tasks actions to provide same options
https://bugs.kde.org/show_bug.cgi?id=448061 Michail Vourlakos changed: What|Removed |Added Summary|[feature] - merege lists of |[feature] - merge lists of |tasks actions to provide|tasks actions to provide |same options|same options -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 448061] [feature] - merege lists of tasks actions to provide same options
https://bugs.kde.org/show_bug.cgi?id=448061 Michail Vourlakos changed: What|Removed |Added Severity|normal |wishlist Summary|Tasks Actions: Merge list |[feature] - merege lists of |off possible actions|tasks actions to provide ||same options -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 443538] Download New Stuff cannot be closed after closing Dolphin
https://bugs.kde.org/show_bug.cgi?id=443538 count changed: What|Removed |Added CC||count.negat...@gmx.de Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #1 from count --- Can reproduce on Dolphin 22.03.70, Framework 5.90.0 inside KDevelop. Configure Dolphin - Context Menu - Download New Services then: - Close Configure Window via Window Close Button (not via Dialog Buttons!) - Close Dolphin via Window Close Button - Close Download New Services via Window Close Button SegFault QtCore/qlist.h:853 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 438784] Panning and zooming bug in Krita
https://bugs.kde.org/show_bug.cgi?id=438784 Alvin Wong changed: What|Removed |Added CC||al...@alvinhc.com --- Comment #13 from Alvin Wong --- Very reproducible on my Surface Pro 2017. Some quick notes after experimenting: - Press down Spacebar, press stylus to pan, release stylus, press down Shift, press stylus to rotate, release stylus, THEN release Shift, press stylus to pan works normally - Press down Spacebar, press stylus to pan, release stylus, press down Shift, press stylus to rotate, release Shift, THEN release stylus, press stylus and it starts painting instead -- You are receiving this mail because: You are watching all bug changes.
[kget] [Bug 444591] KGet crashes when attempting to download anything
https://bugs.kde.org/show_bug.cgi?id=444591
--- Comment #24 from Frank Kruger ---
(In reply to Wolfgang Bauer from comment #23)
> Git commit 13187db5a4288ad5e852c851eec16ea6e0a8ccd2 by Wolfgang Bauer.
> Committed on 03/01/2022 at 19:22.
> Pushed by wbauer into branch 'release/21.12'.
>
> Fix destination filesystem type check for downloads bigger than 4 GiB
>
> `m_dest` is a QUrl, we need to use `toLocalFile()` to get a local path.
> `toString()` results in a URL instead ("file://...") which causes the
> mountpoint lookup to fail.
>
> Also, the check whether the mountpoint was found was reversed. It
> actually tried to compare the filesystem type when the mount point was
> *not* found, resulting in a crash because of the nullptr dereference.
> FIXED-IN: 21.12.1
>
> M +3-3core/datasourcefactory.cpp
>
> https://invent.kde.org/network/kget/commit/
> 13187db5a4288ad5e852c851eec16ea6e0a8ccd2
kget 21.12.1 works fine here (openSUSE Tumbleweed 20220106). Thx.
--
You are receiving this mail because:
You are watching all bug changes.
[dolphin] [Bug 444097] Custom "Create Folder" shortcut doesn't work within application file dialogs
https://bugs.kde.org/show_bug.cgi?id=444097 count changed: What|Removed |Added CC||count.negat...@gmx.de --- Comment #1 from count --- Could you please try: System Settings - Shortcuts - Shortcuts - Common Actions - File - Create Folder == F10 Set your desired shortcut. This works for me in e.g. Kate (System wide KDE shortcuts BUT not for Gtk based Apps like Firefox an Chrome. Maybe someone could help here out? -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 448099] Two (out of three) docks not showing up after reboot
https://bugs.kde.org/show_bug.cgi?id=448099 --- Comment #1 from Michail Vourlakos --- If you restart Latte are they showing correctly? -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 448028] sometimes vertical line or rectangle at the beginning of a line - input and/or output
https://bugs.kde.org/show_bug.cgi?id=448028 --- Comment #2 from Helmut B --- On 07.01.22 22:17, Alexander Semke wrote: > https://bugs.kde.org/show_bug.cgi?id=448028 > > Alexander Semke changed: > > What|Removed |Added > > CC||alexander.se...@web.de > > --- Comment #1 from Alexander Semke --- > (In reply to Helmut B from comment #0) >> Created attachment 145165 [details] >> extract from Haager, Computeralgebra mit Maxima >> >> sometimes vertical line or rectangle at the beginning of a line - input >> and/or output > I have troubles opening Cantor projects with embedded EPS images for the LaTeX > output and I cannot check your project right now. Can you please do a > screenshot of the vertical line you mentioned? Thank you. > -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 448099] Two (out of three) docks not showing up after reboot
https://bugs.kde.org/show_bug.cgi?id=448099 kde-b...@spaetzle.info changed: What|Removed |Added CC||kde-b...@spaetzle.info -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 448099] New: Two (out of three) docks not showing up after reboot
https://bugs.kde.org/show_bug.cgi?id=448099 Bug ID: 448099 Summary: Two (out of three) docks not showing up after reboot Product: lattedock Version: 0.10.6 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: application Assignee: mvourla...@gmail.com Reporter: kde-b...@spaetzle.info Target Milestone: --- SUMMARY *** I have three latte docks enabled. After a reboot/restart only one of them is showing, the other two are not visible anymore. This happens since the upgrade to 0.10.6. Before it worked all fine. *** STEPS TO REPRODUCE 1. Enable three latte docks (on the latest stable Manjaro, KDE Plasma) 2. Restart OBSERVED RESULT Only one latte dock is visible after a restart EXPECTED RESULT I expect all latte docks enabled to show up SOFTWARE/OS VERSIONS KDE Plasma Version: 5.23.4 KDE Frameworks Version: 5.89.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 447866] [class diagram] Multiple association ends are drawn on the same edge point
https://bugs.kde.org/show_bug.cgi?id=447866
--- Comment #8 from Oliver Kellogg ---
Git commit dc485c16219a61d802ddf462f809e9cd7c514af3 by Oliver Kellogg.
Committed on 08/01/2022 at 08:19.
Pushed by okellogg into branch 'master'.
First stab at smoothing associationwidget endpoint update as announced
in https://bugs.kde.org/show_bug.cgi?id=447866#c5
umbrello/umlwidgets/associationwidget.{h,cpp}
- At function calculateEndingPoints add argument UMLWidget *pWidget
indicating the selected widget of move or resize. If passed in as
null then updateAssociations() will be called twice, once for the
current associationwidget's role A widget and again for its role B
widget.
- Add function findIntercept(const QRectF& rect, const QPointF& point,
QPointF& result)
returning bool true if the line from the center of `rect' to `point'
intersects with one of rect's sides, and returning the intersection
point in `result'.
- Remove functions updateRegionLineCount and doUpdates.
- Declare function updateAssociations `static' and change arguments to
UMLWidget *pWidget, AssociationWidgetList list.
For details see documentation at the implementation.
M +184 -285 umbrello/umlwidgets/associationwidget.cpp
M +3-12 umbrello/umlwidgets/associationwidget.h
https://invent.kde.org/sdk/umbrello/commit/dc485c16219a61d802ddf462f809e9cd7c514af3
--
You are receiving this mail because:
You are watching all bug changes.
