Bug 285939 - System Settings crashed right after the root partition became full
Summary: System Settings crashed right after the root partition became full
Status: RESOLVED WORKSFORME
Alias: None
Product: kdelibs
Classification: Unmaintained
Component: kshareddatacache (show other bugs)
Version: unspecified
Platform: Fedora RPMs Linux
: NOR crash
Target Milestone: ---
Assignee: kdelibs bugs
URL:
Keywords:
: 308145 (view as bug list)
Depends on:
Blocks:
 
Reported: 2011-11-06 22:07 UTC by Andrei ILIE
Modified: 2021-01-13 04:33 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Andrei ILIE 2011-11-06 22:07:41 UTC
Application: systemsettings (1.0)
KDE Platform Version: 4.6.5 (4.6.5)
Qt Version: 4.7.4
Operating System: Linux 2.6.40.6-0.fc15.x86_64 x86_64
Distribution (Platform): Fedora RPMs

-- Information about the crash:
- What I was doing when the application crashed:
The root partition became full and, right after that, the "System Settings" app crashed. A few second later, KDE displayed, in the notifications area, a warning about low disk space ...


It's a pretty common situation for the HDD / SSD to become full and I think an robust app should withstand this tragedy :)

-- Backtrace:
Application: System Settings (systemsettings), signal: Bus error
82	T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS)
[KCrash Handler]
#6  __memcpy_ssse3 () at ../sysdeps/x86_64/multiarch/memcpy-ssse3.S:2615
#7  0x00000038a163cfa2 in KSharedDataCache::insert (this=<optimized out>, key=..., data=...) at /usr/include/bits/string3.h:52
#8  0x00000038a33f373b in KIconLoaderPrivate::insertCachedPixmapWithPath (this=0xf5b8f0, key=..., data=..., path=...) at /usr/src/debug/kdelibs-4.6.5/kdeui/icons/kiconloader.cpp:841
#9  0x00000038a33f41d1 in KIconLoader::loadIcon (this=0xf55370, _name=<optimized out>, group=KIconLoader::Desktop, size=24, state=0, overlays=..., path_store=0x0, canReturnNull=false) at /usr/src/debug/kdelibs-4.6.5/kdeui/icons/kiconloader.cpp:1319
#10 0x00000038a33eb5cf in KIconEngine::pixmap (this=<optimized out>, size=..., mode=<optimized out>, state=<optimized out>) at /usr/src/debug/kdelibs-4.6.5/kdeui/icons/kiconengine.cpp:103
#11 0x000000389b45e015 in QIcon::pixmap (this=<optimized out>, size=<optimized out>, mode=<optimized out>, state=<optimized out>) at image/qicon.cpp:676
#12 0x0000000000410c4a in ToolTipManager::generateToolTipLine (this=<optimized out>, item=0x7fff003e9b10, toolTip=0x1373da0, iconSize=..., comment=<optimized out>) at /usr/src/debug/kdebase-workspace-4.6.5/systemsettings/app/ToolTips/tooltipmanager.cpp:234
#13 0x00000000004110a0 in ToolTipManager::createTipContent (this=0x116fc90, item=...) at /usr/src/debug/kdebase-workspace-4.6.5/systemsettings/app/ToolTips/tooltipmanager.cpp:191
#14 0x0000000000411225 in ToolTipManager::showToolTip (this=0x116fc90, menuItem=...) at /usr/src/debug/kdebase-workspace-4.6.5/systemsettings/app/ToolTips/tooltipmanager.cpp:137
#15 0x00000000004113af in ToolTipManager::prepareToolTip (this=<optimized out>) at /usr/src/debug/kdebase-workspace-4.6.5/systemsettings/app/ToolTips/tooltipmanager.cpp:128
#16 0x000000000041144c in ToolTipManager::qt_metacall (this=0x116fc90, _c=QMetaObject::InvokeMetaMethod, _id=<optimized out>, _a=0x7fff003e9d00) at /usr/src/debug/kdebase-workspace-4.6.5/x86_64-redhat-linux-gnu/systemsettings/app/tooltipmanager.moc:77
#17 0x000000389ad6cfea in QMetaObject::activate (sender=0x116f690, m=<optimized out>, local_signal_index=<optimized out>, argv=0x0) at kernel/qobject.cpp:3278
#18 0x000000389ad708d9 in QObject::event (this=0x116f690, e=<optimized out>) at kernel/qobject.cpp:1181
#19 0x000000389b3b9324 in notify_helper (e=0x7fff003ea400, receiver=0x116f690, this=0xed44a0) at kernel/qapplication.cpp:4481
#20 QApplicationPrivate::notify_helper (this=0xed44a0, receiver=0x116f690, e=0x7fff003ea400) at kernel/qapplication.cpp:4453
#21 0x000000389b3be1b1 in QApplication::notify (this=0x7fff003ea700, receiver=0x116f690, e=0x7fff003ea400) at kernel/qapplication.cpp:4360
#22 0x00000038a34431c6 in KApplication::notify (this=0x7fff003ea700, receiver=0x116f690, event=0x7fff003ea400) at /usr/src/debug/kdelibs-4.6.5/kdeui/kernel/kapplication.cpp:311
#23 0x000000389ad5a20c in QCoreApplication::notifyInternal (this=0x7fff003ea700, receiver=0x116f690, event=0x7fff003ea400) at kernel/qcoreapplication.cpp:787
#24 0x000000389ad86c02 in sendEvent (event=0x7fff003ea400, receiver=<optimized out>) at kernel/qcoreapplication.h:215
#25 QTimerInfoList::activateTimers (this=0xeccb00) at kernel/qeventdispatcher_unix.cpp:603
#26 0x000000389ad84468 in timerSourceDispatch (source=<optimized out>) at kernel/qeventdispatcher_glib.cpp:184
#27 idleTimerSourceDispatch (source=<optimized out>) at kernel/qeventdispatcher_glib.cpp:231
#28 0x00000038934427ed in g_main_dispatch (context=0xecb8e0) at gmain.c:2441
#29 g_main_context_dispatch (context=0xecb8e0) at gmain.c:3014
#30 0x0000003893442fc8 in g_main_context_iterate (context=0xecb8e0, block=<optimized out>, dispatch=1, self=<optimized out>) at gmain.c:3092
#31 0x000000389344325c in g_main_context_iteration (context=0xecb8e0, may_block=1) at gmain.c:3155
#32 0x000000389ad84dcf in QEventDispatcherGlib::processEvents (this=0xea09e0, flags=<optimized out>) at kernel/qeventdispatcher_glib.cpp:422
#33 0x000000389b45c12e in QGuiEventDispatcherGlib::processEvents (this=<optimized out>, flags=<optimized out>) at kernel/qguieventdispatcher_glib.cpp:207
#34 0x000000389ad59722 in QEventLoop::processEvents (this=<optimized out>, flags=...) at kernel/qeventloop.cpp:149
#35 0x000000389ad5991f in QEventLoop::exec (this=0x7fff003ea690, flags=...) at kernel/qeventloop.cpp:201
#36 0x000000389ad5da67 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1064
#37 0x000000000040ac55 in main (argc=5, argv=0x7fff003ea9c8) at /usr/src/debug/kdebase-workspace-4.6.5/systemsettings/app/main.cpp:49

Reported using DrKonqi
Comment 1 Michael Pyne 2011-11-08 22:54:38 UTC
This should be rectified already since KSharedDataCache uses posix_fallocate() to ensure that there is sufficient disk space for the entire mapped memory segment... although it's possible that if you've been running KDE 4 for awhile that the cache had been created before that feature was introduced into KDE.

The only thing I'm realistically able to do from there is a fairly involved method to capture thread-directed signals, but that is not compatible with other parts of kdelibs (and is dangerous in general for library code...).

:-/
Comment 2 Christoph Feck 2014-06-25 09:44:35 UTC
*** Bug 308145 has been marked as a duplicate of this bug. ***
Comment 3 Justin Zobel 2020-12-14 01:32:48 UTC
Thank you for the crash reports.

As it has been a while since this was reported, can you please test and confirm if this issue is still occurring or if this bug report can be marked as resolved.

I have set the bug status to "needsinfo" pending your response, please change back to "reported" or "resolved/worksforme" when you respond, thank you.
Comment 4 Bug Janitor Service 2020-12-29 04:34:17 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 5 Bug Janitor Service 2021-01-13 04:33:49 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!