[kde] [Bug 372880] New: Crash on baloo
https://bugs.kde.org/show_bug.cgi?id=372880 Bug ID: 372880 Summary: Crash on baloo Product: kde Version: unspecified Platform: unspecified OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: soler...@wonder.com.br Target Milestone: --- Application: baloo_file (5.18.0) Qt Version: 5.5.1 Operating System: Linux 4.4.0-47-generic x86_64 Distribution: Ubuntu 16.04.1 LTS -- Information about the crash: - What I was doing when the application crashed: Configuring kmail for use, nothing much special desktop. Couldn't find which file caused the problem -- 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 0x7f8a451148c0 (LWP 10950))] Thread 2 (Thread 0x7f88fa06e700 (LWP 12319)): #0 0x7f8a43230b5d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f8a4040139c in g_main_context_iterate (priority=2147483647, n_fds=1, fds=0x7f88f40418c0, timeout=, context=0x7f88f40030b0) at /build/glib2.0-7IO_Yw/glib2.0-2.48.1/./glib/gmain.c:4135 #2 0x7f8a4040139c in g_main_context_iterate (context=context@entry=0x7f88f40030b0, block=block@entry=1, dispatch=dispatch@entry=1, self=) at /build/glib2.0-7IO_Yw/glib2.0-2.48.1/./glib/gmain.c:3835 #3 0x7f8a404014ac in g_main_context_iteration (context=0x7f88f40030b0, may_block=may_block@entry=1) at /build/glib2.0-7IO_Yw/glib2.0-2.48.1/./glib/gmain.c:3901 #4 0x7f8a43e667eb in QEventDispatcherGlib::processEvents(QFlags) (this=0x7f88f4003320, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #5 0x7f8a43e0db4a in QEventLoop::exec(QFlags) (this=this@entry=0x7f88fa06dbc0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #6 0x00420cd8 in Baloo::FileContentIndexer::run() (this=0x2211500) at /build/baloo-kf5-wIK3t6/baloo-kf5-5.18.0/src/file/filecontentindexer.cpp:71 #7 0x7f8a43c2c2d3 in QThreadPoolThread::run() (this=0x2455d00) at thread/qthreadpool.cpp:93 #8 0x7f8a43c2f7be in QThreadPrivate::start(void*) (arg=0x2455d00) at thread/qthread_unix.cpp:331 #9 0x7f8a4289370a in start_thread (arg=0x7f88fa06e700) at pthread_create.c:333 #10 0x7f8a4323c82d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 1 (Thread 0x7f8a451148c0 (LWP 10950)): [KCrash Handler] #6 0x7f8a4430073b in Baloo::IdFilenameDB::get(unsigned long long) (this=this@entry=0x7ffc45080ac0, docId=docId@entry=4513297663526917) at /build/baloo-kf5-wIK3t6/baloo-kf5-5.18.0/src/engine/idfilenamedb.cpp:96 #7 0x7f8a44315984 in Baloo::WriteTransaction::replaceDocument(Baloo::Document const&, QFlags) (shouldDeleteFolder=..., url=..., docId=4513297663526917, this=0x7ffc45080ab0) at /build/baloo-kf5-wIK3t6/baloo-kf5-5.18.0/src/engine/documenturldb.h:92 #8 0x7f8a44315984 in Baloo::WriteTransaction::replaceDocument(Baloo::Document const&, QFlags) (this=, doc=..., operations=...) at /build/baloo-kf5-wIK3t6/baloo-kf5-5.18.0/src/engine/writetransaction.cpp:231 #9 0x7f8a4430e019 in Baloo::Transaction::replaceDocument(Baloo::Document const&, QFlags) (this=this@entry=0x7ffc45080ce0, doc=..., operations=..., operations@entry=...) at /build/baloo-kf5-wIK3t6/baloo-kf5-5.18.0/src/engine/transaction.cpp:254 #10 0x00429a25 in Baloo::MetadataMover::updateMetadata(Baloo::Transaction*, QString const&, QString const&) (this=this@entry=0x223dc50, tr=tr@entry=0x7ffc45080ce0, from=..., to=...) at /build/baloo-kf5-wIK3t6/baloo-kf5-5.18.0/src/file/metadatamover.cpp:116 #11 0x0042a023 in Baloo::MetadataMover::moveFileMetadata(QString const&, QString const&) (this=0x223dc50, from=..., to=...) at /build/baloo-kf5-wIK3t6/baloo-kf5-5.18.0/src/file/metadatamover.cpp:56 #12 0x7f8a43e3ebaf in QMetaObject::activate(QObject*, int, int, void**) (a=0x7ffc45080e40, r=0x7ffc45081500, this=) at ../../include/QtCore/../../src/corelib/kernel/qobject_impl.h:124 #13 0x7f8a43e3ebaf in QMetaObject::activate(QObject*, int, int, void**) (sender=sender@entry=0x221a3d0, signalOffset=, local_signal_index=local_signal_index@entry=7, argv=argv@entry=0x7ffc45080e40) at kernel/qobject.cpp:3698 #14 0x7f8a43e3f537 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) (sender=sender@entry=0x221a3d0, m=m@entry=0x644cc0 , local_signal_index=local_signal_index@entry=7, argv=argv@entry=0x7ffc45080e40) at kernel/qobject.cpp:3578 #15 0x0042aaba in KInotify::moved(QString const&, QString const&) (this=this@entry=0x221a3d0, _t1=..., _t2=...) at /build/baloo-kf5-wIK3t6/baloo-kf5-5.18.0/obj-x86_64-linux-gnu/src/file/moc_kinotify.cpp:330 #16 0x0042cbff in KInotify::slotEvent(int) (this=, socket=) at /build/baloo-kf5-wIK3t6/baloo-kf5-5.18.0/src/file/kinotify.cpp:421 #17 0x000
[kmail2] [Bug 300142] Kmail can't render a html signature
https://bugs.kde.org/show_bug.cgi?id=300142 Solerman Kaplon changed: What|Removed |Added CC||soler...@wonder.com.br --- Comment #16 from Solerman Kaplon --- I upgraded to KMail 5.1.3 and image signatures are now showing correctly for me -- You are receiving this mail because: You are watching all bug changes.
[kmail] [Bug 254285] Kmail cannot include/insert remote images in signatures
https://bugs.kde.org/show_bug.cgi?id=254285 Solerman Kaplon changed: What|Removed |Added CC||soler...@wonder.com.br --- Comment #3 from Solerman Kaplon --- Works for me in kmail 5.1.3 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kactivities-stats] [Bug 458928] New: Recent files for programs not displaying folders
https://bugs.kde.org/show_bug.cgi?id=458928 Bug ID: 458928 Summary: Recent files for programs not displaying folders Product: frameworks-kactivities-stats Version: 5.95.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: ivan.cu...@kde.org Reporter: soler...@wonder.com.br CC: plasma-b...@kde.org Target Milestone: --- SUMMARY Recent files seems broken on plasma 5.25.5 (kubuntu 22.04, used to work in 20.04) STEPS TO REPRODUCE 1. Using dolphin or the places widget 2. Right click on a folder and asks it to open with a program (vscode, smartgit or gwenview) 3. Go to the menu (all launchers I tested exhibit the bug), find the program and right click it OBSERVED RESULT No folder is listed in the recent opened menu. Files seems to work EXPECTED RESULT The folder should be listed there if it was explicit opened with a program SOFTWARE/OS VERSIONS KDE Plasma Version: 5.25.5 KDE Frameworks Version: 5.95.0 Qt Version: 5.15.3 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 459021] New: Compare command is always disabled/grayed out
https://bugs.kde.org/show_bug.cgi?id=459021 Bug ID: 459021 Summary: Compare command is always disabled/grayed out Product: dolphin Version: 22.04.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: soler...@wonder.com.br CC: kfm-de...@kde.org Target Milestone: --- SUMMARY The compare function that shortcuts to opening kompare with 2 files/folders is always disabled, regardless of the selection done STEPS TO REPRODUCE 1. Open some folder or 2 folders with split view 2. Select 2 items 3. Try to use the compare command OBSERVED RESULT The button is disabled EXPECTED RESULT The button should be enabled for 2 selected items (or at most 2) SOFTWARE/OS VERSIONS KDE Plasma Version: 5.25.5 KDE Frameworks Version: 5.95.0 Qt Version: 5.15.3 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 459021] Compare command is always disabled/grayed out
https://bugs.kde.org/show_bug.cgi?id=459021 Solerman Kaplon changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG --- Comment #1 from Solerman Kaplon --- The upgrade failed and kompare got uninstalled instead of upgraded. With kompare installed works as intended, sorry for the noise -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 421135] Flickering Issue with Blur enabled
https://bugs.kde.org/show_bug.cgi?id=421135 Solerman Kaplon changed: What|Removed |Added CC||soler...@wonder.com.br --- Comment #14 from Solerman Kaplon --- I'm experiencing this while dragging a konsole window with blurred background on 5.24.6, 2 screens (laptop with one edp and another hdmi), extract from qdbus org.kde.KWin /KWin supportInformation : >Compositing >=== >Compositing is active >Compositing Type: OpenGL >OpenGL vendor string: Intel >OpenGL renderer string: Mesa Intel(R) HD Graphics 630 (KBL GT2) >OpenGL version string: 4.6 (Compatibility Profile) Mesa 22.0.5 >OpenGL platform interface: GLX >OpenGL shading language version string: 4.60 >Driver: Intel >GPU class: Kaby Lake >OpenGL version: 4.6 >GLSL version: 4.60 >Mesa version: 22.0.5 >X server version: 1.21.1 >Linux kernel version: 5.15 >Direct rendering: Requires strict binding: yes >GLSL shaders: yes >Texture NPOT support: yes >Virtual Machine: no >OpenGL 2 Shaders are used -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 428699] Please implement automatic reconnection
https://bugs.kde.org/show_bug.cgi?id=428699 Solerman Kaplon changed: What|Removed |Added CC||soler...@wonder.com.br --- Comment #1 from Solerman Kaplon --- Reconnection seems to be implemented for VNC accourding to https://bugs.kde.org/show_bug.cgi?id=158452 RDP reconnection still needed -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 432669] Corruption of screen when using ncurses when terminal resized depending on line content
https://bugs.kde.org/show_bug.cgi?id=432669 Solerman Kaplon changed: What|Removed |Added CC||soler...@wonder.com.br --- Comment #2 from Solerman Kaplon --- Might be related https://www.dedoimedo.com/computers/plasma-scaling-konsole-lines.html -- You are receiving this mail because: You are watching all bug changes.
[kopete] [Bug 264736] Crash in kopete while closing
https://bugs.kde.org/show_bug.cgi?id=264736 --- Comment #2 from Solerman Kaplon --- Sorry, I don't use Kopete anymore, or msn at all. Give the time and the callstack, might as well be an old qt bug likely fixed -- You are receiving this mail because: You are watching all bug changes.
[kopete] [Bug 303405] Kopete crashed by itself
https://bugs.kde.org/show_bug.cgi?id=303405 --- Comment #2 from Solerman Kaplon --- Sorry, I don't use Kopete anymore. Given the time and the callstack, might as well be an old qt bug likely fixed -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 399234] Compositing breaks system tray functionality in programs running under Wine Staging
https://bugs.kde.org/show_bug.cgi?id=399234 --- Comment #14 from Solerman Kaplon --- Testing the example program and also other non-rectangular icons on windows 10, the click works anywhere, not just in the visible icon. It seems there isn't any non-rectangular mask applied -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 399234] Compositing breaks system tray functionality in programs running under Wine Staging
https://bugs.kde.org/show_bug.cgi?id=399234 --- Comment #15 from Solerman Kaplon --- I think the correct fix would be to grab the x/y where the mouse was clicked and send it straight to wine so they handle the mask themselves. Maybe some client-to-absolute -> absolute-to-client translation might be needed -- You are receiving this mail because: You are watching all bug changes.
[kiofuse] [Bug 75324] Integrate KIO Slaves into file system using FUSE gateway
https://bugs.kde.org/show_bug.cgi?id=75324 Solerman Kaplon changed: What|Removed |Added CC||soler...@wonder.com.br --- Comment #47 from Solerman Kaplon --- Can't GVFS (refactored to) be used as a library and share so all environments benefit? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 399234] Compositing breaks system tray functionality in programs running under Wine Staging
https://bugs.kde.org/show_bug.cgi?id=399234 Solerman Kaplon changed: What|Removed |Added CC||soler...@wonder.com.br --- Comment #8 from Solerman Kaplon --- Looks like using stable wine 4.0 and not staging works. So wine-staging bug then? -- You are receiving this mail because: You are watching all bug changes.
[ksnapshot] [Bug 268260] WISH - Add basic draw functions
https://bugs.kde.org/show_bug.cgi?id=268260 Solerman Kaplon changed: What|Removed |Added CC|soler...@wonder.com.br | -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 376525] New: Plasma crash with clean profile
https://bugs.kde.org/show_bug.cgi?id=376525 Bug ID: 376525 Summary: Plasma crash with clean profile Product: plasmashell Version: 5.5.5 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: solerman.kap...@gmail.com CC: bhus...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.5.5) Qt Version: 5.5.1 Operating System: Linux 4.4.0-62-generic x86_64 Distribution: Ubuntu 16.04.2 LTS -- Information about the crash: I shutdown the sddm service and cleared all things kde and baloo in .local and .cache. Other reports suggests this might be a database corruption, but this one I got with a new-ish profile The crash can be reproduced sometimes. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". __pthread_self () at pthread_self.c:27 [Current thread is 1 (Thread 0x7effe97748c0 (LWP 1701))] Thread 16 (Thread 0x7eff097fa700 (LWP 2132)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7effe457fa5b in QWaitConditionPrivate::wait (time=18446744073709551615, this=0x49acb70) at thread/qwaitcondition_unix.cpp:136 #2 QWaitCondition::wait (this=, mutex=0x4d31290, time=time@entry=18446744073709551615) at thread/qwaitcondition_unix.cpp:208 #3 0x7eff2cd9850b in ThreadWeaver::Weaver::blockThreadUntilJobsAreBeingAssigned_locked (this=this@entry=0x4e02b50, th=) at ../../src/weaver.cpp:594 #4 0x7eff2cd992bf in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait (this=0x4e02b50, th=th@entry=0x7eff04002f90, threadWasBusy=threadWasBusy@entry=false, suspendIfInactive=suspendIfInactive@entry=false, justReturning=justReturning@entry=false) at ../../src/weaver.cpp:554 #5 0x7eff2cd9d4e8 in ThreadWeaver::WorkingHardState::applyForWork (this=0x4e02cd0, th=0x7eff04002f90, wasBusy=) at ../../src/workinghardstate.cpp:66 #6 0x7eff2cd9846d in ThreadWeaver::Weaver::applyForWork (this=, th=0x7eff04002f90, wasBusy=) at ../../src/weaver.cpp:568 #7 0x7eff2cd9d542 in ThreadWeaver::WorkingHardState::applyForWork (this=0x4e02cd0, th=0x7eff04002f90, wasBusy=) at ../../src/workinghardstate.cpp:73 #8 0x7eff2cd9846d in ThreadWeaver::Weaver::applyForWork (this=, th=0x7eff04002f90, wasBusy=) at ../../src/weaver.cpp:568 #9 0x7eff2cd9d542 in ThreadWeaver::WorkingHardState::applyForWork (this=0x4e02cd0, th=0x7eff04002f90, wasBusy=) at ../../src/workinghardstate.cpp:73 #10 0x7eff2cd9846d in ThreadWeaver::Weaver::applyForWork (this=, th=0x7eff04002f90, wasBusy=) at ../../src/weaver.cpp:568 #11 0x7eff2cd9d542 in ThreadWeaver::WorkingHardState::applyForWork (this=0x4e02cd0, th=0x7eff04002f90, wasBusy=) at ../../src/workinghardstate.cpp:73 #12 0x7eff2cd9846d in ThreadWeaver::Weaver::applyForWork (this=, th=0x7eff04002f90, wasBusy=) at ../../src/weaver.cpp:568 #13 0x7eff2cd9d542 in ThreadWeaver::WorkingHardState::applyForWork (this=0x4e02cd0, th=0x7eff04002f90, wasBusy=) at ../../src/workinghardstate.cpp:73 #14 0x7eff2cd9846d in ThreadWeaver::Weaver::applyForWork (this=, th=0x7eff04002f90, wasBusy=) at ../../src/weaver.cpp:568 #15 0x7eff2cd9d542 in ThreadWeaver::WorkingHardState::applyForWork (this=0x4e02cd0, th=0x7eff04002f90, wasBusy=) at ../../src/workinghardstate.cpp:73 #16 0x7eff2cd9846d in ThreadWeaver::Weaver::applyForWork (this=, th=0x7eff04002f90, wasBusy=) at ../../src/weaver.cpp:568 #17 0x7eff2cd9b353 in ThreadWeaver::Thread::run (this=0x7eff04002f90) at ../../src/thread.cpp:103 #18 0x7effe457e7be in QThreadPrivate::start (arg=0x7eff04002f90) at thread/qthread_unix.cpp:331 #19 0x7effe366b6ba in start_thread (arg=0x7eff097fa700) at pthread_create.c:333 #20 0x7effe3e9482d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 15 (Thread 0x7eff09ffb700 (LWP 2131)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7effe457fa5b in QWaitConditionPrivate::wait (time=18446744073709551615, this=0x49acb70) at thread/qwaitcondition_unix.cpp:136 #2 QWaitCondition::wait (this=, mutex=0x4d31290, time=time@entry=18446744073709551615) at thread/qwaitcondition_unix.cpp:208 #3 0x7eff2cd9850b in ThreadWeaver::Weaver::blockThreadUntilJobsAreBeingAssigned_locked (this=this@entry=0x4e02b50, th=) at ../../src/weaver.cpp:594 #4 0x7eff2cd992bf in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait (this=0x4e02b50, th=th@entry=0x7eff3190, threadWasBusy=threadWasBusy@entry=false, suspendIfInactive=suspendIfInactive@entry=false, justReturning=justReturning@entry=false) at ../../src/weaver.cpp:554 #5 0x7eff2cd9d4e8 in ThreadWeaver::WorkingH
[muon] [Bug 313596] muon package manager search results are not sorted properly on package name
https://bugs.kde.org/show_bug.cgi?id=313596 --- Comment #5 from Solerman Kaplon --- Well, if sorting after search is costly, maybe disable the column click so that the user doesn't get the impression that sorting is going to do anything useful -- You are receiving this mail because: You are watching all bug changes.
