[gwenview] [Bug 447955] Gwenview crashed after clicking Places sidebar/Recent Locations
https://bugs.kde.org/show_bug.cgi?id=447955 Jiri Palecek changed: What|Removed |Added CC||jpale...@web.de --- Comment #5 from Jiri Palecek --- I experienced this crash in gwenview as well, but it seems very peculiar. It seems some invalid index is accessed and I can't see where is it going from. Moreover, I can't reproduce the issue - does the recent folders list have to be empty or something? Or can somebody reproduce the issue under valgrind? -- You are receiving this mail because: You are watching all bug changes.
[kio] [Bug 185030] Revival of kio_rar and kio_p7zip
https://bugs.kde.org/show_bug.cgi?id=185030 Jiri Palecek changed: What|Removed |Added CC||jpale...@web.de -- You are receiving this mail because: You are watching all bug changes.
[kalendar] [Bug 468929] Kalendar crashes when tasks are edited
https://bugs.kde.org/show_bug.cgi?id=468929 Jiri Palecek changed: What|Removed |Added CC||jpale...@web.de --- Comment #3 from Jiri Palecek --- Hi! (In reply to Beyley Thomas from comment #2) > Happen consistently every time i edit any task in Kalendar > > -- Backtrace (Reduced): > #4 0x7fa3b1ba1250 in QDateTime::operator=(QDateTime const&) () at > /usr/lib/libQt5Core.so.5 > [...] > #7 0x7fa3b1c46c41 in QAbstractItemModel::dataChanged(QModelIndex > const&, QModelIndex const&, QVector const&) () at > /usr/lib/libQt5Core.so.5 These are unfortunately not very interesting, but if you can reproduce the crash, can you please install the debugging info for kf5itemmodels (libkf5itemmodels5 or somesuch) and libkpim5akonadicore and post the backtrace? These are probably the culprits. -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 465699] System monitor segfault
https://bugs.kde.org/show_bug.cgi?id=465699 Jiri Palecek changed: What|Removed |Added CC||jpale...@web.de -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 465765] Menubewerker crasht plotseling
https://bugs.kde.org/show_bug.cgi?id=465765 Jiri Palecek changed: What|Removed |Added CC||jpale...@web.de -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 469923] New: Kdiff3 crashes when the compared directories contain symlinks with nonexistent targets
https://bugs.kde.org/show_bug.cgi?id=469923 Bug ID: 469923 Summary: Kdiff3 crashes when the compared directories contain symlinks with nonexistent targets Classification: Applications Product: kdiff3 Version: 1.10.0 Platform: Debian testing OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: application Assignee: reeves...@gmail.com Reporter: jpale...@web.de Target Milestone: --- Application: kdiff3 (1.9.70 (64 bit)) Qt Version: 5.15.8 Frameworks Version: 5.103.0 Operating System: Linux 6.1.0-6-amd64 x86_64 Windowing System: X11 Distribution: Debian GNU/Linux 12 (bookworm) DrKonqi: 5.27.2 [KCrashBackend] -- Information about the crash: Hello when I tried to compare two directories, kdiff 3 crashed. From the bactrace and inspection under gdb, I can see this is because it tripped on a file which is a symlink with nonexistant target. QFileInfo can't provide a modification time in that case, therefore the modification time is invalid, which causes an assert failure. The crash can be reproduced every time. -- Backtrace: Application: KDiff3 (kdiff3), signal: Aborted [KCrash Handler] #4 __pthread_kill_implementation (threadid=, signo=signo@entry=6, no_tid=no_tid@entry=0) at ./nptl/pthread_kill.c:44 #5 0x7ff257ea9d2f in __pthread_kill_internal (signo=6, threadid=) at ./nptl/pthread_kill.c:78 #6 0x7ff257e5aef2 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #7 0x7ff257e45472 in __GI_abort () at ./stdlib/abort.c:79 #8 0x7ff257e45395 in __assert_fail_base (fmt=0x7ff2515db91f "%s%s%s:%u: %s%sP\305\231edpoklad \342\200\236%s\342\200\234 nespln\304\233n.\n%n", assertion=assertion@entry=0x55f87554a7a8 "!m_modificationTime.isNull()", file=file@entry=0x55f87554a728 "./src/fileaccess.cpp", line=line@entry=762, function=function@entry=0x55f87554aa38 "QDateTime FileAccess::lastModified() const") at ./assert/assert.c:92 #9 0x7ff257e53df2 in __GI___assert_fail (assertion=0x55f87554a7a8 "!m_modificationTime.isNull()", file=0x55f87554a728 "./src/fileaccess.cpp", line=762, function=0x55f87554aa38 "QDateTime FileAccess::lastModified() const") at ./assert/assert.c:101 #10 0x55f8754d41c0 in FileAccess::lastModified (this=) at ./src/fileaccess.cpp:762 #11 0x55f875510182 in MergeFileInfos::compareFilesAndCalcAges (this=this@entry=0x55f87cff1aa0, errors=..., pOptions=..., pDMW=0x55f87757aaa0) at ./src/MergeFileInfos.cpp:192 #12 0x55f87546e4d0 in DirectoryMergeWindow::DirectoryMergeWindowPrivate::prepareListView (this=this@entry=0x55f8775bcc80, pp=...) at ./src/directorymergewindow.cpp:1331 #13 0x55f875471fbb in DirectoryMergeWindow::DirectoryMergeWindowPrivate::init (this=0x55f8775bcc80, bDirectoryMerge=, bReload=) at ./src/directorymergewindow.cpp:951 #14 0x55f875472ee0 in DirectoryMergeWindow::init (this=, bDirectoryMerge=, bReload=) at ./src/directorymergewindow.cpp:736 #15 0x55f875488d59 in KDiff3App::doDirectoryCompare (this=this@entry=0x55f8772d05e0, bCreateNewInstance=bCreateNewInstance@entry=false) at ./src/pdiff.cpp:1627 #16 0x55f87545da3f in KDiff3App::completeInit (this=0x55f8772d05e0, fn1=..., fn2=..., fn3=...) at ./src/kdiff3.cpp:432 #17 0x55f87544fda8 in KDiff3Shell::KDiff3Shell (this=0x55f876f6a410, bCompleteInit=, __in_chrg=, __vtt_parm=) at ./src/kdiff3_shell.cpp:60 #18 0x55f8754447bb in main (argc=, argv=) at ./src/main.cpp:197 [Inferior 1 (process 78517) detached] -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 469530] Arrow keys fail to focus windows in present-window mode launched from the taskbar icons
https://bugs.kde.org/show_bug.cgi?id=469530 Jiri Palecek changed: What|Removed |Added CC||jpale...@web.de --- Comment #1 from Jiri Palecek --- (In reply to Alex A.D. from comment #0) > Created attachment 158799 [details] > Demo of arrow key failure to select window > > Clicking on a taskbar icon of an app (chrome in this case) present-window is > launched but arrow keys are unresponsive. > > See attached demo: note screenkey capture afterward. > > Instead of windows in present-mode actual windows handle keystrokes, like > they don't loose focus at all. Does this apply to normal keys as well? Like, does pressing letter keys filter the windows? I tried it and after fixing bug#466120 it seems to work OK. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 469497] New: Kwin freezes when I try to quickly switch windows twice
https://bugs.kde.org/show_bug.cgi?id=469497 Bug ID: 469497 Summary: Kwin freezes when I try to quickly switch windows twice Classification: Plasma Product: kwin Version: 5.26.90 Platform: Debian testing OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: core Assignee: kwin-bugs-n...@kde.org Reporter: jpale...@web.de Target Milestone: --- SUMMARY Sometimes when I press Alt-Tab twice quickly in succession kwin, and therefore all desktop freezes. This is recoverable by killing kwin. The backtrace when the freeze happened is: #0 __futex_abstimed_wait_common64 (private=0, cancel=true, abstime=0x0, op=393, expected=0, futex_word=0x55a42bee68d4) at ./nptl/futex-internal.c:57 #1 __futex_abstimed_wait_common (futex_word=futex_word@entry=0x55a42bee68d4, expected=expected@entry=0, clockid=clockid@entry=0, abstime=abstime@entry=0x0, private=private@entry=0, cancel=cancel@entry=true) at ./nptl/futex-internal.c:87 #2 0x7fe643aa4d9b in __GI___futex_abstimed_wait_cancelable64 (futex_word=futex_word@entry=0x55a42bee68d4, expected=expected@entry=0, clockid=clockid@entry=0, abstime=abstime@entry=0x0, private=private@entry=0) at ./nptl/futex-internal.c:139 #3 0x7fe643aa73f8 in __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x55a42bee6880, cond=0x55a42bee68a8) at ./nptl/pthread_cond_wait.c:503 #4 ___pthread_cond_wait (cond=0x55a42bee68a8, mutex=0x55a42bee6880) at ./nptl/pthread_cond_wait.c:618 #5 0x7fe6448d1a2b in QWaitConditionPrivate::wait(QDeadlineTimer) (deadline=..., this=0x55a42bee6880) at thread/qwaitcondition_unix.cpp:146 #6 QWaitCondition::wait(QMutex*, QDeadlineTimer) (this=, mutex=0x55a42bf61078, deadline=...) at thread/qwaitcondition_unix.cpp:225 #7 0x7fe64620bd58 in QSGThreadedRenderLoop::polishAndSync(QSGThreadedRenderLoop::Window*, bool) (this=0x55a42b174710, w=0x55a42be30f80, inExpose=) at scenegraph/qsgthreadedrenderloop.cpp:1603 #8 0x7fe646276e20 in QQuickWindow::event(QEvent*) (this=0x55a42beda340, e=0x7ffd9db8e490) at items/qquickwindow.cpp:1863 #9 0x7fe644162fae in QApplicationPrivate::notify_helper(QObject*, QEvent*) (this=, receiver=0x55a42beda340, e=0x7ffd9db8e490) at kernel/qapplication.cpp:3640 #10 0x7fe644ab16f8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) (receiver=0x55a42beda340, event=0x7ffd9db8e490) at kernel/qcoreapplication.cpp:1064 #11 0x7fe644ab18be in QCoreApplication::sendEvent(QObject*, QEvent*) (receiver=, event=) at kernel/qcoreapplication.cpp:1462 #12 0x7fe644f2c4b3 in QPlatformWindow::deliverUpdateRequest() (this=) at kernel/qplatformwindow.cpp:796 #13 QPlatformWindow::windowEvent(QEvent*) (this=, event=) at kernel/qplatformwindow.cpp:476 #14 0x7fe64416a1f9 in QApplication::notify(QObject*, QEvent*) (this=0x7ffd9db8ea10, receiver=0x55a42beda340, e=0x7ffd9db8e6f0) at kernel/qapplication.cpp:2882 #15 0x7fe644ab16f8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) (receiver=0x55a42beda340, event=0x7ffd9db8e6f0) at kernel/qcoreapplication.cpp:1064 #16 0x7fe644ab18be in QCoreApplication::sendEvent(QObject*, QEvent*) (receiver=, event=) at kernel/qcoreapplication.cpp:1462 #17 0x7fe644b08c31 in QTimerInfoList::activateTimers() (this=0x55a42a60fa60) at kernel/qtimerinfo_unix.cpp:643 #18 0x7fe644b094c4 in timerSourceDispatch(GSource*, GSourceFunc, gpointer) (source=) at kernel/qeventdispatcher_glib.cpp:183 #19 0x7fe6428627a9 in g_main_context_dispatch () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #20 0x7fe642862a38 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #21 0x7fe642862acc in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 This indicates IMHO that the problem is in QSGThreadedRenderLoop, because it is waiting on a condition variable it uses to wait for processing of the individual events. However, I'm not quite sure what to do about it. SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.27.2 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 458315] App crashes upon starting (possibly as its trying to start a server)
https://bugs.kde.org/show_bug.cgi?id=458315 Jiri Palecek changed: What|Removed |Added CC||jpale...@web.de -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 460586] KOrganizer crashes on startup when invoked by opening an .ics file (from Dolphin(
https://bugs.kde.org/show_bug.cgi?id=460586 Jiri Palecek changed: What|Removed |Added CC||jpale...@web.de -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 458497] App crashes upon starting
https://bugs.kde.org/show_bug.cgi?id=458497 Jiri Palecek changed: What|Removed |Added CC||jpale...@web.de -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 460653] Crash While Using Firefox
https://bugs.kde.org/show_bug.cgi?id=460653 Jiri Palecek changed: What|Removed |Added CC||jpale...@web.de -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 461131] Korganizer sometimes crashes on startup
https://bugs.kde.org/show_bug.cgi?id=461131 Jiri Palecek changed: What|Removed |Added CC||jpale...@web.de -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 462169] KOrganizer crashes right after running
https://bugs.kde.org/show_bug.cgi?id=462169 Jiri Palecek changed: What|Removed |Added CC||jpale...@web.de -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 462213] korganizer has failed
https://bugs.kde.org/show_bug.cgi?id=462213 Jiri Palecek changed: What|Removed |Added CC||jpale...@web.de -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 464275] KOrganizer crashes on startup
https://bugs.kde.org/show_bug.cgi?id=464275 Jiri Palecek changed: What|Removed |Added CC||jpale...@web.de -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 465245] KOrganizer crashes on launch
https://bugs.kde.org/show_bug.cgi?id=465245 Jiri Palecek changed: What|Removed |Added CC||jpale...@web.de -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 468343] Korganizer crashed on startup
https://bugs.kde.org/show_bug.cgi?id=468343 Jiri Palecek changed: What|Removed |Added CC||jpale...@web.de -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 468343] Korganizer crashed on startup
https://bugs.kde.org/show_bug.cgi?id=468343 Jiri Palecek changed: What|Removed |Added Component|general |libakonadi Product|korganizer |Akonadi -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 468343] New: Korganizer crashed on startup
https://bugs.kde.org/show_bug.cgi?id=468343
Bug ID: 468343
Summary: Korganizer crashed on startup
Classification: Applications
Product: korganizer
Version: unspecified
Platform: Debian testing
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: general
Assignee: kdepim-b...@kde.org
Reporter: jpale...@web.de
Target Milestone: ---
Application: korganizer (5.22.2 (22.12.2))
Qt Version: 5.15.8
Frameworks Version: 5.103.0
Operating System: Linux 6.1.0-6-amd64 x86_64
Windowing System: X11
Distribution: Debian GNU/Linux bullseye/sid
DrKonqi: 5.26.90 [KCrashBackend]
-- Information about the crash:
As soon as the desktop started, KOrganizer which was automatically launched by
the session crashed.
The reporter is unsure if this crash is reproducible.
-- Backtrace:
Application: KOrganizer (korganizer), signal: Segmentation fault
[KCrash Handler]
#4 KJob::setError (this=this@entry=0x0, errorCode=errorCode@entry=100) at
./src/lib/jobs/kjob.cpp:254
#5 0x7fe8bd516da4 in Akonadi::SessionPrivate::serverStateChanged
(this=, state=) at ./src/core/session.cpp:297
#6 0x7fe8bbce8f4f in QtPrivate::QSlotObjectBase::call (a=0x7ffedd00b930,
r=0x5564780769a0, this=0x5564780741e0) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#7 doActivate (sender=0x556477de44b0, signal_index=5,
argv=0x7ffedd00b930) at kernel/qobject.cpp:3923
#8 0x7fe8bbce21ef in QMetaObject::activate (sender=,
m=m@entry=0x7fe8bd625dc0 ,
local_signal_index=local_signal_index@entry=2, argv=argv@entry=0x7ffedd00b930)
at kernel/qobject.cpp:3983
#9 0x7fe8bd511ce1 in Akonadi::ServerManager::stateChanged (this=, _t1=, _t1@entry=Akonadi::ServerManager::Broken) at
./obj-x86_64-linux-gnu/src/core/KF5AkonadiCore_autogen/include/moc_servermanager.cpp:180
#10 0x7fe8bd51507c in Akonadi::ServerManagerPrivate::setState
(state=Akonadi::ServerManager::Broken, this=0x7fe8bd62e400 <(anonymous
namespace)::Q_QGS_sInstance::innerFunction()::holder>) at
./src/core/servermanager.cpp:73
#11 Akonadi::ServerManagerPrivate::timeout (this=0x7fe8bd62e400 <(anonymous
namespace)::Q_QGS_sInstance::innerFunction()::holder>) at
./src/core/servermanager.cpp:93
#12
Akonadi::ServerManagerPrivate::ServerManagerPrivate()::{lambda()#1}::operator()()
const (__closure=) at ./src/core/servermanager.cpp:52
#13 QtPrivate::FunctorCall, QtPrivate::List<>, void,
Akonadi::ServerManagerPrivate::ServerManagerPrivate()::{lambda()#1}>::call(Akonadi::ServerManagerPrivate::ServerManagerPrivate()::{lambda()#1}&,
void**) (arg=, f=...) at
/usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:146
#14
QtPrivate::Functor::call,
void>(Akonadi::ServerManagerPrivate::ServerManagerPrivate()::{lambda()#1}&,
void*, void**) (arg=, f=...) at
/usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:256
#15
QtPrivate::QFunctorSlotObject, void>::impl(int, QtPrivate::QSlotObjectBase*, QObject*,
void**, bool*) (which=, this_=, r=, a=, ret=) at
/usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:443
#16 0x7fe8bbce8f4f in QtPrivate::QSlotObjectBase::call (a=0x7ffedd00ba40,
r=0x556477de44b0, this=0x556477df9220) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#17 doActivate (sender=0x7fe8900095c0, signal_index=3,
argv=0x7ffedd00ba40) at kernel/qobject.cpp:3923
#18 0x7fe8bbce21ef in QMetaObject::activate (sender=,
m=m@entry=0x7fe8bbf4c2e0 ,
local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffedd00ba40)
at kernel/qobject.cpp:3983
#19 0x7fe8bbcecd6a in QTimer::timeout (this=, _t1=...) at
.moc/moc_qtimer.cpp:205
#20 0x7fe8bbcdd50d in QObject::event (this=0x7fe8900095c0,
e=0x7ffedd00bb90) at kernel/qobject.cpp:1369
#21 0x7fe8bc962fae in QApplicationPrivate::notify_helper (this=, receiver=0x7fe8900095c0, e=0x7ffedd00bb90) at
kernel/qapplication.cpp:3640
#22 0x7fe8bbcb16f8 in QCoreApplication::notifyInternal2
(receiver=0x7fe8900095c0, event=0x7ffedd00bb90) at
kernel/qcoreapplication.cpp:1064
#23 0x7fe8bbcb18be in QCoreApplication::sendEvent (receiver=, event=) at kernel/qcoreapplication.cpp:1462
#24 0x7fe8bbd08c31 in QTimerInfoList::activateTimers (this=0x556477d95390)
at kernel/qtimerinfo_unix.cpp:643
#25 0x7fe8bbd094c4 in timerSourceDispatch (source=) at
kernel/qeventdispatcher_glib.cpp:183
#26 0x7fe8b96627a9 in g_main_context_dispatch () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#27 0x7fe8b9662a38 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#28 0x7fe8b9662acc in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#29 0x7fe8bbd09836 in QEventDispatcherGlib::processEvents
(this=0x556477d97880, flags=...) at kernel/qeventdispatcher_glib.cpp:423
#30 0x7fe8bbcb017b in QEventLoop::exec (this=this@entry=0x7ffedd00bdd0,
flags=..., flags@entry=...) at
[ktimetracker] [Bug 463727] KTimeTracker opened 600+ questions about idle desktop while session was locked
https://bugs.kde.org/show_bug.cgi?id=463727 Jiri Palecek changed: What|Removed |Added CC||jpale...@web.de --- Comment #1 from Jiri Palecek --- Same thing here. The freeze is caused by kwin handling the windows too slowly, which I solved by patching kwin. It is still rogue behaviour by ktimetracker. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 372305] Crash in ContrastEffect::uploadRegion
https://bugs.kde.org/show_bug.cgi?id=372305 --- Comment #58 from Jiri Palecek --- (In reply to Vlad Zahorodnii from comment #57) > Git commit ddd60a0c1b6a6bbf7a1ba7e34cdc63582048b862 by Vlad Zahorodnii, on > behalf of Aleix Pol. > Committed on 11/01/2023 at 14:37. > Pushed by vladz into branch 'master'. > > backgroundcontrast: Guard against calling a nullptr > > There are cases where GLVertexBuffer::map will return null (as seen in > kwinglutils.cpp:1816) which does happen (as seen in the backtrace of bug > 462017) > Make sure we don't call the null map in that case. > https://invent.kde.org/plasma/kwin/commit/ddd60a0c1b6a6bbf7a1ba7e34cdc63582048b862 Are you sure this fixes the problem? In many of the backtraces, you can see that the map pointer isn't actually zero, although some of the backtraces seem different and I suspect they might indicate a different problem. Did you try to reproduce it and confirm it is fixed, by the procedure in my other comment? I used to have this problem, but since then I've changed my computer. I still have the graphics card in question around so maybe I could try to see what it does, but I can't promise anything. Without a clear idea of what's wrong and how to fix it, I don't think this can move forward. It seems like some peculiarity of NVidia drivers, but then again, other gl apps don't crash on Nvidia, or do they? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kidletime] [Bug 392679] playing a video with mpv counts as activity to RSIbreak
https://bugs.kde.org/show_bug.cgi?id=392679 Jiri Palecek changed: What|Removed |Added CC||jpale...@web.de --- Comment #5 from Jiri Palecek --- (In reply to Oswald Buddenhagen from comment #4) > according to the investigation in the mpv bug, the issue is that its > screensaver/suspend prevention "punches through" to the idle time detection. > there isn't really much to be done about that as long as it uses legacy apis > - nowadays, it should be using the dbus inhibitor api. but according to my > test it still doesn't. It should be fixed if the Monitoring phase of rsibreak used the "short input" filter just as the resting phase does. I'm not sure whether it wouldn't filter out too much activity -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 453090] Can't connect to a Windows samba share with samba-libs 4.16
https://bugs.kde.org/show_bug.cgi?id=453090 --- Comment #4 from Jiri Palecek --- A similar problem with nautilus was already discussed here: https://bugzilla.samba.org/show_bug.cgi?id=14983 They resolved it by handling/ignoring EINVAL returns: https://gitlab.gnome.org/GNOME/gvfs/-/issues/611 -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 453090] Can't connect to a Windows samba share with samba-libs 4.16
https://bugs.kde.org/show_bug.cgi?id=453090 --- Comment #2 from Jiri Palecek --- (In reply to Harald Sitter from comment #1) > I take it your credentials are correct? If so please file this upstream at > bugzilla.samba.org you are getting EINVAL which seems an entirely > unreasonable return value there. No, these credentials are, in fact, wrong. I need to connect to the system as a different user, but that should be no problem, shouldn't it? It used to pop up a box where I entered a username/password, and often it just connects right away. Another problem is that I don't have a Samba bugzilla account. -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 453090] New: Can't connect to a Windows samba share with samba-libs 4.16
https://bugs.kde.org/show_bug.cgi?id=453090
Bug ID: 453090
Summary: Can't connect to a Windows samba share with samba-libs
4.16
Product: kio-extras
Version: 21.12.3
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: Samba
Assignee: plasma-b...@kde.org
Reporter: jpale...@web.de
CC: sit...@kde.org
Target Milestone: ---
Hello
after upgrading samba-libs from 4.13 to 4.16, I can't display files on my
windows computer from linux in dolphin anymore. I open the smb:// URL, the
remote system shows up, then I click on it and it shows an error "Soubor nebo
složka smb://laptop-jvsbr4b4.local/ neexistuje." (File or directory doesn't
exist).
I bisected this in samba down to this commit:
commit 34771e1931587807d0395c7ac7f4be18654997f4 (refs/bisect/bad)
Author: Elia Geretto
Date: Fri Mar 11 19:32:30 2022 +0100
s3:libsmb: Fix errno for failed authentication in SMBC_server_internal()
In SMBC_server_internal(), when authentication fails, the errno value is
currently hard-coded to EPERM, while it should be EACCES instead. Use the
NT_STATUS map to set the appropriate value.
This bug was found because it breaks listing printers protected by
authentication in GNOME Control Panel.
BUG: https://bugzilla.samba.org/show_bug.cgi?id=14983
Signed-off-by: Elia Geretto
Reviewed-by: Jeremy Allison
Reviewed-by: Volker Lendecke
Autobuild-User(master): Jeremy Allison
Autobuild-Date(master): Wed Mar 16 19:44:18 UTC 2022 on sn-devel-184
(cherry picked from commit 70b9977a46e5242174b4461a7f49d5f640c1db62)
diff --git a/source3/libsmb/libsmb_server.c b/source3/libsmb/libsmb_server.c
index b92477c88fe..09d27868c0e 100644
--- a/source3/libsmb/libsmb_server.c
+++ b/source3/libsmb/libsmb_server.c
@@ -572,7 +572,7 @@ SMBC_server_internal(TALLOC_CTX *ctx,
!NT_STATUS_IS_OK(cli_session_setup_anon(c))) {
cli_shutdown(c);
-errno = EPERM;
+ errno = map_errno_from_nt_status(status);
return NULL;
}
}
The debugging messages from kio are:
kf.kio.slaves.smb: open "smb:///" url-type: 1 dirfd: -1 errNum: 111
kf.kio.slaves.smb: QUrl("smb://")
kf.kio.slaves.smb: QUrl("smb://laptop-jvsbr4b4.kio-discovery-wsd/")
kf.kio.slaves.smb: checkURL QUrl("smb://laptop-jvsbr4b4.kio-discovery-wsd/")
kf.kio.slaves.smb: Resolved DNSSD name: "laptop-jvsbr4b4.local"
kf.kio.slaves.smb: checkURL return3 QUrl("smb://laptop-jvsbr4b4.local/")
kf.kio.slaves.smb: QUrl("smb://laptop-jvsbr4b4.local/")
kf.kio.slaves.smb: checkURL QUrl("smb://laptop-jvsbr4b4.local/")
kf.kio.slaves.smb: checkURL return3 QUrl("smb://laptop-jvsbr4b4.local/")
kf.kio.slaves.smb: updateCache "/"
kf.kio.slaves.smb: Starting discovery.
kf.kio.slaves.smb: auth_smbc_get_dat: set user= jirka , workgroup= WORKGROUP
server= laptop-jvsbr4b4.local , share= IPC$
kf.kio.slaves.smb: updateCache "/IPC$"
kf.kio.slaves.smb: libsmb-auth-callback URL:
QUrl("smb://laptop-jvsbr4b4.local/IPC$")
kf.kio.slaves.smb: auth_smbc_get_dat: set user= jirka , workgroup= WORKGROUP
server= laptop-jvsbr4b4.local , share= IPC$
kf.kio.slaves.smb: updateCache "/IPC$"
kf.kio.slaves.smb: libsmb-auth-callback URL:
QUrl("smb://laptop-jvsbr4b4.local/IPC$")
kf.kio.slaves.smb: open "smb://laptop-jvsbr4b4.local/" url-type: 2 dirfd: -1
errNum: 22
kf.kio.slaves.smb: Discovery finished.
kf.kio.slaves.smb: reporting generic error: 22
kf.kio.slaves.smb: errNum 22
kf.kio.core: "Soubor nebo složka smb://laptop-jvsbr4b4.local/ neexistuje."
SOFTWARE/OS VERSIONS
Windows: 10
Linux: 5.16.18
(available in About System)
KDE Plasma Version:
KDE Frameworks Version:
Qt Version:
--
You are receiving this mail because:
You are watching all bug changes.
[ksysguard] [Bug 350140] KSysGuard crashed on close
https://bugs.kde.org/show_bug.cgi?id=350140 --- Comment #57 from Jiri Palecek --- This should be fixed by https://phabricator.kde.org/D29616 Can you test it? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 436900] Memory leak with Nvidia driver
https://bugs.kde.org/show_bug.cgi?id=436900
--- Comment #4 from Jiri Palecek ---
(In reply to Grzesiek11 from comment #3)
> Here is the Valgrind report:
> https://grzesiek11.stary.pc.pl/files/texts/436900_valgrind.log (~80 MiB, be
> warned).
Thank you. 80Mb, that's nothing :). Even emacs loads it.
> I have no idea if I had done this right, I just copy-pasted the command
> found on the Wiki ('valgrind --leak-check=full --show-reachable=yes
> --track-origins=yes --trace-children=yes --log-file=plasmashell.log
> plasmashell') and left it overnight.
That's good, only the backtraces stop just short before showing useful info, so
I'd like you to do it again. For the command:
- --trace-children=yes is unnecessary, I don't think this has anything to do
with children, and also, it prevents valgrind from tracing chromium ;)
- --track-origins=yes does nothing for leaks
However, I'd like you to add --num-callers=30, because some of the stack traces
are too shallow, they don't go beyond the nvidia driver. So the command should
be:
valgrind --leak-check=full --show-reachable=yes --num-callers=30
--log-file=plasmashell.log plasmashell
However, most of all, to get useful backtraces, you need the debugging infos
for all the executables. The most suspicious for me is this record:
==103236== 28,516,944 bytes in 4 blocks are possibly lost in loss record 54,997
of 54,997
==103236==at 0x483877F: malloc (vg_replace_malloc.c:307)
==103236==by 0x625404D: QImageData::create(QSize const&, QImage::Format)
(in /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5.15.2)
==103236==by 0x625426A: QImage::QImage(QSize const&, QImage::Format) (in
/usr/lib/x86_64-linux-gnu/libQt5Gui.so.5.15.2)
==103236==by 0x62BFBFF: ??? (in
/usr/lib/x86_64-linux-gnu/libQt5Gui.so.5.15.2)
==103236==by 0x6274B18: QImageReader::read(QImage*) (in
/usr/lib/x86_64-linux-gnu/libQt5Gui.so.5.15.2)
==103236==by 0x6275294: QImageReader::read() (in
/usr/lib/x86_64-linux-gnu/libQt5Gui.so.5.15.2)
==103236==by 0x625E3A7: QImage::fromData(unsigned char const*, int, char
const*) (in /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5.15.2)
==103236==by 0x6225523: QInternalMimeData::retrieveData(QString const&,
QVariant::Type) const (in /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5.15.2)
==103236==by 0x6A6198F: ??? (in
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5.15.2)
==103236==by 0x6A627B8: QMimeData::imageData() const (in
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5.15.2)
==103236==by 0x259CB337: ??? (in
/usr/lib/x86_64-linux-gnu/qt5/plugins/plasma/dataengine/plasma_engine_clipboard.so)
==103236==by 0x259BA854: ??? (in
/usr/lib/x86_64-linux-gnu/qt5/plugins/plasma/dataengine/plasma_engine_clipboard.so)
but 0x259CB337: ??? (in
/usr/lib/x86_64-linux-gnu/qt5/plugins/plasma/dataengine/plasma_engine_clipboard.so)
doesn't tell me much.
To get debug symbols, since you're on debian, follow these instructions:
https://wiki.debian.org/HowToGetABacktrace, mostly the part "Installing the
debugging symbols". Particular debugging packages you need are:
- plasma-workspace-dbgsym for plasmashell and plasma_engine_clipboard.so
- libkf5plasmaquick5-dbgsym for libKF5PlasmaQuick.so.5.83.0
- libkf5plasma5-dbgsym for libKF5Plasma.so.5.83.0
and maybe
- libqt5core5a-dbgsym
- libqt5quick5-dbgsym
- libqt5qml5-dbgsym
> plasmashell became very slow and unresponsive (which I guess is how Valgrind
> works),
Sadly that's the way it is.
> so I didn't use it at all and started everything from Konsole (that
> was not started by plasmashell, so it wouldn't be it's child). I don't know
Please try to interact with plasma as usual. The leak might be tied to some
user actions. Or alternatively, think what could be contributing to the problem
so it can be reproduced. If it is tied to the clipboard, do you use it
specifically? Do you use some special widgets? etc.
> if I reproduced the issue, since Valgrind replaces the plasmashell process
> and it used 1.1 GiB at start (it grew to 1.7 GiB when I stopped it).
Yeah that's OK, valgrind uses a lot for its bookkeeping.
--
You are receiving this mail because:
You are watching all bug changes.
[ksysguard] [Bug 417080] Add support for huge pages
https://bugs.kde.org/show_bug.cgi?id=417080 Jiri Palecek changed: What|Removed |Added CC||jpale...@web.de -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 436900] Memory leak with Nvidia driver
https://bugs.kde.org/show_bug.cgi?id=436900 Jiri Palecek changed: What|Removed |Added CC||jpale...@web.de --- Comment #1 from Jiri Palecek --- Hi! I can't see such a drastic increase in plasmashell memory usage, however that might be due to different nvidia driver version. Still, it could just be something else than the graphics driver. Would it be possible for you to run plasmashell under valgrind? You need debug info for plasmashell and libraries to get usable results. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 364039] Dolphin crashed on file transfer
https://bugs.kde.org/show_bug.cgi?id=364039 Jiri Palecek changed: What|Removed |Added CC||jpale...@web.de -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 350140] KSysGuard crashed on close
https://bugs.kde.org/show_bug.cgi?id=350140 Jiri Palecek changed: What|Removed |Added CC||jpale...@web.de --- Comment #43 from Jiri Palecek --- This one is easy; I will post a fix to phabricator -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 350140] KSysGuard crashed on close
https://bugs.kde.org/show_bug.cgi?id=350140 Jiri Palecek changed: What|Removed |Added CC||francisco.mosquera@outlook. ||es --- Comment #42 from Jiri Palecek --- *** Bug 419784 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 419784] KSysGuard crashes when try to close.
https://bugs.kde.org/show_bug.cgi?id=419784 Jiri Palecek changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED CC||jpale...@web.de --- Comment #1 from Jiri Palecek --- *** This bug has been marked as a duplicate of bug 350140 *** -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 419940] KSysGuard sometimes crashes when closed
https://bugs.kde.org/show_bug.cgi?id=419940 Jiri Palecek changed: What|Removed |Added CC||jpale...@web.de Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #1 from Jiri Palecek --- *** This bug has been marked as a duplicate of bug 350140 *** -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 350140] KSysGuard crashed on close
https://bugs.kde.org/show_bug.cgi?id=350140 Jiri Palecek changed: What|Removed |Added CC||ckri...@gmail.com --- Comment #41 from Jiri Palecek --- *** Bug 419940 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 350140] KSysGuard crashed on close
https://bugs.kde.org/show_bug.cgi?id=350140 Jiri Palecek changed: What|Removed |Added CC||elizab...@interlinked.me --- Comment #40 from Jiri Palecek --- *** Bug 420281 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 420281] ksysguard crashes on close
https://bugs.kde.org/show_bug.cgi?id=420281 Jiri Palecek changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED CC||jpale...@web.de --- Comment #1 from Jiri Palecek --- *** This bug has been marked as a duplicate of bug 350140 *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 372305] Crash in ContrastEffect::uploadRegion
https://bugs.kde.org/show_bug.cgi?id=372305 --- Comment #39 from Jiri Palecek --- Please have a look at https://phabricator.kde.org/D27924. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 372305] Crash in ContrastEffect::uploadRegion
https://bugs.kde.org/show_bug.cgi?id=372305 --- Comment #37 from Jiri Palecek --- (In reply to David Edmundson from comment #36) > Could you test https://phabricator.kde.org/P548 as an alternate fix Yes. Still crashes, unfortunately. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 372305] Crash in ContrastEffect::uploadRegion
https://bugs.kde.org/show_bug.cgi?id=372305 --- Comment #34 from Jiri Palecek --- Created attachment 126458 --> https://bugs.kde.org/attachment.cgi?id=126458=edit A crude patch which reinitializes the VBO -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 372305] Crash in ContrastEffect::uploadRegion
https://bugs.kde.org/show_bug.cgi?id=372305 --- Comment #33 from Jiri Palecek --- Good news everyone! I've been experiencing similar crashes, and after finding an easy way to reproduce, I've been able to dissect it further. My crash is this: #4 0xb7eeebb8 in () #5 0xb5878691 in KWin::WindowQuadList::makeInterleavedArrays(unsigned int, KWin::GLVertex2D*, QMatrix4x4 const&) const (this=0xbfe81d84, type=7, vertices=0xa94b9b60, textureMatrix=...) at ./libkwineffects/kwineffects.cpp:1171 #6 0xad9b362d in KWin::SceneOpenGL2Window::performPaint(int, QRegion, KWin::WindowPaintData) (this=0xbfe81fc4, mask=-1075306552, region=..., data=...) at ./plugins/scenes/opengl/scene_opengl.cpp:1431 also caused by vbo mapping pointing to inaccessible memory. I reproduced it by putting kwin under stress with this (don't laugh): ( for((;;)); do qdbus org.kde.kopete /kopete/MainWindow_1 org.qtproject.Qt.QWidget.minimumHeight 100; qdbus org.kde.kopete /kopete/MainWindow_1 org.qtproject.Qt.QWidget.maximumHeight 100; qdbus org.kde.kopete /kopete/MainWindow_1 org.qtproject.Qt.QWidget.maximumHeight 1600; for i in $(seq 1 10); do qdbus org.kde.kopete /kopete/MainWindow_1 org.qtproject.Qt.QWidget.minimumHeight $((i*100)); done; done ) & and then provoke the crash by cycling the computer through suspend-to-ram: for i in $(seq 1 60); do rtcwake -m mem -s 30; sleep 20; done In my experience, kwin crashes within the first 10 iterations if vulnerable to this particular bug. With this, I found that: 1) KWIN_PERSISTENT_VBO=0 avoids the crash 2) reinitializing GLVertexBuffer::streamingBuffer while handling graphics reset also avoids the crash. I hope with this a way to fix this bug can be found. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 283477] Missing language specific characters when filling in forms
https://bugs.kde.org/show_bug.cgi?id=283477 Jiri Palecek changed: What|Removed |Added CC||jpale...@web.de -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 407526] Plasmashell and ksysguardd uses cpu
https://bugs.kde.org/show_bug.cgi?id=407526 --- Comment #2 from Jiri Palecek --- I was having similar problems on my computer, turns out it was caused by one mount point mentioned twice in mtab. I created some patches addressing this, could you have a look at them (and perhaps test them) here: https://phabricator.kde.org/T11473 It may be the case that your problems are different than what I was having, in that case, if you can reproduce it, a strace of plasmashell would be handy. -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 253742] ksysguardd: inefficient read loop
https://bugs.kde.org/show_bug.cgi?id=253742 Jiri Palecek changed: What|Removed |Added CC||jpale...@web.de --- Comment #4 from Jiri Palecek --- Speaking about inefficiency in ksysguardd, is there an actual reason why it doesn't use Qt's normal means for IO, container implementations etc. and instead uses some home brew structures and algos with questionable efficiency and interfaces? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 407526] Plasmashell and ksysguardd uses cpu
https://bugs.kde.org/show_bug.cgi?id=407526 Jiri Palecek changed: What|Removed |Added CC||jpale...@web.de -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 410596] Crash when importing alarms
https://bugs.kde.org/show_bug.cgi?id=410596 --- Comment #13 from Jiri Palecek --- (In reply to David Jarvie from comment #12) > Can you please commit your Phabricator patch so that this bug report can be > closed? Thanks. Hardly, I have no access. -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 410596] Crash when importing alarms
https://bugs.kde.org/show_bug.cgi?id=410596 --- Comment #10 from Jiri Palecek --- (In reply to David Jarvie from comment #9) > Yes, there is a bug in removeKAEvents, and your patch looks good. I'll wait > for you to submit it in Phabricator. I've posted it. > The valgrind trace shows that a calendar added is being processed, and that > that is interrupted (while a 'new' is being executed) by the removal of a > calendar, and that in turn is interrupted (while a 'delete' is being > executed) by another removal of a calendar. I think this is a misunderstanding, the valgrind report for a wrong access contains three traces, one at the time of the access, second one at the time of the block being freed, third one at the time of its allocation. It isn't one backtrace of new interrupted while being executed. It would be very odd if that actually could happen. I admit it's not entirely legible here. I'll try to use attachments the next time, although it's tricky when you just copy output from terminal. -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 410596] Crash when importing alarms
https://bugs.kde.org/show_bug.cgi?id=410596 --- Comment #8 from Jiri Palecek --- Created attachment 122029 --> https://bugs.kde.org/attachment.cgi?id=122029=edit This patch looks better -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 410596] Crash when importing alarms
https://bugs.kde.org/show_bug.cgi?id=410596 Jiri Palecek changed: What|Removed |Added Attachment #122027|0 |1 is obsolete|| --- Comment #7 from Jiri Palecek --- Comment on attachment 122027 --> https://bugs.kde.org/attachment.cgi?id=122027 proposed patch Disregard that -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 410596] Crash when importing alarms
https://bugs.kde.org/show_bug.cgi?id=410596 --- Comment #6 from Jiri Palecek --- Created attachment 122027 --> https://bugs.kde.org/attachment.cgi?id=122027=edit proposed patch Will send it through Phabricator in a few days, just sending so you can comment on it now. -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 410596] Crash when importing alarms
https://bugs.kde.org/show_bug.cgi?id=410596 --- Comment #5 from Jiri Palecek --- Hello, thanks for your effort. Yes, there are duplicate items: $ grep ^UID ~/.kde/share/apps/kalarm/*.ics | sort -k 3 -t: /home/jirka/.kde/share/apps/kalarm/calendar.ics:UID:b355410c-07af-4ded-abf3-d88743a1 /home/jirka/.kde/share/apps/kalarm/displaying.ics:UID:KAlarm-disp-1593075078.221 /home/jirka/.kde/share/apps/kalarm/expired.ics:UID:KAlarm-exp-959849771.278 /home/jirka/.kde/share/apps/kalarm/expired.ics:UID:KAlarm-exp-959849771.278 /home/jirka/.kde/share/apps/kalarm/expired.ics:UID:KAlarm-exp-981216950.140 /home/jirka/.kde/share/apps/kalarm/expired.ics:UID:KAlarm-exp-981216950.140 /home/jirka/.kde/share/apps/kalarm/calendar.ics:UID:KAlarm-1906626020.755 /home/jirka/.kde/share/apps/kalarm/calendar.ics:UID:KAlarm-727370443.645 /home/jirka/.kde/share/apps/kalarm/calendar.ics:UID:6e28d948-c6ba-4127-ac36-8a01b672de95 /home/jirka/.kde/share/apps/kalarm/calendar.ics:UID:9f3cd70a-9e1d-4d08-81ae-8dea00eaa34c (In reply to David Jarvie from comment #4) > The valgrind crash is in fact different from the original crash. The I don't think so; yes, the backtraces (their upper frames) are different, however, I think this isn't important. The immediate place of the crash is the same, and the reason - a dangling pointer - is the same in both traces. I discovered the dangling pointer also in gdb. My hypothesis is, that while the native run goes through the same dangling pointer dereference as the valgrind run, natively it goes through because the memory hasn't been overwritten yet. It just crashes later when the freed memory gets reused. > valgrind crash shows that multiple calendar status changes are being > received in AlarmCalendar, before the processing of the previous one has > completed. What you mean? I don't see any indication of that from valgrind, IMHO it just crashed inside the same removeKAEvents call that deleted the data. Given that, I looked at AlarmCalendar::removedKAevents and it really seems fishy. It haphazardly deletes some events, then it randomly removes the collection which might or might not contain the pointers to data which were deleted. It seems this could cause the crash I see. Anyway, I have prepared a patch that fixes this method, by only leaving valid pointers in mResourceMap. It makes the crash go away (although I got another crash under valgrind, accompanied by the message that connection to akonadi was lost, possibly because execution under valgrind was so slow). I will post the patch here, although I was planning to send it through phabricator. -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 410596] Crash when importing alarms
https://bugs.kde.org/show_bug.cgi?id=410596 --- Comment #1 from Jiri Palecek --- BTW valgrind says this about the problem: ==23380== Invalid read of size 4 ==23380==at 0x4BF3134: KAlarmCal::KAEvent::category() const (kaevent.cpp:1769) ==23380==by 0x1B0C31: AlarmCalendar::events(Akonadi::Collection const&, QFlags) const (alarmcalendar.cpp:1340) ==23380==by 0x1B0EAA: events (alarmcalendar.h:68) ==23380==by 0x1B0EAA: AlarmCalendar::checkForDisabledAlarms() (alarmcalendar.cpp:1439) ==23380==by 0x1B22F0: AlarmCalendar::removeKAEvents(long long, bool, QFlags) (alarmcalendar.cpp:502) ==23380==by 0x756C483: QMetaObject::activate(QObject*, int, int, void**) (in /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5.11.3) ==23380==by 0x756C90C: QMetaObject::activate(QObject*, QMetaObject const*, int, void**) (in /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5.11.3) ==23380==by 0x2A2B91: AkonadiModel::collectionStatusChanged(Akonadi::Collection const&, AkonadiModel::Change, QVariant const&, bool) (moc_akonadimodel.cpp:416) ==23380==by 0x268546: AkonadiModel::setCollectionChanged(Akonadi::Collection const&, QSet const&, bool) (akonadimodel.cpp:1707) ==23380==by 0x2A90E5: slotCollectionChanged (akonadimodel.h:261) ==23380==by 0x2A90E5: AkonadiModel::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) (moc_akonadimodel.cpp:214) ==23380==by 0x756C33A: QMetaObject::activate(QObject*, int, int, void**) (in /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5.11.3) ==23380==by 0x756C90C: QMetaObject::activate(QObject*, QMetaObject const*, int, void**) (in /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5.11.3) ==23380==by 0x5431EB5: Akonadi::Monitor::collectionChanged(Akonadi::Collection const&, QSet const&) (in /usr/lib/i386-linux-gnu/libKF5AkonadiCore.so.5.9.3.abi2) ==23380== Address 0x1081c7b8 is 0 bytes inside a block of size 4 free'd ==23380==at 0x480BD67: operator delete(void*) (in /usr/lib/i386-linux-gnu/valgrind/vgpreload_memcheck-x86-linux.so) ==23380==by 0x1B209E: AlarmCalendar::removeKAEvents(long long, bool, QFlags) (alarmcalendar.cpp:485) ==23380==by 0x756C483: QMetaObject::activate(QObject*, int, int, void**) (in /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5.11.3) ==23380==by 0x756C90C: QMetaObject::activate(QObject*, QMetaObject const*, int, void**) (in /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5.11.3) ==23380==by 0x2A2B91: AkonadiModel::collectionStatusChanged(Akonadi::Collection const&, AkonadiModel::Change, QVariant const&, bool) (moc_akonadimodel.cpp:416) ==23380==by 0x268546: AkonadiModel::setCollectionChanged(Akonadi::Collection const&, QSet const&, bool) (akonadimodel.cpp:1707) ==23380==by 0x2A90E5: slotCollectionChanged (akonadimodel.h:261) ==23380==by 0x2A90E5: AkonadiModel::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) (moc_akonadimodel.cpp:214) ==23380==by 0x756C33A: QMetaObject::activate(QObject*, int, int, void**) (in /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5.11.3) ==23380==by 0x756C90C: QMetaObject::activate(QObject*, QMetaObject const*, int, void**) (in /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5.11.3) ==23380==by 0x5431EB5: Akonadi::Monitor::collectionChanged(Akonadi::Collection const&, QSet const&) (in /usr/lib/i386-linux-gnu/libKF5AkonadiCore.so.5.9.3.abi2) ==23380==by 0x543A461: Akonadi::MonitorPrivate::emitCollectionNotification(Akonadi::Protocol::CollectionChangeNotification const&, Akonadi::Collection const&, Akonadi::Collection const&, Akonadi::Collection const&) (in /usr/lib/i386-linux-gnu/libKF5AkonadiCore.so.5.9.3.abi2) ==23380==by 0x543FD3F: Akonadi::MonitorPrivate::emitNotification(QSharedPointer const&) (in /usr/lib/i386-linux-gnu/libKF5AkonadiCore.so.5.9.3.abi2) ==23380== Block was alloc'd at ==23380==at 0x480ACAB: operator new(unsigned int) (in /usr/lib/i386-linux-gnu/valgrind/vgpreload_memcheck-x86-linux.so) ==23380==by 0x1B3A5A: AlarmCalendar::slotEventChanged(AkonadiModel::Event const&) (alarmcalendar.cpp:564) ==23380==by 0x1B3CAE: AlarmCalendar::slotEventsAdded(QList const&) (alarmcalendar.cpp:530) ==23380==by 0x756C483: QMetaObject::activate(QObject*, int, int, void**) (in /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5.11.3) ==23380==by 0x756C90C: QMetaObject::activate(QObject*, QMetaObject const*, int, void**) (in /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5.11.3) ==23380==by 0x2A2BF1: AkonadiModel::eventsAdded(QList const&) (moc_akonadimodel.cpp:423) ==23380==by 0x268D5C: AkonadiModel::slotRowsInserted(QModelIndex const&, int, int) (akonadimodel.cpp:1634) ==23380==by 0x756C483: QMetaObject::activate(QObject*, int, int, void**) (in /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5.11.3) ==23380==by 0x756C90C: QMetaObject::activate(QObject*, QMetaObject const*, int, void**) (in /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5.11.3)
[kalarm] [Bug 410596] New: Crash when importing alarms
https://bugs.kde.org/show_bug.cgi?id=410596 Bug ID: 410596 Summary: Crash when importing alarms Product: kalarm Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: djar...@kde.org Reporter: jpale...@web.de Target Milestone: --- By some (to me unknown) action probably connected to copying my disk drive to another one I lost several of my alarms in KAlarm. When I clicked some of the items in the left pane of the main window (calendars), the alarms came back, but I got a crash. Backtrace is: (gdb) bt #0 0xb7f1a881 in __kernel_vsyscall () #1 0xb4c129eb in __GI___nanosleep (remaining=0xbfa8ee64, requested_time=0xbfa8ee64) at ../sysdeps/unix/sysv/linux/nanosleep.c:28 #2 __GI___nanosleep (requested_time=0xbfa8ee64, remaining=0xbfa8ee64) at ../sysdeps/unix/sysv/linux/nanosleep.c:25 #3 0xb4c128fd in __sleep (seconds=0) at ../sysdeps/posix/sleep.c:55 #4 0xb68f93ea in startProcessInternal (argc=argc@entry=21, argv=argv@entry=0xbfa8ef38, waitAndExit=waitAndExit@entry=true, directly=false) at ./src/kcrash.cpp:672 #5 0xb68f9bf3 in KCrash::startProcess (argc=21, argv=0xbfa8ef38, waitAndExit=true) at ./src/kcrash.cpp:637 #6 0xb68fa0fb in KCrash::defaultCrashHandler (sig=11) at ./src/kcrash.cpp:540 #7 #8 0xb7b1a136 in KAlarmCal::KAEvent::category() const () from /usr/lib/i386-linux-gnu/libKF5AlarmCalendar.so.5abi1 #9 0x004c5c32 in AlarmCalendar::events (this=0x17ef5a0, collection=..., type=...) at /usr/include/i386-linux-gnu/qt5/QtCore/qarraydata.h:209 #10 0x004c5eab in AlarmCalendar::events (s=..., this=0x17ef5a0) at ./src/alarmcalendar.h:68 #11 AlarmCalendar::checkForDisabledAlarms (this=0x17ef5a0) at ./src/alarmcalendar.cpp:1439 #12 0x004c8a9e in AlarmCalendar::slotEventChanged (this=, event=...) at ./src/alarmcalendar.cpp:567 #13 0x004c8caf in AlarmCalendar::slotEventsAdded (this=0x17ef5a0, events=...) at /usr/include/i386-linux-gnu/qt5/QtCore/qlist.h:544 #14 0xb51ae484 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5 #15 0xb51ae90d in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5 #16 0x005b7bf2 in AkonadiModel::eventsAdded (this=0x1796c80, _t1=...) at ./obj-i686-linux-gnu/src/kalarm_bin_autogen/EWIEGA46WW/moc_akonadimodel.cpp:423 #17 0x0057dd5d in AkonadiModel::slotRowsInserted (this=, parent=..., start=, end=) at ./src/akonadimodel.cpp:1634 #18 0xb51ae484 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5 #19 0xb51ae90d in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5 #20 0xb51325c9 in QAbstractItemModel::rowsInserted(QModelIndex const&, int, int, QAbstractItemModel::QPrivateSignal) () from /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5 #21 0xb513a139 in QAbstractItemModel::endInsertRows() () from /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5 #22 0xb731390b in ?? () from /usr/lib/i386-linux-gnu/libKF5AkonadiCore.so.5abi2 #23 0xb73013b3 in ?? () from /usr/lib/i386-linux-gnu/libKF5AkonadiCore.so.5abi2 #24 0xb51ae33b in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5 #25 0xb51ae90d in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5 #26 0xb7224b56 in Akonadi::Monitor::itemAdded(Akonadi::Item const&, Akonadi::Collection const&) () from /usr/lib/i386-linux-gnu/libKF5AkonadiCore.so.5abi2 #27 0xb7232a70 in Akonadi::MonitorPrivate::emitItemsNotification(Akonadi::Protocol::ItemChangeNotification const&, QVector const&, Akonadi::Collection const&, Akonadi::Collection const&) () from /usr/lib/i386-linux-gnu/libKF5AkonadiCore.so.5abi2 #28 0xb7233198 in Akonadi::MonitorPrivate::emitNotification(QSharedPointer const&) () from /usr/lib/i386-linux-gnu/libKF5AkonadiCore.so.5abi2 #29 0xb71d8ace in ?? () from /usr/lib/i386-linux-gnu/libKF5AkonadiCore.so.5abi2 #30 0xb72351f2 in Akonadi::MonitorPrivate::flushPipeline() () from /usr/lib/i386-linux-gnu/libKF5AkonadiCore.so.5abi2 #31 0xb723556a in Akonadi::MonitorPrivate::dataAvailable() () from /usr/lib/i386-linux-gnu/libKF5AkonadiCore.so.5abi2 #32 0xb72268ad in ?? () from /usr/lib/i386-linux-gnu/libKF5AkonadiCore.so.5abi2 #33 0xb51ae33b in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5 #34 0xb51ae90d in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5 #35 0xb7207d83 in ?? () from /usr/lib/i386-linux-gnu/libKF5AkonadiCore.so.5abi2 #36 0xb71cc6ef in ?? () from /usr/lib/i386-linux-gnu/libKF5AkonadiCore.so.5abi2 #37 0xb7207dd7 in ?? () from
[kwin] [Bug 317765] Dangeling pointer in unconstrained_stacking_order
https://bugs.kde.org/show_bug.cgi?id=317765 Jiri Palecek changed: What|Removed |Added CC||jpale...@web.de -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kdesu] [Bug 389049] stuck with sudo and wrong password
https://bugs.kde.org/show_bug.cgi?id=389049 Jiri Palecek changed: What|Removed |Added CC||kdeb...@whamra.com --- Comment #9 from Jiri Palecek --- *** Bug 170155 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kdesu] [Bug 170155] doesn't report wrong password
https://bugs.kde.org/show_bug.cgi?id=170155 Jiri Palecek changed: What|Removed |Added Resolution|--- |DUPLICATE CC||jpale...@web.de Status|REPORTED|RESOLVED --- Comment #4 from Jiri Palecek --- *** This bug has been marked as a duplicate of bug 389049 *** -- You are receiving this mail because: You are watching all bug changes.
[kdesu] [Bug 292176] kdesu hang when wrong password is entered in sudo mode.
https://bugs.kde.org/show_bug.cgi?id=292176 Jiri Palecek changed: What|Removed |Added Resolution|--- |DUPLICATE CC||jpale...@web.de Status|REPORTED|RESOLVED --- Comment #27 from Jiri Palecek --- *** This bug has been marked as a duplicate of bug 389049 *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kdesu] [Bug 389049] stuck with sudo and wrong password
https://bugs.kde.org/show_bug.cgi?id=389049 Jiri Palecek changed: What|Removed |Added CC||de.tec...@gmail.com --- Comment #8 from Jiri Palecek --- *** Bug 292176 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 372305] Crash in ContrastEffect::uploadRegion
https://bugs.kde.org/show_bug.cgi?id=372305 Jiri Palecek changed: What|Removed |Added CC||jpale...@web.de --- Comment #8 from Jiri Palecek --- I just want to add that I am seeing this crash as well, after resume w/ NVidia 390.77 driver, and it seems vbo.d->persistent is true, but vbo.d->map is not pointing to accessible memory (although set). -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 388127] Kwin crashes when switching desktops
https://bugs.kde.org/show_bug.cgi?id=388127 Jiri Palecek changed: What|Removed |Added CC||jpale...@web.de -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 386370] kwin randomly crashes when switching desktops
https://bugs.kde.org/show_bug.cgi?id=386370 Jiri Palecek changed: What|Removed |Added CC||jpale...@web.de -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 73821] kioslaves should be nestable; e.g. browsing a zip inside a zip should work
https://bugs.kde.org/show_bug.cgi?id=73821 Jiri Palecek <jpale...@web.de> changed: What|Removed |Added CC||jpale...@web.de -- You are receiving this mail because: You are watching all bug changes.
[kopete] [Bug 216021] Kopete crashes when the network connection is lost [QList::*, DNSSD::ServiceBrowserPrivate::gotRemoveService, ..., OrgFreedesktopAvahiServiceBrowserInterface::ItemRemove]
https://bugs.kde.org/show_bug.cgi?id=216021 --- Comment #8 from Jiri Palecek <jpale...@web.de> --- Created attachment 111955 --> https://bugs.kde.org/attachment.cgi?id=111955=edit Full backtrace showing the nested event loop problem -- You are receiving this mail because: You are watching all bug changes.
[kopete] [Bug 216021] Kopete crashes when the network connection is lost [QList::*, DNSSD::ServiceBrowserPrivate::gotRemoveService, ..., OrgFreedesktopAvahiServiceBrowserInterface::ItemRemove]
https://bugs.kde.org/show_bug.cgi?id=216021 --- Comment #7 from Jiri Palecek <jpale...@web.de> --- This seems to be a problem with DNSSD::ServiceBrowserPrivate::gotRemoveService code. It emits a signal and then proceeds to delete some element of the m_services QList: emit m_parent->serviceRemoved(found); m_services.removeAll(found); What happens in Kopete, and particularly its Bonjour code, is that from that signal, Kopete goes offline and deletes the ServiceBrowser instance. The control then returns to gotRemovalService, which tries to do the deletion an a freed object. The best solution is probably to postpone the deletion of found to the main loop with QTimer::singleShot, because that can be made so deletion of the ServiceBrowser object automatically cancels its execution. (I've got a patch for it, tested and seems to work.) However, I wonder whether in essence all code that emits signals shouldn't be treated that way, since you don't really know what happens when the slot connected to the signal executes. I've also considered if Kopete couldn't be changed so as not to delete the ServiceBrowser, however, I haven't found a way. 1. Stopping the ServiceBrowser without actually deleting it (and then maybe restarting it) could work, but I can't see how you could do it. 2. Postponing the deletion to the main loop via ->deleteLater doesn't work, because it just so happens that the main loop can be nested in kopete. The call stack looks like this: (BonjourAccount::disconnect would be called here) 0xaffd45dd in DNSSD::ServiceBrowserPrivate::gotRemoveService (this=0x21ace40, name=..., type=..., domain=...) at ./dnssd/avahi-servicebrowser.cpp:137 ... 0xaffd8a05 in DNSSD::RemoteService::resolve (this=0x21a9e00) at ./dnssd/avahi-remoteservice.cpp:49 0xb006fefe in BonjourAccount::goingOffline (this=0x207abe0, pointer=...) at ./protocols/bonjour/bonjouraccount.cpp:273 ... 0xaffd3e01 in DNSSD::ServiceBrowser::serviceRemoved (this=0x21133f0, _t1=...) at ./obj-i686-linux-gnu/dnssd/servicebrowser.moc:111 0xaffd45c9 in DNSSD::ServiceBrowserPrivate::gotRemoveService (this=0x21ace40, name=..., type=..., domain=...) at ./dnssd/avahi-servicebrowser.cpp:136 DNSSD::RemoteService::resolve contains an event loop, which means the deferred deletion would be effective by the time control returns there. The gotRemoveService sitting up above it in the stack, would be doomed. (Also tested.) Of course this nested event loop is bad design, but what can you do? -- You are receiving this mail because: You are watching all bug changes.
[kopete] [Bug 265440] turn off wireless -> kopete crashes
https://bugs.kde.org/show_bug.cgi?id=265440 Jiri Palecek <jpale...@web.de> changed: What|Removed |Added CC||jpale...@web.de -- You are receiving this mail because: You are watching all bug changes.
[kopete] [Bug 216021] Kopete crashes when the network connection is lost [QList::*, DNSSD::ServiceBrowserPrivate::gotRemoveService, ..., OrgFreedesktopAvahiServiceBrowserInterface::ItemRemove]
https://bugs.kde.org/show_bug.cgi?id=216021 Jiri Palecek <jpale...@web.de> changed: What|Removed |Added CC||jpale...@web.de -- You are receiving this mail because: You are watching all bug changes.
[kopete] [Bug 301743] kopete crashes on NetworkManager restart
https://bugs.kde.org/show_bug.cgi?id=301743 Jiri Palecek <jpale...@web.de> changed: What|Removed |Added CC||jpale...@web.de -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 372114] Crash in threaded KWin::X11StandalonePlatform::createOpenGLSafePoint
https://bugs.kde.org/show_bug.cgi?id=372114 --- Comment #32 from Jiri Palecek <jpale...@web.de> --- (In reply to Martin Flöser from comment #30) > KSharedConfig::openConfig introduces a slight other problem: internally KWin > uses the kwinApp()->config() to make it possible to have config not use > kwinrc, but different config files (that is extensively used by e.g. > autotests). The idea behind it is that we can swap out the config at runtime > for different form factors (tablet -> notebook -> tablet). While that's not > yet fully implemented, the config part is prepared. If we use openConfig > again we don't know whether it's the same or not. Oh I see. > If KSharedConfig::openConfig(kwinApp()->config()->name()) works as well, > that might be a solution. Anyway if you have a patch, please put it on > phabricator.kde.org and use #KWin as review group. Good! If KSharedConfig::openConfig(kwinApp()->config()->name()) is acceptable in principle, so be it. I'll just test it a bit more. About the phabricator: is there some tutorial or manual about how to use it? I have to say I'm not that familiar with KDE dev process. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 372114] Crash in threaded KWin::X11StandalonePlatform::createOpenGLSafePoint
https://bugs.kde.org/show_bug.cgi?id=372114 --- Comment #29 from Jiri Palecek <jpale...@web.de> --- Well the patch does actually help, because while the KConfig instances are not thread-safe, KSharedConfig::openConfig _is_ (see https://api.kde.org/frameworks/kconfig/html/classKSharedConfig.html). Access to the file is locked on the file level. Dreaming about making KConfig thread-safe (or almost any other Qt or KDE classes for that matter) is an utopia, and totally unnecessary in this case. As for the freezes in OpenGL, I don't deny them. However, the current method of detecting them gives an awful lot of false detections, and maybe something could be done about that. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 384316] New: Crash on SIGTERM related to threading issues
https://bugs.kde.org/show_bug.cgi?id=384316 Bug ID: 384316 Summary: Crash on SIGTERM related to threading issues Product: ksmserver Version: 5.8.7 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: l.lu...@kde.org Reporter: jpale...@web.de Target Milestone: --- Created attachment 107666 --> https://bugs.kde.org/attachment.cgi?id=107666=edit Proposed patch Hello I got an odd crash from ksmserver with this backtrace: Core was generated by `/usr/bin/ksmserver'. #0 0xb770dcf9 in __kernel_vsyscall () [Current thread is 1 (Thread 0xaf2bfb40 (LWP 2170))] (gdb) bt #0 0xb770dcf9 in __kernel_vsyscall () #1 0xb758308f in waitpid () at ../sysdeps/unix/syscall-template.S:84 #2 0xb49b0b6e in ?? () from /usr/lib/i386-linux-gnu/libKF5Crash.so.5 #3 0xb49b1860 in KCrash::defaultCrashHandler(int) () from /usr/lib/i386-linux-gnu/libKF5Crash.so.5 #4 #5 0xb770dcf9 in __kernel_vsyscall () #6 0xb74fddc0 in __libc_signal_restore_set (set=0xaf2be080) at ../sysdeps/unix/sysv/linux/nptl-signals.h:79 #7 __GI_raise (sig=6) at ../sysdeps/unix/sysv/linux/raise.c:48 #8 0xb74ff287 in __GI_abort () at abort.c:89 #9 0xb4d100d3 in qt_message_fatal (context=..., message=...) at global/qlogging.cpp:1682 #10 QMessageLogger::fatal (this=0xaf2be338, msg=0xb4f94f40 "ASSERT failure in %s: \"%s\", file %s, line %d") at global/qlogging.cpp:793 #11 0xb4d0b06a in qt_assert_x (where=0xb504aced "QCoreApplication::sendEvent", what=0xae902e38 "Cannot send events to objects owned by a different thread. Current thread 804b9708. Receiver '' (of type 'QProcess') was created in thread 804869f8", file=0xb504ac98 "kernel/qcoreapplication.cpp", line=541) at global/qglobal.cpp:3089 #12 0xb4edd18a in QCoreApplicationPrivate::checkReceiverThread (receiver=) at kernel/qcoreapplication.cpp:533 #13 0xb582d1f2 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/i386-linux-gnu/libQt5Widgets.so.5 #14 0xb4eddab2 in QCoreApplication::notifyInternal2 (receiver=0x80505a38, event=0xaf2be6e8) at kernel/qcoreapplication.cpp:988 #15 0xb4f15644 in QCoreApplication::sendEvent (event=0xaf2be6e8, receiver=) at kernel/qcoreapplication.h:231 #16 QObjectPrivate::setParent_helper (this=0x804fdea8, o=) at kernel/qobject.cpp:1996 #17 0xb4f15b2c in QObject::~QObject (this=, __in_chrg=) at kernel/qobject.cpp:1048 #18 0xb4f1b7ff in QSocketNotifier::~QSocketNotifier (this=0x804fdf70, __in_chrg=) at kernel/qsocketnotifier.cpp:162 #19 0xb4f1b82a in QSocketNotifier::~QSocketNotifier (this=0x804fdf70, __in_chrg=) at kernel/qsocketnotifier.cpp:165 #20 0xb4e6f19d in QProcessPrivate::waitForDeadChild (this=0x804fd878) at io/qprocess_unix.cpp:919 #21 0xb4e17c21 in QProcessPrivate::_q_processDied (this=0x804fd878) at io/qprocess.cpp:1128 #22 0xb4e6effd in QProcessPrivate::waitForFinished (this=, msecs=) at io/qprocess_unix.cpp:895 #23 0xb4e111f1 in QProcess::waitForFinished (this=0x80505a38, msecs=3) at io/qprocess.cpp:1922 #24 0xb4e11a3d in QProcess::~QProcess (this=, __in_chrg=) at io/qprocess.cpp:1261 #25 0xb611493d in KProcess::~KProcess() () from /usr/lib/i386-linux-gnu/libKF5CoreAddons.so.5 #26 0xb611497a in KProcess::~KProcess() () from /usr/lib/i386-linux-gnu/libKF5CoreAddons.so.5 #27 0xb4f14b13 in QObjectPrivate::deleteChildren (this=0x804ecc60) at kernel/qobject.cpp:1970 #28 0xb4f15af3 in QObject::~QObject (this=, __in_chrg=) at kernel/qobject.cpp:1041 #29 0xb769c6d3 in KSMServer::~KSMServer (this=0x804f0998, __in_chrg=) at ./ksmserver/server.cpp:728 #30 0xb769f01a in KSMServer::~KSMServer (this=0x804f0998, __in_chrg=) at ./ksmserver/server.cpp:733 #31 0xb769adba in sighandler (sig=15) at ./ksmserver/server.cpp:539 #32 Apparently, ksmserver got a SIGTERM signal which resulted in a SIGABRT due to the SIGTERM being received in another thread than the main thread (or, more importantly, the thread where the objects that are subsequently destroyed live), as we can see from the assertion message. Also, the code doesn't seem safe - in a signal handler, only a limited number of functions can be called, and I'm pretty sure this doesn't include QObject functions. To remedy both issues, I propose to use the self-pipe trick - alert the main loop in the signal handler by writing to a pipe (or, in this case, socket), and terminate ksmserver gracefully. See the attached patch. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 372114] Crash in threaded KWin::X11StandalonePlatform::createOpenGLSafePoint
https://bugs.kde.org/show_bug.cgi?id=372114 --- Comment #27 from Jiri Palecek <jpale...@web.de> --- ... oh and mind you, the patch actually changes the situation from an unexpected crash on SIGSEGV to a SIGABRT anticipated by the code, so DrKonqi gets triggered either way. This sould be thought over as well IMHO. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 372114] Crash in threaded KWin::X11StandalonePlatform::createOpenGLSafePoint
https://bugs.kde.org/show_bug.cgi?id=372114 --- Comment #26 from Jiri Palecek <jpale...@web.de> --- Created attachment 107663 --> https://bugs.kde.org/attachment.cgi?id=107663=edit Proposed patch -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 372114] Crash in threaded KWin::X11StandalonePlatform::createOpenGLSafePoint
https://bugs.kde.org/show_bug.cgi?id=372114 Jiri Palecek <jpale...@web.de> changed: What|Removed |Added CC||jpale...@web.de --- Comment #25 from Jiri Palecek <jpale...@web.de> --- Hello the problem here seems to be the fact that KConfig instances are *totally* not thread safe, and the freeze protection thread uses the same one as the main thread. When they stomp over each other, this crash ensues. I'll attach a proposed patch to use a different KConfig instance. On a deeper note, is that freeze check really necessary, safe and effective? I would say 99%+ of times the freeze alarm goes off, it is actually the system thrashing after startup/closing a big application (like a game), when all of the other applications are resizing their windows/repainting and not really an opengl driver freeze (of these duplicates, only bugs 372078, 373485 seem to be genuinely related to the graphics. Any thoughts on that? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 381974] Start menu crashed
https://bugs.kde.org/show_bug.cgi?id=381974 --- Comment #7 from Jiri Palecek <jpale...@web.de> --- Thanks Eike, good to hear that. Could you elaborate on how is the issue likely going to be resolved? I mean, as a problem of Qt or Plasma? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 381974] Start menu crashed
https://bugs.kde.org/show_bug.cgi?id=381974 Jiri Palecek <jpale...@web.de> changed: What|Removed |Added CC||jpale...@web.de --- Comment #4 from Jiri Palecek <jpale...@web.de> --- David Edmundson this is not a duplicate of bug 342763, the backtraces are totally different (for one thing, the crash isn't occuring on slot activation). Could you consider rethinking this bug? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 381974] Start menu crashed
https://bugs.kde.org/show_bug.cgi?id=381974 --- Comment #3 from Jiri Palecek <jpale...@web.de> --- Hello I tried to get to the bottom of this crash, because I encountered it several times (about once a week-once a month). My system is Debian sid, Plasma 5.8.7 and Qt 5.7.1. The backtrace I got was: Thread 1 (Thread 0xafa61200 (LWP 2190)): #0 0xb77d8cf9 in __kernel_vsyscall () #1 0xb4d412fa in nanosleep () at ../sysdeps/unix/syscall-template.S:84 #2 0xb4d41225 in __sleep (seconds=0) at ../sysdeps/posix/sleep.c:55 #3 0xb77a1c3a in ?? () from /usr/lib/i386-linux-gnu/libKF5Crash.so.5 #4 0xb77a23e0 in ?? () from /usr/lib/i386-linux-gnu/libKF5Crash.so.5 #5 0xb77a2860 in KCrash::defaultCrashHandler(int) () from /usr/lib/i386-linux-gnu/libKF5Crash.so.5 #6 #7 QSortFilterProxyModelPrivate::updateChildrenMapping (this=this@entry=0x80c51650, source_parent=..., parent_mapping=parent_mapping@entry=0x81a6f338, start=, end=, delta_item_count=, remove=true, orient=Qt::Vertical) at itemmodels/qsortfilterproxymodel.cpp:975 #8 0xb51ecd3f in QSortFilterProxyModelPrivate::source_items_removed (orient=Qt::Vertical, end=, start=0, source_parent=..., this=0x80c51650) at itemmodels/qsortfilterproxymodel.cpp:917 ---Type to continue, or q to quit--- #9 QSortFilterProxyModelPrivate::_q_sourceRowsRemoved (this=0x80c51650, source_parent=..., start=0, end=) at itemmodels/qsortfilterproxymodel.cpp:1424 #10 0xb51f4b8d in QSortFilterProxyModel::qt_static_metacall (_o=0x80c4af78, _c=QMetaObject::InvokeMetaMethod, _id=14, _a=0xbfc79d1c) at .moc/moc_qsortfilterproxymodel.cpp:211 #11 0xb5257fdb in QMetaObject::activate (sender=, signalOffset=, local_signal_index=, argv=) at kernel/qobject.cpp:3740 #12 0xb525885d in QMetaObject::activate (sender=0x80c5c490, m=0xb54a1fd0 , local_signal_index=12, argv=0xbfc79d1c) at kernel/qobject.cpp:3602 #13 0xb52d6821 in QAbstractItemModel::rowsRemoved (this=0x80c5c490, _t1=..., _t2=, _t3=) at .moc/moc_qabstractitemmodel.cpp:615 #14 0xb51cc349 in QAbstractItemModel::endRemoveRows (this=0x80c5c490) at itemmodels/qabstractitemmodel.cpp:2715 #15 0xa42f76f2 in TaskManager::TaskGroupingProxyModel::Private::sourceRowsAboutToBeRemoved (this=0x80c31898, parent=..., first=7, last=7) at ./libtaskmanager/taskgroupingproxymodel.cpp:197 #16 0xa42fafed in TaskManager::TaskGroupingProxyModel::qt_static_metacall (_o=0x80c5c490, _c=QMetaObject::InvokeMetaMethod, _id=7, _a=0xbfc79f6c) at ./obj-i686-linux-gnu/libtaskmanager/moc_taskgroupingproxymodel.cpp:152 #17 0xb5257fdb in QMetaObject::activate (sender=, signalOffset=, local_signal_index=, argv=) at kernel/qobject.cpp:3740 #18 0xb525885d in QMetaObject::activate (sender=0x80c5c048, m=0xb54a1fd0 , local_signal_index=11, argv=0xbfc79f6c) at kernel/qobject.cpp:3602 #19 0xb52d67b1 in QAbstractItemModel::rowsAboutToBeRemoved (this=0x80c5c048, _t1=..., _t2=, _t3=) at .moc/moc_qabstractitemmodel.cpp:608 #20 0xb51cbc00 in QAbstractItemModel::beginRemoveRows (this=0x80c5c048, parent=..., first=7, last=7) at itemmodels/qabstractitemmodel.cpp:2698 #21 0xb51f24f0 in QSortFilterProxyModelPrivate::remove_proxy_interval (emit_signal=true, orient=Qt::Vertical, proxy_parent=..., proxy_end=7, proxy_start=7, proxy_to_source=..., source_to_proxy=..., this=0x80c94388) at itemmodels/qsortfilterproxymodel.cpp:583 #22 QSortFilterProxyModelPrivate::remove_source_items (this=, source_to_proxy=..., proxy_to_source=..., source_items=..., source_parent=..., orient=Qt::Vertical, emit_signal=true) at itemmodels/qsortfilterproxymodel.cpp:565 #23 0xb51f26cb in QSortFilterProxyModelPrivate::source_items_about_to_be_removed (this=, source_parent=..., start=, end=, orient=) at itemmodels/qsortfilterproxymodel.cpp:866 #24 0xb51f4b6d in QSortFilterProxyModelPrivate::_q_sourceRowsAboutToBeRemoved (end=7, start=, source_parent=..., this=) at itemmodels/qsortfilterproxymodel.cpp:1417 #25 QSortFilterProxyModel::qt_static_metacall (_o=0x80c5c048, _c=QMetaObject::InvokeMetaMethod, _id=13, _a=0xbfc7a23c) at .moc/moc_qsortfilterproxymodel.cpp:210 #26 0xb5257fdb in QMetaObject::activate (sender=, signalOffset=, local_signal_index=, argv=) at kernel/qobject.cpp:3740 #27 0xb525885d in QMetaObject::activate (sender=0x80c5a490, m=0xb54a1fd0 , local_signal_index=11, argv=0xbfc7a23c) at kernel/qobject.cpp:3602 #28 0xb52d67b1 in QAbstractItemModel::rowsAboutToBeRemoved (this=0x80c5a490, _t1=..., _t2=, _t3=) at .moc/moc_qabstractitemmodel.cpp:608 #29 0xb51cbc00 in QAbstractItemModel::beginRemoveRows (this=0x80c5a490, parent=..., first=7, last=7) at itemmodels/qabstractitemmodel.cpp:2698 #30 0xa482d386 in KConcatenateRowsProxyModelPrivate::slotRowsAboutToBeRemoved (this=0x80c5a448, start=7, end=7) at ./src/kconcatenaterowsproxymodel.cpp:241 #31 0xa482e7cd in KConcatenateRowsProxyModel::qt_static_metacall (_o=0x80c5a490, _c=QMetaObject::InvokeMetaMethod, _id=2, _a=0xbfc7a45c) at ./obj-i686-linux-gnu/src/moc_kconcatenaterowsproxymodel.cpp:130 #32 0xb5257fdb in QMetaObject::activate (sender=, signal
[konsole] [Bug 367899] Please consider sanitizing middle-click-pasted text control characters for security reasons
https://bugs.kde.org/show_bug.cgi?id=367899 Jiri Palecek <jpale...@web.de> changed: What|Removed |Added CC||jpale...@web.de --- Comment #3 from Jiri Palecek <jpale...@web.de> --- Maybe showing the text being pasted with a warning would suffice. What do you think? -- You are receiving this mail because: You are watching all bug changes.
