|
Bugzilla – Full Text Bug Listing |
| Summary: | Kicker crash (maybe related to system monitor) | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 10.2 | Reporter: | Christian Boltz <suse-beta> |
| Component: | KDE | Assignee: | Dirk Mueller <dmueller> |
| Status: | VERIFIED FIXED | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Major | ||
| Priority: | P5 - None | ||
| Version: | Alpha 1 | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: |
backtrace
valgrind log - but without crash valgrind log after uninstalling kdebase3-wireless |
||
Created attachment 77005 [details]
backtrace
The same kicker crash just appeared after login even when entering the correct passphrase. BTW: the zen-updater icon openen in a separate window instead of the kicker tray. the backtrace is pretty useless ;( But if you have the debuginfo packages, please killall kicker and then try valgrind kicker --nofork It seams I know every debugging tool until 10.1 is final ;-) (read: it's the first time I use valgrind.) valgrind reported lots of errors (I'll attach the log), but kicker didn't crash this time. But the system monitor didn't display anything (indicating it missed the SSH passphrase) - which was confirmed by pressing Ctrl-C in valgrind: [...] ==7247== More than 100000 total errors detected. I'm not reporting any more. ==7247== Final error counts will be inaccurate. Go fix your program! ==7247== Rerun with --error-limit=no to disable this cutoff. Note ==7247== that errors may occur in your program without prior warning from ==7247== Valgrind, because errors are no longer being displayed. ==7247== [pressed Ctrl-C] Enter passphrase for key '/home/cb/.ssh/id_dsa': Hmm, why text mode for the SSH passphrase this time? ;-) I'll test again and try to reproduce the crash - but I guess this will need a re-login with canceling ssh-add. Created attachment 78119 [details]
valgrind log - but without crash
maybe you can find some hints even without actually seeing the crash ;-)
Damn! It seems valgrind avoids the crash :-(
In the last minutes, I could reproduce the crash easily with this small script:
eval `ssh-agent`
strace kicker --nofork 2>&1 | tee /beta9/kicker-strace.log
(I run this script via Alt-F2 to get the graphical passphrase dialog and always pressed escape in the passphrase dialog.)
But I currently cannot reproduce the crash using valgrind :-(
I can offer a strace log with the crash - would that help? Are there other tools that could help?
Its okay when it doesn't crash under valgrind - the log is still helpful. you have two problematic cases. for eliminating one, please deinstall kdenetwork3-wireless and try again. Created attachment 78371 [details]
valgrind log after uninstalling kdebase3-wireless
again, kicker didn't crash in valgrind - but the log contains some errors.
At the end, I killed valgrind (including kicker) using "kill <pid of valgrind>".
BTW: I'll update to RC1 tomorrow - so if there's something I need to test with beta9, please tell me ASAP ;-)
I fixed this now upstream. AJ: for 10.1 ? FYI: this is the topmost reported kicker related crash for 3.5.1. Approved: MaintenanceTracker-4431 If you provide me a URL to the fixed packages, I will test before the official YOU goes out ;-) . I didn't see this crash again after installing the patch via YOU :-) |
I just had a reproducable kicker crash here :-( I guess it's related to the system monitor applet ("Systemüberwachung") I have in the kicker. It asks for the SSH passphrase at startup [1]. If I click "cancel" in the passphrase dialog repeatedly, kicker crashes. I'll attach a backtrace. Unfortunately, it has some "no debugging symbols found" even after installing kdebase3-debuginfo. Do I need more debuginfo packages? Which ones? My system is a beta9 + kdebase3-3.5.1-52 from factory (including kdebase3-debuginfo) because I could not find the debuginfo for the beta9 kdebase3 package on the mirrors I checked. [1] that's annoying, but not in this bugreport ;-)