Bug 1572 - XFdrake crashed (cannot ensure a safe /home/steve/tmp/.drakx.Xoutput at /usr/lib/libDrakX/common.pm line 270.)
Summary: XFdrake crashed (cannot ensure a safe /home/steve/tmp/.drakx.Xoutput at /usr/...
Status: RESOLVED DUPLICATE of bug 1396
Alias: None
Product: Mageia
Classification: Unclassified
Component: Installer (show other bugs)
Version: 1
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-06-04 12:00 CEST by Steve Edgar
Modified: 2011-06-04 22:49 CEST (History)
0 users

See Also:
Source RPM: drakx-kbd-mouse-x11-0.97-1.mga1
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Steve Edgar 2011-06-04 12:00:13 CEST 
The "XFdrake" program crashed. Drakbug-13.58 caught it.

I am trying to reconfigure my display to a higher resolution, I have just changed my monitor type from generic to Compaq P710 (which it is).
Cheers

Backtrace was:
cannot ensure a safe /home/steve/tmp/.drakx.Xoutput at /usr/lib/libDrakX/common.pm line 270.
standalone::bug_handler() called from /usr/lib/libDrakX/mygtk2.pm:1425
mygtk2::main() called from /usr/lib/libDrakX/ugtk2.pm:767
ugtk2::main() called from /usr/lib/libDrakX/interactive/gtk.pm:883
interactive::gtk::ask_fromW() called from /usr/lib/libDrakX/interactive.pm:533
interactive::ask_from_real() called from /usr/lib/libDrakX/interactive.pm:521
interactive::ask_from_() called from /usr/lib/libDrakX/Xconfig/main.pm:152
Xconfig::main::configure_chooser_raw() called from /usr/lib/libDrakX/Xconfig/main.pm:165
Xconfig::main::configure_chooser() called from /usr/lib/libDrakX/Xconfig/main.pm:188
Xconfig::main::configure_everything_or_configure_chooser() called from /usr/sbin/XFdrake:48

Kernel version = 2.6.38.7-desktop-1.mga
Distribution=Mageia release 1 (Official) for x86_64
CPU=AMD Athlon(tm) 64 X2 Dual Core Processor 3800+
Comment 1 Ahmad Samir 2011-06-04 22:49:13 CEST 
A duplicate.

*** This bug has been marked as a duplicate of bug 1396 ***

Status: NEW => RESOLVED
Resolution: (none) => DUPLICATE
Note You need to log in before you can comment on or make changes to this bug.