[kdenlive] [Bug 377859] High CPU usage while idle.
https://bugs.kde.org/show_bug.cgi?id=377859 francisco_t <leviat...@gmx.com> changed: What|Removed |Added CC||leviat...@gmx.com -- You are receiving this mail because: You are watching all bug changes.
[user-manager] [Bug 354315] Just the icon of the admin is shown, Some Users are hidden
https://bugs.kde.org/show_bug.cgi?id=354315 francisco_t <leviat...@gmx.com> changed: What|Removed |Added CC||leviat...@gmx.com --- Comment #2 from francisco_t <leviat...@gmx.com> --- I have 3 user (1 admin and 2 normal) and I can't see the last normal user. KDE Neon with Plasma 5.11 qt 5.9 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 385056] New: Baloo crash on delete a lots files on my home
https://bugs.kde.org/show_bug.cgi?id=385056 Bug ID: 385056 Summary: Baloo crash on delete a lots files on my home Product: frameworks-baloo Version: 5.38.0 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: Baloo File Daemon Assignee: pinak.ah...@gmail.com Reporter: leviat...@gmx.com Target Milestone: --- Application: baloo_file (5.38.0) Qt Version: 5.9.1 Frameworks Version: 5.38.0 Operating System: Linux 4.10.0-35-generic x86_64 Distribution: KDE neon User Edition 5.10 -- Information about the crash: - What I was doing when the application crashed: I was deleting a lot of files from my personal folder. It was completely deleted (pushing keys Control + Delete), didn't move to the recycling bin. -- Backtrace: Application: Baloo File Indexing Daemon (baloo_file), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f650ca368c0 (LWP 1559))] Thread 2 (Thread 0x7f6501e0c700 (LWP 1588)): #0 0x7f6507d33a79 in g_mutex_lock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f6507cee929 in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f6507cef2bb in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f6507cef49c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f650b6d594b in QEventDispatcherGlib::processEvents (this=0x7f64fc0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #5 0x7f650b67e7ca in QEventLoop::exec (this=this@entry=0x7f6501e0bcd0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #6 0x7f650b4a7cd4 in QThread::exec (this=) at thread/qthread.cpp:515 #7 0x7f650cb4db75 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #8 0x7f650b4ac989 in QThreadPrivate::start (arg=0x7f650cbc3da0) at thread/qthread_unix.cpp:368 #9 0x7f650a1366ba in start_thread (arg=0x7f6501e0c700) at pthread_create.c:333 #10 0x7f650aab03dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 1 (Thread 0x7f650ca368c0 (LWP 1559)): [KCrash Handler] #6 0x7f650a9de428 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:54 #7 0x7f650a9e002a in __GI_abort () at abort.c:89 #8 0x7f650aa207ea in __libc_message (do_abort=do_abort@entry=2, fmt=fmt@entry=0x7f650ab39e98 "*** Error in `%s': %s: 0x%s ***\n") at ../sysdeps/posix/libc_fatal.c:175 #9 0x7f650aa2937a in malloc_printerr (ar_ptr=, ptr=, str=0x7f650ab39f88 "double free or corruption (top)", action=3) at malloc.c:5006 #10 _int_free (av=, p=, have_lock=0) at malloc.c:3867 #11 0x7f650aa2d53c in __GI___libc_free (mem=) at malloc.c:2968 #12 0x7f650b4add91 in QArrayData::deallocate (data=, objectSize=objectSize@entry=2, alignment=alignment@entry=8) at tools/qarraydata.cpp:167 #13 0x00421f00 in QTypedArrayData::deallocate (data=) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qarraydata.h:237 #14 QString::~QString (this=0x7fff4684aa70, __in_chrg=) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qstring.h:1084 #15 Baloo::PendingFileQueue::enqueue (this=0xb162f0, file=...) at /workspace/build/src/file/pendingfilequeue.cpp:66 #16 0x0041fc16 in Baloo::FileWatch::slotFileDeleted (this=0x7fff4684b2f0, urlString=..., isDir=) at /workspace/build/src/file/filewatch.cpp:116 #17 0x7f650b6acf46 in QtPrivate::QSlotObjectBase::call (a=0x7fff4684ad30, r=0x7fff4684b2f0, this=) at ../../include/QtCore/../../src/corelib/kernel/qobject_impl.h:101 #18 QMetaObject::activate (sender=sender@entry=0xb12540, signalOffset=, local_signal_index=local_signal_index@entry=5, argv=argv@entry=0x7fff4684ad30) at kernel/qobject.cpp:3749 #19 0x7f650b6ad527 in QMetaObject::activate (sender=sender@entry=0xb12540, m=m@entry=0x641be0 , local_signal_index=local_signal_index@entry=5, argv=argv@entry=0x7fff4684ad30) at kernel/qobject.cpp:3628 #20 0x00426a04 in KInotify::deleted (_t2=true, _t1=..., this=0xb12540) at /workspace/build/obj-x86_64-linux-gnu/src/file/moc_kinotify.cpp:330 #21 KInotify::slotEvent (this=, socket=) at /workspace/build/src/file/kinotify.cpp:381 #22 0x7f650b6acf46 in QtPrivate::QSlotObjectBase::call (a=0x7fff4684aeb0, r=0xb12540, this=) at ../../include/QtCore/../../src/corelib/kernel/qobject_impl.h:101 #23 QMetaObject::activate (sender=sender@entry=0xb360b0, signalOffset=, local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7fff4684aeb0) at kernel/qobject.cpp:3749 #24 0x7f650b6ad527 in QMetaObject::activate (sender=sender@entry=0xb360b0, m=m@entry=0x7f650b937cc0 , local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7fff4684aeb0) at kernel/qobject.cpp:3628 #25 0x7f650b6b8ec8 in QSocketNotifier::activated (this=this@entry=0xb360b0, _t1=14, _t2=...) at
[frameworks-kio] [Bug 364039] Dolphin crashed on file transfer
https://bugs.kde.org/show_bug.cgi?id=364039 francisco_t <leviat...@gmx.com> changed: What|Removed |Added CC||leviat...@gmx.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365010] Allow free icon positioning in widget mode (currently containment-only)
https://bugs.kde.org/show_bug.cgi?id=365010 francisco_t <leviat...@gmx.com> changed: What|Removed |Added CC||leviat...@gmx.com -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 386510] New: Explains how krunner works to a beginner user
https://bugs.kde.org/show_bug.cgi?id=386510 Bug ID: 386510 Summary: Explains how krunner works to a beginner user Product: krunner Version: 5.11.2 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: k...@privat.broulik.de Reporter: leviat...@gmx.com Target Milestone: --- I think krunner is an underrated tool because for a new user it is extremely difficult to know how it works. Not just to open documents or programs. For example, what command do you have to use to do a google search? Explain it to me like I'm a kid, please. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 394052] Open discover to update always crash.
https://bugs.kde.org/show_bug.cgi?id=394052 --- Comment #1 from francisco_t <leviat...@gmx.com> --- The list of package to upgrade: Normal appstream-0.11.1-1+16.04+xenial+build26.amd64 (neon-xenial-main)Software component metadata management Normal ark-4:18.04.1-0neon+16.04+xenial+build51.amd64 (neon-xenial-main) archive utility Bug fix distro-info-data-0.28ubuntu0.8.all (ubuntu-xenial-updates-main) information about the distributions' releases (data files) Normal dolphin-4:18.04.1-0neon+16.04+xenial+build41.amd64 (neon-xenial-main) file manager Normal ffmpegthumbs-4:18.04.1-0neon+16.04+xenial+build33.amd64 (neon-xenial-main) video thumbnail generator using ffmpeg Normal filelight-4:18.04.1-0neon+16.04+xenial+build37.amd64 (neon-xenial-main) show where your diskspace is being used Bug fix flashplugin-installer-29.0.0.171ubuntu0.16.04.1.amd64 (ubuntu-xenial-updates-multiverse)Adobe Flash Player plugin installer Normal gwenview-4:18.04.1-0neon+16.04+xenial+build49.amd64 (neon-xenial-main) image viewer Normal kaccounts-providers-4:18.04.1-0neon+16.04+xenial+build27.amd64 (neon-xenial-main) KDE providers for accounts sign-on Normal kamera-4:18.04.1-0neon+16.04+xenial+build34.amd64 (neon-xenial-main)digital camera support for KDE applications Normal kate-4:18.04.1-0neon+16.04+xenial+build55.amd64 (neon-xenial-main) powerful text editor Normal kate5-data-4:18.04.1-0neon+16.04+xenial+build55.all (neon-xenial-main) shared data files for Kate text editor Normal kbackup-18.04.1-0neon+16.04+xenial+build4.amd64 (neon-xenial-main) Easy to use backup program Normal kcalc-4:18.04.1-0neon+16.04+xenial+build38.amd64 (neon-xenial-main) simple and scientific calculator Normal kde-config-cddb-4:18.04.1-0neon+16.04+xenial+build35.amd64 (neon-xenial-main) CDDB retrieval configuration Normal kde-config-tablet-3.0.0-1+16.04+xenial+build1.amd64 (neon-xenial-main) implements a KDE configuration GUI for the Wacom drivers Normal kde-spectacle-18.04.1-0neon+16.04+xenial+build55.amd64 (neon-xenial-main) Screenshot capture utility, replaces KSnapshot Normal kdegraphics-thumbnailers-4:18.04.1-0neon+16.04+xenial+build48.amd64 (neon-xenial-main) graphics file format thumbnailers for KDE SC Normal kdialog-4:18.04.1-0neon+16.04+xenial+build28.amd64 (neon-xenial-main) Dialog display utility Normal kfind-4:18.04.1-0neon+16.04+xenial+build30.amd64 (neon-xenial-main) file search utility Normal kio-audiocd-4:18.04.1-0neon+16.04+xenial+build33.amd64 (neon-xenial-main) transparent audio CD access for applications using the KDE Platform Normal kio-extras-4:18.04.1-0neon+16.04+xenial+build41.amd64 (neon-xenial-main)Extra functionality for kioslaves. Normal kio-extras-data-4:18.04.1-0neon+16.04+xenial+build41.all (neon-xenial-main) Extra functionality for kioslaves data files. Normal kompare-4:18.04.1-0neon+16.04+xenial+build37.amd64 (neon-xenial-main) file difference viewer Normal konsole-4:18.04.1-0neon+16.04+xenial+build44.amd64 (neon-xenial-main) X terminal emulator Normal konsole-kpart-4:18.04.1-0neon+16.04+xenial+build44.amd64 (neon-xenial-main) Konsole plugin for Qt applications Normal kpart5-kompare-4:18.04.1-0neon+16.04+xenial+build37.amd64 (neon-xenial-main)file difference viewer - kpart Normal krita-1:4.0.2-0neon+16.04+xenial+build24.amd64 (neon-xenial-main) pixel-based image manipulation program Normal krita-data-1:4.0.2-0neon+16.04+xenial+build24.all (neon-xenial-main)data files for Krita painting program Normal krita-l10n-1:4.0.2-0neon+16.04+xenial+build24.all (neon-xenial-main)translations for Krita painting program Normal ksystemlog-4:18.04.1-0neon+16.04+xenial+build37.amd64 (neon-xenial-main)system log viewer Normal kwalletmanager-4:18.04.1-0neon+16.04+xenial+build33.amd64 (neon-xenial-main)secure password wallet manager Normal kwave-18.04.1-0neon+16.04+xenial+build24.amd64 (neon-xenial-main) sound editor for KDE Normal kwrite-4:18.04.1-0neon+16.04+xenial+build55.amd64 (neon-xenial-main)simple text editor Normal libappstream4-0.11.1-1+16.04+xenial+build26.amd64 (neon-xenial-main)Library to access AppStream services Normal libappstreamqt2-0.11.1-1+16.04+xenial+build26.amd64 (neon-xenial-main) Qt5 library to access AppStream services Normal libdolphinvcs5-4:18.04.1-0neon+16.04+xenial+build41.amd64 (neon-xenial-main)library to show version control in Dolphin Normal libkaccounts1-4:18.04.1-0neon+16.04+xenial+build36.amd64 (neon-xenial-main) System to administer web accounts - shared library Normal libkf5baloowidgets-bin-4:18.04.1-0neon
[Discover] [Bug 394052] New: Open discover to update always crash.
https://bugs.kde.org/show_bug.cgi?id=394052 Bug ID: 394052 Summary: Open discover to update always crash. Product: Discover Version: 5.12.5 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: normal Priority: NOR Component: discover Assignee: aleix...@kde.org Reporter: leviat...@gmx.com Target Milestone: --- Application: plasma-discover (5.12.5) Qt Version: 5.10.0 Frameworks Version: 5.45.0 Operating System: Linux 4.13.0-39-generic x86_64 Distribution: KDE neon User Edition 5.12 -- Information about the crash: - What I was doing when the application crashed: Open discover from widget to update. Always it is crashing. The crash can be reproduced every time. -- Backtrace: Application: Discover (plasma-discover), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fc74b2568c0 (LWP 2619))] Thread 29 (Thread 0x7fc6c5ffb700 (LWP 2753)): #0 0x7fc74657a74d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fc7411d538c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fc7411d549c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fc6fbdd3d7e in ?? () from /usr/lib/x86_64-linux-gnu/libostree-1.so.1 #4 0x7fc7411fbbb5 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7fc7432cd6ba in start_thread (arg=0x7fc6c5ffb700) at pthread_create.c:333 #6 0x7fc74658641d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 28 (Thread 0x7fc6b7fff700 (LWP 2752)): #0 0x7fc74657a74d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fc70c9381d5 in g_socket_condition_timed_wait () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 #2 0x7fc70c9390ea in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 #3 0x7fc70c91f2e2 in g_input_stream_read () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 #4 0x7fc6ebdef475 in ?? () from /usr/lib/x86_64-linux-gnu/gio/modules/libgiognutls.so #5 0x7fc6eb87cd6e in ?? () from /usr/lib/x86_64-linux-gnu/libgnutls.so.30 #6 0x7fc6eb87727f in ?? () from /usr/lib/x86_64-linux-gnu/libgnutls.so.30 #7 0x7fc6eb87e150 in ?? () from /usr/lib/x86_64-linux-gnu/libgnutls.so.30 #8 0x7fc6eb880d0c in ?? () from /usr/lib/x86_64-linux-gnu/libgnutls.so.30 #9 0x7fc6eb882c82 in gnutls_handshake () from /usr/lib/x86_64-linux-gnu/libgnutls.so.30 #10 0x7fc6ebdef873 in ?? () from /usr/lib/x86_64-linux-gnu/gio/modules/libgiognutls.so #11 0x7fc6ebdefcc9 in ?? () from /usr/lib/x86_64-linux-gnu/gio/modules/libgiognutls.so #12 0x7fc70c94730d in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 #13 0x7fc7411fc54e in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #14 0x7fc7411fbbb5 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #15 0x7fc7432cd6ba in start_thread (arg=0x7fc6b7fff700) at pthread_create.c:333 #16 0x7fc74658641d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 27 (Thread 0x7fc6eaf56700 (LWP 2751)): #0 0x7fc74657a74d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fc70c9381d5 in g_socket_condition_timed_wait () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 #2 0x7fc70c9390ea in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 #3 0x7fc70c91f2e2 in g_input_stream_read () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 #4 0x7fc6ebdef475 in ?? () from /usr/lib/x86_64-linux-gnu/gio/modules/libgiognutls.so #5 0x7fc6eb87cd6e in ?? () from /usr/lib/x86_64-linux-gnu/libgnutls.so.30 #6 0x7fc6eb87727f in ?? () from /usr/lib/x86_64-linux-gnu/libgnutls.so.30 #7 0x7fc6eb87e150 in ?? () from /usr/lib/x86_64-linux-gnu/libgnutls.so.30 #8 0x7fc6eb880d0c in ?? () from /usr/lib/x86_64-linux-gnu/libgnutls.so.30 #9 0x7fc6eb882c82 in gnutls_handshake () from /usr/lib/x86_64-linux-gnu/libgnutls.so.30 #10 0x7fc6ebdef873 in ?? () from /usr/lib/x86_64-linux-gnu/gio/modules/libgiognutls.so #11 0x7fc6ebdefcc9 in ?? () from /usr/lib/x86_64-linux-gnu/gio/modules/libgiognutls.so #12 0x7fc70c94730d in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 #13 0x7fc7411fc54e in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #14 0x7fc7411fbbb5 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #15 0x7fc7432cd6ba in start_thread (arg=0x7fc6eaf56700) at pthread_create.c:333 #16 0x7fc74658641d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 26 (Thread 0x7fc6c57fa700 (LWP 2729)): #0 0x7fc74657a74d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fc70c9381d5 in g_socket_condition_timed_wait () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 #2 0x7fc70c9390ea in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 #3 0x7fc70c91f2e2 in
[Discover] [Bug 394052] Open discover to update always crash.
https://bugs.kde.org/show_bug.cgi?id=394052 --- Comment #2 from francisco_t <leviat...@gmx.com> --- Another Backtrace more complete: Application: Discover (plasma-discover), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7efffd5b08c0 (LWP 3413))] Thread 16 (Thread 0x7eff89ffb700 (LWP 3446)): #0 0x7efff88d474d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7efff352f38c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7efff352f49c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7efff352f4d9 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7efff3555bb5 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7efff56276ba in start_thread (arg=0x7eff89ffb700) at pthread_create.c:333 #6 0x7efff88e041d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 15 (Thread 0x7effadbab700 (LWP 3436)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7effd8afc48b in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #2 0x7effd8afc397 in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #3 0x7efff56276ba in start_thread (arg=0x7effadbab700) at pthread_create.c:333 #4 0x7efff88e041d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 14 (Thread 0x7effae3ac700 (LWP 3434)): #0 0x7efff3573a94 in g_mutex_unlock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7efff352e910 in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7efff352f2bb in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7efff352f49c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7efff95105cb in QEventDispatcherGlib::processEvents (this=0x7eff9c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #5 0x7efff94b764a in QEventLoop::exec (this=this@entry=0x7effae3abd00, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #6 0x7efff92d7554 in QThread::exec (this=) at thread/qthread.cpp:522 #7 0x7efff92dc6eb in QThreadPrivate::start (arg=0x223af30) at thread/qthread_unix.cpp:376 #8 0x7efff56276ba in start_thread (arg=0x7effae3ac700) at pthread_create.c:333 #9 0x7efff88e041d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 13 (Thread 0x7effb7bbb700 (LWP 3429)): #0 0x7efff88d027d in read () at ../sysdeps/unix/syscall-template.S:84 #1 0x7efff35726f0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7efff352ee74 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7efff352f330 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7efff352f49c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7efff95105cb in QEventDispatcherGlib::processEvents (this=0x7effb8c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #6 0x7efff94b764a in QEventLoop::exec (this=this@entry=0x7effb7bbad00, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #7 0x7efff92d7554 in QThread::exec (this=) at thread/qthread.cpp:522 #8 0x7efff92dc6eb in QThreadPrivate::start (arg=0x46dacb0) at thread/qthread_unix.cpp:376 #9 0x7efff56276ba in start_thread (arg=0x7effb7bbb700) at pthread_create.c:333 #10 0x7efff88e041d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 12 (Thread 0x7effc3fff700 (LWP 3427)): #0 0x7efff950ed37 in QTimerInfoList::timerWait (this=0x7effb8002cd0, tm=...) at kernel/qtimerinfo_unix.cpp:413 #1 0x7efff951033e in timerSourcePrepareHelper (timeout=0x7effc3ffeb34, src=) at kernel/qeventdispatcher_glib.cpp:132 #2 timerSourcePrepare (source=, timeout=0x7effc3ffeb34) at kernel/qeventdispatcher_glib.cpp:165 #3 0x7efff352e91d in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7efff352f2bb in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7efff352f49c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7efff95105cb in QEventDispatcherGlib::processEvents (this=0x7effb80008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #7 0x7efff94b764a in QEventLoop::exec (this=this@entry=0x7effc3ffed00, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #8 0x7efff92d7554 in QThread::exec (this=) at thread/qthread.cpp:522 #9 0x7efff92dc6eb in QThreadPrivate::start (arg=0x2852de0) at thread/qthread_unix.cpp:376 #10 0x7efff56276ba in start_thread (arg=0x7effc3fff700) at pthread_create.c:333 #11 0x7efff88e041d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 11 (Thread 0x7effcbf47700 (LWP 3425)): #0 0x7efff3573a79 in g_mutex_lock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7efff352f34e in ?? () from /lib/x86_64-linux-gnu/lib
[kaddressbook] [Bug 282567] Krunner / Search and launch containment do not search Akonadi Google data Contacts and list them
https://bugs.kde.org/show_bug.cgi?id=282567 francisco_t <leviat...@gmx.com> changed: What|Removed |Added CC|leviat...@gmx.com | -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 247681] Kontact crashed when reading feeds in Akregator
https://bugs.kde.org/show_bug.cgi?id=247681 francisco_t <leviat...@gmx.com> changed: What|Removed |Added CC|leviat...@gmx.com | -- You are receiving this mail because: You are watching all bug changes.
[kaddressbook] [Bug 315526] Suggestion: kaddressbook-4.9.5 assign colours to addressbook folders
https://bugs.kde.org/show_bug.cgi?id=315526 francisco_t <leviat...@gmx.com> changed: What|Removed |Added CC|leviat...@gmx.com | -- You are receiving this mail because: You are watching all bug changes.
[khotkeys] [Bug 182150] Infinite instances of ksnapshot pressing "Stamp"
https://bugs.kde.org/show_bug.cgi?id=182150 francisco_t <leviat...@gmx.com> changed: What|Removed |Added CC|leviat...@gmx.com | -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 229859] Option to save album to album folder
https://bugs.kde.org/show_bug.cgi?id=229859 francisco_t <leviat...@gmx.com> changed: What|Removed |Added CC|leviat...@gmx.com | -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 394891] New: Krita crashes each fews minutes with PSD file
https://bugs.kde.org/show_bug.cgi?id=394891 Bug ID: 394891 Summary: Krita crashes each fews minutes with PSD file Product: krita Version: 4.0.3 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: leviat...@gmx.com Target Milestone: --- Created attachment 112982 --> https://bugs.kde.org/attachment.cgi?id=112982=edit Complete trace from gbm This crash is occurring now with this image, where is was not occurring previously with images of similar characteristics nor with the same image up until now. the PSD file is 2624x2624 300ppi. With 19 layers, some with effects including texture overlay which is not supported by krita. colour: sRGB 8 bit MY SYSTEM: Krita Version: 4.0.3 OS Information Build ABI: x86_64-little_endian-lp64 Build CPU: x86_64 CPU: x86_64 Kernel Type: linux Kernel Version: 4.13.0-43-generic Pretty Productname: KDE neon User Edition 5.12 Product Type: neon Product Version: 16.04 OpenGL Info Vendor: X.Org Renderer: "AMD BONAIRE (DRM 2.50.0 / 4.13.0-43-generic, LLVM 5.0.0)" Version: "3.0 Mesa 17.2.8" Shading language: 1.30 Requested format: QSurfaceFormat(version 3.0, options QFlags(DeprecatedFunctions), depthBufferSize 24, redBufferSize -1, greenBufferSize -1, blueBufferSize -1, alphaBufferSize -1, stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::SwapBehavior(DoubleBuffer), swapInterval 0, colorSpace QSurfaceFormat::ColorSpace(DefaultColorSpace), profile QSurfaceFormat::OpenGLContextProfile(CompatibilityProfile)) Current format:QSurfaceFormat(version 3.0, options QFlags(DeprecatedFunctions), depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 0, stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::SwapBehavior(DoubleBuffer), swapInterval 0, colorSpace QSurfaceFormat::ColorSpace(DefaultColorSpace), profile QSurfaceFormat::OpenGLContextProfile(NoProfile)) Version: 3.0 Supports deprecated functions true is OpenGL ES: false -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 386510] Show help of the active plugins in krunner
https://bugs.kde.org/show_bug.cgi?id=386510 francisco_t <leviat...@gmx.com> changed: What|Removed |Added Summary|Explains how krunner works |Show help of the active |to a beginner user |plugins in krunner --- Comment #1 from francisco_t <leviat...@gmx.com> --- I did a mockup with an example. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 386510] Show help of the active plugins in krunner
https://bugs.kde.org/show_bug.cgi?id=386510 --- Comment #2 from francisco_t <leviat...@gmx.com> --- Created attachment 110012 --> https://bugs.kde.org/attachment.cgi?id=110012=edit Mockup krunner An example of mockup to show more help -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 389991] Sleep key no longer initiates sleep
https://bugs.kde.org/show_bug.cgi?id=389991 francisco_t <leviat...@gmx.com> changed: What|Removed |Added CC||leviat...@gmx.com --- Comment #3 from francisco_t <leviat...@gmx.com> --- In my case, I have several users on my system with different languages. The problem described here is with English language users, but it doesn't happen with Spanish language users. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 390346] Plasma-discover and others packages were not updated to 5.11.1
https://bugs.kde.org/show_bug.cgi?id=390346 --- Comment #2 from francisco_t <leviat...@gmx.com> --- Created attachment 110584 --> https://bugs.kde.org/attachment.cgi?id=110584=edit term log on octuber -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 390346] New: Plasma-discover and others packages were not updated to 5.11.1
https://bugs.kde.org/show_bug.cgi?id=390346 Bug ID: 390346 Summary: Plasma-discover and others packages were not updated to 5.11.1 Product: neon Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Packages User Edition Assignee: neon-b...@kde.org Reporter: leviat...@gmx.com CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- Created attachment 110582 --> https://bugs.kde.org/attachment.cgi?id=110582=edit dkpg log on octuber Upgrade from 5.11 to 5.12, five packages were not updated: plasma-discover/now 4:5.11.0-0neon+16.04+xenial+build83 amd64 [instalado, local] plasma-discover-common/now 4:5.11.0-0neon+16.04+xenial+build83 all [instalado, local] plasma-discover-private/now 4:5.11.0-0neon+16.04+xenial+build83 amd64 [instalado, local] plasma-discover-updater/now 4:5.11.0-0neon+16.04+xenial+build83 amd64 [instalado, local] plasma-integration/now 4:5.11.0-0neon+16.04+xenial+build58 amd64 [instalado, local] I upgraded to 5.11.1 on 17-10-2017 at 20:55:53 and plasma-discover-* and plasma-integraticon were missing. I attach the logs. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 390346] Plasma-discover and others packages were not updated to 5.11.1
https://bugs.kde.org/show_bug.cgi?id=390346 --- Comment #1 from francisco_t <leviat...@gmx.com> --- Created attachment 110583 --> https://bugs.kde.org/attachment.cgi?id=110583=edit history log on octuber -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 390005] crash during search
https://bugs.kde.org/show_bug.cgi?id=390005 francisco_t <leviat...@gmx.com> changed: What|Removed |Added CC||leviat...@gmx.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 390005] crash during search
https://bugs.kde.org/show_bug.cgi?id=390005 --- Comment #3 from francisco_t <leviat...@gmx.com> --- Created attachment 110521 --> https://bugs.kde.org/attachment.cgi?id=110521=edit New crash information added by DrKonqi systemsettings5 (5.12.0) using Qt 5.9.3 - What I was doing when the application crashed: Same here. Just searching in the system setting. But I don't use wayland. -- Backtrace (Reduced): #6 MenuItem::name (this=this@entry=0x0) at /workspace/build/core/MenuItem.cpp:108 #7 0x7ff3d4b8fcf6 in ToolTipManager::generateToolTipLine (this=this@entry=0x1a07140, item=item@entry=0x7fff27e1b630, toolTip=toolTip@entry=0x1a798f0, iconSize=..., comment=comment@entry=true) at /workspace/build/sidebar/ToolTips/tooltipmanager.cpp:178 #8 0x7ff3d4b9030f in ToolTipManager::createTipContent (this=this@entry=0x1a07140, item=...) at /workspace/build/sidebar/ToolTips/tooltipmanager.cpp:150 #9 0x7ff3d4b904d9 in ToolTipManager::showToolTip (this=0x1a07140, menuItem=...) at /workspace/build/sidebar/ToolTips/tooltipmanager.cpp:129 #10 0x7ff3d4b90636 in ToolTipManager::prepareToolTip (this=) at /workspace/build/sidebar/ToolTips/tooltipmanager.cpp:120 -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 390346] Plasma-discover and others packages were not updated to 5.11.1
https://bugs.kde.org/show_bug.cgi?id=390346 --- Comment #5 from francisco_t <leviat...@gmx.com> --- Created attachment 110623 --> https://bugs.kde.org/attachment.cgi?id=110623=edit simulation.txt log -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 390346] Plasma-discover and others packages were not updated to 5.11.1
https://bugs.kde.org/show_bug.cgi?id=390346 --- Comment #4 from francisco_t <leviat...@gmx.com> --- Created attachment 110622 --> https://bugs.kde.org/attachment.cgi?id=110622=edit pk.txt log -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 390346] Plasma-discover and others packages were not updated to 5.11.1
https://bugs.kde.org/show_bug.cgi?id=390346 --- Comment #6 from francisco_t <leviat...@gmx.com> --- Please let me know when I can update the packages and if you can tell me the best way to update it without breaking anything. Thank you very much for your help! -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 390346] Plasma-discover and others packages were not updated to 5.11.1
https://bugs.kde.org/show_bug.cgi?id=390346 --- Comment #8 from francisco_t <leviat...@gmx.com> --- Created attachment 110632 --> https://bugs.kde.org/attachment.cgi?id=110632=edit simulation log with updates -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 390346] Plasma-discover and others packages were not updated to 5.11.1
https://bugs.kde.org/show_bug.cgi?id=390346 --- Comment #7 from francisco_t <leviat...@gmx.com> --- Created attachment 110631 --> https://bugs.kde.org/attachment.cgi?id=110631=edit pk log with updates -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 389991] Sleep key no longer initiates sleep
https://bugs.kde.org/show_bug.cgi?id=389991 --- Comment #31 from francisco_t <leviat...@gmx.com> --- (In reply to David Edmundson from comment #30) > Can someone with the bug please copy and paste the following into a terminal > and report back: > > dbus-send --dest=org.kde.kglobalaccel /kglobalaccel > org.kde.KGlobalAccel.unregister string:kded5 "string:Hibernate" > dbus-send --dest=org.kde.kglobalaccel /kglobalaccel > org.kde.KGlobalAccel.unregister string:kded5 "string:PowerOff" > dbus-send --dest=org.kde.kglobalaccel /kglobalaccel > org.kde.KGlobalAccel.unregister string:kded5 "string:Sleep" > dbus-send --dest=org.kde.kglobalaccel /kglobalaccel > org.kde.KGlobalAccel.unregister string:kded5 "string:Decrease Keyboard > Brightness" > dbus-send --dest=org.kde.kglobalaccel /kglobalaccel > org.kde.KGlobalAccel.unregister string:kded5 "string:Decrease Screen > Brightness" > dbus-send --dest=org.kde.kglobalaccel /kglobalaccel > org.kde.KGlobalAccel.unregister string:kded5 "string:Increase Keyboard > Brightness" > dbus-send --dest=org.kde.kglobalaccel /kglobalaccel > org.kde.KGlobalAccel.unregister string:kded5 "string:Increase Screen > Brightness" > dbus-send --dest=org.kde.kglobalaccel /kglobalaccel > org.kde.KGlobalAccel.unregister string:kded5 "string:Toggle Keyboard > Backlight" Nothing happens here. In Spanish or English users. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 389991] Powerdevil global shortcuts not working after 5.12 config migration
https://bugs.kde.org/show_bug.cgi?id=389991 --- Comment #47 from francisco_t <leviat...@gmx.com> --- (In reply to David Edmundson from comment #46) > Git commit 4ae36aee91a23dcb0736418295269da14152 by David Edmundson. > Committed on 20/02/2018 at 12:26. > Pushed by davidedmundson into branch 'Plasma/5.12'. > > Fix PowerDevil shortcuts migration > > Summary: > 5.11 -> 5.12 migrated shortcuts from kded5 to the correct component name > org_kde_powerdevil for good reasons > However, despite a kconfupdate script working correctly and moving the > old keys, kglobalaccel is running whilst we update and it syncs the old > values later. On future loads it detects the duplication and removes the > powerdevil entries. > > This patch removes the old powermanagent entries in the kded5 component > at powerdevil startup which is at runtime where we can talk to > kglobalaccel, but before powerdevil has registered the new actions. > > This should handle both users that haven't upgraded to 5.12 yet, as well > as users who hit the previous config script. > > Ideally kconf_update needs to be patched to do migration at appropriate > times. > FIXED-IN: 5.12.2 > > Test Plan: > "broke" my config by putting in values in the old place with a custom > shortcut for poweroff > Restarted kglobalaccel > Ran powerdevil > Shortucts worked > Cleanly quit kglobalaccel > Config stayed synced > > Reviewers: #plasma, broulik > > Reviewed By: #plasma, broulik > > Subscribers: broulik, fvogt, aacid, cfeck, plasma-devel > > Tags: #plasma > > Differential Revision: https://phabricator.kde.org/D10668 > > M +0-2CMakeLists.txt > M +55 -0daemon/powerdevilapp.cpp > M +1-0daemon/powerdevilapp.h > D +0-1kconf_update/CMakeLists.txt > D +0-12 kconf_update/powerdevil_move_shortcuts.upd > > https://commits.kde.org/powerdevil/4ae36aee91a23dcb0736418295269da14152 Will the fix work for multiple users with different languages? The last update updated my spanish (root) user, but not in the english users. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 391609] autostart script is not executed, log claims it is
https://bugs.kde.org/show_bug.cgi?id=391609 --- Comment #6 from francisco_t --- (In reply to Arek Guzinski from comment #5) > > @francisco_t: many of the things xmodmap does, would be overwritten when kde > sets the keyboard layout. are you sure that's not happening? (i don't think > it should, but.. maybe..) > as a workaround, you could try a script with the line > (sleep 5; xmodmap ~/.xmodmaprc)& It's working! Thanks! -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 389133] Exiting Web Shortcuts crashes System Settings
https://bugs.kde.org/show_bug.cgi?id=389133 francisco_t <leviat...@gmx.com> changed: What|Removed |Added CC||leviat...@gmx.com -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 391609] autostart script is not executed, log claims it is
https://bugs.kde.org/show_bug.cgi?id=391609 francisco_t <leviat...@gmx.com> changed: What|Removed |Added CC||leviat...@gmx.com --- Comment #2 from francisco_t <leviat...@gmx.com> --- I have a "command" in autostart. It's a .desktop file: [Desktop Entry] Comment[es_ES]= Comment= Exec=xmodmap ~/.xmodmaprc GenericName[es_ES]= GenericName= Icon=system-run MimeType= Name[es_ES]= Name= Path= StartupNotify=true Terminal=false TerminalOptions= Type=Application X-DBUS-ServiceName= X-DBUS-StartupType= X-KDE-SubstituteUID=false X-KDE-Username= And doesn't work too in 5.12.x -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 399718] New: "Flatpak" not listed in the sources page if there are no repositories
https://bugs.kde.org/show_bug.cgi?id=399718 Bug ID: 399718 Summary: "Flatpak" not listed in the sources page if there are no repositories Product: Discover Version: 5.14.0 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Flatpak Backend Assignee: aleix...@kde.org Reporter: leviat...@gmx.com CC: jgrul...@redhat.com Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Fresh install of KDE neon from 2018/10/04 with 5.14.0 2. Discover don't show flatpak in the preferences. 3. Plasma-discover-flatpak is installed. ADDITIONAL INFORMATION Workaround is adding a repositorie. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 386510] Show help of the active plugins in krunner
https://bugs.kde.org/show_bug.cgi?id=386510 --- Comment #5 from francisco_t --- (In reply to Simone Gaiarin from comment #4) > Well, the help feature existed in the KDE4 version of KRunner and it was > very similar to the mockup provided by francisco t. > > According to the comments on the bug 216368, people were complaining about > the bad design of that help feature and the feature has been removed. > > In the wiki this feature is still documented: > https://userbase.kde.org/Plasma/Krunner#Discover_KRunner > > For me, even if not perfect, the KDE4 help feature was not bad, for sure > infinitely better than not having it. My idea is a very *simple* and quick help. If you need more information or to learn in depth, linking to the wiki is the best option. That was my intention with the link "+info". -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 404111] New: Double click on desktop stopped working after last neon's update
https://bugs.kde.org/show_bug.cgi?id=404111 Bug ID: 404111 Summary: Double click on desktop stopped working after last neon's update Product: neon Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: general Assignee: neon-b...@kde.org Reporter: leviat...@gmx.com CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- SUMMARY After the last update of neon (2019-02-07) I can't use double click on desktop files, folders or icons. I have the problem in two different computers. Looks like this bug: https://bugs.kde.org/show_bug.cgi?id=400299 But I don't use any "scale display". SOFTWARE/OS VERSIONS Sistema operativo: KDE neon 5.14 Versión de KDE Plasma: 5.14.5 Versión de Qt: 5.12.0 Versión de KDE Frameworks: 5.54.0 Versión del kernel: 4.15.0-45-generic Tipo de OS: 64 bits Procesadores: 4 × AMD Phenom(tm) II X4 B50 Processor -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 404105] Double clicking desktop items with no active windows does not activate items
https://bugs.kde.org/show_bug.cgi?id=404105 --- Comment #5 from francisco_t --- Same problem only with neon in two different computers (Nvidia and AMD). Upgrading to 5.15.0 did not fix the problem. Operating System: KDE neon 5.14 KDE Plasma Version: 5.15.0 KDE Frameworks Version: 5.55.0 Qt Version: 5.12.0 Kernel Version: 4.15.0-45-generic OS Type: 64-bit Processors: 8 × Intel® Core™ i7-7700HQ CPU @ 2.80GHz Memory: 7,7 GiB -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 404105] Double clicking desktop items with no active windows does not activate items
https://bugs.kde.org/show_bug.cgi?id=404105 --- Comment #10 from francisco_t --- (In reply to Nate Graham from comment #8) > > Is everybody who's experiencing this using Qt 5.12? So far it looks that > way... In my case after the update of neon on 2019-02-07 And qt 5.12.0 too. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 404105] Double clicking desktop items with no active windows does not activate items
https://bugs.kde.org/show_bug.cgi?id=404105 --- Comment #12 from francisco_t --- (In reply to Talos from comment #7) > Created attachment 118046 [details] > related bugs > > I can confirm this from some KDE Frameworks update and now with Plasma 5.15. > > Also.. new bugs: Open is missing from right click menu and .desktop files > behave strangely. I fill a new bug for your issue: https://bugs.kde.org/show_bug.cgi?id=404432 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 404432] New: Open is missing from right click context menu in desktop
https://bugs.kde.org/show_bug.cgi?id=404432 Bug ID: 404432 Summary: Open is missing from right click context menu in desktop Product: plasmashell Version: master Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Folder Assignee: h...@kde.org Reporter: leviat...@gmx.com CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 118130 --> https://bugs.kde.org/attachment.cgi?id=118130=edit screenshot from context menu SUMMARY When I right-click with the mouse on the plasma desktop (in folder mode) options such as running programs have disappeared from the context menu. Now it looks like files being browsed in dolphin. OBSERVED RESULT Looks like right click in dolphin not in the desktop. EXPECTED RESULT Before I could "open" a program like run, now I get the option "open with kwrite" or "open with...". Operating System: KDE neon 5.15 KDE Plasma Version: 5.15.0 KDE Frameworks Version: 5.55.0 Qt Version: 5.12.0 Kernel Version: 4.15.0-45-generic OS Type: 64-bit Processors: 8 × Intel® Core™ i7-7700HQ CPU @ 2.80GHz Memory: 7,7 GiB of RAM -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 353983] Turning off compositing breaks Plasma panel rendering
https://bugs.kde.org/show_bug.cgi?id=353983 francisco_t changed: What|Removed |Added CC||leviat...@gmx.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 373797] Launching fullscreen applications freezes taskbar
https://bugs.kde.org/show_bug.cgi?id=373797 francisco_t changed: What|Removed |Added CC||leviat...@gmx.com --- Comment #6 from francisco_t --- If I use the composer with opengl instead of xrender, I always get the bug. If I start any game in steam that deactivates the composer, when it goes to full screen, the image of the desktop is frozen as you can see in the video of comment 15. If I press ALT+Shift+F12 and I activate the composer, the desktop image is fine, if I press it again, the desktop is still "frozen". Another way to provoke this bug is when I use the composer in opengl and I deactivate the composer and start steam. In this case I can see that the desktop stays frozen and if I activate the composer manually you can see that the desktop works correctly. My graphics card is hybrid. If I change to intel graphics card I don't experience this problem. Operating System: Manjaro Linux KDE Plasma Version: 5.17.4 KDE Frameworks Version: 5.65.0 Qt Version: 5.14.0 Kernel Version: 4.19.91-1-MANJARO Nvidia drivers: 440.44-4 OS Type: 64-bit Processors: 8 × Intel® Core™ i7-7700HQ CPU @ 2.80GHz Memory: 7,7 GiB graphics card: nVidia GP107M [GeForce GTX 1050 Mobile] Intel VGA compatible controller -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 353983] Turning off compositing breaks Plasma panel rendering
https://bugs.kde.org/show_bug.cgi?id=353983 francisco_t changed: What|Removed |Added CC||sunshinehunte...@gmail.com --- Comment #162 from francisco_t --- *** Bug 373797 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 373797] Launching fullscreen applications freezes taskbar
https://bugs.kde.org/show_bug.cgi?id=373797 francisco_t changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #8 from francisco_t --- *** This bug has been marked as a duplicate of bug 353983 *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 416468] Ramdon crashes on krita.
https://bugs.kde.org/show_bug.cgi?id=416468 --- Comment #2 from francisco_t --- (In reply to Tymond from comment #1) > This seems to be related to bug 414672 and bug 415625, can you please > download Krita Next appimage from the website and test it on transform tool > to see if you get any crashes or assert messages in the console or if the > tool behaves correctly? After I sent the bug report, the error happened 5 times more, every time that I attempted the same action, which was in fact using the transform tools. so yes, it seems to be the same bug you identified. I tried to reproduce the bug with appimage but I had already changed the situation that was causing the crash in the first place and I didn't get any more crashes using the transform tools far.it seems to be working correctly. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 416468] New: Ramdon crashes on krita.
https://bugs.kde.org/show_bug.cgi?id=416468 Bug ID: 416468 Summary: Ramdon crashes on krita. Product: krita Version: 4.2.8 Platform: unspecified OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: leviat...@gmx.com Target Milestone: --- Application: krita (4.2.8) Qt Version: 5.13.2 Frameworks Version: 5.66.0 Operating System: Linux 4.15.0-74-generic x86_64 Distribution: KDE neon User Edition 5.17 -- Information about the crash: - What I was doing when the application crashed: working with animation in timeline, multiple layers and manipulating image. Appeared to be random. - Custom settings of the application: -- Backtrace: Application: Krita (krita), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fb2d419e800 (LWP 10559))] Thread 19 (Thread 0x7fb23cb1e700 (LWP 10716)): [KCrash Handler] #6 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51 #7 0x7fb2cef28801 in __GI_abort () at abort.c:79 #8 0x7fb2cef1839a in __assert_fail_base (fmt=0x7fb2cf09f7d8 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", assertion=assertion@entry=0x7fb26ce678f0 "this->is_initialized()", file=file@entry=0x7fb26ce67760 "/usr/include/boost/optional/optional.hpp", line=line@entry=1107, function=function@entry=0x7fb26ce679a0 ::get()::__PRETTY_FUNCTION__> "boost::optional::reference_type boost::optional::get() [with T = ToolTransformArgs; boost::optional::reference_type = ToolTransformArgs&]") at assert.c:92 #9 0x7fb2cef18412 in __GI___assert_fail (assertion=assertion@entry=0x7fb26ce678f0 "this->is_initialized()", file=file@entry=0x7fb26ce67760 "/usr/include/boost/optional/optional.hpp", line=line@entry=1107, function=function@entry=0x7fb26ce679a0 ::get()::__PRETTY_FUNCTION__> "boost::optional::reference_type boost::optional::get() [with T = ToolTransformArgs; boost::optional::reference_type = ToolTransformArgs&]") at assert.c:101 #10 0x7fb26ce09a01 in boost::optional::get (this=) at /usr/include/boost/optional/optional.hpp:1107 #11 boost::optional::operator*() & (this=) at /usr/include/boost/optional/optional.hpp:1124 #12 TransformStrokeStrategy::finishStrokeCallback (this=) at ./plugins/tools/tool_transform2/strokes/transform_stroke_strategy.cpp:704 #13 0x7fb26ce55ecc in TransformStrokeStrategy::cancelStrokeCallback (this=0x5654db6cde70) at /usr/include/boost/optional/optional.hpp:697 #14 0x7fb2d1b9c849 in non-virtual thunk to KisUpdateJobItem::run() () from /usr/lib/x86_64-linux-gnu/libkritaimage.so.18 #15 0x7fb2cf928472 in QThreadPoolThread::run (this=0x5654d291f390) at thread/qthreadpool.cpp:99 #16 0x7fb2cf924b52 in QThreadPrivate::start (arg=0x5654d291f390) at thread/qthread_unix.cpp:360 #17 0x7fb2c8c9c6db in start_thread (arg=0x7fb23cb1e700) at pthread_create.c:463 #18 0x7fb2cf00988f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 18 (Thread 0x7fb2551db700 (LWP 10615)): #0 0x7fb2c8ca29f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x5654db38ebc8) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x5654db38eb78, cond=0x5654db38eba0) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x5654db38eba0, mutex=0x5654db38eb78) at pthread_cond_wait.c:655 #3 0x7fb2b59d12bb in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #4 0x7fb2b59d0eb7 in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #5 0x7fb2c8c9c6db in start_thread (arg=0x7fb2551db700) at pthread_create.c:463 #6 0x7fb2cf00988f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 17 (Thread 0x7fb2549da700 (LWP 10614)): #0 0x7fb2c8ca29f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x5654da6aa588) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x5654da6aa538, cond=0x5654da6aa560) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x5654da6aa560, mutex=0x5654da6aa538) at pthread_cond_wait.c:655 #3 0x7fb2b59d12bb in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #4 0x7fb2b59d0eb7 in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #5 0x7fb2c8c9c6db in start_thread (arg=0x7fb2549da700) at pthread_create.c:463 #6 0x7fb2cf00988f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 16 (Thread 0x7fb2477fe700 (LWP 10613)): #0 0x7fb2c8ca29f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x5654d8cb9798) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x5654d8cb9748, cond=0x5654d8cb9770) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x5654d8cb9770, mutex=0x5654d8cb9748) at
[plasmashell] [Bug 373797] Launching fullscreen applications freezes taskbar
https://bugs.kde.org/show_bug.cgi?id=373797 --- Comment #7 from francisco_t --- (In reply to francisco_t from comment #6) > If I use the composer with opengl instead of xrender, I always get the bug. > > If I start any game in steam that deactivates the composer, when it goes to > full screen, the image of the desktop is frozen as you can see in the video > of comment 15. I mean video of the comment #5 , sorry I can fix using "kwin_x11 --replace" after the problem, but I think it's not a good solution. How can I to help to debug this bug? -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 430939] Neon 20.04: Bug in Pipewire Package, discrepancy between pipewire and pipewire-bin
https://bugs.kde.org/show_bug.cgi?id=430939 francisco_t changed: What|Removed |Added CC||leviat...@gmx.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 417852] Date in vertical panels is too big until panel is manually resized
https://bugs.kde.org/show_bug.cgi?id=417852 --- Comment #21 from francisco_t --- (In reply to Piotr Mierzwinski from comment #20) > The strange thing here is that if we apply different date type format, like > "Custom: ddd d" then just after this activity the font is OK. Only the > problem appears when we relogin or restart of the Plasma. I fix it changing "/" for "-" in custom date. In my case: d-M- -- You are receiving this mail because: You are watching all bug changes.
[muon] [Bug 425073] Can't configure software sources through Muon package manager
https://bugs.kde.org/show_bug.cgi?id=425073 francisco_t changed: What|Removed |Added CC||leviat...@gmx.com -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 420339] KRunner does not show empty files in a search
https://bugs.kde.org/show_bug.cgi?id=420339 francisco_t changed: What|Removed |Added CC||leviat...@gmx.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 431029] New: Digital clock date take two lines with "/" character in vertical panel
https://bugs.kde.org/show_bug.cgi?id=431029 Bug ID: 431029 Summary: Digital clock date take two lines with "/" character in vertical panel Product: plasmashell Version: 5.20.4 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Digital Clock Assignee: plasma-b...@kde.org Reporter: leviat...@gmx.com Target Milestone: 1.0 Created attachment 134434 --> https://bugs.kde.org/attachment.cgi?id=134434=edit image 1 wrong date SUMMARY I have configured my desktop with a vertical panel (width size 64px) where I have the plasmoid digital clock and it is configured with a short date. Every time I start the session, the date is divided into two lines as you can see in the attached image 1. If I change to a custom date and use the character - instead of / the date remains on a single line in each session (image 2). OBSERVED RESULT EXPECTED RESULT Short date in one line. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 431029] Digital clock date take two lines with "/" character in vertical panel
https://bugs.kde.org/show_bug.cgi?id=431029 --- Comment #1 from francisco_t --- Created attachment 134435 --> https://bugs.kde.org/attachment.cgi?id=134435=edit image 2 fix date -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 431293] New: baloo shows empty results
https://bugs.kde.org/show_bug.cgi?id=431293 Bug ID: 431293 Summary: baloo shows empty results Product: frameworks-baloo Version: 5.77.0 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: stefan.bru...@rwth-aachen.de Reporter: leviat...@gmx.com Target Milestone: --- SUMMARY baloosearch show empty results. I have a txt document for testing baloo in my home: STEPS TO REPRODUCE 1. balooshow /home/one/test.txt 50109452161975045 66309 11667016 /home/one/test.txt Mtime: 1609425559 2020-12-31T15:39:19 Ctime: 1609425559 2020-12-31T15:39:19 Cached properties: Line Count: 2 2. balooshow -x /home/one/test.txt 50109452161975045 66309 11667016 /home/one/test.txt Mtime: 1609425559 2020-12-31T15:39:19 Ctime: 1609425559 2020-12-31T15:39:19 Cached properties: Line Count: 2 Internal Info Terms: Mplain Mtext T5 T8 X20-2 test File Name Terms: Ftest Ftxt XAttr Terms: lineCount: 2 3. baloosearch test.txt Elapsed: 6,26966 msecs 4. If I delete the data base baloo works fine again once, BUT in the next user login session the problem starts again. OBSERVED RESULT Everything seems correct but the results with any search are always empty lines. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 420806] Desktop icons moved down based on column number
https://bugs.kde.org/show_bug.cgi?id=420806 francisco_t changed: What|Removed |Added CC||leviat...@gmx.com --- Comment #3 from francisco_t --- I have the same problem. It is quite random. There are moments that it happens a few times and after an update it disappears. Other times it happens almost continuously and does not go away. I have had that problem in manjaro from 2018 to 2020 and now with kde neon it happens to me again. It is very annoying because the icons appers behind the widgets as you can see in the screenshot and and I have to move everything or delete them. Please, Is there a way to reset / remove the position of the icons on the screen? Operating System: KDE neon 5.22 KDE Plasma Version: 5.22.0 KDE Frameworks Version: 5.83.0 Qt Version: 5.15.3 Kernel Version: 5.8.0-55-generic (64-bit) Graphics Platform: X11 Processors: 12 × Intel® Core™ i7-10750H CPU @ 2.60GHz Memory: 7.6 GiB of RAM Graphics Processor: GeForce GTX 1650/PCIe/SSE2 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 420806] Desktop icons moved down based on column number
https://bugs.kde.org/show_bug.cgi?id=420806 --- Comment #4 from francisco_t --- Created attachment 139312 --> https://bugs.kde.org/attachment.cgi?id=139312=edit Bug icons move in the desktop behind the widgets -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 420806] Desktop icons moved down based on column number
https://bugs.kde.org/show_bug.cgi?id=420806 --- Comment #5 from francisco_t --- More information: I have only a vertical panel. The problem it happens on boot when the vertical panel loads and the icons are moved a bit by the panel. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 438809] offline updates are not installed on restart
https://bugs.kde.org/show_bug.cgi?id=438809 francisco_t changed: What|Removed |Added CC||leviat...@gmx.com --- Comment #6 from francisco_t --- Created attachment 139486 --> https://bugs.kde.org/attachment.cgi?id=139486=edit Press to cancel??? -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 438809] offline updates are not installed on restart
https://bugs.kde.org/show_bug.cgi?id=438809 --- Comment #7 from francisco_t --- When you press c to cancel... the updates install without problem! Doesn't make sense. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 436797] Resize mouse icon visible when it should not be.
https://bugs.kde.org/show_bug.cgi?id=436797 francisco_t changed: What|Removed |Added Resolution|--- |DUPLICATE CC||leviat...@gmx.com Status|REPORTED|RESOLVED --- Comment #2 from francisco_t --- *** This bug has been marked as a duplicate of bug 436473 *** -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 436473] Cursor is stuck to resize icon when hovering into panels across the movable dividers
https://bugs.kde.org/show_bug.cgi?id=436473 francisco_t changed: What|Removed |Added CC||naumenko.dmit...@gmail.com --- Comment #10 from francisco_t --- *** Bug 436797 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 436473] Cursor is stuck to resize icon when hovering into panels across the movable dividers
https://bugs.kde.org/show_bug.cgi?id=436473 francisco_t changed: What|Removed |Added CC||leviat...@gmx.com -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 437292] New: Discover "author" is confusing and wrong
https://bugs.kde.org/show_bug.cgi?id=437292 Bug ID: 437292 Summary: Discover "author" is confusing and wrong Product: Discover Version: 5.21.5 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: discover Assignee: lei...@leinir.dk Reporter: leviat...@gmx.com CC: aleix...@kde.org Target Milestone: --- Created attachment 138528 --> https://bugs.kde.org/attachment.cgi?id=138528=edit Flatpak info from discover about keepassxc STEPS TO REPRODUCE 1. I want to install keepassxc from discover but "author" confuses me. 2. One of the package from developer is Snap: https://keepassxc.org/download/#linux 3. I see the "Author" in discover's flatpak is "Keepassxc developer" but It's not a package from developers: https://github.com/keepassxreboot/keepassxc/issues/1524 EXPECTED RESULT I want the official package. I know snap is not verificated package from Canonical, BUT the flatpak is not from developer! ADDITIONAL INFORMATION Operating System: KDE neon 5.21 KDE Plasma Version: 5.21.5 KDE Frameworks Version: 5.82.0 Qt Version: 5.15.2 Kernel Version: 5.8.0-53-generic OS Type: 64-bit -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 437292] Discover "author" is confusing and wrong
https://bugs.kde.org/show_bug.cgi?id=437292 --- Comment #1 from francisco_t --- Created attachment 138529 --> https://bugs.kde.org/attachment.cgi?id=138529=edit snap info from discover about keepassxc -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 437292] Discover "author" is confusing and wrong
https://bugs.kde.org/show_bug.cgi?id=437292 --- Comment #5 from francisco_t --- (In reply to Nate Graham from comment #4) > Ah, I understand your complaint now. > > However is there really a significant difference between "Developer" and > "Author"? I suppose we could change the word to "Developer" but that feels > like a less friendly more technical term. Can you explain maybe in more > detail what you don't like about the word "Author"? I like the word "author" It's confuse because: - Snap "author" is the publisher (checked to certificate, good point) - Flatpak "author" is the developer (and looks like certificated but who knows) I think a good solution would be that discover shows the author (developer) and the publisher separately, specially in flatpak. P.S. Look firefox in snap and flatpak. Both official packages from mozilla: https://flathub.org/apps/details/org.mozilla.firefox https://snapcraft.io/firefox but flatpak in discover has not author (?!) -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 437292] Discover "author" is confusing and wrong
https://bugs.kde.org/show_bug.cgi?id=437292 --- Comment #3 from francisco_t --- (In reply to Nate Graham from comment #2) > This information comes entirely from the packages' metadata; Discover is > simply consuming that information and passing it onto you. We don't have a > way to verify if the stated author is accurate or not. The people supposed > to be doing this are the packagers of your distro/Snap/FlatHub/wherever > you're getting your apps from If any of this information if incorrect, you > would need to contact the packagers and tell them about it. You are right. But the data from snap or flatpak are different to "Author". Example snap: https://snapcraft.io/keepassxc Info from snap site: Website and contact Discover show me Author: Contact I think the name of "author" is wrong. The data is "contact" Example Flatpak: https://flathub.org/apps/details/org.keepassxc.KeePassXC Info from flatpak site: Developer and publisher Developer: keepass team Publisher: see detail (some guys from flathub) I think "Author" is wrong again. The data from flatpak is who is the devs. I think flatpak and snap information is a big disaster but Discover doesn't help with the "Author" tag. Does the "author" word come from flatpak/snap? I think the name "Author" is confusing and wrong anyway. Sorry, but it's difficult explain the problem. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 435971] Apply offline updates during shutdown process
https://bugs.kde.org/show_bug.cgi?id=435971 --- Comment #2 from francisco_t --- Created attachment 138008 --> https://bugs.kde.org/attachment.cgi?id=138008=edit Fedora/gnome turn off dialog with option to install "offline updates" -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 435971] Apply offline updates during shutdown process
https://bugs.kde.org/show_bug.cgi?id=435971 francisco_t changed: What|Removed |Added CC||leviat...@gmx.com --- Comment #1 from francisco_t --- In Neon with the new deafault "offline updates" Plasma/Discover does not allow you to install updates when shutting down the system. For example: Fedora/gnome you can install "offline updates" in two different ways: 1-. restart -> install -> restart -> boot finally. (like discover now) 2.- Go turn off -> restart -> install -> shutdown finally. I add an screenshot with the option to install updates before confirm the turn off on Fedora. EXPECTED RESULT I want install offline updates while turn off my computer becasue It has less impact in my work. I need a fast start, but I don't care an slow shutdown. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 429006] Deleted files are not removed from the index
https://bugs.kde.org/show_bug.cgi?id=429006 francisco_t changed: What|Removed |Added CC||leviat...@gmx.com --- Comment #7 from francisco_t --- In my case it was when moving many files from one folder to another. Now the results appear duplicated. ppp@moon:~$ baloosearch neon /home/ppp/Documentos/neon install /home/ppp/ppp_old/Documentos/neon install Operating System: KDE neon 5.21 KDE Plasma Version: 5.21.4 KDE Frameworks Version: 5.81.0 Qt Version: 5.15.2 Kernel Version: 5.8.0-50-generic OS Type: 64-bit Graphics Platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 443738] New: Plasma crash to select alternative widget
https://bugs.kde.org/show_bug.cgi?id=443738
Bug ID: 443738
Summary: Plasma crash to select alternative widget
Product: plasmashell
Version: 5.23.0
Platform: Neon Packages
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: general
Assignee: k...@davidedmundson.co.uk
Reporter: leviat...@gmx.com
CC: plasma-b...@kde.org
Target Milestone: 1.0
Application: plasmashell (5.23.0)
Qt Version: 5.15.3
Frameworks Version: 5.87.0
Operating System: Linux 5.11.0-37-generic x86_64
Windowing System: X11
Distribution: KDE neon User - Plasma 25th Anniversary Edition
DrKonqi: 5.23.0 [KCrashBackend]
-- Information about the crash:
- What I was doing when the application crashed:
I changed the Start menu with "alternative widget"
- Unusual behavior I noticed:
After I changed the widget plasmashell crashes and remove the star menu widget.
- Custom settings of the application:
The reporter is unsure if this crash is reproducible.
-- Backtrace:
Application: Plasma (plasmashell), signal: Segmentation fault
[New LWP 1612]
[New LWP 1617]
[New LWP 1743]
[New LWP 1804]
[New LWP 1818]
[New LWP 1819]
[New LWP 1884]
[New LWP 1887]
[New LWP 1969]
[New LWP 1972]
[New LWP 1973]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
0x7f7f0eadfaff in __GI___poll (fds=0x7ffe8e0fbf78, nfds=1, timeout=1000) at
../sysdeps/unix/sysv/linux/poll.c:29
__preamble__
drkonqi_qmltrace_thread:1
Failed to do pygdbmi parsing: No module named 'pygdbmi'
frame={level="0",func="expression for
target",file="/usr/share/plasma/plasmoids/org.kde.plasma.kickoff/contents/ui/Kickoff.qml",fullname="/usr/share/plasma/plasmoids/org.kde.plasma.kickoff/cont".
-
(beware that frames may have been optimized out)
[Current thread is 1 (Thread 0x7f7f0ac349c0 (LWP 1598))]
Thread 12 (Thread 0x7f7ebf3ff700 (LWP 1973)):
#0 futex_wait_cancelable (private=, expected=0,
futex_word=0x5653457f0ed4) at ../sysdeps/nptl/futex-internal.h:183
#1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x5653457f0e80,
cond=0x5653457f0ea8) at pthread_cond_wait.c:508
#2 __pthread_cond_wait (cond=0x5653457f0ea8, mutex=0x5653457f0e80) at
pthread_cond_wait.c:647
#3 0x7f7f0ee7459b in QWaitConditionPrivate::wait (deadline=...,
this=0x5653457f0e80) at thread/qwaitcondition_unix.cpp:146
#4 QWaitCondition::wait (this=this@entry=0x5653435f8b58,
mutex=mutex@entry=0x5653435f8b50, deadline=...) at
thread/qwaitcondition_unix.cpp:225
#5 0x7f7f10addb44 in QSGRenderThreadEventQueue::takeEvent (wait=true,
this=0x5653435f8b48) at
/usr/include/x86_64-linux-gnu/qt5/QtCore/qdeadlinetimer.h:68
#6 QSGRenderThread::processEventsAndWaitForMore
(this=this@entry=0x5653435f8ab0) at scenegraph/qsgthreadedrenderloop.cpp:936
#7 0x7f7f10addfb9 in QSGRenderThread::run (this=0x5653435f8ab0) at
scenegraph/qsgthreadedrenderloop.cpp:1053
#8 0x7f7f0ee6e42c in QThreadPrivate::start (arg=0x5653435f8ab0) at
thread/qthread_unix.cpp:329
#9 0x7f7f0ddbd609 in start_thread (arg=) at
pthread_create.c:477
#10 0x7f7f0eaec293 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95
Thread 11 (Thread 0x7f7ebebfe700 (LWP 1972)):
#0 futex_wait_cancelable (private=, expected=0,
futex_word=0x565346f9bb74) at ../sysdeps/nptl/futex-internal.h:183
#1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x565346f9bb20,
cond=0x565346f9bb48) at pthread_cond_wait.c:508
#2 __pthread_cond_wait (cond=0x565346f9bb48, mutex=0x565346f9bb20) at
pthread_cond_wait.c:647
#3 0x7f7f0ee7459b in QWaitConditionPrivate::wait (deadline=...,
this=0x565346f9bb20) at thread/qwaitcondition_unix.cpp:146
#4 QWaitCondition::wait (this=this@entry=0x7f7efc046488,
mutex=mutex@entry=0x7f7efc046480, deadline=...) at
thread/qwaitcondition_unix.cpp:225
#5 0x7f7f10addb44 in QSGRenderThreadEventQueue::takeEvent (wait=true,
this=0x7f7efc046478) at
/usr/include/x86_64-linux-gnu/qt5/QtCore/qdeadlinetimer.h:68
#6 QSGRenderThread::processEventsAndWaitForMore
(this=this@entry=0x7f7efc0463e0) at scenegraph/qsgthreadedrenderloop.cpp:936
#7 0x7f7f10addfb9 in QSGRenderThread::run (this=0x7f7efc0463e0) at
scenegraph/qsgthreadedrenderloop.cpp:1053
#8 0x7f7f0ee6e42c in QThreadPrivate::start (arg=0x7f7efc0463e0) at
thread/qthread_unix.cpp:329
#9 0x7f7f0ddbd609 in start_thread (arg=) at
pthread_create.c:477
#10 0x7f7f0eaec293 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95
Thread 10 (Thread 0x7f7ebdffd700 (LWP 1969)):
#0 futex_wait_cancelable (private=, expected=0,
futex_word=0x565346f8c934) at ../sysdeps/nptl/futex-internal.h:183
#1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x565346f8c8e0,
cond=0x565346f8c908) at pthread_cond_wait.c:508
#2 __pthread_cond_wait (cond=0x565346f8c908,
[kwin] [Bug 443765] New: Kwin crash while closing firefox
https://bugs.kde.org/show_bug.cgi?id=443765 Bug ID: 443765 Summary: Kwin crash while closing firefox Product: kwin Version: 5.23.0 Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: leviat...@gmx.com Target Milestone: --- Application: kwin_x11 (5.23.0) Qt Version: 5.15.3 Frameworks Version: 5.87.0 Operating System: Linux 5.11.0-37-generic x86_64 Windowing System: X11 Distribution: KDE neon User - Plasma 25th Anniversary Edition DrKonqi: 5.23.0 [KCrashBackend] -- Information about the crash: - What I was doing when the application crashed: Kwin crash while firefox is closing. From I update to plasma 5.23, firefox window have a strange graphic glitchs. Sometimes the window flickers weirdly, sometimes the windows freezes, and now also kwin crash. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: KWin (kwin_x11), signal: Segmentation fault [New LWP 1855] [New LWP 1908] [New LWP 1935] [New LWP 2037] [New LWP 5484] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". futex_wait_cancelable (private=, expected=0, futex_word=0x7f63a00116d4) at ../sysdeps/nptl/futex-internal.h:183 __preamble__ [Current thread is 1 (Thread 0x7f63aeb57080 (LWP 1838))] Thread 6 (Thread 0x7f63a4ee1700 (LWP 5484)): [KCrash Handler] #4 KWin::Toplevel::windowItem (this=0x0) at ./src/toplevel.cpp:475 #5 0x7f63b6343e2e in KWin::Toplevel::visibleGeometry (this=) at ./src/toplevel.cpp:150 #6 0x7f63b6326b7c in KWin::WindowThumbnailItem::paintedRect (this=0x55da36dcf250) at /usr/include/c++/9/bits/atomic_base.h:413 #7 0x7f63b6327254 in KWin::ThumbnailItemBase::updatePaintNode (this=0x55da36dcf250, oldNode=) at ./src/scripting/thumbnailitem.cpp:242 #8 0x7f63b390f2e0 in QQuickWindowPrivate::updateDirtyNode (this=0x55da3647f490, item=0x55da36dcf250) at items/qquickwindow.cpp:3872 #9 0x7f63b390fb9b in QQuickWindowPrivate::updateDirtyNodes (this=this@entry=0x55da3647f490) at items/qquickwindow.cpp:3617 #10 0x7f63b3911290 in QQuickWindowPrivate::syncSceneGraph (this=this@entry=0x55da3647f490) at items/qquickwindow.cpp:524 #11 0x7f63b38aedf7 in QSGRenderThread::sync (this=this@entry=0x55da36dcf690, inExpose=inExpose@entry=false, inGrab=inGrab@entry=false) at scenegraph/qsgthreadedrenderloop.cpp:647 #12 0x7f63b38b0d67 in QSGRenderThread::syncAndRender (this=0x55da36dcf690, grabImage=0x0) at scenegraph/qsgthreadedrenderloop.cpp:778 #13 0x7f63b38b4f77 in QSGRenderThread::run (this=0x55da36dcf690) at scenegraph/qsgthreadedrenderloop.cpp:1043 #14 0x7f63b549042c in QThreadPrivate::start (arg=0x55da36dcf690) at thread/qthread_unix.cpp:329 #15 0x7f63b2efc609 in start_thread (arg=) at pthread_create.c:477 #16 0x7f63b48a1293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 5 (Thread 0x7f638b815700 (LWP 2037)): #0 0x7f63b489712b in __GI___select (nfds=41, readfds=0x7f638b814ba0, writefds=0x0, exceptfds=0x0, timeout=0x7f638b814b90) at ../sysdeps/unix/sysv/linux/select.c:41 #1 0x7f63a6e69981 in ?? () from /lib/x86_64-linux-gnu/libnvidia-glcore.so.460.91.03 #2 0x7f63a6e6746a in ?? () from /lib/x86_64-linux-gnu/libnvidia-glcore.so.460.91.03 #3 0x7f63b2efc609 in start_thread (arg=) at pthread_create.c:477 #4 0x7f63b48a1293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 4 (Thread 0x7f639ea6c700 (LWP 1935)): #0 0x7f63b4894bf6 in __ppoll (fds=fds@entry=0x7f639d98, nfds=nfds@entry=1, timeout=, timeout@entry=0x0, sigmask=sigmask@entry=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:44 #1 0x7f63b56cd4e9 in ppoll (__ss=, __timeout=, __nfds=, __fds=) at /usr/include/x86_64-linux-gnu/bits/poll2.h:77 #2 qt_ppoll (timeout_ts=0x0, nfds=1, fds=0x7f639d98) at kernel/qcore_unix.cpp:132 #3 qt_ppoll (timeout_ts=0x0, nfds=1, fds=0x7f639d98) at kernel/qcore_unix.cpp:129 #4 qt_safe_poll (fds=0x7f639d98, nfds=1, timeout_ts=timeout_ts@entry=0x0) at kernel/qcore_unix.cpp:155 #5 0x7f63b56ceb93 in QEventDispatcherUNIX::processEvents (this=, flags=...) at ../../include/QtCore/../../src/corelib/tools/qarraydata.h:211 #6 0x7f63b567587b in QEventLoop::exec (this=this@entry=0x7f639ea6bbe0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:141 #7 0x7f63b548f292 in QThread::exec (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #8 0x7f63b549042c in QThreadPrivate::start (arg=0x55da3655cef0) at thread/qthread_unix.cpp:329 #9 0x7f63b2efc609 in start_thread (arg=) at pthread_create.c:477 #10 0x7f63b48a1293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7f639700 (LWP 1908)): #0
[plasmashell] [Bug 443961] plasmashell crashes in StatusNotifierItemSource::id() on launch
https://bugs.kde.org/show_bug.cgi?id=443961 francisco_t changed: What|Removed |Added CC||leviat...@gmx.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 443961] plasmashell crashes in StatusNotifierItemSource::id() on launch
https://bugs.kde.org/show_bug.cgi?id=443961 --- Comment #21 from francisco_t --- Created attachment 143726 --> https://bugs.kde.org/attachment.cgi?id=143726=edit New crash information added by DrKonqi plasmashell (5.23.3) using Qt 5.15.3 - What I was doing when the application crashed: First I was connecting to VPN and then I close element app with system tray icon. -- Backtrace (Reduced): #4 QString::QString (other=..., this=0x7ffc8ba59eb0) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qstring.h:1093 #5 StatusNotifierItemSource::id (this=this@entry=0x0) at ./applets/systemtray/statusnotifieritemsource.cpp:140 #6 0x7f2836e1a1e4 in extractItemId (sniData=0x0) at ./applets/systemtray/systemtraymodel.cpp:302 #7 StatusNotifierModel::data (this=0x55d1a6cfcbe0, index=..., role=364) at ./applets/systemtray/systemtraymodel.cpp:302 #8 0x7f2849d686ea in QModelIndex::data (arole=364, this=0x7ffc8ba59f00) at ../../include/QtCore/../../src/corelib/itemmodels/qabstractitemmodel.h:460 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 450056] New: Desktop icons disappear when changing settings in any activity
https://bugs.kde.org/show_bug.cgi?id=450056 Bug ID: 450056 Summary: Desktop icons disappear when changing settings in any activity Product: plasmashell Version: 5.24.0 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Desktop Containment Assignee: notm...@gmail.com Reporter: leviat...@gmx.com CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY *** If I change the settings folder desktop in a new activity, the icons disappear. When I restart the icons appears again but they lost the order. If I open the new actiivty, I lose the icons again. *** STEPS TO REPRODUCE 1. I have a normal default desktop with icons and widgets. 2. I add a new activity. 3. In the desktop settings of the new activity, I change the folder by default to the files of the new activity. 4. I go back the first activity. And the icons are disappear. 5. The icons are in the ~/Desktop anyway. 6. I do log out and log in. The icons are back, but they have lost order and are in a single line. 7. I change to the new activity, I go back to the first activity and the icon gone again... and back to point 6. OBSERVED RESULT Always happen. EXPECTED RESULT Keep the icons of each activity correctly SOFTWARE/OS VERSIONS Operating System: KDE neon 5.24 KDE Plasma Version: 5.24.0 KDE Frameworks Version: 5.90.0 Qt Version: 5.15.3 Kernel Version: 5.13.0-28-generic (64-bit) Graphics Platform: X11 Processors: 12 × Intel® Core™ i7-10750H CPU @ 2.60GHz Memory: 15.5 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1650/PCIe/SSE2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 451312] Shutdown doesn't work anymore
https://bugs.kde.org/show_bug.cgi?id=451312 --- Comment #3 from francisco_t --- Do you have i386 libraries installed? I have the libwayland updates blocked because 32 bits libraries. And Neon doesn't support 32 bits libraries :( -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 451312] Shutdown doesn't work anymore
https://bugs.kde.org/show_bug.cgi?id=451312 francisco_t changed: What|Removed |Added CC||leviat...@gmx.com --- Comment #1 from francisco_t --- Error on systemd: "Failed to start Xdg Desktop Portal For KDE." And I can't open files in firefox, flatpak apps or turn off like Daniel Bruckner. Looks like XDG-Portal-KDE is broken. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 450056] Desktop icons disappear when changing settings in any activity
https://bugs.kde.org/show_bug.cgi?id=450056 --- Comment #1 from francisco_t --- Created attachment 146628 --> https://bugs.kde.org/attachment.cgi?id=146628=edit Example on video -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 450056] Desktop icons disappear when changing settings in any activity
https://bugs.kde.org/show_bug.cgi?id=450056 --- Comment #2 from francisco_t --- Created attachment 146629 --> https://bugs.kde.org/attachment.cgi?id=146629=edit Desktop after next login -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 462009] New: Baloo indexes folders configured not to index in KCM baloo.
https://bugs.kde.org/show_bug.cgi?id=462009 Bug ID: 462009 Summary: Baloo indexes folders configured not to index in KCM baloo. Classification: Applications Product: systemsettings Version: 5.26.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_baloo Assignee: baloo-bugs-n...@kde.org Reporter: leviat...@gmx.com CC: plasma-b...@kde.org Target Milestone: --- Created attachment 153874 --> https://bugs.kde.org/attachment.cgi?id=153874=edit baloo no index SUMMARY Baloo indexes folders configured not to index in KCM baloo. STEPS TO REPRODUCE 0.- I have a search database but I want to purge it. 1.- I have a "games" folder so that it does not index in the searches. 2.- I stop the search in the system preferences. 3.- I uncheck all the search boxes and apply. 4.- I exit the preferences and re-enter the search options. 5.- Now I get the option to delete the database and start over. I delete it and baloo starts from zero. OBSERVED RESULT The folders to not index continue from the previous configuration (check screenshot), but I can't delete them and when the search starts it indexes them even. EXPECTED RESULT Baloo does not index folders configured for non-indexing. SOFTWARE/OS VERSIONS Operating System: Manjaro Linux KDE Plasma Version: 5.26.3 KDE Frameworks Version: 5.99.0 Qt Version: 5.15.7 Kernel Version: 6.0.8-1-MANJARO (64-bit) Graphics Platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 462009] Baloo indexes folders configured not to index in KCM baloo.
https://bugs.kde.org/show_bug.cgi?id=462009 --- Comment #2 from francisco_t --- (In reply to Nate Graham from comment #1) > Does it work if you: > 1. Add the excluded folders using the KCM > 2. Turn off indexing > 3. Purge the index > 4. reboot > 5. Turn on indexing again? You are right. If I reboot my system, the KCM search menu works correctly and Baloo does not index the folders that were previously set up. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 420806] Desktop icons moved down based on column number
https://bugs.kde.org/show_bug.cgi?id=420806 --- Comment #9 from francisco_t --- (In reply to Nate Graham from comment #6) > Fransisco, your issue is probably something subtly different. If you can > reproduce it with Plasma 5.27.5, can you please submit a new bug report for > it? Thanks! > > Max, I can't reproduce your originally described issue in Plasma 5.27.4 with > exactly that desktop icon layout. Can you still reproduce it with Plasma > 5.27.4 and a recent Frameworks version (e.g. 5.104 or later)? Some time ago I changed the panel to horizontal to avoid the problem. I am going to try the vertical panel again and will let you know if there is a problem in a new report. Thanks for your interest. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 468733] New: Desktop icons moved with vertical panel
https://bugs.kde.org/show_bug.cgi?id=468733 Bug ID: 468733 Summary: Desktop icons moved with vertical panel Classification: Plasma Product: plasmashell Version: 5.27.4 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Folder Assignee: plasma-b...@kde.org Reporter: leviat...@gmx.com CC: h...@kde.org Target Milestone: 1.0 Created attachment 158244 --> https://bugs.kde.org/attachment.cgi?id=158244=edit Icons in my desktop SUMMARY *** Since before the year 2021 ( https://bugs.kde.org/show_bug.cgi?id=420806#c3 ) I use plasma with a vertical panel on the left side of my laptop. From time to time randomly the icons moved, sometimes even behind the widgets. *** STEPS TO REPRODUCE 1. I move my panel from the horizontal place to the vertical left side. 2. I think when the panel loads, for example when the desktop starts, I can see that the panel moves the icons a bit to one side. This also happens when I switch from an application in full screen mode (like a video game) to the desktop, when the panel appears it "pushes" the icons a bit. 3. But sometimes when this happens the icons are moved incorrectly many spaces to one side, even behind the widgets. SOFTWARE/OS VERSIONS Operating System: Manjaro Linux KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.8 Kernel Version: 6.1.23-1-MANJARO (64-bit) Graphics Platform: X11 Processors: 12 × Intel® Core™ i7-10750H CPU @ 2.60GHz Memory: 15.5 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1650/PCIe/SSE2 Manufacturer: LENOVO Product Name: 82AU System Version: Lenovo Legion 5 15IMH05 ADDITIONAL INFORMATION -My laptop use a nvidia gpu. -I play videogames on full screen and I switch from full screen to desktop often. - Blocking the icons does not help to solve the problem. - My panel has 68px -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 468733] Desktop icons moved with vertical panel
https://bugs.kde.org/show_bug.cgi?id=468733 --- Comment #1 from francisco_t --- Created attachment 158245 --> https://bugs.kde.org/attachment.cgi?id=158245=edit icons moved -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 193415] mouse gestures only buttons
https://bugs.kde.org/show_bug.cgi?id=193415 francisco_t changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 468733] Desktop icons moved with vertical panel
https://bugs.kde.org/show_bug.cgi?id=468733 --- Comment #2 from francisco_t --- Created attachment 158246 --> https://bugs.kde.org/attachment.cgi?id=158246=edit plasma-org.kde.plasma.desktop-appletsrc BEFORE -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 468733] Desktop icons moved with vertical panel
https://bugs.kde.org/show_bug.cgi?id=468733 --- Comment #3 from francisco_t --- Created attachment 158247 --> https://bugs.kde.org/attachment.cgi?id=158247=edit plasma-org.kde.plasma.desktop-appletsrc AFTER -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 458007] Desktop icons shift when non-auto-hide Panel loads on boot which can position icons weirdly; desktop should reserve space for it in advance
https://bugs.kde.org/show_bug.cgi?id=458007 --- Comment #31 from francisco_t --- (In reply to Nate Graham from comment #30) > *** Bug 468733 has been marked as a duplicate of this bug. *** In my case (https://bugs.kde.org/show_bug.cgi?id=468733) the problem is the vertical panel moves the icons many columns randomly. Original icons: https://bugs.kde.org/attachment.cgi?id=158244 Moved icons: https://bugs.kde.org/attachment.cgi?id=158245 Is it the same problem? -- You are receiving this mail because: You are watching all bug changes.
[kio] [Bug 76380] Moving to trash shouldn't move across partitions
https://bugs.kde.org/show_bug.cgi?id=76380 francisco_t <leviat...@gmx.com> changed: What|Removed |Added CC||leviat...@gmx.com -- You are receiving this mail because: You are watching all bug changes.
