[plasmashell] [Bug 361521] Insane virtual memory consumption and icon-cache mappings
https://bugs.kde.org/show_bug.cgi?id=361521 --- Comment #8 from Laurent Bonnaud --- > Do you see the same? As far as baloo is concerned: yes. It usually uses 5GB of virtual memory. But today I rechecked and it uses an even more insane figure of 256GB ! I wonder how baloo can work on a 32 bits system :>. USER PID %CPU %MEMVSZ RSS TTY STAT START TIME COMMAND bonnaudl 2191 0.0 0.0 268768452 9996 ? SNl Nov22 0:01 baloo_file But perhaps this baloo problem deserves a separate bug report. This report was about plasmashell. Here are details of the mappings it uses: $ cat /proc/2191/maps 564d4f846000-564d4f889000 r-xp 00:15 48261996 /usr/bin/baloo_file 564d4fa88000-564d4fa8b000 r--p 00042000 00:15 48261996 /usr/bin/baloo_file 564d4fa8b000-564d4fa8c000 rw-p 00045000 00:15 48261996 /usr/bin/baloo_file 564d5075d000-564d508b1000 rw-p 00:00 0 [heap] 7f7e-7f7e001cf000 rw-p 00:00 0 7f7e001cf000-7f7e0400 ---p 00:00 0 7f7e0800-7fbe0800 r--s 00:15 36330789 /home/bonnaudl/.local/share/baloo/index 7fbe0800-7fbe08061000 rw-p 00:00 0 7fbe08061000-7fbe0c00 ---p 00:00 0 7fbe0e7b7000-7fbe0e7dc000 r--s 00:15 49178502 /usr/share/mime/mime.cache 7fbe0e7dc000-7fbe0e7dd000 ---p 00:00 0 7fbe0e7dd000-7fbe0f2df000 rw-p 00:00 0 7fbe0f2df000-7fbe0f2e ---p 00:00 0 7fbe0f2e-7fbe0fae rw-p 00:00 0 7fbe0fae-7fbe0fdb9000 r--p 00:15 48519444 /usr/lib/locale/locale-archive 7fbe0fdb9000-7fbe0fdcb000 r-xp 00:15 45344847 /lib/x86_64-linux-gnu/libgpg-error.so.0.19.1 7fbe0fdcb000-7fbe0ffcb000 ---p 00012000 00:15 45344847 /lib/x86_64-linux-gnu/libgpg-error.so.0.19.1 7fbe0ffcb000-7fbe0ffcc000 r--p 00012000 00:15 45344847 /lib/x86_64-linux-gnu/libgpg-error.so.0.19.1 7fbe0ffcc000-7fbe0ffcd000 rw-p 00013000 00:15 45344847 /lib/x86_64-linux-gnu/libgpg-error.so.0.19.1 7fbe0ffcd000-7fbe0ffdb000 r-xp 00:15 45275699 /usr/lib/x86_64-linux-gnu/libdrm.so.2.4.0 7fbe0ffdb000-7fbe101da000 ---p e000 00:15 45275699 /usr/lib/x86_64-linux-gnu/libdrm.so.2.4.0 7fbe101da000-7fbe101db000 r--p d000 00:15 45275699 /usr/lib/x86_64-linux-gnu/libdrm.so.2.4.0 7fbe101db000-7fbe101dc000 rw-p e000 00:15 45275699 /usr/lib/x86_64-linux-gnu/libdrm.so.2.4.0 7fbe101dc000-7fbe101e1000 r-xp 00:15 24859766 /usr/lib/x86_64-linux-gnu/libXxf86vm.so.1.0.0 7fbe101e1000-7fbe103e ---p 5000 00:15 24859766 /usr/lib/x86_64-linux-gnu/libXxf86vm.so.1.0.0 7fbe103e-7fbe103e1000 r--p 4000 00:15 24859766 /usr/lib/x86_64-linux-gnu/libXxf86vm.so.1.0.0 7fbe103e1000-7fbe103e2000 rw-p 5000 00:15 24859766 /usr/lib/x86_64-linux-gnu/libXxf86vm.so.1.0.0 7fbe103e2000-7fbe103e6000 r-xp 00:15 35260453 /usr/lib/x86_64-linux-gnu/libxcb-dri2.so.0.0.0 7fbe103e6000-7fbe105e5000 ---p 4000 00:15 35260453 /usr/lib/x86_64-linux-gnu/libxcb-dri2.so.0.0.0 7fbe105e5000-7fbe105e6000 r--p 3000 00:15 35260453 /usr/lib/x86_64-linux-gnu/libxcb-dri2.so.0.0.0 7fbe105e6000-7fbe105e7000 rw-p 4000 00:15 35260453 /usr/lib/x86_64-linux-gnu/libxcb-dri2.so.0.0.0 7fbe105e7000-7fbe105fe000 r-xp 00:15 35260396 /usr/lib/x86_64-linux-gnu/libxcb-glx.so.0.0.0 7fbe105fe000-7fbe107fd000 ---p 00017000 00:15 35260396 /usr/lib/x86_64-linux-gnu/libxcb-glx.so.0.0.0 7fbe107fd000-7fbe107ff000 r--p 00016000 00:15 35260396 /usr/lib/x86_64-linux-gnu/libxcb-glx.so.0.0.0 7fbe107ff000-7fbe1080 rw-p 00018000 00:15 35260396 /usr/lib/x86_64-linux-gnu/libxcb-glx.so.0.0.0 7fbe1080-7fbe10801000 r-xp 00:15 45275755 /usr/lib/x86_64-linux-gnu/libX11-xcb.so.1.0.0 7fbe10801000-7fbe10a0 ---p 1000 00:15 45275755 /usr/lib/x86_64-linux-gnu/libX11-xcb.so.1.0.0 7fbe10a0-7fbe10a01000 r--p 00:15 45275755 /usr/lib/x86_64-linux-gnu/libX11-xcb.so.1.0.0 7fbe10a01000-7fbe10a02000 rw-p 1000 00:15 45275755 /usr/lib/x86_64-linux-gnu/libX11-xcb.so.1.0.0 7fbe10a02000-7fbe10a07000 r-xp 00:15 45275811 /usr/lib/x86_64-linux-gnu/libXfixes.so.3.1.0 7fbe10a07000-7fbe10c06000 ---p 5000 00:15 45275811 /usr/lib/x86_64-linux-gnu/libXfixes.so.3.1.0 7fbe10c06000-7fbe10c07000 r--p 4000 00:15 45275811 /usr/lib/x86_64-linux-gnu/libXfixes.so.3.1.0 7fbe10c07000-7fbe10c08000 rw-p 5000 00:15 45275811 /usr/lib/x86_64-lin
[plasmashell] [Bug 361521] Insane virtual memory consumption and icon-cache mappings
https://bugs.kde.org/show_bug.cgi?id=361521 --- Comment #9 from Laurent Bonnaud --- Since my initial report I updated my systems to Ubuntu 16.10, Plasma 5.8, and KF5 5.27/5.28. The icon-cache problem is solved: the icon-cache.kcache file is only mapped once. However the DRM problem remains: $ grep /drm /proc/$(pidof plasmashell)/maps | wc 3483132 34104 on one system and on the other: $ grep /drm /proc/$(pidof plasmashell)/maps | wc 2512259 24598 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361521] Large virtual memory consumption and many DRM mmaped objects
https://bugs.kde.org/show_bug.cgi?id=361521 Laurent Bonnaud changed: What|Removed |Added Summary|Insane virtual memory |Large virtual memory |consumption and icon-cache |consumption and many DRM |mappings|mmaped objects Version|5.6.3 |5.8.4 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361521] Large virtual memory consumption and many DRM mmaped objects
https://bugs.kde.org/show_bug.cgi?id=361521 --- Comment #11 from Laurent Bonnaud --- OK, sorry for the misunderstanding ! In my plasmashell process the baloo file is not mapped, probably because I do not use a search plasmoid. Do you use a search plasmoid ? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361521] Large virtual memory consumption and many DRM mmaped objects
https://bugs.kde.org/show_bug.cgi?id=361521 --- Comment #13 from Laurent Bonnaud --- > Virtual memory being high is pretty much a non issue until proved otherwise. Agreed. However the DRM mapping are deleted which probably indicate a resource leak. Here is a sample of the 200+ deleted DRM objects I see on my system just after a session start: 7f0e2574f000-7f0e2578f000 rw-s 00:05 54568 /drm mm object (deleted) 7f0e2578f000-7f0e257cf000 rw-s 00:05 54566 /drm mm object (deleted) 7f0e257cf000-7f0e257d7000 rw-s 00:05 116514 /drm mm object (deleted) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361521] Numerous deleted DRM mmaped objects
https://bugs.kde.org/show_bug.cgi?id=361521 Laurent Bonnaud changed: What|Removed |Added Summary|Large virtual memory|Numerous deleted DRM mmaped |consumption and many DRM|objects |mmaped objects | -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361521] Numerous deleted DRM mmaped objects
https://bugs.kde.org/show_bug.cgi?id=361521 --- Comment #15 from Laurent Bonnaud --- This "deleted drm mm object" problem is not specific to plasma. Several other KDE software have it, the main offender being akregator (see below). Therefore this is probably a more systemic problem, either in KF5 or Qt. Process 13064 - akregator Summary The process akregator (with pid 13064) is using approximately 316.2 MB of memory. It is using 307.7 MB privately, and a further 57.1 MB that is, or could be, shared with other programs. Dividing up the shared memory between all the processes sharing that memory we get a reduced shared memory usage of 8.5 MB. Adding that to the private usage, we get the above mentioned total memory footprint of 316.2 MB. 14.6 MB is swapped out to disk, probably due to a low amount of available memory left. Library Usage The memory usage of a process is found by adding up the memory usage of each of its libraries, plus the process's own heap, stack and any other mappings, plus the stack of its 23 threads. Private 276636 KB [heap] 18296 KB/drm mm object (deleted) 7556 KB /SYSV (deleted) 3460 KB /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5.7.0 816 KB /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5.7.0 Shared 13276 KB/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5.7.0 4396 KB /usr/lib/x86_64-linux-gnu/dri/i965_dri.so 3268 KB /usr/lib/x86_64-linux-gnu/libQt5Core.so.5.7.0 3212 KB /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5.7.0 1492 KB /lib/x86_64-linux-gnu/libc-2.24.so -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 450245] New: dolphin crashed while I was trying to connect to a SMB share
https://bugs.kde.org/show_bug.cgi?id=450245 Bug ID: 450245 Summary: dolphin crashed while I was trying to connect to a SMB share Product: dolphin Version: 21.12.2 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: l.bonn...@laposte.net CC: kfm-de...@kde.org Target Milestone: --- Application: dolphin (21.12.2) Qt Version: 5.15.2 Frameworks Version: 5.91.0 Operating System: Linux 5.16.9-051609-lowlatency x86_64 Windowing System: X11 Distribution: Ubuntu 21.10 DrKonqi: 5.24.0 [KCrashBackend] -- Information about the crash: - What I was doing when the application crashed: I was trying to connect to a SMB share by typing the following URL in the address bar: smb://servername/ The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Dolphin (dolphin), signal: Aborted [KCrash Handler] #4 __pthread_kill_implementation (no_tid=0, signo=6, threadid=139904213823104) at pthread_kill.c:44 #5 __pthread_kill_internal (signo=6, threadid=139904213823104) at pthread_kill.c:80 #6 __GI___pthread_kill (threadid=139904213823104, signo=signo@entry=6) at pthread_kill.c:91 #7 0x7f3e01aff476 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #8 0x7f3e01ae57b7 in __GI_abort () at abort.c:79 #9 0x7f3e03b68f67 in KCoreDirListerCache::printDebug (this=) at ./src/core/kcoredirlister.cpp:2099 #10 0x7f3e03c380ba in KCoreDirListerCache::slotUpdateResult (this=0x7f3e03caa540 <(anonymous namespace)::Q_QGS_kDirListerCache::innerFunction()::holder>, j=0x7ffcc89c7f10) at ./src/core/kcoredirlister.cpp:1735 #11 0x7f3e021eaa53 in QtPrivate::QSlotObjectBase::call (a=0x7ffcc89c8060, r=0x7f3e03caa540 <(anonymous namespace)::Q_QGS_kDirListerCache::innerFunction()::holder>, this=0x5609f4f4f0f0) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #12 doActivate (sender=0x5609f4fa99f0, signal_index=6, argv=0x7ffcc89c8060) at kernel/qobject.cpp:3886 #13 0x7f3e033ea9a0 in KJob::result(KJob*, KJob::QPrivateSignal) () from /lib/x86_64-linux-gnu/libKF5CoreAddons.so.5 #14 0x7f3e033b in KJob::finishJob(bool) () from /lib/x86_64-linux-gnu/libKF5CoreAddons.so.5 #15 0x7f3e021eaa53 in QtPrivate::QSlotObjectBase::call (a=0x7ffcc89c8130, r=0x5609f4fa99f0, this=0x5609f4ffd8d0) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #16 doActivate (sender=0x5609f5c01ad0, signal_index=7, argv=0x7ffcc89c8130) at kernel/qobject.cpp:3886 #17 0x7f3e021e3d67 in QMetaObject::activate (sender=sender@entry=0x5609f5c01ad0, m=m@entry=0x7f3e03ca4c00 , local_signal_index=local_signal_index@entry=4, argv=argv@entry=0x0) at kernel/qobject.cpp:3946 #18 0x7f3e03bc1607 in KIO::SlaveInterface::finished (this=this@entry=0x5609f5c01ad0) at ./obj-x86_64-linux-gnu/src/core/KF5KIOCore_autogen/include/moc_slaveinterface.cpp:464 #19 0x7f3e03bc3853 in KIO::SlaveInterface::dispatch (this=0x5609f5c01ad0, _cmd=, rawdata=...) at ./src/core/slaveinterface.cpp:149 #20 0x7f3e03bc1ead in KIO::SlaveInterface::dispatch (this=0x5609f5c01ad0) at ./src/core/slaveinterface.cpp:78 #21 0x7f3e03bc65c2 in KIO::Slave::gotInput (this=0x5609f5c01ad0) at ./src/core/slave.cpp:336 #22 0x7f3e021eaa53 in QtPrivate::QSlotObjectBase::call (a=0x7ffcc89c8380, r=0x5609f5c01ad0, this=0x5609f4f51810) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #23 doActivate (sender=0x5609f50345b0, signal_index=3, argv=0x7ffcc89c8380) at kernel/qobject.cpp:3886 #24 0x7f3e021e073e in QObject::event (this=0x5609f50345b0, e=0x5609f46d7d80) at kernel/qobject.cpp:1314 #25 0x7f3e02ca16b3 in QApplicationPrivate::notify_helper (this=, receiver=0x5609f50345b0, e=0x5609f46d7d80) at kernel/qapplication.cpp:3632 #26 0x7f3e021b316a in QCoreApplication::notifyInternal2 (receiver=0x5609f50345b0, event=0x5609f46d7d80) at kernel/qcoreapplication.cpp:1063 #27 0x7f3e021b6257 in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x5609f446aec0) at kernel/qcoreapplication.cpp:1817 #28 0x7f3e0220cef7 in postEventSourceDispatch (s=0x5609f4568d60) at kernel/qeventdispatcher_glib.cpp:277 #29 0x7f3dffe328bb in g_main_dispatch (context=0x7f3df4005000) at ../../../glib/gmain.c:3337 #30 g_main_context_dispatch (context=0x7f3df4005000) at ../../../glib/gmain.c:4055 #31 0x7f3dffe85f08 in g_main_context_iterate.constprop.0 (context=context@entry=0x7f3df4005000, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ../../../glib/gmain.c:4131 #32 0x7f3dffe30003 in g_main_context_iteration (context=0x7f3df4005000, may_block=1) at ../../../glib/gmain.c:4196 #33 0x7f3e0220c548 in QEventDispatcherGlib::processEvents (this=0x5609f4563400, flags=...) at kerne
[dolphin] [Bug 450245] dolphin crashed while I was trying to connect to a SMB share
https://bugs.kde.org/show_bug.cgi?id=450245
--- Comment #1 from Laurent Bonnaud ---
I tried again and Dolphin crashed again.
Here is console output:
$ dolphin
Qt: Session management error: networkIdsList argument is NULL
kf.kio.core: Internal error: itemsInUse did not contain
QUrl("smb://DOMAINNAME%5Cbonnaudl@servername/")
kf.kio.core: Fatal Error: HUH? Lister KDirLister(0x55ad7a38ffb0) is supposed to
be listing, but has no job!
KCrash: crashing... crashRecursionCounter = 2
KCrash: Application Name = dolphin path = /usr/bin pid = 6392
KCrash: Arguments: /usr/bin/dolphin
KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi
--
You are receiving this mail because:
You are watching all bug changes.
[ktorrent] [Bug 450811] New: ktorrent crash while downloading a file
https://bugs.kde.org/show_bug.cgi?id=450811 Bug ID: 450811 Summary: ktorrent crash while downloading a file Product: ktorrent Version: 21.12.2 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: joris.guis...@gmail.com Reporter: l.bonn...@laposte.net Target Milestone: --- Application: ktorrent (21.12.2) Qt Version: 5.15.2 Frameworks Version: 5.91.0 Operating System: Linux 5.16.11-051611-lowlatency x86_64 Windowing System: X11 Distribution: Ubuntu 21.10 DrKonqi: 5.24.2 [KCrashBackend] -- Information about the crash: - What I was doing when the application crashed: I was waiting for the file to finish downlading. ktorrent sometimes crashes when the dowload speed is very high and saturates my Internet access (1Gb/s). I have never seen it crash when the download speed is limited by peers and is below my ISP limit. The crash can be reproduced sometimes. -- Backtrace: Application: KTorrent (ktorrent), signal: Aborted [KCrash Handler] #4 __pthread_kill_implementation (no_tid=0, signo=6, threadid=140033914699328) at pthread_kill.c:44 #5 __pthread_kill_internal (signo=6, threadid=140033914699328) at pthread_kill.c:80 #6 __GI___pthread_kill (threadid=140033914699328, signo=signo@entry=6) at pthread_kill.c:91 #7 0x7f5c342ba476 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #8 0x7f5c342a07b7 in __GI_abort () at abort.c:79 #9 0x7f5c3463ba31 in __gnu_cxx::__verbose_terminate_handler () at ../../../../src/libstdc++-v3/libsupc++/vterminate.cc:95 #10 0x7f5c346474ec in __cxxabiv1::__terminate (handler=) at ../../../../src/libstdc++-v3/libsupc++/eh_terminate.cc:48 #11 0x7f5c346464b9 in __cxa_call_terminate (ue_header=0x557799907a40) at ../../../../src/libstdc++-v3/libsupc++/eh_call.cc:54 #12 0x7f5c34646c3a in __cxxabiv1::__gxx_personality_v0 (version=, actions=6, exception_class=5138137972254386944, ue_header=0x557799907a40, context=) at ../../../../src/libstdc++-v3/libsupc++/eh_personality.cc:685 #13 0x7f5c344ad484 in _Unwind_RaiseException_Phase2 (exc=0x557799907a40, context=0x7ffc43055ea0, frames_p=0x7ffc43055da8) at ../../../src/libgcc/unwind.inc:64 #14 0x7f5c344adebe in _Unwind_Resume (exc=exc@entry=0x557799907a40) at ../../../src/libgcc/unwind.inc:241 #15 0x7f5c36716676 in bt::TorrentControl::stop (this=, wjob=) at ./src/torrent/torrentcontrol.cpp:452 #16 0x7f5c367971cc in bt::TorrentControl::~TorrentControl (this=0x557798d9ab80, __in_chrg=) at ./src/torrent/torrentcontrol.cpp:104 #17 0x7f5c3679723d in bt::TorrentControl::~TorrentControl (this=0x557798d9ab80, __in_chrg=) at ./src/torrent/torrentcontrol.cpp:124 #18 0x7f5c368ca32e in qDeleteAll::const_iterator> (end=..., begin=...) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qalgorithms.h:320 #19 qDeleteAll (c=...) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qalgorithms.h:328 #20 kt::QueueManager::~QueueManager (this=, this=) at ./libktcore/torrent/queuemanager.cpp:52 #21 0x7f5c368ca3ad in kt::QueueManager::~QueueManager (this=, this=) at ./libktcore/torrent/queuemanager.cpp:53 #22 0x5577989000a4 in kt::Core::~Core (this=, this=) at ./ktorrent/core.cpp:115 #23 0x557798909c12 in kt::Core::~Core (this=, this=) at ./ktorrent/core.cpp:113 #24 kt::GUI::~GUI (this=, this=) at ./ktorrent/gui.cpp:115 #25 0x5577988f2c8b in main (argc=, argv=) at ./ktorrent/main.cpp:236 [Inferior 1 (process 48552) detached] Possible duplicates by query: bug 447918. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 461176] Applications don't prompt to save unsaved work when logging out on Wayland
https://bugs.kde.org/show_bug.cgi?id=461176 Laurent Bonnaud changed: What|Removed |Added CC||l.bonn...@laposte.net -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 468064] New: Could you please update the krdc snap?
https://bugs.kde.org/show_bug.cgi?id=468064 Bug ID: 468064 Summary: Could you please update the krdc snap? Classification: KDE Neon Product: neon Version: unspecified Platform: Snap OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Snaps Assignee: sgmo...@kde.org Reporter: l.bonn...@laposte.net CC: neon-b...@kde.org Target Milestone: --- Hi, I am using this snap: $ snap info krdc [...] channels: latest/stable:22.08.22022-10-31 (64) 9MB - latest/candidate: 22.08.32022-11-07 (68) 9MB - latest/beta: ↑ latest/edge: master+142480e 2020-01-08 (46) 3MB - installed: 22.08.2 (64) 9MB - and noticed the following: 1. version 22.08.x is old and versions 22.12.x are out 2. it depends on an old kf5/qt snap: $ snap connections krdc Interface Plug Slot Notes [...] content[kde-frameworks-5-98-qt-5-15-6-core20-all] krdc:kde-frameworks-5-98-qt-5-15-6-core20 kde-frameworks-5-98-qt-5-15-6-core20:kde-frameworks-5-98-qt-5-15-6-core20-slot - The krdc snap is the only one on my system that depends on kde-frameworks-5-98-qt-5-15-6-core20 and updating it would allow me to lighten my system from this outdated snap. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 419181] okular could use more hardening
https://bugs.kde.org/show_bug.cgi?id=419181 Laurent Bonnaud changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #1 from Laurent Bonnaud --- I am closing this bug because the okular snap is now on the same hardening level as apt packages and flatpak bundles. -- You are receiving this mail because: You are watching all bug changes.
[marble] [Bug 448108] free(): invalid pointer
https://bugs.kde.org/show_bug.cgi?id=448108 Laurent Bonnaud changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #3 from Laurent Bonnaud --- This bug no longer exists. -- You are receiving this mail because: You are watching all bug changes.
[ktorrent] [Bug 450811] ktorrent crash while downloading a file
https://bugs.kde.org/show_bug.cgi?id=450811 Laurent Bonnaud changed: What|Removed |Added Version|21.12.2 |22.12.3 -- You are receiving this mail because: You are watching all bug changes.
[marble] [Bug 448111] Map is unreadable when it is moved with the mouse pointer
https://bugs.kde.org/show_bug.cgi?id=448111 Laurent Bonnaud changed: What|Removed |Added Version|21.12.1 |22.12.3 -- You are receiving this mail because: You are watching all bug changes.
[trojita] [Bug 452284] The Trojita flatpak uses the end-of-life org.kde.Platform//5.15 runtime
https://bugs.kde.org/show_bug.cgi?id=452284 Laurent Bonnaud changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #2 from Laurent Bonnaud --- I am closing this bug because trojita is no longer available from the flathub repository, but only from beta or development repositories: $ flatpak install org.kde.trojita Looking for matches… Remotes found with refs similar to ‘org.kde.trojita’: 1) ‘flathub-beta’ (system) 2) ‘kdeapps’ (system) and the flatpak from kdeapps is up to date: $ flatpak info org.kde.trojita Trojitá - IMAP E-mail Client ID: org.kde.trojita Ref: app/org.kde.trojita/x86_64/master Arch: x86_64 Branch: master Version: 0.7 License: GPL-2.0+ Origin: kdeapps Collection: Installation: system Installed: 55.9 MB Runtime: org.kde.Platform/x86_64/5.15-22.08 Sdk: org.kde.Sdk/x86_64/5.15-22.08 Commit: fdb3f35da1744f05dacfbe9ac4315a7337a5c558f77720277ce5ee1f2e8d5c12 Parent: ccf7a188ec5d6ac8b527fcca452ab3ba27d1ec3d1f9a7a83081775c8366b8146 Subject: Built on Sat Apr 1 16:30:12 CEST 2023 Date: 2023-04-01 14:30:40 + -- You are receiving this mail because: You are watching all bug changes.
[marble] [Bug 339867] Some data is stored in $XDG_DATA_HOME (~/.local/share) but $XDG_CACHE_HOME (~/.cache) would be more appropriate
https://bugs.kde.org/show_bug.cgi?id=339867 Laurent Bonnaud changed: What|Removed |Added Version|2.5 (KDE Applications |22.12.3 |18.04) | -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kconfig] [Bug 360561] KConfig warnings cannot be silenced
https://bugs.kde.org/show_bug.cgi?id=360561 Laurent Bonnaud changed: What|Removed |Added Version|5.56.0 |5.104.0 -- You are receiving this mail because: You are watching all bug changes.
[marble] [Bug 448111] Map is unreadable when it is moved with the mouse pointer
https://bugs.kde.org/show_bug.cgi?id=448111 --- Comment #6 from Laurent Bonnaud --- Great! Thanks for the info, and for the new default setting! -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 468064] Could you please update the krdc snap?
https://bugs.kde.org/show_bug.cgi?id=468064 --- Comment #3 from Laurent Bonnaud --- Thank you for the updated package! -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 411402] Ktorrent Snap crashes on start because it needs Qt 5.12
https://bugs.kde.org/show_bug.cgi?id=411402 --- Comment #4 from Laurent Bonnaud --- Thanks a lot for the fix! -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 307824] Wrong character spacing makes text unreadable
https://bugs.kde.org/show_bug.cgi?id=307824 --- Comment #28 from Laurent Bonnaud --- I do not use konqueror any longer, so let's this bug die... -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 436318] Save session doesn't work under Wayland
https://bugs.kde.org/show_bug.cgi?id=436318 --- Comment #86 from Laurent Bonnaud --- > We've introduced a fallback. plasma-fallback-session-save which provides > something. Thanks! > It's not perfect. It just sees which apps were open and then reopens them. > The application has no mechanism to save any state. Let's take Konsole as an example. Does this mean that Konsole will not save its current directory? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 436318] Save session doesn't work under Wayland
https://bugs.kde.org/show_bug.cgi?id=436318 --- Comment #90 from Laurent Bonnaud --- How about using this piece of software? https://github.com/Vladimir-csp/uwsm -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 436318] Save session doesn't work under Wayland
https://bugs.kde.org/show_bug.cgi?id=436318 Laurent Bonnaud changed: What|Removed |Added CC||l.bonn...@laposte.net -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 421870] windows on wrong desktop after session restore on Wayland
https://bugs.kde.org/show_bug.cgi?id=421870 Laurent Bonnaud changed: What|Removed |Added CC||l.bonn...@laposte.net -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 450245] dolphin crashed while I was trying to connect to a SMB share
https://bugs.kde.org/show_bug.cgi?id=450245 Laurent Bonnaud changed: What|Removed |Added Version|21.12.2 |22.04.1 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 450245] dolphin crashed while I was trying to connect to a SMB share
https://bugs.kde.org/show_bug.cgi?id=450245 --- Comment #2 from Laurent Bonnaud --- The bug still exists with those versions: Dolphin Version 22.04.1 KDE Frameworks Version 5.94.0 Qt Version 5.15.3 (built against 5.15.3) The xcb windowing system -- You are receiving this mail because: You are watching all bug changes.
[trojita] [Bug 452284] New: The Trojita flatpak uses the end-of-life org.kde.Platform//5.15 runtime
https://bugs.kde.org/show_bug.cgi?id=452284 Bug ID: 452284 Summary: The Trojita flatpak uses the end-of-life org.kde.Platform//5.15 runtime Product: trojita Version: 0.7 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Other Assignee: trojita-b...@kde.org Reporter: l.bonn...@laposte.net Target Milestone: --- Hi, here is the problem: $ flatpak update Looking for updates… Info: org.kde.Platform//5.15 is end-of-life, with reason: We strongly recommend moving to the latest stable version of the Plaform and SDK Applications using this runtime: org.kde.trojita -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 389942] konsole crash on logout
https://bugs.kde.org/show_bug.cgi?id=389942 Laurent Bonnaud changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|BACKTRACE |FIXED --- Comment #22 from Laurent Bonnaud --- Some time ago I did some cleanup in the session management files in my home directory and since then I never saw a crash. Therefore, if nobody objects I am going to close this bug... -- You are receiving this mail because: You are watching all bug changes.
[marble] [Bug 339867] Some data is stored in $XDG_DATA_HOME (~/.local/share) but $XDG_CACHE_HOME (~/.cache) would be more appropriate
https://bugs.kde.org/show_bug.cgi?id=339867 --- Comment #10 from Laurent Bonnaud --- This bug still exists in Ubuntu 20.10 and this package version: Package: marble Version: 4:20.08.1-0ubuntu1 -- You are receiving this mail because: You are watching all bug changes.
[marble] [Bug 339867] Some data is stored in $XDG_DATA_HOME (~/.local/share) but $XDG_CACHE_HOME (~/.cache) would be more appropriate
https://bugs.kde.org/show_bug.cgi?id=339867 Laurent Bonnaud changed: What|Removed |Added Version|1.9 (KDE 4.14) |2.5 (KDE Applications ||18.04) -- You are receiving this mail because: You are watching all bug changes.
[marble] [Bug 339867] Some data is stored in $XDG_DATA_HOME (~/.local/share) but $XDG_CACHE_HOME (~/.cache) would be more appropriate
https://bugs.kde.org/show_bug.cgi?id=339867 --- Comment #11 from Laurent Bonnaud --- BTW version information is not up to date in the KDE Bugtracking System. The latest known marble version is 18.04. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 438632] New: Invalid escape sequence in rae.desktop
https://bugs.kde.org/show_bug.cgi?id=438632
Bug ID: 438632
Summary: Invalid escape sequence in rae.desktop
Product: frameworks-kio
Version: 5.83.0
Platform: Kubuntu Packages
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: kio-bugs-n...@kde.org
Reporter: l.bonn...@laposte.net
CC: kdelibs-b...@kde.org
Target Milestone: ---
Hi,
here is the error message:
kf.config.core: "KConfigIni: In file
/usr/share/kservices5/searchproviders/rae.desktop, line 94: " "Invalid escape
sequence \"\\{\"."
Here is line 94 of rae.desktop:
Query=https://dle.rae.es/\{@}
--
You are receiving this mail because:
You are watching all bug changes.
[drkonqi] [Bug 438637] New: drkonqi crash with Wayland
https://bugs.kde.org/show_bug.cgi?id=438637 Bug ID: 438637 Summary: drkonqi crash with Wayland Product: drkonqi Version: 5.22.0 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: l.bonn...@laposte.net Target Milestone: --- Hi, I was testing plasma 5.22 under Wayland and some KDE software crashed. DrKonqi poped-up and crahed itself. Here is the backtrace: Application: The KDE Crash Handler (drkonqi), signal: Segmentation fault [KCrash Handler] #4 0x7f2179518341 in QtWaylandClient::WlCallback::callback_done (callback_data=, this=0x559f4c045300) at qwaylandinputdevice.cpp:183 #5 QtWaylandClient::WlCallback::callback_done (this=0x559f4c045300, callback_data=) at qwaylandinputdevice.cpp:179 #6 0x7f2177539249 in ffi_call_unix64 () at ../src/x86/unix64.S:106 #7 0x7f2177538639 in ffi_call_int (cif=, fn=, rvalue=, avalue=, closure=) at ../src/x86/ffi64.c:669 #8 0x7f2179498502 in wl_closure_invoke (closure=closure@entry=0x559f4c05cb30, flags=flags@entry=1, target=, target@entry=0x559f4c03a470, opcode=opcode@entry=0, data=) at ../src/connection.c:1018 #9 0x7f2179494aea in dispatch_event (display=display@entry=0x559f4bb62000, queue=, queue=) at ../src/wayland-client.c:1445 #10 0x7f21794961dc in dispatch_queue (queue=0x559f4bb620d0, display=0x559f4bb62000) at ../src/wayland-client.c:1591 #11 wl_display_dispatch_queue_pending (display=0x559f4bb62000, queue=0x559f4bb620d0) at ../src/wayland-client.c:1833 #12 0x7f2179496230 in wl_display_dispatch_pending (display=) at ../src/wayland-client.c:1896 #13 0x7f2179519f83 in QtWaylandClient::QWaylandDisplay::flushRequests (this=0x559f4bb5e270) at qwaylanddisplay.cpp:221 #14 0x7f217ac79b44 in doActivate (sender=0x559f4bbd4df0, signal_index=4, argv=0x7ffd3b389d00, argv@entry=0x0) at kernel/qobject.cpp:3898 #15 0x7f217ac72cb8 in QMetaObject::activate (sender=sender@entry=0x559f4bbd4df0, m=m@entry=0x7f217aedb7e0 , local_signal_index=local_signal_index@entry=1, argv=argv@entry=0x0) at kernel/qobject.cpp:3946 #16 0x7f217ac3ec47 in QAbstractEventDispatcher::awake (this=this@entry=0x559f4bbd4df0) at .moc/moc_qabstracteventdispatcher.cpp:149 #17 0x7f217ac9b5cc in QEventDispatcherGlib::processEvents (this=0x559f4bbd4df0, flags=...) at kernel/qeventdispatcher_glib.cpp:430 #18 0x7f217ac40b8b in QEventLoop::exec (this=this@entry=0x7ffd3b389e20, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:69 #19 0x7f217ac49024 in QCoreApplication::exec () at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #20 0x559f4aa790f1 in main (argc=, argv=) at ./src/main.cpp:219 [Inferior 1 (process 19637) detached] SOFTWARE/OS VERSIONS Linux: Ubuntu 21.04 KDE Plasma Version: 5.22 KDE Frameworks Version: 5.83 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 432860] [wayland] tooltips appear in wrong place
https://bugs.kde.org/show_bug.cgi?id=432860 Laurent Bonnaud changed: What|Removed |Added CC||l.bonn...@laposte.net --- Comment #1 from Laurent Bonnaud --- I observe the same problem on my system (see attached screenshot): Ubuntu 21.04 Plasma 5.22 KF5 5.83 Here is a way to reproduce the problem: 1. Go to "Workspace Behavior", "General Behavior" 2. Place the mouse pointer on the "Reset" button 3. Wait for the tooltip to appear 4. Move the pointer to the "Default" button 5. Wait for the tooltip to appear 6. Move the pointer to the "Help" button 7. Wait for the tooltip to appear -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 432860] [wayland] tooltips appear in wrong place
https://bugs.kde.org/show_bug.cgi?id=432860 Laurent Bonnaud changed: What|Removed |Added Version|5.20.5 |5.22.0 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 432860] [wayland] tooltips appear in wrong place
https://bugs.kde.org/show_bug.cgi?id=432860 --- Comment #2 from Laurent Bonnaud --- Created attachment 139317 --> https://bugs.kde.org/attachment.cgi?id=139317&action=edit Screenshot with wrongly placed tooltip -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 438643] New: tooltip displayed at the wrong place in Wayland
https://bugs.kde.org/show_bug.cgi?id=438643 Bug ID: 438643 Summary: tooltip displayed at the wrong place in Wayland Product: drkonqi Version: 5.22.0 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: l.bonn...@laposte.net Target Milestone: --- SUMMARY While reporting a bug with drkonqi I noticed that tooltips do not appear at the right place STEPS TO REPRODUCE 1. Open a drkonqi window 2. Maximize it vertically 3. Put the mouse pointer on the "Close" button 4. Wait for the tooltip to appear OBSERVED RESULT tooltip appears where it would have if the window had not been maximized EXPECTED RESULT tooltip appears at the usual location SOFTWARE/OS VERSIONS Linux: Ubuntu 21.04 KDE Plasma Version: 5.22 KDE Frameworks Version: 5.83 Qt Version: 5.12.5 -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 438643] tooltip displayed at the wrong place in Wayland
https://bugs.kde.org/show_bug.cgi?id=438643 --- Comment #1 from Laurent Bonnaud --- Created attachment 139318 --> https://bugs.kde.org/attachment.cgi?id=139318&action=edit Screenshot with wrongly placed tooltip -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 432860] [wayland] tooltips appear in wrong place
https://bugs.kde.org/show_bug.cgi?id=432860 --- Comment #4 from Laurent Bonnaud --- > Cannot reproduce with a full git master session. I can reproduce it in KDE neon "Unstable Edition/Unstable branches" with updates from today, see attached screenshot. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 432860] [wayland] tooltips appear in wrong place
https://bugs.kde.org/show_bug.cgi?id=432860 --- Comment #5 from Laurent Bonnaud --- Created attachment 139332 --> https://bugs.kde.org/attachment.cgi?id=139332&action=edit tooltip problem in KDE neon -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 432860] [wayland] tooltips appear in wrong place
https://bugs.kde.org/show_bug.cgi?id=432860 Laurent Bonnaud changed: What|Removed |Added Status|NEEDSINFO |CONFIRMED Ever confirmed|0 |1 Resolution|WAITINGFORINFO |--- --- Comment #6 from Laurent Bonnaud --- > Do you see this issue in any other apps, or just System Settings? I saw a similar (but not quite the same) problem with drkonqi, see bug #438643. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 438670] New: Discover notifies about updates whereas there are none
https://bugs.kde.org/show_bug.cgi?id=438670 Bug ID: 438670 Summary: Discover notifies about updates whereas there are none Product: Discover Version: 5.22.0 Platform: Neon Packages OS: Linux Status: REPORTED Severity: major Priority: NOR Component: Notifier Assignee: aleix...@kde.org Reporter: l.bonn...@laposte.net Target Milestone: --- SUMMARY I updated my KDE neon system and then discover still notifies me about available updates STEPS TO REPRODUCE 1. Update the system with "apt full-update" 2. Log out 3. Log in again OBSERVED RESULT discover-notifier displays a notification with "Updates available" EXPECTED RESULT no notification SOFTWARE/OS VERSIONS Linux: KDE neon unstable KDE Plasma Version: 5.22.80 KDE Frameworks Version: 5.84 Qt Version: 5.15.3 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 438670] Discover notifies about updates whereas there are none
https://bugs.kde.org/show_bug.cgi?id=438670 --- Comment #1 from Laurent Bonnaud --- Created attachment 139333 --> https://bugs.kde.org/attachment.cgi?id=139333&action=edit Illustration of the problem -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 438643] tooltip displayed at the wrong place in Wayland
https://bugs.kde.org/show_bug.cgi?id=438643 Laurent Bonnaud changed: What|Removed |Added Status|RESOLVED|REPORTED Resolution|WORKSFORME |--- --- Comment #3 from Laurent Bonnaud --- I made a mistake while typing the Qt version. It really is: Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 325566] KWin should export the tiling state for clients which should restore either tiling or the pre-tiled size
https://bugs.kde.org/show_bug.cgi?id=325566 Laurent Bonnaud changed: What|Removed |Added Version|4.11.1 |5.22.1 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 438632] Invalid escape sequence in rae.desktop
https://bugs.kde.org/show_bug.cgi?id=438632 --- Comment #2 from Laurent Bonnaud --- Thanks for the fix! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 477579] Plasma only tries to close native Wayland windows and not Xwayland ones causing data loss
https://bugs.kde.org/show_bug.cgi?id=477579 Laurent Bonnaud changed: What|Removed |Added CC||l.bonn...@laposte.net -- You are receiving this mail because: You are watching all bug changes.
[Haruna] [Bug 456482] hardware decoding doesn't work
https://bugs.kde.org/show_bug.cgi?id=456482 Laurent Bonnaud changed: What|Removed |Added CC||l.bonn...@laposte.net -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 475793] New: Please update okular snap
https://bugs.kde.org/show_bug.cgi?id=475793 Bug ID: 475793 Summary: Please update okular snap Classification: KDE Neon Product: neon Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Snaps Assignee: sgmo...@kde.org Reporter: l.bonn...@laposte.net CC: neon-b...@kde.org Target Milestone: --- Hi, the Okular snap package is version 23.04.3 whereas version 23.08.x exists. $ snap info okular [...] channels: latest/stable:23.04.3 2023-08-18 (142) 256MB - latest/candidate: 23.04.3 2023-08-18 (142) 256MB - latest/beta: ↑ latest/edge: ↑ installed: 23.04.3(142) 256MB - -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 475793] Please update okular snap
https://bugs.kde.org/show_bug.cgi?id=475793 --- Comment #3 from Laurent Bonnaud --- And it arrived on my system :>. Thanks a lot! -- You are receiving this mail because: You are watching all bug changes.
[marble] [Bug 448108] New: free(): invalid pointer
https://bugs.kde.org/show_bug.cgi?id=448108 Bug ID: 448108 Summary: free(): invalid pointer Product: marble Version: 21.12.1 Platform: Flatpak OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: marble-b...@kde.org Reporter: l.bonn...@laposte.net Target Milestone: --- SUMMARY marble free()s an invalid pointer on exit STEPS TO REPRODUCE 1. flatpak run org.kde.marble 2. quit marble OBSERVED RESULT $ flatpak run org.kde.marble Start: MarblePart::readSettings() Updating Settings ... kf.xmlgui: Shortcut for action "" "Hide &All Panels" set with QAction::setShortcut()! Use KActionCollection::setDefaultShortcut(s) instead. free(): invalid pointer Sometimes I also get a crash: $ flatpak run org.kde.marble Start: MarblePart::readSettings() Updating Settings ... kf.xmlgui: Shortcut for action "" "Hide &All Panels" set with QAction::setShortcut()! Use KActionCollection::setDefaultShortcut(s) instead. free(): invalid pointer KCrash: crashing... crashRecursionCounter = 2 KCrash: Application Name = marble path = /app/bin pid = 2 KCrash: Arguments: /app/bin/marble EXPECTED RESULT no invalid free and no crash SOFTWARE/OS VERSIONS $ flatpak info org.kde.marble//stable Marble - Virtual Globe ID: org.kde.marble Ref: app/org.kde.marble/x86_64/stable Arch: x86_64 Branch: stable Version: 21.12.1 License: LGPL-2.1-or-later Origin: flathub Collection: org.flathub.Stable Installation: system Installed: 237.3 MB Runtime: org.kde.Platform/x86_64/5.15-21.08 Sdk: org.kde.Sdk/x86_64/5.15-21.08 Commit: e5df76dd61ee708f4b8b7a838331fa6dcba0fa99d0ca635057fa12710d3ed2d1 Parent: 562104dc0f72eeeda48d4fc3216436bb77dbde998076e4cfbd1881a0b11e52c9 Subject: Update to 21.12.1 (0a4b16e6) Date: 2022-01-06 20:08:40 + -- You are receiving this mail because: You are watching all bug changes.
[marble] [Bug 448108] free(): invalid pointer
https://bugs.kde.org/show_bug.cgi?id=448108 --- Comment #1 from Laurent Bonnaud --- I also observe a similar behavior with the Ubuntu package: Package: marble Status: install ok installed Priority: optional Section: misc Installed-Size: 1112 Maintainer: Kubuntu Developers Architecture: amd64 Version: 4:21.12.1-0ubuntu1~ubuntu21.10~ppa1 Replaces: marble-data (<< 4:17.08.1) Depends: marble-data (>= 4:21.12.1-0ubuntu1~ubuntu21.10~ppa1), marble-plugins (= 4:21.12.1-0ubuntu1~ubuntu21.10~ppa1), kio, libc6 (>= 2.34), libgcc-s1 (>= 3.0), libkf5configcore5 (>= 4.98.0), libkf5configgui5 (>= 4.97.0), libkf5configwidgets5 (>= 4.96.0), libkf5coreaddons5 (>= 5.7.0~), libkf5crash5 (>= 5.7.0~), libkf5i18n5 (>= 5.7.0~), libkf5kiowidgets5 (>= 5.7.0~), libkf5parts5 (>= 5.7.0~), libkf5widgetsaddons5 (>= 4.96.0), libkf5xmlgui5 (>= 4.98.0), libmarblewidget-qt5-28 (= 4:21.12.1-0ubuntu1~ubuntu21.10~ppa1), libqt5core5a (>= 5.15.1), libqt5dbus5 (>= 5.7.0~), libqt5gui5 (>= 5.7.0) | libqt5gui5-gles (>= 5.7.0), libqt5network5 (>= 5.7.0~), libqt5printsupport5 (>= 5.7.0~), libqt5widgets5 (>= 5.7.0~), libqt5xml5 (>= 5.7.0~), libstdc++6 (>= 4.1.1) Suggests: gosmore, monav-routing-daemon, routino Breaks: marble-data (<< 4:17.08.1) Description: globe and map widget Marble is a generic geographical map widget and framework for KDE applications. The Marble widget shows the earth as a sphere but does not require hardware acceleration. A minimal set of geographical data is included, so it can be used without an internet connection. . This package is part of the KDE education module. Homepage: https://marble.kde.org/ Original-Maintainer: Debian Qt/KDE Maintainers -- You are receiving this mail because: You are watching all bug changes.
[marble] [Bug 448108] free(): invalid pointer
https://bugs.kde.org/show_bug.cgi?id=448108 --- Comment #2 from Laurent Bonnaud --- Running marble with valgrind gives the following (among many other) error: ==94== Invalid free() / delete / delete[] / realloc() ==94==at 0x484684F: operator delete(void*) (vg_replace_malloc.c:802) ==94==by 0x66DC4E2: QObject::event(QEvent*) (qobject.cpp:1301) ==94==by 0x4FBC0CC: KXmlGuiWindow::event(QEvent*) (kxmlguiwindow.cpp:219) ==94==by 0x57C46B2: QApplicationPrivate::notify_helper(QObject*, QEvent*) (qapplication.cpp:3632) ==94==by 0x66AF169: QCoreApplication::notifyInternal2(QObject*, QEvent*) (qcoreapplication.cpp:1063) ==94==by 0x66B2256: QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) (qcoreapplication.cpp:1817) ==94==by 0x6708EF6: postEventSourceDispatch(_GSource*, int (*)(void*), void*) (qeventdispatcher_glib.cpp:277) ==94==by 0x80108BA: UnknownInlinedFun (gmain.c:3337) ==94==by 0x80108BA: g_main_context_dispatch (gmain.c:4055) ==94==by 0x8063F07: g_main_context_iterate.constprop.0 (gmain.c:4131) ==94==by 0x800E002: g_main_context_iteration (gmain.c:4196) ==94==by 0x6708547: QEventDispatcherGlib::processEvents(QFlags) (qeventdispatcher_glib.cpp:423) ==94==by 0x66ADA9A: QEventLoop::exec(QFlags) (qeventloop.cpp:232) ==94== Address 0x1ffefff8c0 is on thread 1's stack -- You are receiving this mail because: You are watching all bug changes.
[marble] [Bug 448111] New: Map is unreadable when it is moved with the mouse pointer
https://bugs.kde.org/show_bug.cgi?id=448111 Bug ID: 448111 Summary: Map is unreadable when it is moved with the mouse pointer Product: marble Version: 21.12.1 Platform: Flatpak OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: marble-b...@kde.org Reporter: l.bonn...@laposte.net Target Milestone: --- SUMMARY Moving the map with the mouse pointer makes the map temporarily unreadable STEPS TO REPRODUCE 1. Move the map with the mouse pointer and do not release the mouse button 2. Map is strongly degraded 3. Release the mouse button and see how the map suddenly improves OBSERVED RESULT Quality degradation during movement EXPECTED RESULT Same map quality during movement as when map is static SOFTWARE/OS VERSIONS $ flatpak info org.kde.marble//stable Marble - Virtual Globe ID: org.kde.marble Ref: app/org.kde.marble/x86_64/stable Arch: x86_64 Branch: stable Version: 21.12.1 License: LGPL-2.1-or-later Origin: flathub Collection: org.flathub.Stable Installation: system Installed: 237.3 MB Runtime: org.kde.Platform/x86_64/5.15-21.08 Sdk: org.kde.Sdk/x86_64/5.15-21.08 Commit: e5df76dd61ee708f4b8b7a838331fa6dcba0fa99d0ca635057fa12710d3ed2d1 Parent: 562104dc0f72eeeda48d4fc3216436bb77dbde998076e4cfbd1881a0b11e52c9 Subject: Update to 21.12.1 (0a4b16e6) Date: 2022-01-06 20:08:40 + -- You are receiving this mail because: You are watching all bug changes.
[marble] [Bug 448111] Map is unreadable when it is moved with the mouse pointer
https://bugs.kde.org/show_bug.cgi?id=448111 --- Comment #1 from Laurent Bonnaud --- Created attachment 145217 --> https://bugs.kde.org/attachment.cgi?id=145217&action=edit Degraded map Note how the "Paris" label is not degraded -- You are receiving this mail because: You are watching all bug changes.
[marble] [Bug 448111] Map is unreadable when it is moved with the mouse pointer
https://bugs.kde.org/show_bug.cgi?id=448111 --- Comment #2 from Laurent Bonnaud --- Created attachment 145218 --> https://bugs.kde.org/attachment.cgi?id=145218&action=edit Normal quality map Note how the "Paris" label is now perfectly readable -- You are receiving this mail because: You are watching all bug changes.
[marble] [Bug 448111] Map is unreadable when it is moved with the mouse pointer
https://bugs.kde.org/show_bug.cgi?id=448111 --- Comment #3 from Laurent Bonnaud --- (In reply to Laurent Bonnaud from comment #1) > Created attachment 145217 [details] > Degraded map > > Note how the "Paris" label is not degraded Note how the "Paris" label is *unreadable* -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 387706] Crash while inserting/mouting/ejecting optical media
https://bugs.kde.org/show_bug.cgi?id=387706 --- Comment #3 from Laurent Bonnaud --- Since then, I did not use optical media anymore and now I do not have access to an optical drive. Therefore, I cannot answer your question. -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 256034] Feed content is displayed with date 07.02.2106 07:28
https://bugs.kde.org/show_bug.cgi?id=256034 Laurent Bonnaud changed: What|Removed |Added CC||l.bonn...@laposte.net -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 389942] konsole crash on logout
https://bugs.kde.org/show_bug.cgi?id=389942 --- Comment #16 from Laurent Bonnaud --- I have the master flatpak version (konsole 19.07.70), but unfortunately session management does not work with it: $ flatpak run org.kde.konsole//master Qt: Session management error: Could not open network socket and my bug seems to be related to session management because I see this in the backtrace: #42 0x7f3d5641f44b in QProcess::waitForFinished (this=, msecs=1000) at io/qprocess.cpp:1919 #43 0x7f3d57a885f5 in Konsole::Session::closeInNormalWay() () from /usr/lib/x86_64-linux-gnu/libkonsoleprivate.so.18 #44 0x7f3d57a889f5 in Konsole::Session::close() () from /usr/lib/x86_64-linux-gnu/libkonsoleprivate.so.18 #45 0x7f3d57a9ae08 in Konsole::SessionManager::closeAllSessions() () from /usr/lib/x86_64-linux-gnu/libkonsoleprivate.so.18 #46 0x7f3d57d27614 in Konsole::Application::~Application (this=0x7ffc33e2d150, __in_chrg=) at ./src/Application.cpp:158 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 389942] konsole crash on logout
https://bugs.kde.org/show_bug.cgi?id=389942 --- Comment #17 from Laurent Bonnaud --- The bug is still in Ubuntu 19.04 with the following versions: konsole 4:18.12.3-0ubuntu2 KF5 5.56.0-0ubuntu1 Qt 5.12.2+dfsg-2ubuntu1 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 389942] konsole crash on logout
https://bugs.kde.org/show_bug.cgi?id=389942
--- Comment #18 from Laurent Bonnaud ---
Here is a backtrace:
#0 0x7f3d57c39729 in __GI___poll (fds=0x7f3d40004e30, nfds=2, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
resultvar = 2
sc_cancel_oldtype = 0
sc_ret =
#1 0x7f3d54716cb6 in g_main_context_poll (priority=,
n_fds=2, fds=0x7f3d40004e30, timeout=, context=0x7f3d4bf0)
at ../../../glib/gmain.c:4228
ret =
errsv =
poll_func = 0x7f3d547264d0
poll_func =
ret =
errsv =
#2 g_main_context_iterate (context=context@entry=0x7f3d4bf0,
block=block@entry=1, dispatch=dispatch@entry=1, self=) at
../../../glib/gmain.c:3922
max_priority = 2147483647
timeout = -1
some_ready =
nfds = 2
allocated_nfds = 2
fds = 0x7f3d40004e30
#3 0x7f3d54716ddc in g_main_context_iteration (context=0x7f3d4bf0,
may_block=may_block@entry=1) at ../../../glib/gmain.c:3988
retval =
#4 0x7f3d564ec047 in QEventDispatcherGlib::processEvents
(this=0x7f3d4b20, flags=...) at kernel/qeventdispatcher_glib.cpp:422
d = 0x7f3d4b40
canWait = true
savedFlags = {i = 0}
result =
#5 0x7f3d564975bb in QEventLoop::exec (this=this@entry=0x7f3d4ec2dd70,
flags=..., flags@entry=...) at
../../include/QtCore/../../src/corelib/global/qflags.h:140
d = 0x7f3d40003800
locker = {val = 94103253173360}
ref = {d = 0x7f3d40003800, locker = @0x7f3d4ec2dcf8, exceptionCaught =
true}
app =
#6 0x7f3d562e22c6 in QThread::exec (this=this@entry=0x7f3d55ac2d80
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
../../include/QtCore/../../src/corelib/global/qflags.h:120
d = 0x55961efa4400
locker = {val = 94103253173360}
eventLoop = { = {_vptr.QObject = 0x7f3d567453c8 , static staticMetaObject = {d = {superdata = 0x0, stringdata =
0x7f3d566370c0 , data = 0x7f3d56636fa0
, static_metacall = 0x7f3d564c9470
,
relatedMetaObjects = 0x0, extradata = 0x0}}, d_ptr = {d = 0x7f3d40003800},
static staticQtMetaObject = {d = {superdata = 0x0, stringdata = 0x7f3d56639fe0
, data = 0x7f3d566371e0 ,
static_metacall = 0x0, relatedMetaObjects = 0x0, extradata = 0x0}}}, static
staticMetaObject = {d = {superdata = 0x7f3d5673d980
, stringdata = 0x7f3d56631ae0
, data = 0x7f3d56631a80
, static_metacall = 0x7f3d564972e0
,
relatedMetaObjects = 0x0, extradata = 0x0}}}
returnCode =
#7 0x7f3d55a42565 in QDBusConnectionManager::run (this=0x7f3d55ac2d80
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
qdbusconnection.cpp:178
locker =
#8 0x7f3d562e3612 in QThreadPrivate::start (arg=0x7f3d55ac2d80
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
thread/qthread_unix.cpp:361
thr = 0x7f3d55ac2d80 <(anonymous
namespace)::Q_QGS__q_manager::innerFunction()::holder>
data =
__clframe = {__cancel_routine = 0x7f3d562e2b40
, __cancel_arg = 0x7f3d55ac2d80 <(anonymous
namespace)::Q_QGS__q_manager::innerFunction()::holder>, __do_it = 1,
__cancel_type = }
#9 0x7f3d54f31182 in start_thread (arg=) at
pthread_create.c:486
ret =
pd =
now =
unwind_buf = {cancel_jmp_buf = {{jmp_buf = {139901291128576,
-3784097251147283699, 140721178987678, 140721178987679, 140721178987888,
139901291126528, 3820937170979750669, 3820889216029131533}, mask_was_saved =
0}}, priv = {pad = {0x0, 0x0, 0x0, 0x0}, data = {prev = 0x0, cleanup = 0x0,
canceltype = 0}}}
not_first_call =
#10 0x7f3d57c45b1f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95
No locals.
.
Thread 1 (Thread 0x7f3d517bcd80 (LWP 2236)):
#0 __GI_raise (sig=) at ../sysdeps/unix/sysv/linux/raise.c:50
set = {__val = {0, 17678122487503011840, 0, 139901436319509,
139901436331328, 139901442150508, 94103259618752, 42, 42, 139901436331008,
1256, 0, 0, 0, 0, 0}}
pid =
tid =
ret =
#1 0x7f3d576a62bc in KCrash::defaultCrashHandler(int) () from
/usr/lib/x86_64-linux-gnu/libKF5Crash.so.5
No symbol table info available.
#2
No locals.
#3 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
set = {__val = {0, 0, 13827369929818582336, 0, 282042221696779236, 0,
7233170478761014387, 109330211561823, 4621304461106629456, 0,
13827369929818582336, 0, 282042221696779236, 0, 4651831386980745216, 0}}
pid =
tid =
ret =
#4 0x7f3d57b4d535 in __GI_abort () at abort.c:79
save_stage = 1
act = {__sigaction_handler = {sa_handler = 0xb, sa_sigaction = 0xb},
sa_mask = {__val = {139901443036800, 3432, 1, 139901443036931, 139901441637425,
14, 139901443036800, 10, 139901177858880, 139901426168304, 8, 139901329313632,
139901441638643, 139901329313632, 13990144158310
[konsole] [Bug 389942] konsole crash on logout
https://bugs.kde.org/show_bug.cgi?id=389942 Laurent Bonnaud changed: What|Removed |Added Version|17.12.2 |18.12.3 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kded] [Bug 407496] New: many KDE processes have rwx memory mappings
https://bugs.kde.org/show_bug.cgi?id=407496 Bug ID: 407496 Summary: many KDE processes have rwx memory mappings Product: frameworks-kded Version: 5.57.0 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: fa...@kde.org Reporter: l.bonn...@laposte.net CC: kdelibs-b...@kde.org Target Milestone: --- SUMMARY As a defense against machine code injection against buffer overflow bugs, most Linux distributions have worked over the years to remove as many rwx memory mappings as possible in processes. I checked this on several of my systems and unfortunately I found that many KDE processes do have rwx memory mappings. I chose to report this bug against the kded package because it is one of the most fundamental affected KDE process I found. However the problem seems to be more general in KDE. I apologize in advance for not finding a better software package to report this problem. STEPS TO REPRODUCE 1. Log in Plasma 2. Run the following command: $ grep rwx /proc/$(pidof kded5)/maps OBSERVED RESULT $ grep rwx /proc/$(pidof kded5)/maps 7f68d7c2a000-7f68d7c3a000 rwxp 00:00 0 EXPECTED RESULT No output SOFTWARE/OS VERSIONS Linux: KDE neon updated today KDE Plasma Version: 5.15.5+p18.04+git20190510.0013-0 KDE Frameworks Version: 5.58.0+p18.04+git20190510.1522-0 Qt Version: 5.12.0+dfsg-0+xneon+18.04+bionic+build56 ADDITIONAL INFORMATION I observe similar problems in Kubuntu. -- You are receiving this mail because: You are watching all bug changes.
[ktorrent] [Bug 396088] Assertion 'close_nointr(fd) != -EBADF' failed
https://bugs.kde.org/show_bug.cgi?id=396088 Laurent Bonnaud changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #1 from Laurent Bonnaud --- Closing since I have not seen this bug again. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 405893] baloo_file_extractor crashes in Baloo::DocTermsCodec::encode()
https://bugs.kde.org/show_bug.cgi?id=405893 Laurent Bonnaud changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #1 from Laurent Bonnaud --- The crash no longer occurs. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kconfig] [Bug 360561] KConfig warnings cannot be silenced
https://bugs.kde.org/show_bug.cgi?id=360561 --- Comment #8 from Laurent Bonnaud --- This bug still exists in Kubuntu 19.04 and this package version: Package: libkf5configcore5 Version: 5.56.0-0ubuntu1 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kconfig] [Bug 360561] KConfig warnings cannot be silenced
https://bugs.kde.org/show_bug.cgi?id=360561 Laurent Bonnaud changed: What|Removed |Added Version|5.31.0 |5.56.0 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 396204] Graphical glitches that makes the calendar unusable when compositing is disabled
https://bugs.kde.org/show_bug.cgi?id=396204 Laurent Bonnaud changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #2 from Laurent Bonnaud --- I am closing this bug that no longer occurs. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 386109] truncated panel after disconnecting an external display
https://bugs.kde.org/show_bug.cgi?id=386109 Laurent Bonnaud changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #7 from Laurent Bonnaud --- I am closing this bug since it is now fixed. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 406984] okular snap does not start because it needs Qt 5.12
https://bugs.kde.org/show_bug.cgi?id=406984 Laurent Bonnaud changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #1 from Laurent Bonnaud --- This bug is fixed in the "candidate" okular version: $ snap info okular [...] candidate: 19.04.12019-05-09 (60) 20MB - -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 389942] konsole crash on logout
https://bugs.kde.org/show_bug.cgi?id=389942 Laurent Bonnaud changed: What|Removed |Added Version|18.12.3 |19.04.2 --- Comment #19 from Laurent Bonnaud --- I upgraded my Ubuntu 19.04 system with KDE backports and still saw a konsole crash on logout with the following versions: konsole 19.04.2-0ubuntu1~ubuntu19.04~ppa1 KF5 5.59.0-0ubuntu1~ubuntu19.04~ppa2 Qt 5.12.2+dfsg-2ubuntu1 -- You are receiving this mail because: You are watching all bug changes.
[kdesrc-build] [Bug 409198] kdesrc-build does not know to which module qca belongs
https://bugs.kde.org/show_bug.cgi?id=409198 Laurent Bonnaud changed: What|Removed |Added Summary|kdesrc-build does not know |kdesrc-build does not know |to which module gca belongs |to which module qca belongs -- You are receiving this mail because: You are watching all bug changes.
[kdesrc-build] [Bug 409198] New: kdesrc-build does not know to which module gca belongs
https://bugs.kde.org/show_bug.cgi?id=409198 Bug ID: 409198 Summary: kdesrc-build does not know to which module gca belongs Product: kdesrc-build Version: Git Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: mp...@kde.org Reporter: l.bonn...@laposte.net Target Milestone: --- STEPS TO REPRODUCE 1. run ./kdesrc-build OBSERVED RESULT [...] Building qca from (126/351) EXPECTED RESULT A module name should be displayed SOFTWARE/OS VERSIONS Linux/KDE Plasma: Ubuntu 19.04 Qt Version: 5.12.2 -- You are receiving this mail because: You are watching all bug changes.
[kdesrc-build] [Bug 409198] kdesrc-build does not know to which module qca belongs
https://bugs.kde.org/show_bug.cgi?id=409198 --- Comment #2 from Laurent Bonnaud --- Thanks *you* for the fix! -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 389942] konsole crash on logout
https://bugs.kde.org/show_bug.cgi?id=389942
--- Comment #20 from Laurent Bonnaud ---
And here a backtrace with those versions. The crash seems to be from an
unhandled exception in QHashData::detach_helper():
Stacktrace:
#0 __GI_raise (sig=) at ../sysdeps/unix/sysv/linux/raise.c:50
set = {__val = {0, 4761159347100344576, 0, 139842019272469,
139842019284288, 139842025181292, 94380020655792, 42, 42, 139842019283968,
1256, 0, 0, 0, 0, 0}}
pid =
tid =
ret =
#1 0x7f2f81e232bc in KCrash::defaultCrashHandler(int) () from
/usr/lib/x86_64-linux-gnu/libKF5Crash.so.5
No symbol table info available.
#2
No locals.
#3 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
set = {__val = {0, 0, 282042221696779236, 0, 0, 3472332698304410724,
7233170478761014387, 109330211561823, 4620940544017971324, 0,
4651831386980745216, 0, 4651831386980745216, 0, 4621304461106629456, 0}}
pid =
tid =
ret =
#4 0x7f2f822dd535 in __GI_abort () at abort.c:79
save_stage = 1
act = {__sigaction_handler = {sa_handler = 0xb, sa_sigaction = 0xb},
sa_mask = {__val = {139842026067584, 3432, 1, 139842026067715, 139842024668209,
14, 139842026067584, 10, 94380019967200, 139842009092592, 8, 139841912201056,
139842024669427, 139841912201056, 139842024613887, 139842026068032}}, sa_flags
= -2138708656, sa_restorer = 0x7f2f8249d840 }
sigs = {__val = {32, 0 }}
#5 0x7f2f80853672 in __gnu_cxx::__verbose_terminate_handler () at
../../../../src/libstdc++-v3/libsupc++/vterminate.cc:95
terminating = true
t =
#6 0x7f2f8085f2b6 in __cxxabiv1::__terminate (handler=) at
../../../../src/libstdc++-v3/libsupc++/eh_terminate.cc:47
No locals.
#7 0x7f2f8085f301 in std::terminate () at
../../../../src/libstdc++-v3/libsupc++/eh_terminate.cc:57
No locals.
#8 0x7f2f8085f589 in __cxxabiv1::__cxa_rethrow () at
../../../../src/libstdc++-v3/libsupc++/eh_throw.cc:133
globals =
header =
#9 0x7f2f80a244d3 in QHashData::detach_helper (this=0x55d68f6e4360,
node_duplicate=node_duplicate@entry=0x7f2f7b805f60 ::duplicateNode(QHashData::Node*, void*)>,
node_delete=node_delete@entry=0x7f2f7b805f50 ::deleteNode2(QHashData::Node*)>,
nodeSize=nodeSize@entry=24, nodeAlign=nodeAlign@entry=8) at tools/qhash.cpp:525
this_e =
d =
e =
#10 0x7f2f7b800faa in QHash::detach_helper (this=) at
../../../../include/QtCore/../../src/corelib/tools/qhash.h:597
x =
#11 0x7f2f7b806461 in QHash::detach (this=0x55d68f3c1588) at
../../../../include/QtCore/../../src/corelib/tools/qrefcount.h:102
No locals.
#12 QHash::remove
(this=0x55d68f3c1588, akey=@0x7ffe670adefc: 85986414,
akey@entry=@0x7ffe670adefc: ) at
../../../../include/QtCore/../../src/corelib/tools/qhash.h:803
oldSize =
node =
#13 0x7f2f7b8044c9 in QXcbConnection::removeWindowEventListener
(this=, id=) at qxcbconnection.cpp:179
No locals.
#14 0x7f2f7b817554 in QXcbWindow::destroy (this=this@entry=0x55d68f9250e0)
at qxcbobject.h:53
No locals.
#15 0x7f2f7b817641 in QXcbWindow::~QXcbWindow (this=0x55d68f9250e0,
__in_chrg=) at qxcbwindow.cpp:537
No locals.
#16 0x7f2f7a2229ad in QXcbGlxWindow::~QXcbGlxWindow (this=0x55d68f9250e0,
__in_chrg=) at qxcbglxwindow.cpp:53
No locals.
#17 QXcbGlxWindow::~QXcbGlxWindow (this=0x55d68f9250e0, __in_chrg=) at qxcbglxwindow.cpp:55
No locals.
#18 0x7f2f80fef1a7 in QWindowPrivate::destroy (this=0x55d68f707c70) at
kernel/qwindow.cpp:1908
q = 0x55d68f9811b0
e = { = {_vptr.QEvent = 0x7f2f8145c2e0 , static staticMetaObject = {d = {superdata = 0x0,
stringdata = 0x7f2f80da89e0 , data = 0x7f2f80da8420
, static_metacall = 0x0, relatedMetaObjects = 0x0,
extradata = 0x0}}, d = 0x0, t = 217, posted = 0, spont = 0, m_accept = 1,
reserved = 3712}, m_surfaceEventType =
QPlatformSurfaceEvent::SurfaceAboutToBeDestroyed}
childrenWindows = {> = {}, {p = {static shared_null = {ref = {atomic = {_q_value =
{> = {static _S_alignment = 4, _M_i = -1}, static
is_always_lock_free = true}}}, alloc = 0, begin = 0, end = 0, array = {0x0}}, d
= 0x7f2f80ce66e0 }, d = 0x7f2f80ce66e0
}}
wasVisible =
pw =
q =
childrenWindows =
wasVisible =
e =
pw =
i =
object =
w =
i =
#19 QWindowPrivate::destroy (this=0x55d68f707c70) at kernel/qwindow.cpp:1860
q =
childrenWindows =
wasVisible =
e =
pw =
i =
object =
w =
i =
#20 0x7f2f81605304 in QWidgetPrivate::deleteTLSysExtra
(this=0x55d68f80cb30) at kernel/qwidget.cpp:1896
No locals.
#21 QWidgetPrivate::deleteTLSysExtra (this=0x55d68f80cb30) at
kernel/qwidget.cpp:1876
No locals.
#22 0x7f2f81609db8 in QWidget::destroy (this=this@entry=0x55d68f796e10,
d
[neon] [Bug 406984] New: okular snap does not start because it needs Qt 5.12
https://bugs.kde.org/show_bug.cgi?id=406984 Bug ID: 406984 Summary: okular snap does not start because it needs Qt 5.12 Product: neon Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Snaps Assignee: neon-b...@kde.org Reporter: l.bonn...@laposte.net CC: neon-b...@kde.org Target Milestone: --- SUMMARY okular snap does not start because it needs Qt 5.12 STEPS TO REPRODUCE 1. run /snap/bin/okular OBSERVED RESULT $ /snap/bin/okular utils.go:684: cannot change mount namespace of snap "okular" according to change mount (/snap/kde-frameworks-5-core18/29 /snap/okular/52/kf5-2 none bind,ro 0 0): permission denied /bin/bash: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF-8) okular: /snap/okular/52/kf5/usr/lib/x86_64-linux-gnu/libQt5Core.so.5: version `Qt_5.12' not found (required by okular) EXPECTED RESULT okular does start SOFTWARE/OS VERSIONS Linux/KDE Plasma: Ubuntu 19.04 KDE Plasma Version: KDE Frameworks Version: Qt Version: $ snap list | grep kde-framework kde-frameworks-5 5.47.0 27stable kde* - kde-frameworks-5-core18 5.56.0 29stable kde* - ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 407291] New: kglobalaccel5 crashes every time on logout
https://bugs.kde.org/show_bug.cgi?id=407291 Bug ID: 407291 Summary: kglobalaccel5 crashes every time on logout Product: frameworks-kglobalaccel Version: 5.56.0 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: kdelibs-b...@kde.org Reporter: l.bonn...@laposte.net Target Milestone: --- SUMMARY Each time I logout kglobalaccel5 crashes. STEPS TO REPRODUCE 1. log in Plasma 2. log out OBSERVED RESULT A crash file is created in /var/crash/ : -rw-r- 1 bonnaudl whoopsie 783428 05-07 14:18 /var/crash/_usr_bin_kglobalaccel5.1000.crash EXPECTED RESULT No crash SOFTWARE/OS VERSIONS Linux: Ubuntu 19.04 KDE Plasma Version: 4:5.15.4-0ubuntu1 KDE Frameworks Version: 5.56.0-0ubuntu1 Qt Version: 5.12.2+dfsg-2ubuntu1 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 406426] kglobalaccel5 crashes often
https://bugs.kde.org/show_bug.cgi?id=406426 Laurent Bonnaud changed: What|Removed |Added CC||l.bonn...@laposte.net -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 407291] kglobalaccel5 crashes every time on logout
https://bugs.kde.org/show_bug.cgi?id=407291 Laurent Bonnaud changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Laurent Bonnaud --- *** This bug has been marked as a duplicate of bug 406426 *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 406426] kglobalaccel5 crashes often
https://bugs.kde.org/show_bug.cgi?id=406426 --- Comment #32 from Laurent Bonnaud --- *** Bug 407291 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 389942] konsole crash on logout
https://bugs.kde.org/show_bug.cgi?id=389942 --- Comment #14 from Laurent Bonnaud --- Created attachment 118804 --> https://bugs.kde.org/attachment.cgi?id=118804&action=edit Backtrace #2 I got a different backtrace in Qt C++ destructors. Version info: konsole: 4:18.04.3-0ubuntu1 KF5: 5.54.0-0ubuntu1~ubuntu18.10~ppa1 Qt: 5.11.1+dfsg-7ubuntu3 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 405893] New: baloo crash during initial indexing of my homedir
https://bugs.kde.org/show_bug.cgi?id=405893 Bug ID: 405893 Summary: baloo crash during initial indexing of my homedir Product: frameworks-baloo Version: 5.56.0 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: Baloo File Daemon Assignee: baloo-bugs-n...@kde.org Reporter: l.bonn...@laposte.net Target Milestone: --- Application: baloo_file (5.56.0) Qt Version: 5.11.3 Frameworks Version: 5.56.0 Operating System: Linux 5.0.4-050004-generic x86_64 Distribution: Ubuntu Disco Dingo (development branch) -- Information about the crash: - What I was doing when the application crashed: I deleted all baloo files/directories in my homedir (for a clean re-indexing) and logged in. Running "balooctl start" also crashes immediately. The crash can be reproduced every time. -- Backtrace: Application: Baloo File Indexing Daemon (baloo_file), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f1a14a13f80 (LWP 14035))] Thread 3 (Thread 0x7f1a1397e700 (LWP 14038)): [KCrash Handler] #6 0x7f1a18e7485a in QByteArray::append (this=this@entry=0x7f1a1397da48, ba=...) at /usr/include/c++/8/bits/atomic_base.h:390 #7 0x7f1a193cc11a in Baloo::DocTermsCodec::encode (this=this@entry=0x7f1a1397da47, terms=...) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qarraydata.h:213 #8 0x7f1a193a3d28 in Baloo::DocumentDB::put (this=this@entry=0x7f1a1397db10, docId=, docId@entry=114349209288731, list=...) at ./src/engine/documentdb.cpp:71 #9 0x7f1a193c815b in Baloo::WriteTransaction::addDocument (this=0x7eda04004de0, doc=...) at ./src/engine/writetransaction.cpp:62 #10 0x7f1a193c0a39 in Baloo::Transaction::addDocument (this=this@entry=0x7f1a1397dc50, doc=...) at ./src/engine/transaction.cpp:233 #11 0x55df300acf76 in Baloo::FirstRunIndexer::run (this=0x55df31a32d40) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qrefcount.h:60 #12 0x7f1a18e68f91 in QThreadPoolThread::run (this=0x55df31a8b820) at thread/qthreadpool.cpp:101 #13 0x7f1a18e70c77 in QThreadPrivate::start (arg=0x55df31a8b820) at thread/qthread_unix.cpp:367 #14 0x7f1a179c3182 in start_thread (arg=) at pthread_create.c:486 #15 0x7f1a189b1faf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7f1a144a1700 (LWP 14037)): #0 0x7f1a189a5ba9 in __GI___poll (fds=0x7f1a0c005260, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f1a170ffcb6 in g_main_context_poll (priority=, n_fds=1, fds=0x7f1a0c005260, timeout=, context=0x7f1a0c000bf0) at ../../../glib/gmain.c:4228 #2 g_main_context_iterate (context=context@entry=0x7f1a0c000bf0, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ../../../glib/gmain.c:3922 #3 0x7f1a170ffddc in g_main_context_iteration (context=0x7f1a0c000bf0, may_block=may_block@entry=1) at ../../../glib/gmain.c:3988 #4 0x7f1a1906b04b in QEventDispatcherGlib::processEvents (this=0x7f1a0c000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #5 0x7f1a1901814b in QEventLoop::exec (this=this@entry=0x7f1a144a0d70, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:140 #6 0x7f1a18e670d6 in QThread::exec (this=this@entry=0x7f1a19466d60 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at ../../include/QtCore/../../src/corelib/global/qflags.h:120 #7 0x7f1a193ec545 in QDBusConnectionManager::run (this=0x7f1a19466d60 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at qdbusconnection.cpp:178 #8 0x7f1a18e70c77 in QThreadPrivate::start (arg=0x7f1a19466d60 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread_unix.cpp:367 #9 0x7f1a179c3182 in start_thread (arg=) at pthread_create.c:486 #10 0x7f1a189b1faf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 1 (Thread 0x7f1a14a13f80 (LWP 14035)): #0 0x7f1a189a5ba9 in __GI___poll (fds=0x55df319e6d10, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f1a170ffcb6 in g_main_context_poll (priority=, n_fds=1, fds=0x55df319e6d10, timeout=, context=0x55df319cf4d0) at ../../../glib/gmain.c:4228 #2 g_main_context_iterate (context=context@entry=0x55df319cf4d0, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ../../../glib/gmain.c:3922 #3 0x7f1a170ffddc in g_main_context_iteration (context=0x55df319cf4d0, may_block=may_block@entry=1) at ../../../glib/gmain.c:3988 #4 0x7f1a1906b04b in QEventDispatcherGlib::processEvents (this=0x55df319ceb40, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #5 0x7f1a1901814b in QEventLoop::exec (this=this@entry=0x7ffeea6a3e40, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:140 #6 0x7f1a1
[kio-extras] [Bug 414905] New: crash while creating a thumbnail for some specific EPS file
https://bugs.kde.org/show_bug.cgi?id=414905 Bug ID: 414905 Summary: crash while creating a thumbnail for some specific EPS file Product: kio-extras Version: 19.08.1 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: Thumbnails and previews Assignee: plasma-b...@kde.org Reporter: l.bonn...@laposte.net Target Milestone: --- SUMMARY KDE's thumnailer crashes in GSCreator::create() STEPS TO REPRODUCE 1. put the attached file in a directory 2. view this directory with dolphin OBSERVED RESULT crash EXPECTED RESULT no crash SOFTWARE/OS VERSIONS KDE Plasma Version: 5.17.4 KDE Frameworks Version: 5.64 kio-extra: 19.08.3 Qt Version: 5.12.4 ADDITIONAL INFORMATION Application: kdeinit5 (kdeinit5), signal: Floating point exception Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f19f67cf480 (LWP 9827))] Thread 3 (Thread 0x7f19ebd13700 (LWP 9830)): #0 0x7f19f9a74c2f in __GI___poll (fds=0x7f19e00029e0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f19f8687a3e in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f19f8687b73 in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f19f9e2d6c3 in QEventDispatcherGlib::processEvents (this=0x7f19eb60, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #4 0x7f19f9dd463b in QEventLoop::exec (this=this@entry=0x7f19ebd12df0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:140 #5 0x7f19f9c0da75 in QThread::exec (this=this@entry=0x7f19f5d26d80 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at ../../include/QtCore/../../src/corelib/global/qflags.h:120 #6 0x7f19f5ca3efa in QDBusConnectionManager::run (this=0x7f19f5d26d80 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at qdbusconnection.cpp:178 #7 0x7f19f9c0ecc2 in QThreadPrivate::start (arg=0x7f19f5d26d80 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread_unix.cpp:361 #8 0x7f19f8fef669 in start_thread (arg=) at pthread_create.c:479 #9 0x7f19f9a81323 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7f19f1a27700 (LWP 9829)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x55a7e5d2c498) at ../sysdeps/unix/sysv/linux/futex-internal.h:80 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x55a7e5d2c448, cond=0x55a7e5d2c470) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x55a7e5d2c470, mutex=0x55a7e5d2c448) at pthread_cond_wait.c:638 #3 0x7f19f20f497b in cnd_wait (mtx=0x55a7e5d2c448, cond=0x55a7e5d2c470) at ../include/c11/threads_posix.h:155 #4 util_queue_thread_func (input=input@entry=0x55a7e5ba40f0) at ../src/util/u_queue.c:258 #5 0x7f19f20f459b in impl_thrd_routine (p=) at ../include/c11/threads_posix.h:87 #6 0x7f19f8fef669 in start_thread (arg=) at pthread_create.c:479 #7 0x7f19f9a81323 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 1 (Thread 0x7f19f67cf480 (LWP 9827)): [KCrash Handler] #6 0x7f19ea1aa1f0 in GSCreator::create (this=, path=..., width=128, height=128, img=...) at ./ps/gscreator.cpp:281 #7 0x7f19fa8f684d in ThumbnailProtocol::createSubThumbnail (this=this@entry=0x7ffeabf088f0, thumbnail=..., filePath=..., segmentWidth=segmentWidth@entry=108, segmentHeight=segmentHeight@entry=68) at ./thumbnail/thumbnail.cpp:727 #8 0x7f19fa8f6e6a in ThumbnailProtocol::drawSubThumbnail (this=this@entry=0x7ffeabf088f0, p=..., filePath=..., width=width@entry=108, height=height@entry=68, xPos=xPos@entry=19, yPos=76, frameWidth=3) at ./thumbnail/thumbnail.cpp:759 #9 0x7f19fa8f74cf in ThumbnailProtocol::thumbForDirectory (this=this@entry=0x7ffeabf088f0, directory=...) at ./thumbnail/thumbnail.cpp:562 #10 0x7f19fa8f8bc2 in ThumbnailProtocol::get (this=0x7ffeabf088f0, url=...) at ./thumbnail/thumbnail.cpp:238 #11 0x7f19f6136bc6 in KIO::SlaveBase::dispatch(int, QByteArray const&) () from /usr/lib/x86_64-linux-gnu/libKF5KIOCore.so.5 #12 0x7f19f6137266 in KIO::SlaveBase::dispatchLoop() () from /usr/lib/x86_64-linux-gnu/libKF5KIOCore.so.5 #13 0x7f19fa8f5b72 in kdemain (argc=, argv=0x55a7e5b03f10) at ./thumbnail/thumbnail.cpp:138 #14 0x55a7e445a77d in ?? () #15 0x55a7e445b86a in ?? () #16 0x55a7e445c25a in ?? () #17 0x55a7e445712f in ?? () #18 0x7f19f99861e3 in __libc_start_main (main=0x55a7e4456750, argc=5, argv=0x7ffeabf090e8, init=, fini=, rtld_fini=, stack_end=0x7ffeabf090d8) at ../csu/libc-start.c:308 #19 0x55a7e4457d9e in ?? () [Inferior 1 (process 9827) detached] -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 414905] crash while creating a thumbnail for some specific EPS file
https://bugs.kde.org/show_bug.cgi?id=414905 --- Comment #1 from Laurent Bonnaud --- Created attachment 124345 --> https://bugs.kde.org/attachment.cgi?id=124345&action=edit File to reproduce the crash -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 406463] PostScript thumbnailer crashes with floating point exception
https://bugs.kde.org/show_bug.cgi?id=406463 Laurent Bonnaud changed: What|Removed |Added Version|18.12.3 |19.08.1 -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 406463] PostScript thumbnailer crashes with floating point exception
https://bugs.kde.org/show_bug.cgi?id=406463 --- Comment #6 from Laurent Bonnaud --- Created attachment 124525 --> https://bugs.kde.org/attachment.cgi?id=124525&action=edit File to reproduce the crash -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 415445] New: crash while trying to connect to a Wifi network
https://bugs.kde.org/show_bug.cgi?id=415445 Bug ID: 415445 Summary: crash while trying to connect to a Wifi network Product: plasmashell Version: 5.17.4 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: l.bonn...@laposte.net CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.17.4) Qt Version: 5.12.4 Frameworks Version: 5.65.0 Operating System: Linux 5.4.5-050405-generic x86_64 Distribution: Ubuntu 19.10 -- Information about the crash: - What I was doing when the application crashed: I was trying to connect to a Wifi network. I cannot tell precisely which action caused the crash because error reporting is asynchronous. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". futex_wait_cancelable (private=, expected=0, futex_word=0x559a9c0f5484) at ../sysdeps/unix/sysv/linux/futex-internal.h:80 [Current thread is 1 (Thread 0x7fee76f16100 (LWP 2559))] Thread 12 (Thread 0x7fee3e800700 (LWP 1418)): #0 0x7fee57cbf95d in pa_read () at /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-13.0.so #1 0x7fee57d47406 in pa_mainloop_prepare () at /usr/lib/x86_64-linux-gnu/libpulse.so.0 #2 0x7fee57d47ea4 in pa_mainloop_iterate () at /usr/lib/x86_64-linux-gnu/libpulse.so.0 #3 0x7fee57d47f60 in pa_mainloop_run () at /usr/lib/x86_64-linux-gnu/libpulse.so.0 #4 0x7fee57d5610d in () at /usr/lib/x86_64-linux-gnu/libpulse.so.0 #5 0x7fee57cee37c in () at /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-13.0.so #6 0x7fee79edc669 in start_thread (arg=) at pthread_create.c:479 #7 0x7fee7a6b7323 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 11 (Thread 0x7fee3f28a700 (LWP 1385)): #0 0x7fee79ee32c6 in futex_wait_cancelable (private=, expected=0, futex_word=0x559a9a21e490) at ../sysdeps/unix/sysv/linux/futex-internal.h:80 #1 0x7fee79ee32c6 in __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x559a9a21e440, cond=0x559a9a21e468) at pthread_cond_wait.c:508 #2 0x7fee79ee32c6 in __pthread_cond_wait (cond=0x559a9a21e468, mutex=0x559a9a21e440) at pthread_cond_wait.c:638 #3 0x7fee7aa3adef in QWaitConditionPrivate::wait(QDeadlineTimer) (deadline=..., this=0x559a9a21e440) at thread/qwaitcondition_unix.cpp:146 #4 0x7fee7aa3adef in QWaitCondition::wait(QMutex*, QDeadlineTimer) (this=, mutex=0x7fee70013e50, deadline=...) at thread/qwaitcondition_unix.cpp:225 #5 0x7fee7aa3aee1 in QWaitCondition::wait(QMutex*, unsigned long) (this=this@entry=0x7fee70013e58, mutex=mutex@entry=0x7fee70013e50, time=time@entry=18446744073709551615) at ../../include/QtCore/../../src/corelib/kernel/qdeadlinetimer.h:68 #6 0x7fee7c6f17b9 in QSGRenderThreadEventQueue::takeEvent(bool) (wait=true, this=0x7fee70013e48) at scenegraph/qsgthreadedrenderloop.cpp:245 #7 0x7fee7c6f17b9 in QSGRenderThread::processEventsAndWaitForMore() (this=this@entry=0x7fee70013dd0) at scenegraph/qsgthreadedrenderloop.cpp:710 #8 0x7fee7c6f1a1a in QSGRenderThread::run() (this=0x7fee70013dd0) at scenegraph/qsgthreadedrenderloop.cpp:739 #9 0x7fee7aa34cc2 in QThreadPrivate::start(void*) (arg=0x7fee70013dd0) at thread/qthread_unix.cpp:361 #10 0x7fee79edc669 in start_thread (arg=) at pthread_create.c:479 #11 0x7fee7a6b7323 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 10 (Thread 0x7fee54b5e700 (LWP 5271)): [KCrash Handler] #6 0x7fee6cb72128 in PlotSGNode::bind() (this=0x7575757575757575) at ./src/qmlcontrols/kquickcontrolsaddons/plotter.cpp:692 #7 0x7fee6cb72128 in Plotter::render() (this=0x7fee68101d90) at ./src/qmlcontrols/kquickcontrolsaddons/plotter.cpp:692 #8 0x7fee7ac275c8 in QtPrivate::QSlotObjectBase::call(QObject*, void**) (a=0x7fee54b5dc00, r=0x7fee68101d90, this=0x7fee44262ab0) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:394 #9 0x7fee7ac275c8 in QMetaObject::activate(QObject*, int, int, void**) (sender=0x559a99dda400, signalOffset=, local_signal_index=, argv=) at kernel/qobject.cpp:3781 #10 0x7fee7c746ba4 in QQuickWindowPrivate::renderSceneGraph(QSize const&) (this=this@entry=0x559a99e4be30, size=...) at items/qquickwindow.cpp:462 #11 0x7fee7c6edc68 in QSGRenderThread::syncAndRender() (this=this@entry=0x7fee7000f750) at scenegraph/qsgthreadedrenderloop.cpp:646 #12 0x7fee7c6f19d8 in QSGRenderThread::run() (this=0x7fee7000f750) at scenegraph/qsgthreadedrenderloop.cpp:730 #13 0x7fee7aa34cc2 in QThreadPrivate::start(void*) (arg=0x7fee7000f750) at thread/qthread_unix.cpp:361 #14 0x7fee79edc669 in start_thread (arg=) at pthread_create.c:479 #15 0x7fee7a6b7323 in clone () at ../sysdeps/unix
[frameworks-solid] [Bug 415474] New: Crash while closing the "Energy Information" window
https://bugs.kde.org/show_bug.cgi?id=415474 Bug ID: 415474 Summary: Crash while closing the "Energy Information" window Product: frameworks-solid Version: 5.65.0 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: lu...@kde.org Reporter: l.bonn...@laposte.net CC: kdelibs-b...@kde.org Target Milestone: --- STEPS TO REPRODUCE 1. right clic on the battery mini icon 2. clic on "Show Energy Information" 2. close the "Energy Information" window OBSERVED RESULT The crash can be reproduced every time. EXPECTED RESULT No crash. SOFTWARE/OS VERSIONS Linux: Ubuntu 19.10, kernel 5.4.6 KDE Plasma Version: 5.17.4 KDE Frameworks Version: 5.65 Qt Version: 5.12.4 ADDITIONAL INFORMATION -- Backtrace: Application: System Settings Module (kcmshell5), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f02444f2c80 (LWP 24422))] Thread 4 (Thread 0x7f0231923700 (LWP 24427)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x565480caf18c) at ../sysdeps/unix/sysv/linux/futex-internal.h:80 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x565480caf138, cond=0x565480caf160) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x565480caf160, mutex=0x565480caf138) at pthread_cond_wait.c:638 #3 0x7f0231ff097b in cnd_wait (mtx=0x565480caf138, cond=0x565480caf160) at ../include/c11/threads_posix.h:155 #4 util_queue_thread_func (input=input@entry=0x565480cb15f0) at ../src/util/u_queue.c:258 #5 0x7f0231ff059b in impl_thrd_routine (p=) at ../include/c11/threads_posix.h:87 #6 0x7f02476dc669 in start_thread (arg=) at pthread_create.c:479 #7 0x7f0249fa4323 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7f02424f2700 (LWP 24424)): #0 __GI___libc_read (nbytes=16, buf=0x7f02424f1b60, fd=7) at ../sysdeps/unix/sysv/linux/read.c:26 #1 __GI___libc_read (fd=7, buf=buf@entry=0x7f02424f1b60, nbytes=nbytes@entry=16) at ../sysdeps/unix/sysv/linux/read.c:24 #2 0x7f0246bfb69f in read (__nbytes=16, __buf=0x7f02424f1b60, __fd=) at /usr/include/x86_64-linux-gnu/bits/unistd.h:44 #3 g_wakeup_acknowledge (wakeup=0x5654808387b0) at ../../../glib/gwakeup.c:210 #4 0x7f0246bb358e in g_main_context_check (context=context@entry=0x7f0234000c30, max_priority=2147483647, fds=fds@entry=0x7f0234012020, n_fds=n_fds@entry=1) at ../../../glib/gmain.c:3695 #5 0x7f0246bb39e2 in g_main_context_iterate (context=context@entry=0x7f0234000c30, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ../../../glib/gmain.c:3914 #6 0x7f0246bb3b73 in g_main_context_iteration (context=0x7f0234000c30, may_block=may_block@entry=1) at ../../../glib/gmain.c:3978 #7 0x7f0248a3c6c3 in QEventDispatcherGlib::processEvents (this=0x7f0234000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #8 0x7f02489e363b in QEventLoop::exec (this=this@entry=0x7f02424f1d70, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:140 #9 0x7f024881ca75 in QThread::exec (this=this@entry=0x7f0249a65d80 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at ../../include/QtCore/../../src/corelib/global/qflags.h:120 #10 0x7f02499e2efa in QDBusConnectionManager::run (this=0x7f0249a65d80 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at qdbusconnection.cpp:178 #11 0x7f024881dcc2 in QThreadPrivate::start (arg=0x7f0249a65d80 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread_unix.cpp:361 #12 0x7f02476dc669 in start_thread (arg=) at pthread_create.c:479 #13 0x7f0249fa4323 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7f0243640700 (LWP 24423)): #0 0x7f0249f97c2f in __GI___poll (fds=fds@entry=0x7f024363fca8, nfds=nfds@entry=1, timeout=timeout@entry=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f02473bf917 in poll (__timeout=-1, __nfds=1, __fds=0x7f024363fca8) at /usr/include/x86_64-linux-gnu/bits/poll2.h:46 #2 _xcb_conn_wait (c=c@entry=0x5654807742c0, cond=cond@entry=0x565480774300, vector=vector@entry=0x0, count=count@entry=0x0) at ../../src/xcb_conn.c:479 #3 0x7f02473c153a in xcb_wait_for_event (c=c@entry=0x5654807742c0) at ../../src/xcb_in.c:697 #4 0x7f0243df9288 in QXcbEventQueue::run (this=0x565480780720) at qxcbeventqueue.cpp:228 #5 0x7f024881dcc2 in QThreadPrivate::start (arg=0x565480780720) at thread/qthread_unix.cpp:361 #6 0x7f02476dc669 in start_thread (arg=) at pthread_create.c:479 #7 0x7f0249fa4323 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 1 (Thread 0x7f02444f2c80 (LWP 24422)): [KCrash Handler] #6 QPointer::data (this=0x28) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qpointer
[kio-extras] [Bug 406463] PostScript thumbnailer crashes with floating point exception
https://bugs.kde.org/show_bug.cgi?id=406463 --- Comment #9 from Laurent Bonnaud --- Thanks a lot for the fix! -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 411402] Ktorrent Snap crashes on start because it needs Qt 5.12
https://bugs.kde.org/show_bug.cgi?id=411402 Laurent Bonnaud changed: What|Removed |Added CC||l.bonn...@laposte.net -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 411402] Ktorrent Snap crashes on start because it needs Qt 5.12
https://bugs.kde.org/show_bug.cgi?id=411402 --- Comment #2 from Laurent Bonnaud --- With this ktorrent snap version: $ snap info ktorrent [...] installed: 5.1.2(7) 10MB - error messages are slightly different: $ /snap/bin/ktorrent /bin/bash: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF-8) ktorrent: /snap/ktorrent/7/kf5/usr/lib/x86_64-linux-gnu/libQt5Core.so.5: version `Qt_5.14' not found (required by ktorrent) ktorrent: /snap/ktorrent/7/kf5/usr/lib/x86_64-linux-gnu/libQt5Core.so.5: version `Qt_5.14' not found (required by /snap/ktorrent/7/usr/lib/x86_64-linux-gnu/libktcore.so.16) ktorrent: /snap/ktorrent/7/kf5/usr/lib/x86_64-linux-gnu/libQt5Core.so.5: version `Qt_5.12' not found (required by /snap/ktorrent/7/usr/lib/x86_64-linux-gnu/libKF5Torrent.so.6) ktorrent: /snap/ktorrent/7/kf5/usr/lib/x86_64-linux-gnu/libQt5Core.so.5: version `Qt_5.14' not found (required by /snap/ktorrent/7/usr/lib/x86_64-linux-gnu/libqca-qt5.so.2) -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 419181] New: okular could use more hardening
https://bugs.kde.org/show_bug.cgi?id=419181 Bug ID: 419181 Summary: okular could use more hardening Product: neon Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Snaps Assignee: neon-b...@kde.org Reporter: l.bonn...@laposte.net CC: neon-b...@kde.org Target Milestone: --- Hi, could you please enable more hardening when compiling okular? STEPS TO REPRODUCE 1. snap install okular 2. hardening-check /snap/okular/current/usr/bin/okular OBSERVED RESULT /snap/okular/current/usr/bin/okular: Position Independent Executable: yes Stack protected: yes Fortify Source functions: no, only unprotected functions found! Read-only relocations: yes Immediate binding: yes Stack clash protection: unknown, no -fstack-clash-protection instructions found Control flow integrity: unknown, no -fcf-protection instructions found! EXPECTED RESULT Stack clash protection and Control flow integrity enabled in okular. SOFTWARE/OS VERSIONS irrelevent -- You are receiving this mail because: You are watching all bug changes.
[ktorrent] [Bug 396088] New: Assertion 'close_nointr(fd) != -EBADF' failed
https://bugs.kde.org/show_bug.cgi?id=396088 Bug ID: 396088 Summary: Assertion 'close_nointr(fd) != -EBADF' failed Product: ktorrent Version: 5.1 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: joris.guis...@gmail.com Reporter: l.bonn...@laposte.net Target Milestone: --- Hi, after several days of uptime, ktorrent often stops with the following assertion failure: Assertion 'close_nointr(fd) != -EBADF' failed at ../src/basic/fd-util.c:81, function safe_close(). Aborting. Steps to reproduce: 1. download the ubuntu-18.04-desktop-amd64.iso torrent 2. leave ktorrent running to seed this torrent 3. wait for several days Version info: Ubuntu 18.04 ktorrent 5.1.0 KF5 5.47 Qt 5.9.5 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 396204] New: Graphical glitches that makes the calendar unusable when compositing is disabled
https://bugs.kde.org/show_bug.cgi?id=396204 Bug ID: 396204 Summary: Graphical glitches that makes the calendar unusable when compositing is disabled Product: plasmashell Version: 5.12.6 Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: l.bonn...@laposte.net CC: plasma-b...@kde.org Target Milestone: 1.0 Version info: - Ubuntu 18.04 - Plasma 5.12.6 - KF5 5.47 - CPU/GPU: Core i7-2640M - Mesa 18.1.3 from x-swat PPA Steps to reproduce: 1. start Plasma with compositing disabled and focus follows mouse setting 2. open a Konsole window in the lower right part of the desktop, just above the clock 3. click on the clock and try to reach the calendar What happens: - a thin stripe of white from Konsole remains around the calendar - trying to reach the calendar causes the mouse to cross this stripe, the focus to change to the Konsole, and the calendar closes - enabling compositing instantly fixes the problem (but causes other and worse graphical glitches) - closing the Konsole hides the focus problem, but the missing stripe still appears This bug also happened with previous versions of Ubuntu, Plasma, KF5 and Mesa. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 396204] Graphical glitches that makes the calendar unusable when compositing is disabled
https://bugs.kde.org/show_bug.cgi?id=396204 --- Comment #1 from Laurent Bonnaud --- Created attachment 113779 --> https://bugs.kde.org/attachment.cgi?id=113779&action=edit video capture Here is a video capture that should help to see the problem. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361521] Numerous deleted DRM mmaped objects
https://bugs.kde.org/show_bug.cgi?id=361521 Laurent Bonnaud changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED -- You are receiving this mail because: You are watching all bug changes.
