This Problem is offen come on the desktop screen that report the bug signal crashed Reproducible: Always Steps to Reproduce: 1.when the Fedora is Re-stared 2. 3. Actual Results: No prblem is occured only one Report bug window is open on the screen with red alert Expected Results: No window should not come on the desktops
Without a proper backtrace, nobody can guess out what has happened. You can get the backtrace by switching to the second tab when the "Report bug window" appears. Paste it here. Also, Fedora 15 is outdated. You are probably using outdated KDE installation.
Thanks for your quick response, so How should I upgrade to Fedora KDE 17 from Fedora KDE 15, Is all the installed applications are remain the same If I upgrade to Fedora KDE 17. Please guide me which is the best spin to install to My desktop. Thanking you On Sat, Sep 29, 2012 at 8:23 AM, Jekyll Wu <adaptee@gmail.com> wrote: > https://bugs.kde.org/show_bug.cgi?id=307566 > > Jekyll Wu <adaptee@gmail.com> changed: > > What |Removed |Added > > ---------------------------------------------------------------------------- > Status|UNCONFIRMED |NEEDSINFO > Resolution|--- |BACKTRACE > > --- Comment #1 from Jekyll Wu <adaptee@gmail.com> --- > Without a proper backtrace, nobody can guess out what has happened. You > can > get the backtrace by switching to the second tab when the "Report bug > window" > appears. Paste it here. > > Also, Fedora 15 is outdated. You are probably using outdated KDE > installation. > > -- > You are receiving this mail because: > You reported the bug. >
Created attachment 74234 [details] kded4-20120929-161147.kcrash I'm not a daily fedora user, so I can only point you to http://fedoraproject.org/wiki/Upgrading_Fedora_using_yum But upgrading is a bit off-topic. You should first try to provide a backtrace using your current installation.
Once again thank full to your Here I am attached the backtrace that I had saved, One more thing I would like say is, I am this is the first time I am used to install the fedora, I very happy about Fedora KDE 15, Ok please check the backtrace is it usefull to debug, if not please guide me how to save the back trace. Thanking you On 9/29/12, Jekyll Wu <adaptee@gmail.com> wrote: > https://bugs.kde.org/show_bug.cgi?id=307566 > > --- Comment #3 from Jekyll Wu <adaptee@gmail.com> --- > I'm not a daily fedora user, so I can only point you to > http://fedoraproject.org/wiki/Upgrading_Fedora_using_yum > > But upgrading is a bit off-topic. You should first try to provide a > backtrace > using your current installation. > > -- > You are receiving this mail because: > You reported the bug. >
Paste the crash report inline for better searching ------------------------------------------------------------------------------------------ Application: kded4 ($Id$) KDE Platform Version: 4.6.5 (4.6.5) Qt Version: 4.7.4 Operating System: Linux 2.6.43.8-1.fc15.i686 i686 -- Information about the crash: <In detail, tell us what you were doing when the application crashed.> The crash can be reproduced every time. -- Backtrace: Application: KDE Daemon (kded4), signal: Segmentation fault [Current thread is 1 (Thread 0xb76fd780 (LWP 3234))] Thread 3 (Thread 0xb444db70 (LWP 3246)): #0 0x4bb12564 in __pthread_mutex_unlock_usercnt () from /lib/libpthread.so.0 #1 0x4bbfcc13 in ?? () from /lib/libglib-2.0.so.0 #2 0x4bbfd457 in g_main_loop_run () from /lib/libglib-2.0.so.0 #3 0xb4507032 in ?? () from /lib/libgio-2.0.so.0 #4 0x4bc24535 in ?? () from /lib/libglib-2.0.so.0 #5 0x4bb0fa2e in start_thread () from /lib/libpthread.so.0 #6 0x4ba5581e in clone () from /lib/libc.so.6 Thread 2 (Thread 0xb3affb70 (LWP 3247)): #0 0x4bb2fc60 in clock_gettime () from /lib/librt.so.1 #1 0x4c11c6a6 in ?? () from /usr/lib/libQtCore.so.4 #2 0x4c1efa87 in ?? () from /usr/lib/libQtCore.so.4 #3 0x4c1efdeb in ?? () from /usr/lib/libQtCore.so.4 #4 0x4c1ee673 in ?? () from /usr/lib/libQtCore.so.4 #5 0x4c1ee70d in ?? () from /usr/lib/libQtCore.so.4 #6 0x4bbfbb5c in g_main_context_prepare () from /lib/libglib-2.0.so.0 #7 0x4bbfc9d8 in ?? () from /lib/libglib-2.0.so.0 #8 0x4bbfd06f in g_main_context_iteration () from /lib/libglib-2.0.so.0 #9 0x4c1ef177 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4 #10 0x4c1bfe1e in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4 #11 0x4c1c0071 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4 #12 0x4c0c1bac in QThread::exec() () from /usr/lib/libQtCore.so.4 #13 0x4c1a041e in ?? () from /usr/lib/libQtCore.so.4 #14 0x4c0c4ae4 in ?? () from /usr/lib/libQtCore.so.4 #15 0x4bb0fa2e in start_thread () from /lib/libpthread.so.0 #16 0x4ba5581e in clone () from /lib/libc.so.6 Thread 1 (Thread 0xb76fd780 (LWP 3234)): [KCrash Handler] #7 0x002d0000 in ?? () #8 0xb4fc84d2 in ?? () from /usr/lib/kde4/kded_networkmanagement.so #9 0xb4fc898a in ?? () from /usr/lib/kde4/kded_networkmanagement.so #10 0xb4fd1167 in ?? () from /usr/lib/kde4/kded_networkmanagement.so #11 0xb4fd23a3 in ?? () from /usr/lib/kde4/kded_networkmanagement.so #12 0xb4fc5e13 in ?? () from /usr/lib/kde4/kded_networkmanagement.so #13 0xb4fc5137 in ?? () from /usr/lib/kde4/kded_networkmanagement.so #14 0x4c1c728e in QMetaObject::metacall(QObject*, QMetaObject::Call, int, void**) () from /usr/lib/libQtCore.so.4 #15 0x4c1d51aa in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/libQtCore.so.4 #16 0x4ad4ee76 in SessionAbstractedService::DoFinishInitialization() () from /usr/lib/libknmservice.so.4 #17 0x4ad6344c in SessionAbstractedService::FinishInitialization() () from /usr/lib/libknmservice.so.4 #18 0x4ad4f11c in SessionAbstractedService::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libknmservice.so.4 #19 0x4bd178b8 in ?? () from /usr/lib/libQtDBus.so.4 #20 0x4bd18a19 in ?? () from /usr/lib/libQtDBus.so.4 #21 0x4bd193b0 in ?? () from /usr/lib/libQtDBus.so.4 #22 0x4bd195c9 in ?? () from /usr/lib/libQtDBus.so.4 #23 0x4c1d8fff in QObject::event(QEvent*) () from /usr/lib/libQtCore.so.4 #24 0x4cdda144 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4 #25 0x4cddf583 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4 #26 0x4a41aa32 in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5 #27 0x4c1c0ade in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/libQtCore.so.4 #28 0x4c1c45d4 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib/libQtCore.so.4 #29 0x4c1c471d in QCoreApplication::sendPostedEvents(QObject*, int) () from /usr/lib/libQtCore.so.4 #30 0x4c1eecd5 in ?? () from /usr/lib/libQtCore.so.4 #31 0x4bbfc5bf in g_main_context_dispatch () from /lib/libglib-2.0.so.0 #32 0x4bbfcd30 in ?? () from /lib/libglib-2.0.so.0 #33 0x4bbfd06f in g_main_context_iteration () from /lib/libglib-2.0.so.0 #34 0x4c1ef118 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4 #35 0x4ce8ecab in ?? () from /usr/lib/libQtGui.so.4 #36 0x4c1bfe1e in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4 #37 0x4c1c0071 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4 #38 0x4c1c47cb in QCoreApplication::exec() () from /usr/lib/libQtCore.so.4 #39 0x4cdd7f45 in QApplication::exec() () from /usr/lib/libQtGui.so.4 #40 0x4ab66bd3 in kdemain () from /usr/lib/libkdeinit4_kded4.so #41 0x080485fc in ?? () #42 0x4b9943f3 in __libc_start_main () from /lib/libc.so.6 #43 0x08048621 in _start () Report to https://bugs.kde.org
Which Plasma NM version do you use? You can see the version string by clicking on "Manage connections" then in "Other". If your installation is that old then you are probably using an old version of Plasma NM with several bugs (including crashes) already fixed. You should really upgrade to the lastest Plasma NM version (0.9.0.4). There is at least this bug https://bugs.kde.org/show_bug.cgi?id=300113 that may be the cause of the crash you see.
kde-plasma-networkmanagement-0.9.0.2-1.fc15 is the latest available for fedora 15 ( which is now EOL'd, so no new updates coming)
Thanks As of you Same version kde-plasma-networkmanagement-0.9.0-1.fc15 is updated to my fedora KDE 15 before updation the bug is generated, now the My fedora is booting with no problem even every application and every thing going smoothly, only thing is every time I boot the fedora bug window will seen about reporting the bug. Is there any application software that I directly install to fedora & search the bug & solve the bug problem. Thanking you On 9/29/12, Rex Dieter <rdieter@math.unl.edu> wrote: > https://bugs.kde.org/show_bug.cgi?id=307566 > > Rex Dieter <rdieter@math.unl.edu> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > CC| |rdieter@math.unl.edu > > --- Comment #7 from Rex Dieter <rdieter@math.unl.edu> --- > kde-plasma-networkmanagement-0.9.0.2-1.fc15 is the latest available for > fedora > 15 ( which is now EOL'd, so no new updates coming) > > -- > You are receiving this mail because: > You reported the bug. >
You can try removing the line with "Connections=" from ~/.kde/share/config/networkmanagementrc and relogin. That will prevent the code that causes crash https://bugs.kde.org/show_bug.cgi?id=300113 from running.
Dear sir, Please guide me with example so that I can easily find out the line. Because I am new to this. don't mistake Me Thanking you On 9/29/12, Lamarque V. Souza <lamarque@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=307566 > > --- Comment #9 from Lamarque V. Souza <lamarque@kde.org> --- > You can try removing the line with "Connections=" from > ~/.kde/share/config/networkmanagementrc and relogin. That will prevent the > code > that causes crash https://bugs.kde.org/show_bug.cgi?id=300113 from > running. > > -- > You are receiving this mail because: > You reported the bug. >
Keep in mind that deleting that line will prevent Plasma NM from importing connections from NetworkManager 0.8. If you have never imported the connection from NetworkManager 0.8 then you have better upgrading to a newer version instead of deleting the line. If you still wants to try it then start a text editor like kate (menu K -> Applications -> Utilities -> Advanced Text Editor (Kate)), click on "new session" if it asks if you want to create a new one, then go to File -> Open, type ".kde" and press ENTER. Then navigate to the share/config directory and open the networkmanagementrc file. Look for the line that starts with "Connections=", delete it and save the file. You can do the same in the command line using: sed -e "/Connections=/d" -i ~/.kde/share/config/networkmanagementrc
Dear sir, Once again I am Back for your help, Sir I would like to install the virtualization for My fedora KDE 15 I am already installed the xen vertualization that is available with fedora updation But I didn't know how to work with it, Is it easy to work with it, or otherwise is it better to install the KVM virtualization if so How can I install the the KVM please guide me how to install the application & how can I work with it Thanking you On Sat, Sep 29, 2012 at 11:45 PM, Lamarque V. Souza <lamarque@kde.org>wrote: > https://bugs.kde.org/show_bug.cgi?id=307566 > > --- Comment #11 from Lamarque V. Souza <lamarque@kde.org> --- > Keep in mind that deleting that line will prevent Plasma NM from importing > connections from NetworkManager 0.8. If you have never imported the > connection > from NetworkManager 0.8 then you have better upgrading to a newer version > instead of deleting the line. > > If you still wants to try it then start a text editor like kate (menu K -> > Applications -> Utilities -> Advanced Text Editor (Kate)), click on "new > session" if it asks if you want to create a new one, then go to File -> > Open, > type ".kde" and press ENTER. Then navigate to the share/config directory > and > open the networkmanagementrc file. Look for the line that starts with > "Connections=", delete it and save the file. > > You can do the same in the command line using: > > sed -e "/Connections=/d" -i ~/.kde/share/config/networkmanagementrc > > -- > You are receiving this mail because: > You reported the bug. >
Here's the best ways to get help/support for using fedora: http://fedoraproject.org/en/get-help (and bugs.kde.org isn't listed there. :) )
Dear sir, All of the above problem solved once again I am facing that k mix is missing from the task bar & even the software up-dation missing form My system setting_ system administration. So please help me how to solve this problems Thanking you On 10/2/12, Rex Dieter <rdieter@math.unl.edu> wrote: > https://bugs.kde.org/show_bug.cgi?id=307566 > > --- Comment #13 from Rex Dieter <rdieter@math.unl.edu> --- > Here's the best ways to get help/support for using fedora: > http://fedoraproject.org/en/get-help > > (and bugs.kde.org isn't listed there. :) ) > > -- > You are receiving this mail because: > You reported the bug. >
(In reply to comment #14) > Dear sir, > All of the above problem solved once again I am facing that > k mix is missing from the task bar & even the software up-dation > missing form My system setting_ system administration. So please help > me how to solve this problems Closing since reporter said this particular problem is solved now. Problems related to kmix should be reported against kmix product.