| Summary: | The widget Network monitor will crash when is changed network connection. | ||
|---|---|---|---|
| Product: | [Unmaintained] plasma4 | Reporter: | Jiri Vosecek <jiri.vosecek> |
| Component: | widget-misc | Assignee: | Plasma Bugs List <plasma-bugs> |
| Status: | RESOLVED FIXED | ||
| Severity: | crash | ||
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | openSUSE | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
Jiri Vosecek
2007-12-16 14:30:34 UTC
Any chance of a backtrace? It should be accessible in Dr Konqi, the dialog that pops up when plasma crashes for the first time. Are you still getting this? I can't reproduce it. I am going to test it on KDE 4 live 0.9, please wait ... On Sat, 05 Jan 2008 23:07:10 +0100, Alex Merry <huntedhacker@tiscali.co.uk> wrote: [bugs.kde.org quoted mail] This is backtrace when i added new ethernet card (wireless card), and now, i am going to break down by changing ethernet card settings ... i hope i will be able to send crash report. 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. [?1034h(no debugging symbols found) Using host libthread_db library "/lib/libthread_db.so.1". (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) (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 0xb62876d0 (LWP 4249)] 0xffffe410 in __kernel_vsyscall () [Current thread is 0 (process 4249)] Thread 1 (Thread 0xb62876d0 (LWP 4249)): #0 0xffffe410 in __kernel_vsyscall () #1 0xb72dc033 in __waitpid_nocancel () from /lib/libpthread.so.0 #2 0xb7a957cb in ?? () from /usr/lib/libkdeui.so.5 #3 0x00001255 in ?? () #4 0x00000000 in ?? () #0 0xffffe410 in __kernel_vsyscall () On 16 Dec 2007 15:29:59 -0000, Alex Merry <huntedhacker@tiscali.co.uk> wrote: [bugs.kde.org quoted mail] It seems that it is impossible to reproduce it via changing settings of ethernet card. The Plasma will crash, but there is neither crash dialog, nor something anything else. I can run "plasma" to get system to standard state. I do not have any crash report, sorry. I can not test it otherwise than on Live CD, maybe this is the problem. On 16 Dec 2007 15:29:59 -0000, Alex Merry <huntedhacker@tiscali.co.uk> wrote: [bugs.kde.org quoted mail] Plasma only displays the crash dialog the first time it crashes. The second time, it just quits. It should probably do something like KWin - only give up if it crashes too frequently (say twice in 5 seconds). The reason you don't get a useful backtrace is you don't have debugging symbols installed. SuSE should provide *-debug packages, I think. You may need to enable an option in the package installer to show debug packages. You'll need qt4-debug, kdelibs4-debug and kdebase4-debug (on the assumption the original packages were qt4, kdelibs4 and kdebase4 respectively). > It should probably do something like KWin -
> only give up if it crashes too frequently
take a look in plasmaapp.cpp. i did the same thing in kicker in 3.5 too.
This is too diffilcut for me, i am not programmer, but only user ... On Mon, 07 Jan 2008 22:46:36 +0100, Aaron J.Seigo <aseigo@kde.org> wrote: [bugs.kde.org quoted mail] Ok, i will try it tomorrow with added packages. On Mon, 07 Jan 2008 22:23:19 +0100, Alex Merry <huntedhacker@tiscali.co.uk> wrote: [bugs.kde.org quoted mail] Jiri: I think Aaron's comment was directed at me, rather than you. Probably, i only read new mail and did not watch thread :) On Mon, 07 Jan 2008 23:59:21 +0100, Alex Merry <huntedhacker@tiscali.co.uk> wrote: [bugs.kde.org quoted mail] > i am going to break down by changing ethernet card settings
Hi,
could you please describe what exactly you did - on the command line or using
any tool or configuration dialog - to reproduce the crash?
Hi Jiri, is the crash still reproducable for you with KDE 4.0.2? I have installed Kubuntu GG Alpha 6 with KDE4, how can i add new widget? I have only clock, new devices etc. On 10 Mar 2008 00:56:58 -0000, Sebastian Sauer <mail@dipe.org> wrote: [bugs.kde.org quoted mail] I discovered the package extragears-plasma, but unfortunately there is not Network widget. On 10 Mar 2008 00:56:58 -0000, Sebastian Sauer <mail@dipe.org> wrote: [bugs.kde.org quoted mail] Hi Jiri, what makes it a bit more difficult to know if that bug was fixed, a local problem or just whatever else. What do you think, should we close this report with the possibility to reopen it if it happens again for you? I do not know, if we can close this bug. Could you give me advice how to install Network monitor widget? Now I can not check it. On 10 Mar 2008 17:35:55 -0000, Sebastian Sauer <mail@dipe.org> wrote: [bugs.kde.org quoted mail] http://techbase.kde.org/index.php?title=Projects/Plasma/Plasmoids does list the known applets. I've really no idea what of them the Network monitor widget is :-( At http://techbase.kde.org/index.php?title=Getting_Started are some tutorials how to setup an environment through I guess if your distributor does provide source-packages, then you should be also able to just compile+install those plasmoid that you like to test. Hmm, there is no Network monitor, i checked it and it ... disappeared from the list of Known Plasmoid, is it possible? On 10 Mar 2008 19:28:17 -0000, Sebastian Sauer <mail@dipe.org> wrote: [bugs.kde.org quoted mail] Hmm, there is no Network monitor, i checked it and it ... disappeared from the list of Known Plasmoid, is it possible?<br><br><div class="gmail_quote">On 10 Mar 2008 19:28:17 -0000, Sebastian Sauer <<a href="mailto:mail@dipe.org">mail@dipe.org</a>> wrote:<br> <blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="Ih2E3d">------- You are receiving this mail because: -------<br> You reported the bug, or are watching the reporter.<br> <br> <a href="http://bugs.kde.org/show_bug.cgi?id=154166" target="_blank">http://bugs.kde.org/show_bug.cgi?id=154166</a><br> <br> <br> <br> <br> </div>------- Additional Comments From mail dipe org 2008-03-10 20:28 -------<br> <a href="http://techbase.kde.org/index.php?title=Projects/Plasma/Plasmoids" target="_blank">http://techbase.kde.org/index.php?title=Projects/Plasma/Plasmoids</a> does list the known applets. I've really no idea what of them the Network monitor widget is :-(<br> At <a href="http://techbase.kde.org/index.php?title=Getting_Started" target="_blank">http://techbase.kde.org/index.php?title=Getting_Started</a> are some tutorials how to setup an environment through I guess if your distributor does provide source-packages, then you should be also able to just compile+install those plasmoid that you like to test.<br> </blockquote></div><br> The applet is in playground but I stopped working on it as I do not have enough time to follow KDE4 development at the moment. So I cannot say if its still working with 4.0.2 or even the development version. So closing the bug would probably make most sense... Ok, is "RESOLVED" right option? Is there some other option how to close bug? On 10 Mar 2008 20:03:33 -0000, Percy Leonhardt <percy@eris23.de> wrote: [bugs.kde.org quoted mail] Ok, is "RESOLVED" right option? Is there some other option how to close bug?<br><br><div class="gmail_quote">On 10 Mar 2008 20:03:33 -0000, Percy Leonhardt <<a href="mailto:percy@eris23.de">percy@eris23.de</a>> wrote:<br> <blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="Ih2E3d">------- You are receiving this mail because: -------<br> You reported the bug, or are watching the reporter.<br> <br> <a href="http://bugs.kde.org/show_bug.cgi?id=154166" target="_blank">http://bugs.kde.org/show_bug.cgi?id=154166</a><br> <br> <br> <br> <br> </div>------- Additional Comments From percy eris23 de 2008-03-10 21:03 -------<br> The applet is in playground but I stopped working on it as I do not have enough time to follow KDE4 development at the moment. So I cannot say if its still working with 4.0.2 or even the development version.<br> <br> So closing the bug would probably make most sense...<br> </blockquote></div><br> Jiri: Nope, resolved is ok. But now I was faster and did mark it as resolved already. Thank you very much for your feedback! and also thanks to Percy for the validation that all this wasn't only a dream :) |