Bug 189805 - The application KDE Daemon (kded4) crashed and caused the signal 11 (SIGSEGV).
Summary: The application KDE Daemon (kded4) crashed and caused the signal 11 (SIGSEGV).
Status: RESOLVED WORKSFORME
Alias: None
Product: kdelibs
Classification: Frameworks and Libraries
Component: kded (show other bugs)
Version: 4.2.2
Platform: unspecified Linux
: NOR crash
Target Milestone: ---
Assignee: David Faure
URL:
Keywords: investigated, triaged
Depends on:
Blocks:
 
Reported: 2009-04-16 15:37 UTC by richu
Modified: 2018-10-21 04:24 UTC (History)
6 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description richu 2009-04-16 15:37:10 UTC
Version:            (using KDE 4.2.2)
OS:                Linux
Installed from:    I Don't Know

The application KDE Daemon (kded4) crashed and caused the signal 11 (SIGSEGV).
Comment 1 Dario Andres 2009-04-17 17:13:20 UTC
A crash without a trace and without information is not useful.
What were you doing when the application crashed? Updating your system packages or installing a new program? Can you reproduce the crash at will ?
Thanks
Comment 2 richu 2009-04-21 15:20:41 UTC
hi,

the error message came when i was running the update manager, i was not installing any software.

today also i got the same error message when i tried to run update manager.

it does download the files.
Comment 3 Dario Andres 2009-04-21 18:09:07 UTC
This may be related to bug 190093
Comment 4 Dario Andres 2009-05-01 17:00:24 UTC
If you still experience the crash, may you read http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports and post a complete backtrace here? Thanks :)
Comment 5 kostaspd 2009-05-12 00:47:35 UTC
i had exactly the same problem as the above "the error message came when i was running the update manager, i was not installing any software."
Comment 6 Dario Andres 2009-05-12 16:29:05 UTC
@kostaspd: If you can reproduce the crash at will, may you read http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports and post a complete backtrace in a NEW report? You may need to install some debug symbols packages. Also, do not forget to say what KDE4 version and Linux distribution are you using. Thanks
Comment 7 George Goldberg 2009-06-04 22:19:26 UTC
Marking this bug as NEEDSINFO as there's nothing we can do about it without more information. @richu: If you can provide more information as requested by Dario in comment #4, please feel free to reopen the bug report.
Comment 8 Richard Walker 2009-06-10 20:10:13 UTC
Fresh install of Mandriva 2009.1 with default Gnome desktop. Added task-kde4-4.2.2-5mdv2009.1.rpm and changed default desktop to KDE. Couple of days later I finally allowed the update daemon to show me the list of (64) packages and accepted them all. The crash did not stop the update process or disturb then desktop in any way. The desktop is configured to cover 2 screens (same 1280x1024 resolution on each) using xinerama. Some anomalies then appeared; desktop wallpaper swapped from one screen to the other and took desktop icons with it. Following day wallpaper is still swapped and default icons are now on both screens. This is the day when the crash was reported. Details from crash pop-up notification screen copied below.

This backtrace appears to be of no use.
This is probably because your packages are built in a way which prevents creation of proper backtraces, or the stack frame was seriously corrupted in the crash.

(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0x7fe486d1a700 (LWP 5990)]
0x00007fe48665ec31 in nanosleep () from /lib64/libc.so.6
[Current thread is 1 (Thread 0x7fe486d1a700 (LWP 5990))]

Thread 1 (Thread 0x7fe486d1a700 (LWP 5990)):
#0  0x00007fe48665ec31 in nanosleep () from /lib64/libc.so.6
#1  0x00007fe48665ea2c in sleep () from /lib64/libc.so.6
#2  0x00007fe4859a25af in ?? () from /usr/lib64/libkdeui.so.5
#3  0x00007fe4859a2eba in KCrash::defaultCrashHandler () from /usr/lib64/libkdeui.so.5
#4  <signal handler called>
#5  0x00007fe4853ba188 in ?? () from /usr/lib64/libkio.so.5
#6  0x00007fe4853bb261 in ?? () from /usr/lib64/libkio.so.5
#7  0x00007fe4853bdf78 in ?? () from /usr/lib64/libkio.so.5
#8  0x00007fe4862dedd2 in QMetaObject::activate () from /usr/lib64/libQtCore.so.4
#9  0x00007fe48631601e in QSocketNotifier::activated () from /usr/lib64/libQtCore.so.4
#10 0x00007fe4862e3a33 in QSocketNotifier::event () from /usr/lib64/libQtCore.so.4
#11 0x00007fe48425749d in QApplicationPrivate::notify_helper () from /usr/lib64/libQtGui.so.4
#12 0x00007fe48425f68a in QApplication::notify () from /usr/lib64/libQtGui.so.4
#13 0x00007fe4859400db in KApplication::notify () from /usr/lib64/libkdeui.so.5
#14 0x00007fe4862c935c in QCoreApplication::notifyInternal () from /usr/lib64/libQtCore.so.4
#15 0x00007fe4862f2c69 in ?? () from /usr/lib64/libQtCore.so.4
#16 0x00007fe483512e91 in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0
#17 0x00007fe483516540 in ?? () from /usr/lib64/libglib-2.0.so.0
#18 0x00007fe4835166dc in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#19 0x00007fe4862f29ef in QEventDispatcherGlib::processEvents () from /usr/lib64/libQtCore.so.4
#20 0x00007fe4842ee64f in ?? () from /usr/lib64/libQtGui.so.4
#21 0x00007fe4862c7c02 in QEventLoop::processEvents () from /usr/lib64/libQtCore.so.4
#22 0x00007fe4862c7fcd in QEventLoop::exec () from /usr/lib64/libQtCore.so.4
#23 0x00007fe4862ca294 in QCoreApplication::exec () from /usr/lib64/libQtCore.so.4
#24 0x00007fe48692b257 in kdemain () from /usr/lib64/libkdeinit4_kded4.so
#25 0x00007fe4865dc446 in __libc_start_main () from /lib64/libc.so.6
#26 0x0000000000400609 in _start ()
Comment 9 Dario Andres 2009-06-20 22:49:33 UTC
@Richard Walker: thanks for the detailed explanation. The crash could be related or not to the originally reported issue. If you experience this crash regularly could you please file a new bug report about it including all the useful information you already provided? Thanks a lot
Comment 10 Richard Walker 2009-06-22 19:33:58 UTC
On Saturday 20 June 2009 21:49:35 Dario Andres wrote:
> https://bugs.kde.org/show_bug.cgi?id=189805
>
>
>
>
>
> --- Comment #9 from Dario Andres <andresbajotierra gmail com>  2009-06-20
> 22:49:33 --- @Richard Walker: thanks for the detailed explanation. The
> crash could be related or not to the originally reported issue. If you
> experience this crash regularly could you please file a new bug report
> about it including all the useful information you already provided? Thanks
> a lot

Sorry Dario, it hasn't happened again. Or perhaps it has. It is very difficult 
to be sure. Certainly this KDE4.2.2 environment has proved quite challenging 
with so many familiar KDE3.5.10 features missing or replaced by seemingly 
less complete alternatives. I have certainly experienced many more 
desktop/application crashes in the last few weeks than in the last two or 
three years. I expect to be reverting to 3.5 very soon.

Richard
Comment 11 Amol Arakh 2009-07-28 03:17:00 UTC
A Fatal Error Occurred
The application KDE Daemon (kded4) crashed and caused the signal 11 (SIGSEGV)
Comment 12 Andrew Crouthamel 2018-09-20 03:14:24 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 set the bug status 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 13 Andrew Crouthamel 2018-10-21 04:24:59 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!