[digikam] [Bug 486632] Camera is never detected using bundled gphoto2 libraries
https://bugs.kde.org/show_bug.cgi?id=486632 --- Comment #2 from Ashley SMITH --- (In reply to Maik Qualmann from comment #1) > See also the same problem in Bug 451719. The hint that a linked installed > GPhoto2 works is interesting and can help Gilles find the cause in the macOS > bundle. > > Maik Some more information after reading the other bug details. When I run the command /Applications/digiKam.org/digikam.app/Contents/lib/libgphoto2/print-camera-list human-readable using the packaged version of libgphoto2 I get an empty list. Using the brew installed version I get the entire database of supported cameras. Ashley -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 486632] New: Camera is never detected using bundled gphoto2 libraries
https://bugs.kde.org/show_bug.cgi?id=486632 Bug ID: 486632 Summary: Camera is never detected using bundled gphoto2 libraries Classification: Applications Product: digikam Version: 8.3.0 Platform: macOS (DMG) OS: macOS Status: REPORTED Severity: normal Priority: NOR Component: Import-Gphoto2 Assignee: digikam-bugs-n...@kde.org Reporter: hh.abr...@gmail.com Target Milestone: --- SUMMARY The gphoto2 libraries packaged with the MacOS version of DIgiKam do not allow the auto detection of my Canon EOS 7D camera. When I install the gphoto2 and libgphoto2 packages using brew, then create symlinks under the DigiKam installation directory, I am then able to auto detect my camera correctly. I've had this problem for the last years and have only just found a solution. STEPS TO REPRODUCE 1. Install DigiKam using the sources available in DMG format and setup 2. Connect the Canon EOS 7D camera using a USB cable 3. Go to the Cameras preference and click Auto-Detect OBSERVED RESULT An error message is displayed that no cameras can be detected EXPECTED RESULT A Canon EOS 7D should be detected connected to the USB port SOFTWARE/OS VERSIONS macOS: Ventura 13.6.6 ADDITIONAL INFORMATION Installing the same versions of gphoto2 and libgphoto2 and then symlinking the packaged directories and dylib files to the ones installed by brew allows the camera to be detected correctly. Below are the symlinks created under /Applications/digiKam.org/digikam.app/Contents/lib: libgphoto2 -> /usr/local/lib/libgphoto2 libgphoto2.6.dylib -> /usr/local/lib/libgphoto2.6.dylib libgphoto2_port -> /usr/local/lib/libgphoto2_port libgphoto2_port.12.dylib -> /usr/local/lib/libgphoto2_port.12.dylib -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 460616] disInstr(arm64): unhandled instruction 0x4E819402 (dotprod/ASIMDDP)
https://bugs.kde.org/show_bug.cgi?id=460616 --- Comment #6 from William Ashley --- Thanks Mark! -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 460616] disInstr(arm64): unhandled instruction 0x4E819402
https://bugs.kde.org/show_bug.cgi?id=460616 William Ashley changed: What|Removed |Added Attachment #160568|0 |1 is obsolete|| --- Comment #3 from William Ashley --- Created attachment 160669 --> https://bugs.kde.org/attachment.cgi?id=160669=edit Patch to add FEAT_DotProd support -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 460616] disInstr(arm64): unhandled instruction 0x4E819402
https://bugs.kde.org/show_bug.cgi?id=460616 --- Comment #2 from William Ashley --- On Friday I submitted the change to the valgrind-developers mailing list, https://sourceforge.net/p/valgrind/mailman/valgrind-developers/thread/ed40273d-295d-445c-8d97-9fc48f535...@amazon.com/ -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 441109] [ARM64] Invalid write of size 8 when it's really 16
https://bugs.kde.org/show_bug.cgi?id=441109
--- Comment #2 from William Ashley ---
With stp (store pair), there's a similar problem. Pairs of 32, 64 and 128-bit
values all get reported as the wrong write sizes.
asm volatile ("stp s0, s1, [%0]" :: "r" (ptr) : "s0", "s1", "memory");
asm volatile ("stp d0, d1, [%0]" :: "r" (ptr) : "d0", "d1", "memory");
asm volatile ("stp q0, q1, [%0]" :: "r" (ptr) : "q0", "q1", "memory");
==26048== Invalid write of size 4
==26048==at 0x400630: main (strtest.c:12)
==26048== Address 0x4a1a140 is 0 bytes after a block of size 256 alloc'd
==26048==at 0x48682A4: malloc (vg_replace_malloc.c:431)
==26048==by 0x4005F3: main (strtest.c:3)
==26048==
==26048== Invalid write of size 8
==26048==at 0x400638: main (strtest.c:13)
==26048== Address 0x4a1a140 is 0 bytes after a block of size 256 alloc'd
==26048==at 0x48682A4: malloc (vg_replace_malloc.c:431)
==26048==by 0x4005F3: main (strtest.c:3)
==26048==
==26048== Invalid write of size 8
==26048==at 0x400640: main (strtest.c:14)
==26048== Address 0x4a1a140 is 0 bytes after a block of size 256 alloc'd
==26048==at 0x48682A4: malloc (vg_replace_malloc.c:431)
==26048==by 0x4005F3: main (strtest.c:3)
--
You are receiving this mail because:
You are watching all bug changes.
[valgrind] [Bug 441109] [ARM64] Invalid write of size 8 when it's really 16
https://bugs.kde.org/show_bug.cgi?id=441109
--- Comment #1 from William Ashley ---
To expand on this a bit, here's a sweep through all of the 'str' sizes:
#include
int main(void) {
char *ptr = malloc(256);
ptr += 256;
asm volatile ("str b0, [%0]" :: "r" (ptr) : "b0", "memory");
asm volatile ("str h0, [%0]" :: "r" (ptr) : "h0", "memory");
asm volatile ("str s0, [%0]" :: "r" (ptr) : "s0", "memory");
asm volatile ("str d0, [%0]" :: "r" (ptr) : "d0", "memory");
asm volatile ("str q0, [%0]" :: "r" (ptr) : "q0", "memory");
free(ptr - 256);
return 0;
}
which under the latest valgrind release shows the expected sizes except for q
==5990== Invalid write of size 1
==5990==at 0x400608: main (strtest.c:5)
==5990== Address 0x4a1a140 is 0 bytes after a block of size 256 alloc'd
==5990==at 0x48682A4: malloc (vg_replace_malloc.c:431)
==5990==by 0x4005F3: main (strtest.c:3)
==5990==
==5990== Invalid write of size 2
==5990==at 0x400610: main (strtest.c:6)
==5990== Address 0x4a1a140 is 0 bytes after a block of size 256 alloc'd
==5990==at 0x48682A4: malloc (vg_replace_malloc.c:431)
==5990==by 0x4005F3: main (strtest.c:3)
==5990==
==5990== Invalid write of size 4
==5990==at 0x400618: main (strtest.c:7)
==5990== Address 0x4a1a140 is 0 bytes after a block of size 256 alloc'd
==5990==at 0x48682A4: malloc (vg_replace_malloc.c:431)
==5990==by 0x4005F3: main (strtest.c:3)
==5990==
==5990== Invalid write of size 8
==5990==at 0x400620: main (strtest.c:8)
==5990== Address 0x4a1a140 is 0 bytes after a block of size 256 alloc'd
==5990==at 0x48682A4: malloc (vg_replace_malloc.c:431)
==5990==by 0x4005F3: main (strtest.c:3)
==5990==
==5990== Invalid write of size 8
==5990==at 0x400628: main (strtest.c:9)
==5990== Address 0x4a1a140 is 0 bytes after a block of size 256 alloc'd
==5990==at 0x48682A4: malloc (vg_replace_malloc.c:431)
==5990==by 0x4005F3: main (strtest.c:3)
Decode for the 'q' case does look correct (GET:V128, so it would be a 16-byte
value)
(arm64) 0x400628: str q0, [x0, #0]
-- IMark(0x400628, 4, 0) --
t21 = Add64(GET:I64(16),0x0:I64)
STle(t21) = GET:V128(320)
PUT(272) = 0x40062C:I64
--
You are receiving this mail because:
You are watching all bug changes.
[valgrind] [Bug 441109] [ARM64] Invalid write of size 8 when it's really 16
https://bugs.kde.org/show_bug.cgi?id=441109 William Ashley changed: What|Removed |Added CC||w...@amazon.com -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 438322] disInstr(arm): unhandled instruction: 0xE320F014
https://bugs.kde.org/show_bug.cgi?id=438322 William Ashley changed: What|Removed |Added CC|w...@amazon.com | -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 438322] disInstr(arm): unhandled instruction: 0xE320F014
https://bugs.kde.org/show_bug.cgi?id=438322 William Ashley changed: What|Removed |Added CC||w...@amazon.com -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 460616] disInstr(arm64): unhandled instruction 0x4E819402
https://bugs.kde.org/show_bug.cgi?id=460616 William Ashley changed: What|Removed |Added CC||w...@amazon.com --- Comment #1 from William Ashley --- Created attachment 160568 --> https://bugs.kde.org/attachment.cgi?id=160568=edit Patch to add FEAT_DotProd support I have implemented support for the dot product instructions (more specifically those under the FEAT_DotProd feature). The attached patch file applies cleanly to 'master' as of this writing. I haven't yet figured out the 'correct' process for submitting changes to the valgrind project. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 459225] New: Canvas when editing or selecting it in any fashion it breaks up only showing small squares as you draw
https://bugs.kde.org/show_bug.cgi?id=459225 Bug ID: 459225 Summary: Canvas when editing or selecting it in any fashion it breaks up only showing small squares as you draw Classification: Unclassified Product: krita Version: 5.1.0 Platform: Android OS: Android 7.x Status: REPORTED Severity: normal Priority: NOR Component: CPU Canvas Assignee: krita-bugs-n...@kde.org Reporter: rebekahmattieme...@gmail.com Target Milestone: --- Krita Version: 5.1.0 Hidpi: true Qt Version (compiled): 5.12.12 Version (loaded): 5.12.12 OS Information Build ABI: x86_64-little_endian-lp64 Build CPU: x86_64 CPU: x86_64 Kernel Type: linux Kernel Version: 3.14.79-x86_64-g7f80a31 Pretty Productname: Android Nougat (7.1) Product Type: android Product Version: 7.1 Product Model: LENOVO Lenovo YB1-X90F Locale Languages: en, en_US, en_Latn_US C locale: C QLocale current: en QLocale system: en QTextCodec for locale: UTF-8 OpenGL Info Vendor: "Intel" Renderer: "Intel(R) HD Graphics for Atom(TM) x5/x7" Version: "OpenGL ES 3.1 - Build 4.70.10069-R" Shading language: "OpenGL ES GLSL ES 3.10 - Build 4.70.10069-R" Requested format: QSurfaceFormat(version 2.0, options QFlags(), depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::DoubleBuffer, swapInterval 0, colorSpace QSurfaceFormat::DefaultColorSpace, profile QSurfaceFormat::NoProfile) Current format: QSurfaceFormat(version 3.1, 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.1 Supports deprecated functions false is OpenGL ES: true supportsBufferMapping: true supportsBufferInvalidation: false forceDisableTextureBuffers: false Extensions: "GL_OES_depth_texture_cube_map" "GL_EXT_sRGB_write_control" "GL_OES_copy_image" "GL_OES_required_internalformat" "GL_EXT_map_buffer_range" "GL_EXT_shader_texture_lod" "GL_OES_element_index_uint" "GL_ANDROID_extension_pack_es31a" "GL_OES_texture_storage_multisample_2d_array" "GL_KHR_debug" "GL_INTEL_fragment_shader_ordering" "GL_OES_texture_3D" "GL_EXT_texture_buffer" "GL_KHR_blend_equation_advanced" "GL_OES_EGL_image_external" "GL_OES_tessellation_shader" "GL_OES_EGL_image_external_essl3" "GL_OES_texture_border_clamp" "GL_EXT_shader_integer_mix" "GL_OES_standard_derivatives" "GL_OES_texture_half_float" "GL_EXT_buffer_storage" "GL_EXT_shader_io_blocks" "GL_EXT_texture_cube_map_array" "GL_OES_shader_multisample_interpolation" "GL_OES_surfaceless_context" "GL_EXT_blend_minmax" "GL_EXT_texture_storage" "GL_OES_gpu_shader5" "GL_EXT_texture_compression_s3tc" "GL_OES_packed_depth_stencil" "GL_OES_compressed_paletted_texture" "GL_EXT_YUV_target" "GL_OES_EGL_image" "GL_EXT_separate_shader_objects" "GL_OES_vertex_array_object" "GL_KHR_texture_compression_astc_ldr" "GL_OES_sample_variables" "GL_OES_geometry_point_size" "GL_OES_tessellation_point_size" "GL_EXT_gpu_shader5" "GL_OES_rgb8_rgba8" "GL_EXT_draw_buffers" "GL_EXT_texture_format_BGRA" "GL_OES_shader_io_blocks" "GL_EXT_read_format_bgra" "GL_EXT_occlusion_query_boolean" "GL_EXT_debug_marker" "GL_EXT_texture_type_2_10_10_10_REV" "GL_EXT_texture_border_clamp" "GL_EXT_texture_rg" "GL_EXT_frag_depth" "GL_EXT_multi_draw_arrays" "GL_EXT_texture_sRGB_decode" "GL_OES_mapbuffer" "GL_INTEL_geometry_shader" "GL_OES_texture_half_float_linear" "GL_EXT_color_buffer_float" "GL_INTEL_tessellation" "GL_OES_depth24" "GL_KHR_robustness" "GL_EXT_instanced_arrays" "GL_INTEL_framebuffer_CMAA" "GL_OES_draw_buffers_indexed" "GL_EXT_geometry_point_size" "GL_OES_texture_npot" "GL_OES_EGL_sync" "GL_NV_polygon_mode" "GL_OES_texture_cube_map_array" "GL_EXT_texture_filter_anisotropic" "GL_OES_compressed_ETC1_RGB8_texture" "GL_EXT_draw_buffers_indexed" "GL_EXT_geometry_shader" "GL_EXT_tessellation_shader" "GL_OES_geometry_shader" "GL_EXT_copy_image" "GL_EXT_discard_framebuffer" "GL_EXT_draw_instanced" "GL_OES_texture_buffer" "GL_OES_draw_elements_base_vertex" "GL_EXT_shadow_samplers" "GL_INTEL_performance_query" "GL_EXT_primitive_bounding_box"
[neon] [Bug 455535] Krita 5.05 crashes at saving and when quiting
https://bugs.kde.org/show_bug.cgi?id=455535 --- Comment #3 from Ashley --- An updated package (-> 5.0.8) was published in Neon and this appears to be fixed now. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 455535] Krita 5.05 crashes at saving and when quiting
https://bugs.kde.org/show_bug.cgi?id=455535 Ashley changed: What|Removed |Added CC||ashley.c.wa...@gmail.com --- Comment #2 from Ashley --- Installed Krita in Neon today and ran into this one, and it sure looks like it is that bug and hasn't been updated. In current state this make Krita basically unusable, so I hope someone is watching that can update the package on Neon. Operating System: KDE neon 5.25 KDE Plasma Version: 5.25.0 KDE Frameworks Version: 5.95.0 Qt Version: 5.15.4 Graphics Platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 453224] Nothing happens when I click on 'Next' button
https://bugs.kde.org/show_bug.cgi?id=453224 Ashley changed: What|Removed |Added CC||ashley.c.wa...@gmail.com --- Comment #4 from Ashley --- Hit a similar issue when attempting to click on the 'Developer Information' button in a konqi dialog. file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/PageRow.qml:878: Error: Error while loading page: qrc:/ui/DeveloperPage.qml:8 module "org.kde.syntaxhighlighting" is not installed Was resolved by installing the package qml-module-org-kde-syntaxhighlighting as initial report suggested. Operating System: KDE neon 5.25 KDE Plasma Version: 5.25.0 KDE Frameworks Version: 5.95.0 Qt Version: 5.15.4 Graphics Platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 450865] New: context menus won't open in kde-connect ios
https://bugs.kde.org/show_bug.cgi?id=450865 Bug ID: 450865 Summary: context menus won't open in kde-connect ios Product: kdeconnect Version: unspecified Platform: Apple App Store OS: iOS Status: REPORTED Severity: major Priority: NOR Component: ios-application Assignee: lucas.w...@tuta.io Reporter: ashr...@icloud.com Target Milestone: --- SUMMARY context menus in the top right corner won't stay open for more than a split second on iPhone se STEPS TO REPRODUCE in kde connect ios, press the context menu button in the top right corner OBSERVED RESULT menu closes before any action can be taken EXPECTED RESULT menu remains open until acted upon by user SOFTWARE/OS VERSIONS IOS version: 14.3 KDE Connect for IOS version: v0.2.0 (8) ADDITIONAL INFORMATION I've only experienced this on an iPhone se 1st gen running ios 14.3 Video link: https://cdn.discordapp.com/attachments/694349674252861481/947038026301833216/RPReplay_Final1645861836.MP4 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 448640] App search in kickoff menu shows no results; works in KRunner
https://bugs.kde.org/show_bug.cgi?id=448640 --- Comment #12 from Ashley --- (In reply to Nate Graham from comment #10) > Hmm, I was looking for a hardcoded list of runners in that file, but I don't > see it. No idea what the issue is then, sorry. :( How to reproduce: I had the default panel on 2 monitors. when I removed the kickoff menu from the second panel, The first kickoff menu started preforming normally. I added the menu back to the panel on the 2nd monitor and the bug came back. I removed the menu on the 2nd screen once more and kickoff is working as it should again. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 448640] App search in kickoff menu shows no results; works in KRunner
https://bugs.kde.org/show_bug.cgi?id=448640 --- Comment #9 from Ashley --- Created attachment 145782 --> https://bugs.kde.org/attachment.cgi?id=145782=edit aste the output of `grep -A 50 > org.kde.plasma.kickoff ~/.config/plasma-org.kde.plasma.desktop-appletsrc (In reply to Nate Graham from comment #8) > Cannot reproduce. Can you paste the output of `grep -A 50 > org.kde.plasma.kickoff ~/.config/plasma-org.kde.plasma.desktop-appletsrc` > from a terminal window? Hey Nate, I attached the output of the command you requested. Let me know if you need anything else thanks! -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 448640] App search in kickoff menu shows no results
https://bugs.kde.org/show_bug.cgi?id=448640 --- Comment #5 from Ashley --- Created attachment 145573 --> https://bugs.kde.org/attachment.cgi?id=145573=edit Menu otherwise working fine -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 448640] App search in kickoff menu shows no results
https://bugs.kde.org/show_bug.cgi?id=448640 --- Comment #4 from Ashley --- Created attachment 145572 --> https://bugs.kde.org/attachment.cgi?id=145572=edit Failed Search for dolphin in kickoff menu. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 448640] App search in kickoff menu shows no results
https://bugs.kde.org/show_bug.cgi?id=448640 --- Comment #3 from Ashley --- Created attachment 145571 --> https://bugs.kde.org/attachment.cgi?id=145571=edit Successful Search for dolphin in krunner. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 448640] App search in kickoff menu shows no results
https://bugs.kde.org/show_bug.cgi?id=448640 --- Comment #2 from Ashley --- Created attachment 145570 --> https://bugs.kde.org/attachment.cgi?id=145570=edit Failed Search for discord in kickoff menu. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 448640] App search in kickoff menu shows no results
https://bugs.kde.org/show_bug.cgi?id=448640 Ashley changed: What|Removed |Added Attachment #145569|1 |Successful Search for description||discord in krunner. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 448640] App search in kickoff menu shows no results
https://bugs.kde.org/show_bug.cgi?id=448640 --- Comment #1 from Ashley --- Created attachment 145569 --> https://bugs.kde.org/attachment.cgi?id=145569=edit 1 -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 448640] New: App search in kickoff menu shows no results
https://bugs.kde.org/show_bug.cgi?id=448640 Bug ID: 448640 Summary: App search in kickoff menu shows no results Product: krunner Version: 5.23.4 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: alexander.loh...@gmx.de Reporter: freakinfedorafr...@gmail.com CC: plasma-b...@kde.org Target Milestone: --- SUMMARY App search in kickoff menu shows no results. krunner search does still show expect results. Kickoff menu works normally outside of failed searches. SOFTWARE/OS VERSIONS Operating System: Fedora Linux 35 KDE Plasma Version: 5.23.4 KDE Frameworks Version: 5.89.0 Qt Version: 5.15.2 Kernel Version: 5.15.14-200.fc35.x86_64 (64-bit) Graphics Platform: Wayland Processors: 4 × Intel® Core™ i5-4210U CPU @ 1.70GHz Memory: 7.7 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 4400 ADDITIONAL INFORMATION below are screenshots of two separate searches done in both krunner search and kickoff search, and a screenshot of menu working properly otherwise. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 448639] New: App search in kickoff menu shows no results
https://bugs.kde.org/show_bug.cgi?id=448639 Bug ID: 448639 Summary: App search in kickoff menu shows no results Product: krunner Version: 5.23.4 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: alexander.loh...@gmx.de Reporter: freakinfedorafr...@gmail.com CC: plasma-b...@kde.org Target Milestone: --- Created attachment 145568 --> https://bugs.kde.org/attachment.cgi?id=145568=edit failed search in kickoff SUMMARY App search in kickoff menu shows no results. krunner search does still show expect results. Kickoff menu works normally outside of failed searches. SOFTWARE/OS VERSIONS Operating System: Fedora Linux 35 KDE Plasma Version: 5.23.4 KDE Frameworks Version: 5.89.0 Qt Version: 5.15.2 Kernel Version: 5.15.14-200.fc35.x86_64 (64-bit) Graphics Platform: Wayland Processors: 4 × Intel® Core™ i5-4210U CPU @ 1.70GHz Memory: 7.7 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 4400 ADDITIONAL INFORMATION below are screenshots of two separate searches done in both krunner search and kickoff search, and a screenshot of menu working properly otherwise. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 431637] Include kaccounts-integration by default
https://bugs.kde.org/show_bug.cgi?id=431637 Ashley Stone changed: What|Removed |Added CC||a...@konqi.dev --- Comment #1 from Ashley Stone --- Some proposed changes to fix this: https://invent.kde.org/neon/neon/seeds/-/merge_requests/1 https://invent.kde.org/neon/kde/purpose/-/merge_requests/1 -- You are receiving this mail because: You are watching all bug changes.
[OCS] [Bug 431619] New: Username length not uniform
https://bugs.kde.org/show_bug.cgi?id=431619 Bug ID: 431619 Summary: Username length not uniform Product: OCS Version: unspecified Platform: Other OS: All Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: lei...@leinir.dk Reporter: a...@konqi.dev Target Milestone: --- SUMMARY Minimum user length is 4 characters, while other KDE infrastructure allows three characters. Right now it is set to 4 and I would like to retain the same username I use everywhere else in KDE's infrastructure, which is 3 characters long. STEPS TO REPRODUCE 1. Visit https://store.kde.org/ 2. Select 'register' in the top right corner 3. Enter a username of 'aaa' OBSERVED RESULT An error message is presented: "The input is less than 4 characters long Username may only contain lower case alphanumeric characters or single hyphens, and cannot begin or end with a hyphen" EXPECTED RESULT Ability to use similar user lengths permitted else where by KDE sites. -- You are receiving this mail because: You are watching all bug changes.
[www.kde.org] [Bug 431618] New: KDE international sites: KDE Ireland link is broken
https://bugs.kde.org/show_bug.cgi?id=431618 Bug ID: 431618 Summary: KDE international sites: KDE Ireland link is broken Product: www.kde.org Version: unspecified Platform: Other OS: All Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kde-...@kde.org Reporter: a...@konqi.dev Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Visit https://kde.org/support/international/ 2. Click "Ireland" link. 3. Bypass SSL errors OBSERVED RESULT The page does not present anything in relation to KDE Ireland. EXPECTED RESULT International site links to link to working sites. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 426457] neondocker script is broken, because uses outdated api
https://bugs.kde.org/show_bug.cgi?id=426457 Ashley Stone changed: What|Removed |Added CC||a...@konqi.dev --- Comment #1 from Ashley Stone --- I have been able to reproduce this on fresh Neon installs. Apparently this cannot be reproduced on some older installations. Uploaded a rapid way of generating a environment that reproduces the issue, see: https://invent.kde.org/ash/bug-426457 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 401275] New: Discover app crashes on load
https://bugs.kde.org/show_bug.cgi?id=401275 Bug ID: 401275 Summary: Discover app crashes on load Product: Discover Version: 5.13.5 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: discover Assignee: aleix...@kde.org Reporter: ash...@zf4.biz Target Milestone: --- Application: plasma-discover (5.13.5) Qt Version: 5.11.1 Frameworks Version: 5.50.0 Operating System: Linux 4.18.0-10-generic x86_64 Distribution: Ubuntu 18.10 -- Information about the crash: - Clicked on toolbar notification icon to open updater (Discover). Crashes almost immediately. Tried opening manually from menu. Same result. The crash can be reproduced every time. -- Backtrace: Application: Discover (plasma-discover), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7ff2271e8cc0 (LWP 15902))] Thread 8 (Thread 0x7ff2097cb700 (LWP 15981)): #0 0x7ff22fa59219 in syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 #1 0x7ff22fd72cf4 in QSemaphore::acquire(int) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7ff22ff4f978 in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7ff22f2e508b in () at /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #4 0x7ff22f38c04d in () at /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #5 0x7ff22ff4f6db in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7ff22f2dadbd in () at /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #7 0x7ff22f2db76d in () at /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #8 0x7ff22ff4f6db in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7ff22f385cff in () at /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #10 0x7ff22f380d39 in () at /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #11 0x7ff22f3811cd in () at /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #12 0x7ff22f363511 in () at /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #13 0x7ff22ff4f6db in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #14 0x7ff22f324d03 in () at /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #15 0x7ff22f324d90 in () at /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #16 0x7ff22f337331 in () at /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #17 0x7ff230d804a1 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #18 0x7ff230d87ae0 in QApplication::notify(QObject*, QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #19 0x7ff22ff26499 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #20 0x7ff22ff78d6a in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #21 0x7ff22d4fcc3e in g_main_context_dispatch () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #22 0x7ff22d4fced8 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #23 0x7ff22d4fcf6c in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #24 0x7ff22ff78143 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #25 0x7ff22ff2516b in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #26 0x7ff22fd740b6 in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #27 0x7ff22fd7dc87 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #28 0x7ff22eb07164 in start_thread (arg=) at pthread_create.c:486 #29 0x7ff22fa5fdef in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 7 (Thread 0x7ff20bfff700 (LWP 15967)): #0 0x7ff22fa59219 in syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 #1 0x7ff22fd72cf4 in QSemaphore::acquire(int) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7ff22ff4f978 in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7ff22f2e508b in () at /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #4 0x7ff22f38c04d in () at /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #5 0x7ff22ff4f6db in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7ff22f2dadbd in () at /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #7 0x7ff22f2db76d in () at /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #8 0x7ff22ff4f6db in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7ff22f385cff in () at /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #10 0x7ff22f380d39 in () at /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #11 0x7ff22f3811cd
[systemsettings] [Bug 372451] mouse cursor is small in titlebar, large elsewhere
https://bugs.kde.org/show_bug.cgi?id=372451 --- Comment #6 from Ashley <ashleylest...@gmail.com> --- Update: the behaviour seems to be consistent now. The cursor is the correct size everywhere apart from Firefox and Emacs, so this may be a GTK related issue. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 372451] mouse cursor is small in titlebar, large elsewhere
https://bugs.kde.org/show_bug.cgi?id=372451 Ashley <ashleylest...@gmail.com> changed: What|Removed |Added CC||ashleylest...@gmail.com --- Comment #5 from Ashley <ashleylest...@gmail.com> --- I'm using KDE Neon (KDE 5.9 on Ubuntu 16.04). I'm running it on a Macbook with Retina display. I scaled the display to 2x in system settings. The mouse cursor behaviour varies from run-to-run. It is normally the correct size (i.e. 48x) when: - on the desktop background - within the window borders in an application, apart from Firefox - on icons, text elements and the taskbar It is normally the incorrect size (i.e. 24x) when: - on the backgrounds of taskbar widgets, e.g. calender, launcher, volume, etc, unless over a text element or icon within that taskbar widget - on window borders (upper, lower, left, right) and the window title (i.e. generally window decorations) Setting the cursor size to 48x instead of resolution dependent does not affect behaviour. Occasionally, a restart, or a power-down, wait a while, power-up, fixes some instances. For example, right now, it's correct everywhere apart from within the window borders on Firefox. The behaviour does not seem to be dependent on cursor theme. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 364549] Cannot boot into lvm encrypted system after kernel upgrade
https://bugs.kde.org/show_bug.cgi?id=364549 --- Comment #10 from Ashley D. <l...@neko.lgbt> --- I've had this happen a few times myself. I've found myself reinstalling Neon for it. On the most current install I noticed it right after a system update that I completed through the update notification/Discover app. I suspected this update had something to do with it so immediately after it was done I checked for lv* commands. All missing. I attached the relevant logs. I'm going to reinstall lvm2 manually. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 364549] Cannot boot into lvm encrypted system after kernel upgrade
https://bugs.kde.org/show_bug.cgi?id=364549 --- Comment #9 from Ashley D. <l...@neko.lgbt> --- Created attachment 100671 --> https://bugs.kde.org/attachment.cgi?id=100671=edit Dpkg log right after the update that removed LVM2 -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 364549] Cannot boot into lvm encrypted system after kernel upgrade
https://bugs.kde.org/show_bug.cgi?id=364549 --- Comment #8 from Ashley D. <l...@neko.lgbt> --- Created attachment 100670 --> https://bugs.kde.org/attachment.cgi?id=100670=edit Apt Term log right after the update that removed LVM2 -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 364549] Cannot boot into lvm encrypted system after kernel upgrade
https://bugs.kde.org/show_bug.cgi?id=364549 Ashley D. <l...@neko.lgbt> changed: What|Removed |Added CC||l...@neko.lgbt --- Comment #7 from Ashley D. <l...@neko.lgbt> --- Created attachment 100669 --> https://bugs.kde.org/attachment.cgi?id=100669=edit Apt History log right after the update that removed LVM2 This is taken moments after Discover installed an update and I found LVM2 missing. No reboots or further apt actions have been taken. Near the bottom you can see the Remove: that gets rid of liblvm2cmd2, libdevmapper, dmeventd, lvm2, liblvm2app2, and libreadline5 -- You are receiving this mail because: You are watching all bug changes.
