Summary: | plasma starts with crash handler disabled | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | renato gallo <renatogallo> |
Component: | Current packages | Assignee: | Gentoo KDE team <kde> |
Status: | RESOLVED NEEDINFO | ||
Severity: | minor | Flags: | tampakrap:
Bugday+
|
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 313999 |
Description
renato gallo
2009-03-05 08:18:15 UTC
Hm then tell us what needs to be changed where :] If I knew I would attach a patch I just would like plasma to start without the nocrashhandler option. (In reply to comment #1) > Hm then tell us what needs to be changed where :] > news ? Possibly fixed in 4.4.0 ??? huettel@pinacolada ~ $ ps ax|grep plasma 18854 ? S 5:19 kdeinit4: plasma-desktop [kdeinit] 19543 pts/1 S+ 0:00 grep --colour=auto plasma huettel@pinacolada ~ $ we'd like some feedback here, it seems fixed for 4.4.2, I couldn't crash my plasma but i tried to kill it. Plasma will most likely fallback to --nocrashhandler anyway when it detects that it has just crashed and automatically starts new 'failsafe' instance - this new instance will most likely have crash handler disabled. Is this the case here? Or it's the first instance (the one run at startup) starts with crash handler disabled? at that time no instance had crash handler enabled and it could be nice to have it by default into the startup script (In reply to comment #6) > Plasma will most likely fallback to --nocrashhandler anyway when it detects > that it has just crashed and automatically starts new 'failsafe' instance - > this new instance will most likely have crash handler disabled. > > Is this the case here? Or it's the first instance (the one run at startup) > starts with crash handler disabled? > No clue. Resolving it since it seems to work properly here. Feel free to reopen if you see the same behaviour on 4.4.2 or 4.4.3 ... |