Bug 527527 - liveinst: unexpected dialog "failed to mount" during install
Summary: liveinst: unexpected dialog "failed to mount" during install
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: LiveCD - Xfce
Version: 12
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Kevin Fenzi
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-10-06 19:27 UTC by Brock Organ
Modified: 2010-12-04 07:32 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-12-04 07:32:55 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
screenshot showing unexpected dialog error (360.56 KB, image/png)
2009-10-06 19:27 UTC, Brock Organ
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Xfce 5838 0 None None None Never

Description Brock Organ 2009-10-06 19:27:11 UTC
Created attachment 363885 [details]
screenshot showing unexpected dialog error

* testing using F12/qemu virtual machine
* nightly livecd compose
* xfce-x86_64-20091005.20.iso

when running the livecd installer, an unexpected dialog box comes up during the install process, it appears informational only and doesn't keep the install from completing ... see attached screenshot

Comment 1 Brock Organ 2009-10-06 19:28:09 UTC
other liveCDs (lxde in particular) didn't have this error, it only appears during xfce liveCD installs ...

Comment 2 Kevin Fenzi 2009-10-06 19:35:14 UTC
Yeah, we were seeing this sporadically before, but now it seems to happen all the time. 

It's Thunar deciding somehow that the newly created volume that anaconda is trying to install on should be automounted. ;( 

Max was going to look at tracking it down further. Adding him to CC here.

Comment 3 Adam Miller 2009-10-06 21:35:44 UTC
http://bugzilla.xfce.org/show_bug.cgi?id=5838

Reported upstream with reference to this bug and some added information.

Comment 4 Bug Zapper 2009-11-16 13:20:18 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 12 development cycle.
Changing version to '12'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 5 Bug Zapper 2010-11-04 09:36:54 UTC
This message is a reminder that Fedora 12 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 12.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '12'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 12's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 12 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 6 Bug Zapper 2010-12-04 07:32:55 UTC
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.


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