Bug 2613

Summary:	No longer able to launch applications after a short time of use.
Product:	Mageia	Reporter:	Danny Roberts <dannyroberts.personal>
Component:	RPM Packages	Assignee:	Mageia Bug Squad <bugsquad>
Status:	RESOLVED OLD	QA Contact:
Severity:	normal
Priority:	Normal	CC:	marja11
Version:	1	Keywords:	NEEDINFO
Target Milestone:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Source RPM:		CVE:
Status comment:

Description Danny Roberts 2011-09-04 00:07:19 CEST

Description of problem:

After having used the OS for a time (it seems to vary) no applications can be launched either from the toolbar, the application launcher or via Alt+F2. If MCC was open at the time no new modules can be launched, error says the suffered a fatal error and exited. I have had this issues on two installs now (Net Install and DVD install). A reboot is required to return this functionality.

Version-Release number of selected component (if applicable):

Mageia 1

How reproducible:

Every time you boot.

Steps to Reproduce:
1. Boot up.
2. Wait.

Comment 1 Manuel Hiebel 2011-09-04 00:24:20 CEST

Wich desktop ? can you attach some logs ?

Keywords: (none) => NEEDINFO

Comment 2 Danny Roberts 2011-09-04 12:20:18 CEST

KDE Desktop - which logs do you need?

Comment 3 Manuel Hiebel 2011-09-21 11:27:25 CEST

reproduce this bug then attach:
var/log/Xorg.0.log /var/log/Xorg.0.log.old  ~./.xsession-errors ~./.xsession-errors.old

Comment 4 Marja Van Waes 2011-11-30 20:02:49 CET

Reporter, could you please reply to the previous question? If you won't reply within two weeks from now, this bug can be closed as OLD. Thank you.

CC: (none) => marja11

Comment 5 Marja Van Waes 2012-01-18 10:51:39 CET

Since there are insufficient details provided in this report for us to investigate the issue further, and we have not received feedback to the information we have requested above, we will assume the problem was not reproducible, or has been fixed in one of the updates we have released for the reporter's distribution.

Users who have experienced this problem are encouraged to upgrade to the latest update of their distribution, and if this issue turns out to still be reproducible in the latest update, please reopen this bug with additional information.

Closing as OLD.

Status: NEW => RESOLVED
Resolution: (none) => OLD