[Bug 338205] Re: [jaunty] plasma crashes on start with SIGSEGV

[Jeremy Kerr]

Running under gdb doesn't seem to catch the SEGV, perhaps because plasma
forks and detaches from the parent process and/or kcrash is catching the
signal?

(gdb) run
[ lines omitted ]
plasma(30010) NetworkManagerApplet::showVpn: SHOWING                            
KCrash: Application 'plasma' crashing...                                        
plasma(29977): Communication problem with  "plasma" , it probably crashed.      
Error message was:  "org.freedesktop.DBus.Error.NoReply" : " "Message did not receive a reply (timeout by message bus)" "                                       


Program exited with code 0377.
(gdb)
 <unknown program name>(30044)/ checkComposite: Plasma has an argb visual 0x915aa10 81788929                                                               
<unknown program name>(30044)/ checkComposite: Plasma can use COMPOSITE for effects on 0x915a360                                                                
QLayout: Attempting to add QLayout "" to QWidget "", which already has a layout 
plasma(30046) Solid::Control::ManagerBasePrivate::loadBackend: Backend loaded:  "NetworkManager 0.7"
[ output continues ]

I'll see if I can coerce gdb into attaching to the forked processes.

-- 
[jaunty] plasma crashes on start with SIGSEGV
https://bugs.launchpad.net/bugs/338205
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to plasma-widget-network-manager in ubuntu.