| 2007-01-11 22:34:46 |
Martin Pitt |
bug |
|
|
added bug |
| 2007-01-11 22:35:03 |
Martin Pitt |
gnome-volume-manager: status |
Unconfirmed |
In Progress |
|
| 2007-01-11 22:35:03 |
Martin Pitt |
gnome-volume-manager: importance |
Undecided |
Critical |
|
| 2007-01-11 22:35:03 |
Martin Pitt |
gnome-volume-manager: statusexplanation |
|
|
|
| 2007-01-11 22:35:03 |
Martin Pitt |
gnome-volume-manager: assignee |
|
pitti |
|
| 2007-01-30 08:17:00 |
Martin Pitt |
gnome-volume-manager: status |
In Progress |
Confirmed |
|
| 2007-01-30 08:17:00 |
Martin Pitt |
gnome-volume-manager: statusexplanation |
|
My initial thought was that g-v-m would not re-read gconf keys while it runs, but it does. With an automatic partitioning, I get:
manager.c/696: setting changed: bool: automount_drives = 0
manager.c/696: setting changed: bool: automount_media = 0
[some partition removals/additions]
manager.c/696: setting changed: bool: automount_drives = 1
manager.c/696: setting changed: bool: automount_media = 1
but if I do manual partitioning, the gconf keys are never set to 0, thus g-v-m picks up the new partition and automatically mounts them. |
|
| 2007-01-30 08:17:22 |
Martin Pitt |
title |
automatically mounts created file systems on live CD |
automatically mounts created file systems on live CD on manual partitioning |
|
| 2007-01-30 08:17:53 |
Martin Pitt |
ubiquity: assignee |
pitti |
kamion |
|
| 2007-01-30 08:17:53 |
Martin Pitt |
ubiquity: statusexplanation |
My initial thought was that g-v-m would not re-read gconf keys while it runs, but it does. With an automatic partitioning, I get:
manager.c/696: setting changed: bool: automount_drives = 0
manager.c/696: setting changed: bool: automount_media = 0
[some partition removals/additions]
manager.c/696: setting changed: bool: automount_drives = 1
manager.c/696: setting changed: bool: automount_media = 1
but if I do manual partitioning, the gconf keys are never set to 0, thus g-v-m picks up the new partition and automatically mounts them. |
|
|
| 2007-01-30 14:14:08 |
Colin Watson |
ubiquity: status |
Confirmed |
Fix Released |
|
| 2007-01-30 14:14:08 |
Colin Watson |
ubiquity: statusexplanation |
|
ubiquity (1.3.15) feisty; urgency=low
* Add --old-partitioner command-line option to force the use of the old
advanced partitioner even when it stops being the default. (Of course,
this won't work for ever, as the old code will eventually be removed.)
* GTK frontend: Disable gnome-volume-manager automounting for the entire
duration of installation (LP: #78862).
* Really install the apport hook.
* Switch the new partitioner on by default. As above, use 'ubiquity
--old-partitioner' to disable it.
-- Colin Watson <cjwatson@ubuntu.com> Tue, 30 Jan 2007 14:10:11 +0000 |
|
| 2007-02-11 04:43:49 |
TomTom27 |
bug |
|
|
assigned to ubiquity (Baltix) |
| 2007-02-11 04:44:17 |
TomTom27 |
ubiquity: assignee |
kamion |
tomcs |
|
| 2007-02-11 04:44:17 |
TomTom27 |
ubiquity: statusexplanation |
ubiquity (1.3.15) feisty; urgency=low
* Add --old-partitioner command-line option to force the use of the old
advanced partitioner even when it stops being the default. (Of course,
this won't work for ever, as the old code will eventually be removed.)
* GTK frontend: Disable gnome-volume-manager automounting for the entire
duration of installation (LP: #78862).
* Really install the apport hook.
* Switch the new partitioner on by default. As above, use 'ubiquity
--old-partitioner' to disable it.
-- Colin Watson <cjwatson@ubuntu.com> Tue, 30 Jan 2007 14:10:11 +0000 |
|
|
| 2009-11-20 21:44:57 |
Przemek K. |
ubiquity (Baltix): status |
New |
Fix Released |
|
| 2010-02-22 10:41:25 |
Launchpad Janitor |
branch linked |
|
lp:ubuntu/ubiquity |
|
| 2012-02-23 22:31:41 |
Kai Kasurinen |
removed subscriber Kai Kasurinen |
|
|
|
