Bug 12643 - Gnome desktop crashes as it refuses to behave itself!
Summary: Gnome desktop crashes as it refuses to behave itself!
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 4
Hardware: i586 Linux
Priority: Normal critical
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL: https://vimeo.com/86086045
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-02-07 07:20 CET by Andrew S
Modified: 2015-03-29 04:04 CEST (History)
2 users (show)

See Also:
Source RPM: task-gnome-minimal 3.10.1 or task-gnome 3.10.1 release 3.mga4
CVE:
Status comment:


Attachments

Description Andrew S 2014-02-07 07:20:13 CET
Description of problem:


Gnome-Classic desktop unstable with the desktop showing the Desktop folder in icons on a grey background when NOT asked to do so. Using the tweak tool to toggle these back in line is no guarantee to the icons staying away and can crash the desktop.


How reproducible:


Steps to Reproduce:
1. Run Gnome-classic desktop
2. Install the desktop Tweak tool
3. Use and wait.....  It will happen within a few days.

Above URL shows the desktop refusing twice in very quick succession to accepting the restored desktop state and the desktop crashing. It failed to fix the problem moments before the film was made.


Reproducible: 

Steps to Reproduce:
Comment 1 Olivier FAURAX 2014-11-21 13:48:12 CET
Can you provide a photo/video of the problem?
Are you able to provide a quicker way to reproduce the problem without waiting several days?

CC: (none) => olivier

Comment 2 Nic Baxter 2015-03-13 04:47:10 CET
Is this still valid?

CC: (none) => nic

Comment 3 Nic Baxter 2015-03-29 04:04:37 CEST
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


Note You need to log in before you can comment on or make changes to this bug.