Bug 779

Summary:	kwrite segfaults on GUI launch after first update from beta1
Product:	Mageia	Reporter:	Barry Jackson <zen25000>
Component:	RPM Packages	Assignee:	John Balcaen <balcaen.john>
Status:	RESOLVED INVALID	QA Contact:
Severity:	normal
Priority:	Normal	CC:	balcaen.john
Version:	Cauldron
Target Milestone:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Source RPM:		CVE:
Status comment:

Description Barry Jackson 2011-04-11 18:35:42 CEST

This is not a one-off. 
I have done a second fresh install to confirm this.
After installation of beta1 kwrite works correctly, but after updating the system it fails to launch from a menu or from dolphin.
The only crash info is:-

Application: KWrite (kdeinit4 (deleted)), signal: Segmentation fault
[Current thread is 1 (process 21367)]

Thread 1 (process 21367):


However it will run from a terminal but issues the following warnings as it launches:-

[baz@localhost ~]$ kwrite
kwrite(21339)/kdeui (kdelibs) KXMLGUIClient::~KXMLGUIClient: 0x17e8ad0 deleted without having been removed from the factory first. This will leak standalone popupmenus and could lead to crashes. 
kwrite(21339)/kdeui (kdelibs) KXMLGUIClient::~KXMLGUIClient: 0x193da98 deleted without having been removed from the factory first. This will leak standalone popupmenus and could lead to crashes.

Comment 1 Barry Jackson 2011-04-11 18:41:32 CEST

Correction the warnings are issued in the terminal as it closes - there are no error messages during use.

Comment 2 John Balcaen 2011-04-11 20:59:12 CEST

Did you try with the xguest user just in case ?
i'm not able to reproduce here with my user or in a xguest session.

Regards,

CC: (none) => balcaen.john

Comment 3 Barry Jackson 2011-04-11 22:35:12 CEST

No but I wish I had!
I have just slowly added all the packages that are in a previous system without the problem, but nothing cleared it.
Kate was also affected.
I finally re-booted and the problem was gone.
There is something that upsets kate and kwrite in an update from a clean install that requires a re-boot.

I would leave this open for now and I will have another go at tracking it down - but not today!

Comment 4 John Balcaen 2011-04-11 22:43:44 CEST

(In reply to comment #3)
> No but I wish I had!
 reproduce with xguest user ?

> I have just slowly added all the packages that are in a previous system without
> the problem, but nothing cleared it.
> Kate was also affected.
> I finally re-booted and the problem was gone.
> There is something that upsets kate and kwrite in an update from a clean
> install that requires a re-boot.
Well a simple log out log in should fix it & not a full reboot if there's an update of kdelibs4 or kdebase4.

Status: NEW => ASSIGNED
Assignee: bugsquad => balcaen.john
Severity: major => normal

Comment 5 John Balcaen 2011-04-22 18:25:20 CEST

ping ?
Did you try with the xguest user ?

Comment 6 Barry Jackson 2011-04-23 10:02:56 CEST

No, as I didn't have a non-updated beta1 installation handy to test with.
Also I have been busy and sort of forgot ;-(
I will do a clean install (not using any existing profile) to check today.

Comment 7 Barry Jackson 2011-04-25 12:07:06 CEST

I think this can be closed as it's so hard to reproduce, and is cleared so easily.
A clean install does still exhibit this after a full update, however changing user seems to clear it as it's not apparent in xguest or then in the original user (having switched back).
I'm closing as invalid - if someone wants to re-open it then fine.

Status: ASSIGNED => RESOLVED
Resolution: (none) => INVALID