[amarok] [Bug 487937] Amarok crashes on startup in Debian
https://bugs.kde.org/show_bug.cgi?id=487937 Josep Febrer changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 487937] Amarok crashes on startup in Debian
https://bugs.kde.org/show_bug.cgi?id=487937 --- Comment #4 from Josep Febrer --- (In reply to Tuomas Nurmi from comment #3) > Thank you for the additional information! > > Sounds somewhat odd. However, the fact that you encounter the crash on > multiple machines, but people using the official Debian packages don't seem > to have the problem in general, would suggest there might be some common > denominator in your environment. > I guess one possibility could be something related to your systems' locale > (the "mysql_embedded: Warning: Charset id '83' csname 'utf8' trying to > replace existing csname 'utf8mb3'" doesn't sound like something I recall > seeing in output myself, but I'm not sure); or, seeing the samba libs in > backtrace, something related to your network environment. > I wonder what would happen if you tried temporarily removing/hiding > libsamba-util.so.0 I finally tracked out the real issue. Your suggestions put me on the right track. However, if I moved libsamba-util.so.0 then amarok didn't start due to a missing library. I did a ldd to /usr/bin/amarok and it showed some samba libraries linked, which seemed odd. Later I tried to build amarok without ffmpeg, but in order to compile it I had to disable also libofa. Then amarok started and it ran flawless! Reviewing my ffmpeg libs packages then I remembered that I'm using deb-multimedia, an external repository, and it's package libavformat60 has a dependency on libsmbclient0 while the official Debian package hasn't. So when I replaced libavformat60 and other ffmpeg library packages to the Debian's ones, then amarok worked and it didn't link to any samba library. Also with the official Debian packages from experimental builded with ffmpeg but not using the external package that linked to samba libraries amarok worked really great. Sorry for all the inconveniences. It feel so great having amarok running up again. I missed it so much! -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 487937] Amarok crashes on startup in Debian
https://bugs.kde.org/show_bug.cgi?id=487937 --- Comment #2 from Josep Febrer --- (In reply to Tuomas Nurmi from comment #1) > Thank you for your report; looks interesting. The fact that bitmap_copy in > libsamba-util.so.0 is called from libmariadbd.so.19 seems a little > suspicious (I could be wrong, though); at least on my openSUSE system, > libmariadbd.so.19 doesn't seem to link against anything samba related. > I'll try to figure out if there's something that could be easily tested (or > possibly I'll try installing a Debian sid system myself later and see if I > can reproduce) Thank you for your response. Also, there are now official amarok packages on Debian experimental, but I've got the same crash on startup in two machines with these packages. If I start amarok from a terminal without --debug I got this output: amarok ** ** AMAROK WAS STARTED IN NORMAL MODE. IF YOU WANT TO SEE DEBUGGING INFORMATION, PLEASE USE: ** ** amarok --debug ** ** mysql_embedded: Warning: Charset id '33' csname 'utf8' trying to replace existing csname 'utf8mb3' mysql_embedded: Warning: Charset id '83' csname 'utf8' trying to replace existing csname 'utf8mb3' Got ERROR: "Can't open and lock privilege tables: Table 'mysql.servers' doesn't exist" errno: 2000 20 -- exe=/usr/bin/amarok 17 -- platform=wayland 15 -- appname=amarok 17 -- apppath=/usr/bin 10 -- signal=11 9 -- pid=9397 17 -- appversion=3.0.1 19 -- programname=Amarok 31 -- bugaddress=sub...@bugs.kde.org KCrash: crashing... crashRecursionCounter = 2 KCrash: Application Name = amarok path = /usr/bin pid = 9397 KCrash: Arguments: /usr/bin/amarok The Wayland connection experienced a fatal error: El descriptor de fitxer no és vàlid Also, I tried to run amarok under Wayland or X11, but with the same crash. It seems that libsamba-util.so.0 it's not directly linked to libmariadbd.so.19: ldd /usr/lib/x86_64-linux-gnu/libmariadbd.so.19 linux-vdso.so.1 (0x7ffe7ce7c000) libpcre2-8.so.0 => /lib/x86_64-linux-gnu/libpcre2-8.so.0 (0x7f811f29c000) libcrypt.so.1 => /lib/x86_64-linux-gnu/libcrypt.so.1 (0x7f811f26) libnuma.so.1 => /lib/x86_64-linux-gnu/libnuma.so.1 (0x7f811f251000) libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x7f811f232000) libssl.so.3 => /lib/x86_64-linux-gnu/libssl.so.3 (0x7f811d10a000) libcrypto.so.3 => /lib/x86_64-linux-gnu/libcrypto.so.3 (0x7f811ca0) liburing.so.2 => /lib/x86_64-linux-gnu/liburing.so.2 (0x7f811f228000) libstdc++.so.6 => /lib/x86_64-linux-gnu/libstdc++.so.6 (0x7f811c60) libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7f811d028000) libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f811c41b000) /lib64/ld-linux-x86-64.so.2 (0x7f811f366000) libzstd.so.1 => /lib/x86_64-linux-gnu/libzstd.so.1 (0x7f811c93f000) libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x7f811cffb000) One more strange thing is that I've got amarok running, but only once executed with: strace amarok. Later crashed while scanning the music folder. But I never got running again, even after I delete all configuration files under .config and .local/share. -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 487937] New: Amarok crashes on startup in Debian
https://bugs.kde.org/show_bug.cgi?id=487937 Bug ID: 487937 Summary: Amarok crashes on startup in Debian Classification: Applications Product: amarok Version: unspecified Platform: Debian unstable OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: amarok-bugs-d...@kde.org Reporter: jfeb...@gmail.com Target Milestone: kf5 Application: amarok (3.0.0-git) Qt Version: 6.6.2 Frameworks Version: 6.3.0 Operating System: Linux 6.9.3-josep1 x86_64 Windowing System: X11 Distribution: Debian GNU/Linux trixie/sid DrKonqi: 6.0.80 [KCrashBackend] -- Information about the crash: I builded Amarok 3.0 and also from current git master but it always crashes on startup. However if I move or remove /usr/lib/x86_64-linux-gnu/qt5/plugins/amarok_collection-mysqlcollection.so then Amarok starts but it's unable to build a local music collection. I'm using Debian unstable with Qt 5.15.13, KDE Plasma 5.27.11, KDE Framework 5.115.0 and MariaDB 10.11.8 same version for the embedded version. Starting Amarok with the --debug from the terminal I get this output: amarok --debug Qt: Session management error: None of the authentication protocols specified are supported amarok: BEGIN: void App::continueInit() amarok: BEGIN: virtual int App::newInstance() amarok: BEGIN: void App::handleCliArgs(const QString&) amarok: END__: void App::handleCliArgs(const QString&) [Took: 0s] amarok: END__: virtual int App::newInstance() [Took: 0s] amarok: BEGIN: EngineController::EngineController() amarok: END__: EngineController::EngineController() [Took: 0s] amarok: BEGIN: void EngineController::initializePhonon() QObject::connect: No such signal Phonon::VLC::MediaObject::angleChanged(int) QObject::connect: No such signal Phonon::VLC::MediaObject::availableAnglesChanged(int) amarok: BEGIN: void EqualizerController::initialize(const Phonon::Path&) amarok: [EqualizerController] Established Phonon equalizer effect with 11 parameters. amarok: BEGIN: void EqualizerController::eqUpdate() amarok: END__: void EqualizerController::eqUpdate() [Took: 0s] amarok: END__: void EqualizerController::initialize(const Phonon::Path&) [Took: 0s] WARNING: Phonon::createPath: Cannot connect Phonon::MediaObject ( no objectName ) to Phonon::AudioDataOutput ( no objectName ). amarok: [EngineController] Tick Interval (actual): 100 amarok: END__: void EngineController::initializePhonon() [Took: 0.016s] amarok: BEGIN: CollectionManager::CollectionManager() amarok: END__: CollectionManager::CollectionManager() [Took: 0s] amarok: BEGIN: MainWindow::MainWindow() amarok: BEGIN: Plugins::PluginManager::PluginManager(QObject*) amarok: BEGIN: void Plugins::PluginManager::checkPluginEnabledStates() amarok: [PluginManager] found plugin: "amarok_collection-ipodcollection" enabled: true amarok: [PluginManager] found plugin: "amarok_service_lastfm" enabled: true amarok: [PluginManager] Plugin "amarok_storage-mysqlserverstorage" is vital amarok: [PluginManager] found plugin: "amarok_storage-mysqlserverstorage" enabled: true amarok: [PluginManager] found plugin: "amarok_service_ampache" enabled: false amarok: [PluginManager] found plugin: "amarok_importer-itunes" enabled: true amarok: [PluginManager] Plugin "amarok_collection-mysqlcollection" is vital amarok: [PluginManager] found plugin: "amarok_collection-mysqlcollection" enabled: true amarok: [PluginManager] found plugin: "amarok_collection-daapcollection" enabled: false amarok: [PluginManager] found plugin: "amarok_collection-umscollection" enabled: true amarok: [PluginManager] Plugin "amarok_storage-mysqlestorage" is vital amarok: [PluginManager] found plugin: "amarok_storage-mysqlestorage" enabled: true amarok: [PluginManager] found plugin: "amarok_importer-clementine" enabled: true amarok: [PluginManager] found plugin: "amarok_importer-banshee" enabled: true amarok: [PluginManager] found plugin: "amarok_service_magnatunestore" enabled: true amarok: [PluginManager] found plugin: "amarok_collection-playdarcollection" enabled: false amarok: [PluginManager] found plugin: "amarok_collection-audiocdcollection" enabled: true amarok: [PluginManager] found plugin: "amarok_collection-mtpcollection" enabled: true amarok: [PluginManager] found plugin: "amarok_service_gpodder" enabled: false amarok: [PluginManager] found plugin: "amarok_importer-rhythmbox" enabled: true amarok: [PluginManager] found plugin: "amarok_importer-fastforward" enabled: true amarok: [PluginManager] found plugin: "amarok_service_opmldirectory" enabled: true amarok: [PluginManager] found plugin: "amarok_importer-amarok" enabled:
[krita] [Bug 471988] Krita crashes on creating a new file or opening a saved one
https://bugs.kde.org/show_bug.cgi?id=471988 --- Comment #8 from Josep Febrer --- With MLT 7.18 Krita no longer crashes. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 471988] Krita crashes on creating a new file or opening a saved one
https://bugs.kde.org/show_bug.cgi?id=471988 --- Comment #6 from Josep Febrer --- I downgraded libmlt from 7.16 to 7.14 rebuild Krita and I've got the same crash. Then I figured out that my 1st May build that works was build without libmlt, as I don't make animation I didn't notice it. Later, I rebuild Krita without libmlt and didn't crash, so that's the reason. I think before I never compiled Krita with libmlt and one day noticed in the build log and installed it, and then I didn't relate the crash to it. It's not something that I will miss as I don't plan to do animation, but the reason maybe the version of libmlt or the way it's packaged on Debian. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 471988] Krita crashes on creating a new file or opening a saved one
https://bugs.kde.org/show_bug.cgi?id=471988 --- Comment #5 from Josep Febrer --- That maybe the reason. I looked at the packages and I see that libmlt was upgraded in my distribution when I started to have this crash. Later I will look and try with other versions. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 471988] Krita crashes on creating a new file or opening a saved one
https://bugs.kde.org/show_bug.cgi?id=471988 --- Comment #3 from Josep Febrer --- (In reply to Halla Rempt from comment #2) > I cannot reproduce this with a build from that git sha1. Is this the nightly > appimage or a build against distribution dependencies? Yes, it's a custom build against distribution dependencies. With the nightly appimage it didn't crash. I had the same problem with Qt 5.15.8, then I upgraded to Qt 5.15.10, but it was the same, so I don't think it's Qt related. I usually build from master from time to time and this problem happened since some weeks ago, unfortunately I can't remember exactly when it started. Likewise, I have a build from 1st May that works and didn't build a new one from master until mid of June, where it was affected by this crash. Also, I remember that I upgraded from xsimd 8.1 to 9.0.1, but I don't know if it can cause this, later I will try to downgrade. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 471988] Krita crashes on creating a new file or opening a saved one
https://bugs.kde.org/show_bug.cgi?id=471988 --- Comment #1 from Josep Febrer --- Created attachment 160094 --> https://bugs.kde.org/attachment.cgi?id=160094=edit gdb backtrace -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 471988] New: Krita crashes on creating a new file or opening a saved one
https://bugs.kde.org/show_bug.cgi?id=471988 Bug ID: 471988 Summary: Krita crashes on creating a new file or opening a saved one Classification: Applications Product: krita Version: git master (please specify the git hash!) Platform: Debian unstable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: jfeb...@gmail.com Target Milestone: --- Created attachment 160093 --> https://bugs.kde.org/attachment.cgi?id=160093=edit Coredump from coredumpctl Krita build from current master starts correctly but it crashes when I choose to create a new file or load a saved one. Krita Version: 5.2.0-prealpha (git abb27a2) Hidpi: false Qt Version (compiled): 5.15.10 Version (loaded): 5.15.10 OS Information Build ABI: x86_64-little_endian-lp64 Build CPU: x86_64 CPU: x86_64 Kernel Type: linux Kernel Version: 6.4.2 Pretty Productname: Debian GNU/Linux trixie/sid Product Type: debian Product Version: unstable Desktop: KDE Plasma 5.27.6 Locale Languages: ca, ca, ca, es, es, es C locale: ca_ES.UTF-8 QLocale current: ca QLocale system: ca QTextCodec for locale: UTF-8 OpenGL Info Vendor: "AMD" Renderer: "AMD Radeon RX 570 Series (polaris10, LLVM 15.0.7, DRM 3.52, 6.4.2-josep1)" Driver version: "4.6 (Core Profile) Mesa 23.1.3-1" Shading language: "4.60" Requested format: QSurfaceFormat(version 3.3, 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::CompatibilityProfile) Current format: QSurfaceFormat(version 4.6, 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::CoreProfile) GL version: 4.6 Supports deprecated functions false Is OpenGL ES: false supportsBufferMapping: true supportsBufferInvalidation: true forceDisableTextureBuffers: false Extensions: GL_ARB_shader_group_vote GL_EXT_framebuffer_multisample_blit_scaled GL_KHR_robust_buffer_access_behavior GL_KHR_blend_equation_advanced GL_ARB_texture_float GL_ARB_vertex_attrib_binding GL_ARB_texture_multisample GL_ARB_get_program_binary GL_EXT_draw_buffers2 GL_ARB_multi_bind GL_AMD_pinned_memory GL_ARB_shader_image_load_store GL_ARB_texture_storage GL_EXT_pixel_buffer_object GL_NVX_gpu_memory_info GL_ARB_texture_buffer_object_rgb32 GL_EXT_demote_to_helper_invocation GL_ARB_texture_filter_anisotropic GL_ARB_texture_compression_rgtc GL_ARB_ES2_compatibility GL_EXT_vertex_array_bgra GL_ARB_shader_stencil_export GL_EXT_debug_label GL_MESA_framebuffer_flip_y GL_NV_compute_shader_derivatives GL_ARB_texture_query_levels GL_ARB_fragment_coord_conventions GL_EXT_texture_sRGB_R8 GL_NV_vdpau_interop GL_AMD_performance_monitor GL_ARB_shader_storage_buffer_object GL_NV_conditional_render GL_EXT_memory_object_fd GL_IBM_multimode_draw_arrays GL_ARB_tessellation_shader GL_ARB_shader_precision GL_ARB_derivative_control GL_EXT_texture_filter_anisotropic GL_ARB_conservative_depth GL_ARB_shader_texture_image_samples GL_EXT_framebuffer_multisample GL_S3_s3tc GL_ARB_copy_image GL_ARB_base_instance GL_ARB_gpu_shader5 GL_ARB_sampler_objects GL_ARB_framebuffer_sRGB GL_ARB_provoking_vertex GL_ARB_shader_objects GL_AMD_multi_draw_indirect GL_ARB_separate_shader_objects GL_ARB_robustness GL_ARB_vertex_array_object GL_EXT_polygon_offset_clamp GL_ARB_texture_cube_map_array GL_KHR_context_flush_control GL_EXT_EGL_image_storage GL_ARB_bindless_texture GL_EXT_texture_swizzle GL_EXT_window_rectangles GL_ARB_copy_buffer GL_ARB_shader_clock GL_EXT_texture_sRGB_decode GL_NV_packed_depth_stencil GL_ARB_sample_shading GL_ANGLE_texture_compression_dxt3 GL_ARB_texture_query_lod GL_ARB_vertex_array_bgra GL_ARB_texture_non_power_of_two GL_AMD_shader_trinary_minmax GL_ARB_depth_buffer_float GL_ARB_shading_language_include GL_ARB_blend_func_extended GL_ARB_transform_feedback_instanced GL_ARB_shading_language_packing GL_NV_shader_atomic_int64 GL_AMD_gpu_shader_int64 GL_ARB_vertex_buffer_object
[Breeze] [Bug 454031] Specific Color Selector does not show color in the RGB sliders
https://bugs.kde.org/show_bug.cgi?id=454031 --- Comment #17 from Josep Febrer --- Thank you! It's a pleasure to use back the Breeze style with Krita. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 454031] Specific Color Selector does not show color in the RGB sliders
https://bugs.kde.org/show_bug.cgi?id=454031 --- Comment #11 from Josep Febrer --- (In reply to David Edmundson from comment #9) > That's a disappointing approach. You'd be frustrated if Plasma devs masked > krita from our menus on immediate receipt of a bug report. I don't think they are comparable situations, what Halla did was just to prevent user's frustration, and not to discredit any KDE developer. I'm sure she will restore Breeze style support when this bug will be fixed. To be fair, I prefer to use Krita with the Breeze style and even I built Krita myself to have better KDE integration, but this bug hits my workflow. In the meanwhile, I prefer to user Krita with the Fusion style until this bug is fixed. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 454031] Specific Color Selector does not show color in the RGB sliders
https://bugs.kde.org/show_bug.cgi?id=454031 --- Comment #2 from Josep Febrer --- I built Krita from latest master, 76a9e434dd, and as this bug explains the sliders from Specific Color Selector docker in my case they only show the black no matter how you move the slider. I suspect that his bug it's due to Qt 5.15, I'll use the version from KDE's git, and even tried to apply Krita patches, most of them are already applied on Qt from KDE git, but still the sliders don't update the color, and they remain in black. With the Krita appimage from Krita Next which uses Qt 5.12 this docker works as expected. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 454031] Specific Color Selector does not show color in the RGB sliders
https://bugs.kde.org/show_bug.cgi?id=454031 Josep Febrer changed: What|Removed |Added CC||jfeb...@gmail.com --- Comment #1 from Josep Febrer --- Created attachment 150398 --> https://bugs.kde.org/attachment.cgi?id=150398=edit Black color in the the color sliders with Qt 5.15 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 446054] Zoom effect freezes screen only on Wayland
https://bugs.kde.org/show_bug.cgi?id=446054 Josep Febrer changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #1 from Josep Febrer --- Fixed by Vlad's commit 1f318a2245f9f887a2bf8aa320dc905a012842df. *** This bug has been marked as a duplicate of bug 445412 *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 445412] Zoom effect causes screen to stop updating
https://bugs.kde.org/show_bug.cgi?id=445412 Josep Febrer changed: What|Removed |Added CC||jfeb...@gmail.com --- Comment #13 from Josep Febrer --- *** Bug 446054 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 446054] New: Zoom effect freezes screen only on Wayland
https://bugs.kde.org/show_bug.cgi?id=446054 Bug ID: 446054 Summary: Zoom effect freezes screen only on Wayland Product: kwin Version: git master Platform: Debian unstable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: effects-various Assignee: kwin-bugs-n...@kde.org Reporter: jfeb...@gmail.com Target Milestone: --- SUMMARY *** After building KWin from the latest git master I found that when I activate the zoom effect on Wayland the screen freezes and the cursor disappears. I haven't found a way to restore it. I have to go to a tty to restart the session. When the freeze happens I discovered that the keyboard is still responding because I can stop a window which is playing music with a keyboard shortcut but even if I exit the session with a keyboard shortcut the screen remains friezed as nothing happened. Under X11 I can use the zoom effect as usual without any issue. *** STEPS TO REPRODUCE 1. Turn on the zoom effect on system settings. 2. Use the zoom effect with a keyboard shortcut. OBSERVED RESULT The screen freezes completely and I have to go a tty to be able to restart the desktop session. EXPECTED RESULT The screen should be zoomed. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Debian GNU/Linux unstable (available in About System) KDE Plasma Version: 5.23.80 KDE Frameworks Version: 5.88.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 394023] Icon request: gPodder application icon
https://bugs.kde.org/show_bug.cgi?id=394023 --- Comment #2 from Josep Febrer --- Thank you! Really nice icon! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 442196] New: Plasmashell crash when power off the monitor under Wayland on Radeon
https://bugs.kde.org/show_bug.cgi?id=442196 Bug ID: 442196 Summary: Plasmashell crash when power off the monitor under Wayland on Radeon Product: plasmashell Version: master Platform: Debian unstable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: generic-crash Assignee: plasma-b...@kde.org Reporter: jfeb...@gmail.com Target Milestone: 1.0 SUMMARY The Plasmashell desktop and it's process crash when I power off and then power on the monitor under Wayland on a Radeon RX 570 graphics card. The desktop and it's panels disappear but the running applications and Kwin didn't crash. I'm using Debian unstable with self compiled packages created from current master git branch. Using the same packages on another machine using an integrated Intel graphics card, plasmashell didn't crash and continue to work as expected. STEPS TO REPRODUCE 1. Power off and the powering on the monitor on Plasma under Wayland on a Radeon graphics card. OBSERVED RESULT The plasma desktop and it's process crash and disappear, but KWin and the running applications didn't. EXPECTED RESULT Plasma desktop should not crash, as it didn't crash on the same machine under a X11 session or it didn't crash on Wayland using Intel integrated graphics card. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Debian Sid with kernel 5.14.2 (available in About System) KDE Plasma Version: 5.22.80 KDE Frameworks Version: 5.86.0 Qt Version: 5.15.2 Mesa 21.2.1 ADDITIONAL INFORMATION coredumpctl debug plasmashell PID: 1307 (plasmashell) UID: 1000 (josep) GID: 1000 (josep) Signal: 6 (ABRT) Timestamp: Wed 2021-09-08 23:48:01 CEST (23s ago) Command Line: /usr/bin/plasmashell --no-respawn Executable: /usr/bin/plasmashell Control Group: /user.slice/user-1000.slice/user@1000.service/session.slice/plasma-plasmashell.service Unit: user@1000.service User Unit: plasma-plasmashell.service Slice: user-1000.slice Owner UID: 1000 (josep) Boot ID: 90118916b25f40428dd45cd5614d29f5 Machine ID: c7e3dc631e753203c63640f50261 Hostname: josep Storage: /var/lib/systemd/coredump/core.plasmashell.1000.90118916b25f40428dd45cd5614d29f5.1307.163113768100.zst Message: Process 1307 (plasmashell) of user 1000 dumped core. Stack trace of thread 1307: #0 0x7f553130e377 __GI___pthread_sigmask (libc.so.6 + 0x85377) #1 0x7f55312c6119 __GI___sigprocmask (libc.so.6 + 0x3d119) #2 0x7f55336b6d2b _ZN6KCrash15setCrashHandlerEPFviE (libKF5Crash.so.5 + 0x4d2b) #3 0x7f55336b7a89 _ZN6KCrash19defaultCrashHandlerEi (libKF5Crash.so.5 + 0x5a89) #4 0x7f55312c5ef0 __restore_rt (libc.so.6 + 0x3cef0) #5 0x7f55312c5e71 __GI_raise (libc.so.6 + 0x3ce71) #6 0x7f55312af536 __GI_abort (libc.so.6 + 0x26536) #7 0x7f55316e7bf1 _ZNK14QMessageLogger5fatalEPKcz (libQt5Core.so.5 + 0x91bf1) #8 0x7f552f36fde0 _ZNK15QtWaylandClient15QWaylandDisplay10checkErrorEv (libQt5WaylandClient.so.5 + 0x74de0) #9 0x7f552f370dfa _ZN15QtWaylandClient15QWaylandDisplay13flushRequestsEv (libQt5WaylandClient.so.5 + 0x75dfa) #10 0x7f552f378cdf n/a (libQt5WaylandClient.so.5 + 0x7dcdf) #11 0x7f5531cea3a3 _ZN14QWindowPrivate10setVisibleEb (libQt5Gui.so.5 + 0x1493a3) #12 0x562b90bdaf08 n/a (plasmashell + 0x47f08) #13 0x7f553193a5a6 n/a (libQt5Core.so.5 + 0x2e45a6) #14 0x7f5531cd0612 _ZN15QGuiApplication20primaryScreenChangedEP7QScreen (libQt5Gui.so.5 + 0x12f612) #15 0x7f5531d07e95 _ZN7QScreenD1Ev (libQt5Gui.so.5 + 0x166e95) #16 0x7f5531d081d9 _ZN7QScreenD0Ev (libQt5Gui.so.5 + 0x1671d9) #17 0x7f5531cb3a77 _ZN22QWindowSystemInterface19handleScreenRemovedEP15QPlatformScreen (libQt5Gui.so.5 + 0x112a77) #18 0x7f552f37249d _ZN15QtWaylandClient15QWaylandDisplay22registry_global_removeEj (libQt5WaylandClient.so.5 + 0x7749d) #19 0x7f552f72cd1d n/a (libffi.so.7 + 0x6d1d) #20 0x7f552f72c289 n/a (libffi.so.7 + 0x6289) #21 0x7f55312392d2 n/a (libwayland-client.so.0 + 0x92d2) #22 0x7f553123597a n/a (libwayland-client.so.0 + 0x597a) #23 0x7f553123703c wl_display_dispatch_queue_pending (libwayland-client.so.0 + 0x703c) #24 0x7f552f370de3 _ZN15QtWaylandClient15QWaylandDisplay13flushRequestsEv (libQt5WaylandClient.so.5 + 0x75de3) #25 0x7f553193a5e0 n/a (libQt5Core.so.5 + 0x2e45e0) #26 0x7f553193d9df
[elisa] [Bug 399249] New: Add support for scrobbling to last.fm
https://bugs.kde.org/show_bug.cgi?id=399249 Bug ID: 399249 Summary: Add support for scrobbling to last.fm Product: elisa Version: 0.3.0 Platform: Debian unstable OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: matthieu_gall...@yahoo.fr Reporter: jfeb...@gmail.com Target Milestone: --- It would be nice if Elisa could do scrobbling to last.fm. SOFTWARE VERSIONS (available in About System) KDE Plasma Version: 5.13.80 KDE Frameworks Version: 5.50 Qt Version: 5.11.1 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 397032] New: [Wayland] Some task switcher visualizations should appear on the center of the screen but instead they appear on the top left
https://bugs.kde.org/show_bug.cgi?id=397032 Bug ID: 397032 Summary: [Wayland] Some task switcher visualizations should appear on the center of the screen but instead they appear on the top left Product: kwin Version: git master Platform: Debian unstable OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: jfeb...@gmail.com Target Milestone: --- Created attachment 114244 --> https://bugs.kde.org/attachment.cgi?id=114244=edit Large Icon task switch visualization appearing on the top left of the screen On a Plasma Wayland session some task switcher visualizations they should appear on the center of the screen, but they appear on the top left of the screen. The affected visualizations are: Small Icons, Informative, Text Only, Large Icons, Compact and Thumbnails. On a Plasma Xorg session they appear on the center of the screen as intended. I'm running a current Debian GNU/Linux sid system, with Qt 5.11.1 and today builds of kwayland, kwin, plasma-workspace and plasma-desktop. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 397029] [Wayland] Some windows or dialogs don't appear below a top panel
https://bugs.kde.org/show_bug.cgi?id=397029 --- Comment #3 from Josep Febrer --- Created attachment 114242 --> https://bugs.kde.org/attachment.cgi?id=114242=edit Yakuake window where it should appeear -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 397029] [Wayland] Some windows or dialogs don't appear below a top panel
https://bugs.kde.org/show_bug.cgi?id=397029 --- Comment #1 from Josep Febrer --- Created attachment 114240 --> https://bugs.kde.org/attachment.cgi?id=114240=edit KRunner dialog where it should appear -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 394023] New: Icon request: gPodder application icon
https://bugs.kde.org/show_bug.cgi?id=394023 Bug ID: 394023 Summary: Icon request: gPodder application icon Product: Breeze Version: 5.12.5 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Icons Assignee: visual-des...@kde.org Reporter: jfeb...@gmail.com CC: kain...@gmail.com Target Milestone: --- gPodder is a very useful podcast application, however its' icon doesn't mix very well with the Breeze icon theme. http://gpodder.org/ -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 392326] New: Krita crashes on exit when there is atleast one Python plugin activated
https://bugs.kde.org/show_bug.cgi?id=392326 Bug ID: 392326 Summary: Krita crashes on exit when there is atleast one Python plugin activated Product: krita Version: git master Platform: Debian unstable OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Scripting Assignee: krita-bugs-n...@kde.org Reporter: jfeb...@gmail.com Target Milestone: --- Created attachment 111637 --> https://bugs.kde.org/attachment.cgi?id=111637=edit Backtrace of the Krita crash when exit the program Krita is working normally but when I quit the program it crashes. I am using the git master v4.0.0.51-735-g56b4749609 compiled in Debian unstable by myself with Qt 5.9.2 and KDE Framework 5.44. If I deactivate all Python plugins, then Krita don't crash on exit. If I activate one, even the Hello World Python plugin then Krita crash on exit. When activated the Python plugins work as expected, but for some reason they cause a crash on Krita exit. I attached a backtrace. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 380347] qdbus can't access plasma scripting when widgets are locked
https://bugs.kde.org/show_bug.cgi?id=380347
Josep Febrer <jfeb...@gmail.com> changed:
What|Removed |Added
CC||jfeb...@gmail.com
--- Comment #5 from Josep Febrer <jfeb...@gmail.com> ---
With this patch I can no longer change the wallpaper via qdbus with or without
the widgets locked.
Even with the widgets unlocked, I get this result:
qdbus org.kde.plasmashell /PlasmaShell org.kde.PlasmaShell.evaluateScript 'var
allDesktops = desktops();print (allDesktops);for (i=0;i<allDesktops.length;i++)
{d = allDesktops[i];d.wallpaperPlugin = "org.kde.image";d.currentConfigGroup =
Array("Wallpaper", "org.kde.image", "General");d.writeConfig("Image",
"file:/home/user/wallpaper.jpg")}'
Error: org.freedesktop.DBus.Error.Failed
Widgets are locked
I think that the logic in the patch it's wrong.
I modified in shell/shellcorona.cpp
if (immutability() != Plasma::Types::SystemImmutable) {
for
if (immutability() == Plasma::Types::SystemImmutable) {
And then it works as intended I can change the wallpaper via qdbus with the
widgets locked and unlocked.
--
You are receiving this mail because:
You are watching all bug changes.
[kwin] [Bug 364509] Applications window disappears while dragging them through Desktop grid effect
https://bugs.kde.org/show_bug.cgi?id=364509 --- Comment #7 from Josep Febrer <jfeb...@gmail.com> --- MichaelD have you checked if kmail, kate, and firefox windows are maximized? Because if they are, any window that is maximized don't disappear, but if they are not maximized is where they disappear. I tested also with Plasma 5.9 and still happens as described in the original report. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 217950] Ability to set desktop wallpaper via a dbus command
https://bugs.kde.org/show_bug.cgi?id=217950 Josep Febrer <jfeb...@gmail.com> changed: What|Removed |Added CC||jfeb...@gmail.com --- Comment #47 from Josep Febrer <jfeb...@gmail.com> --- One thing I don't understand is why it only works when the widgets aren't locked. When the widgets are locked in Plasma, you are able to change the wallpaper with the desktop settings, so I think by coherence it should be able to change the wallpaper with dbus even if the widgets are locked. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 364509] New: Applications window disappears while dragging them through Desktop grid effect
https://bugs.kde.org/show_bug.cgi?id=364509 Bug ID: 364509 Summary: Applications window disappears while dragging them through Desktop grid effect Product: kwin Version: 5.6.4 Platform: Debian unstable OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: effects-various Assignee: kwin-bugs-n...@kde.org Reporter: jfeb...@gmail.com If I move applications between desktops using the Desktop grid effect they disappear at the moment when I press over it's windows to drag them to another desktop. When I release it the window it will appear again. This only happens if the window is unmaximized, if the window is maximized the window doesn't disappear. Reproducible: Always Steps to Reproduce: 1. Have an unmaximized application opened. 2. Press CTRL + F8 to activate the Desktop grid effect. 3. Press over the window to drag to another desktop. Actual Results: The window will disappear. Expected Results: The window shouldn't disappear while dragging it. Currently I'm using Debian unstable with KDE 5.6.4, and frameworks 5.23 with Qt 5.6.1 and Intel display drivers. This bug is present in X11 and Wayland sessions. Also I could reproduce it on an Arch Linux system with the same versions using the nVidia propietary drivers. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 360773] New: Krita fails to build with Vc 1.2.0
https://bugs.kde.org/show_bug.cgi?id=360773 Bug ID: 360773 Summary: Krita fails to build with Vc 1.2.0 Product: krita Version: git master Platform: Debian unstable OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: krita-bugs-n...@kde.org Reporter: jfeb...@gmail.com I can't build Krita from current master with Vc 1.2.0, however with Vc 0.7.5 it builds correctly. I'm using Debian sid with GCC 5.3.1, Qt 5.5.1 and Mesa 11.1.2. The relevant parts of the build and errors: -- Found Vc: /usr/lib/cmake/Vc/VcConfig.cmake (found suitable version "1.2.0", minimum required is "0.6.70") -- Vc found! -- Vc version is greater than 0.7, enabling AVX2 support CMake Warning at /usr/lib/cmake/Vc/AddCompilerFlag.cmake:55 (message): Deprecated use of the AddCompilerFlag macro. Call Stack (most recent call first): CMakeLists.txt:529 (AddCompilerFlag) In file included from /home/josep/src/git/kde/krita/libs/pigment/compositeops/KoOptimizedCompositeOpFactoryPerArch.h:24:0, from /home/josep/src/git/kde/krita/libs/pigment/compositeops/KoOptimizedCompositeOpFactory.cpp:20: /home/josep/src/git/kde/krita/libs/pigment/compositeops/KoVcMultiArchBuildSupport.h: In function ‘typename FactoryType::ReturnType createOptimizedClass(typename FactoryType::ParamType)’: /home/josep/src/git/kde/krita/libs/pigment/compositeops/KoVcMultiArchBuildSupport.h:122:41: error: ‘VC_IMPL’ was not declared in this scope return FactoryType::template create(param); ^ /home/josep/src/git/kde/krita/libs/pigment/compositeops/KoVcMultiArchBuildSupport.h: In instantiation of ‘typename FactoryType::ReturnType createOptimizedClass(typename FactoryType::ParamType) [with FactoryType = KoReportCurrentArch; typename FactoryType::ReturnType = void; typename FactoryType::ParamType = void*]’: /home/josep/src/git/kde/krita/libs/pigment/compositeops/KoOptimizedCompositeOpFactory.cpp:30:52: required from here /home/josep/src/git/kde/krita/libs/pigment/compositeops/KoVcMultiArchBuildSupport.h:122:49: error: ‘create< >’ is not a member of ‘KoReportCurrentArch’ return FactoryType::template create(param); ^ /home/josep/src/git/kde/krita/libs/pigment/compositeops/KoVcMultiArchBuildSupport.h:122:55: error: return-statement with a value, in function returning 'void' [-fpermissive] return FactoryType::template create(param); ^ /home/josep/src/git/kde/krita/libs/pigment/compositeops/KoVcMultiArchBuildSupport.h: In instantiation of ‘typename FactoryType::ReturnType createOptimizedClass(typename FactoryType::ParamType) [with FactoryType = KoOptimizedCompositeOpFactoryPerArch; typename FactoryType::ReturnType = KoCompositeOp*; typename FactoryType::ParamType = const KoColorSpace*]’: /home/josep/src/git/kde/krita/libs/pigment/compositeops/KoOptimizedCompositeOpFactory.cpp:37:111: required from here /home/josep/src/git/kde/krita/libs/pigment/compositeops/KoVcMultiArchBuildSupport.h:122:49: error: ‘create< >’ is not a member of ‘KoOptimizedCompositeOpFactoryPerArch’ return FactoryType::template create(param); ^ /home/josep/src/git/kde/krita/libs/pigment/compositeops/KoVcMultiArchBuildSupport.h: In instantiation of ‘typename FactoryType::ReturnType createOptimizedClass(typename FactoryType::ParamType) [with FactoryType = KoOptimizedCompositeOpFactoryPerArch; typename FactoryType::ReturnType = KoCompositeOp*; typename FactoryType::ParamType = const KoColorSpace*]’: /home/josep/src/git/kde/krita/libs/pigment/compositeops/KoOptimizedCompositeOpFactory.cpp:42:104: required from here /home/josep/src/git/kde/krita/libs/pigment/compositeops/KoVcMultiArchBuildSupport.h:122:49: error: ‘create< >’ is not a member of ‘KoOptimizedCompositeOpFactoryPerArch’ /home/josep/src/git/kde/krita/libs/pigment/compositeops/KoVcMultiArchBuildSupport.h: In instantiation of ‘typename FactoryType::ReturnType createOptimizedClass(typename FactoryType::ParamType) [with FactoryType = KoOptimizedCompositeOpFactoryPerArch; typename FactoryType::ReturnType = KoCompositeOp*; typename FactoryType::ParamType = const KoColorSpace*]’: /home/josep/src/git/kde/krita/libs/pigment/compositeops/KoOptimizedCompositeOpFactory.cpp:47:112: required from here /home/josep/src/git/kde/krita/libs/pigment/compositeops/KoVcMultiArchBuildSupport.h:122:49: error: ‘create< >’ is not a member of ‘KoOptimizedCompositeOpFactoryPerArch’ /home/josep/src/git/kde/krita/libs/pigment/compositeops/KoVcMultiArchBuildSupport.h: In instantiation of ‘typename FactoryType::ReturnType createOptimizedClass(typename FactoryType::ParamType) [with FactoryType = KoOptimizedCompositeOpFactoryPerArch; typename FactoryType::ReturnType = KoCompositeOp*;
