Bug 973 - Graphic installer crash
Summary: Graphic installer crash
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: Installer (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords: NEEDINFO
Depends on:
Blocks:
 
Reported: 2011-04-25 12:44 CEST by Marianne Lombard
Modified: 2011-12-16 14:40 CET (History)
3 users (show)

See Also:
Source RPM:
CVE:
Status comment:

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

Description Marianne Lombard 2011-04-25 12:44:32 CEST 
Description of problem:
I was doing a graphic install with the dual arch beta2 iso. After adding a external media (http) and do a custom selection of package, I see the package installing. I have fear a freeze at some point so I switch to the tty1 to see the logs. There was no freeze but I can't go back to the graphic installer anymore.
There is an error in the tty1 : 

Entering step `Users'
gtk-CRITICAL **: gtk_cell_view_set_cell_data: assertion `cell_view->priv->displayed_row != NULL' failed at /usr/lib/libDrakX/interactive/gtk.pm line 522 


I need to restart the install to finalize it
Marianne Lombard 2011-04-25 12:45:52 CEST

CC: (none) => marianne

Comment 1 Ahmad Samir 2011-05-17 21:43:24 CEST 
Is this still valid with Beta2?
Manuel Hiebel 2011-08-07 15:33:25 CEST

Keywords: (none) => NEEDINFO

Comment 2 Thierry Vignaud 2011-08-09 12:09:26 CEST 
No this is not the error message, that's only a warning.
However the GUI part won't refresh on VT switching.
Are you sure you didn't either suffer from not knowing which VT was used by the installer or the installer wasn't refreshed and so only displayed a white rectangle for a couple minutes?

CC: (none) => thierry.vignaud

Comment 3 Manuel Hiebel 2011-10-25 11:33:24 CEST 
ping ?
Comment 4 Marja Van Waes 2011-12-16 14:40:20 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
CC: (none) => marja11
Resolution: (none) => OLD
Note You need to log in before you can comment on or make changes to this bug.