The ext3 file system creation in partition #1 of SCSI1 (0,0,0) (sda) failed.

Bug #99908 reported by Richard Birnie
18
Affects Status Importance Assigned to Milestone
ubiquity (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

Binary package hint: ubiquity

Testing installation from Kubuntu daily build 20070401.
Test system
HP Pavilion N5472
20GB HDD
256MB RAM

Started installer from desktop icon. At disk partitioning step
selected 'guided - use entire disk'. Proceeded through steps 5 and 6
then clicked the install button. System displays an 'Installing
System' box with a progress bar. Progress bar gets to 5% then a
message box appears with the message:

The ext3 file system creation in partition #1 of SCSI1 (0,0,0) (sda) failed.

Clicking on OK on this message box drops me back to the disk
partitioning page. If I select 'guided - use entire disk' again I get
the same result. I will post /var/log/syslog and /var/log/partman. Is
anything else required?

At the start of today the HDD of this system had a working
installation of Xubuntu feisty on it from an earlier daily build test.
Earlier today I used the same CD that generated the above error to
install Kubuntu selecting 'guided - auto-resize' as the partitioning
method. At this point I had working installations of both Xubuntu and
Kubuntu on this system. It's only if I try to use the entire disk that
installation fails. The md5sum of the ISO checks out and 'Check CD for
defects' returned no errors.

Just ask if any other info is required or if you want extra tests tried.

Revision history for this message
Richard Birnie (rbirnie-deactivatedaccount) wrote :
Revision history for this message
Richard Birnie (rbirnie-deactivatedaccount) wrote :
Revision history for this message
Richard Birnie (rbirnie-deactivatedaccount) wrote :

Update:
Following the error noted above I cancelled the install and shutdown the liveCD from the main menu. Now when I go to boot the system it fails to boot. I just see the following

Grub loading, please wait...
Error 22

So it looks as if the installer got as far as erasing the existing OSs. Not sure how relevant this is I just thought I'd add it for completeness of information. This isn't a problem for me since I only use that box for testing anyway but it could be a problem for someone else.

Revision history for this message
Colin Watson (cjwatson) wrote :

Hmm, I wonder. Before starting the installer, could you please try editing /lib/partman/commit.d/30parted, and putting 'update-dev' right after close_dialog? So the whole script should read:

#!/bin/sh

. /lib/partman/definitions.sh

disable_swap
for dev in $DEVICES/*; do
    [ -d "$dev" ] || continue
    cd $dev
    open_dialog COMMIT
    close_dialog
    update-dev
done

I'd be interested to know if this helps; it seems like a good possibility, as the reason that mkfs.ext3 failed was that the device node /dev/sda1 didn't exist.

Changed in ubiquity:
assignee: nobody → kamion
status: Unconfirmed → Needs Info
Revision history for this message
Richard Birnie (rbirnie-deactivatedaccount) wrote :

The suggested fix works perfectly.

Technically the two tests weren't exactly equal. Originally I had both Kubuntu and Xubuntu installed on the system before the problem occurred. However the original problem hosed these installs. I re-installed Kubuntu 7.04 beta just so there was something on the disk. I launched the installer from a terminal with ubiquity --debug and went through the steps and selected 'guided - use entire disk' on the partitioning page. Clicked through the remaining steps and the installation completed without errors. If you think the quantity of stuff on the disk is an issue I can reinstall both kubuntu and xubuntu and test the fix again. I am about to test todays daily build Kubuntu 20070402, I'll report back if the problem still exists.

Revision history for this message
Richard Birnie (rbirnie-deactivatedaccount) wrote :

OK now things get strange. Following on from above I tested an install with Kubuntu daily build 20070402. Selecting guided - auto resize at the partitioning stage works fine and the install completes without errors. Following this I attempted to install by selecting 'guided - use entire disk' at the partitioning stage. This induced the same error as the original post. So I attempted the same fix suggested by Colin Watson above and repeated the install process. This time the installer crashed at Installing system - 5%

Here's the traceback:

Traceback (most recent call last):
  File "/usr/lib/ubiquity/bin/ubiquity", line 210, in <module>
    main()
  File "/usr/lib/ubiquity/bin/ubiquity", line 207, in main
    install()
  File "/usr/lib/ubiquity/bin/ubiquity", line 58, in install
    ret = wizard.run()
  File "/usr/lib/ubiquity/ubiquity/frontend/kde-ui.py", line 353, in run
    self.process_step()
  File "/usr/lib/ubiquity/ubiquity/frontend/kde-ui.py", line 871, in process_step
    self.progress_loop()
  File "/usr/lib/ubiquity/ubiquity/frontend/kde-ui.py", line 637, in progress_loop
    ret = dbfilter.run_command(auto_process=True)
  File "/usr/lib/ubiquity/ubiquity/filteredcommand.py", line 159, in run_command
    self.start(auto_process=auto_process)
  File "/usr/lib/ubiquity/ubiquity/filteredcommand.py", line 69, in start
    self.db = DebconfCommunicator(PACKAGE, cloexec=True)
  File "/usr/lib/python2.5/site-packages/debconf.py", line 125, in __init__
    write=self.dccomm.tochild)
  File "/usr/lib/python2.5/site-packages/debconf.py", line 48, in __init__
    self.setUp(title)
  File "/usr/lib/python2.5/site-packages/debconf.py", line 51, in setUp
    self.version = self.version(2)
  File "/usr/lib/python2.5/site-packages/debconf.py", line 60, in <lambda>
    lambda *args, **kw: self.command(command, *args, **kw))
  File "/usr/lib/python2.5/site-packages/debconf.py", line 81, in command
    status = int(status)
ValueError: invalid literal for int() with base 10: ''

logs to follow

Revision history for this message
Richard Birnie (rbirnie-deactivatedaccount) wrote :
Revision history for this message
Richard Birnie (rbirnie-deactivatedaccount) wrote :

I've no idea if this is useful or not but it seems relevant so I'll add it anyway

Revision history for this message
Richard Birnie (rbirnie-deactivatedaccount) wrote :

I've just tripped over this bug again in Kubuntu 20070411, the release candidate. The symptoms are exactly as described in the original report. In this case the disk had an existing install of Kubuntu 20070411 on it from an earlier test.

This time the suggested fix of editing /lib/partman/commit.d/30parted did not work. I tried repeating the install launching from the desktop icon and from a terminal with ubiquity --debug. Same results each time. Logs to follow. I'm happy to run tests to diagnose this further if someone can provide instructions.

Revision history for this message
Richard Birnie (rbirnie-deactivatedaccount) wrote :
Revision history for this message
Richard Birnie (rbirnie-deactivatedaccount) wrote :
Revision history for this message
Colin Watson (cjwatson) wrote :

I think this may be due to an out-of-memory condition, although it's hard to be certain, and in any case the installer ought to respond more gracefully.

Revision history for this message
jerrylamos (jerrylamos) wrote :

Feisty Xubuntu 20070414
1.2 gHz Celeron 512mb
4 boot system:
hda1 Win98, hda2 Ubuntu Dapper, hda3 Swap
hdb1 Xubuntu Edgy, hdb2 Swap, hdb3 Ubuntu Feisty up to date

All 4 boot and run just fine.

Test install Xubuntu Feisty on hdb1
manual delete partition
new partition
format partition
migration assistant and all that

"The ext3 file system creation in partition #1 of IDE1 slave (hdb) failed."

This repeats every time with 20070410, 20070411, 20070414

I turned right around and installed Xubuntu Edgy on the same partition successfully. I suspect Kubuntu and Ubuntu would fail as well, I've rsync'd them if useful.

I can re-create this format failure at will; what information would be useful and what steps are taken to get it?

Cheers, Jerry

Revision history for this message
Jesus Gamio (jgamio) wrote :

I had the same that jerry but in version 20070411 BUT when repeat the install after the error just did fine. That mean show the error but if you try again works I reported in Bug #105748 but only when I delete or create the partition in a NTFS is I do the same in a ext3 or another and just work no error.

I havent test 20070414 in a disk with NTFS but to the others options works

Revision history for this message
jerrylamos (jerrylamos) wrote :

Repeat install didn't work for me. I tried to install with delete, new, & reformat, got the failure as usual, while still under install, tried repeating the manual partitioning and formatting, failed again. Then I quit install, started it again, re-did the manual partition and tried to format, failed again, and while still under install, tried again and it failed again.

I then re-booted the hard drive without the CD Live, and the partition selected for manual partitioning still worked showing there had been no partitioning work done and no formatting done.

Cheers, Jerry

Revision history for this message
jerrylamos (jerrylamos) wrote :

"The ext3 file system creation" failure is actually a failure of the manual partitioner. It reads like a "format" failure but it isn't.
"delete" and "new" are failing to do anything. The hard disk isn't changed at all.
"edit" with "resize" also fails to do anything.
"edit" entering the same size and "format" worked. The Feisty Xubuntu install went on to complete and boot up O.K.

I suppose I could crank up stand alone Gparted to see if it would work, but I'm a bit tired of this bug right now. Besides, I've had a couple Feisty partitioning problems causing loss of a Win 98 partition and loss of an XP partition, which I haven't finished re-constructing yet. If Ubuntu would do everything Win98 and XP do for this "ordinary desktop computer user" then I'd be on (several!) Linux's altogether.

The bug is the manual partitioner doesn't work at all in this situation.

Cheers, Jerry

Revision history for this message
Richard Birnie (rbirnie-deactivatedaccount) wrote :

Just for the record I observe the same results as my original report with Kubuntu desktop i386 20070415

Revision history for this message
Colin Watson (cjwatson) wrote :

Jerry, could you attach /var/log/syslog and /var/log/partman from after the failure, please? (I don't need a --debug log in this case.)

Richard's problems do look consistently like either CD read errors or out-of-memory conditions; the logs are certainly not clean of other errors caused by this. Jerry has plenty of memory. Richard's tests are also with automatic partitioning, while Jerry's are with manual partitioning. It's not clear to me that the problems are the same. I have also not seen the same problem with the manual partitioner in any of my tests, so it must be hardware-specific or a race.

Revision history for this message
jerrylamos (jerrylamos) wrote :

Re-created the "ext3 file system creation in partition #1 of IDE1 slave (hdb) failed with 20070215 rsync of Xubuntu. I've got the same level Ubuntu and Kubuntu but haven't tried them. I have screen pictures of the error message and the setup screen if useful.

Attached is /var/log/partman. I don't know how to do two attachments so /etc/var/syslog will follow on next comment.

Cheers, Jerry

Revision history for this message
jerrylamos (jerrylamos) wrote :

Here's the accompanying syslog.

Cheers, Jerry

Revision history for this message
Richard Birnie (rbirnie-deactivatedaccount) wrote :

I tried to reproduce Jerry's problem testing Kubuntu i386 20070415 on the same hardware I described previously. I was unable to do so. Here's what I did:
The disk already had an existing install of Kubuntu feisty on it using the whole of /dev/sda1. Simpler than Jerry's set up but still something on there.
Selected manual partitioning.
Click on sda1, edit partition
Set partition size to 9.6GB (on a 20GB drive)
sda1 was correctly resized

Clicked on the newly created free space.
Clicked New partition /dev/sda3, created as a primary partition.
Set mount point as /
Set sda3 to be reformatted but sda1 to be left alone
Proceeded with installation on sda3.
All of this went without a hitch. Both installs now boot and run just fine. I can supply logs if required but there doesn't seem to be anything useful in them. I will try and test this further tomorrow. Maybe try and create a more realistic test case

Revision history for this message
Colin Watson (cjwatson) wrote :

So, I think Jerry's problem is a different one:

Apr 16 19:00:44 ubuntu hald: mounted /dev/hdb1 on behalf of uid 0
Apr 16 19:00:51 ubuntu partman: mke2fs 1.40-WIP (14-Nov-2006)
Apr 16 19:00:51 ubuntu partman: /dev/hdb1 is mounted; will not make a filesystem here!

I wonder if this particular automounting is Xubuntu-specific?

Revision history for this message
Colin Watson (cjwatson) wrote :

I have reproduced and isolated Jerry's problem, and filed it separately as bug 107259 together with a workaround. Jerry, please see that bug.

Revision history for this message
jerrylamos (jerrylamos) wrote :

Thanks for looking at/finding the bug. As you thought, Ubuntu 20070515 installed successfully on the same configuration Xubuntu failed. This entry is from that install.

I'm on the list to manual install Xubuntu Alternate so let me give that a try, and then the workaround you've designed (time available, chasing bug 106864 on a different computer by putting in another hard drive).

Thanks, Jerry

Revision history for this message
thorwil (t-w-) wrote :

Seems I get hit by this on trying to install 7.04 desktop via live CD.
I disabled removable media auto-mounting and applied https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/99908/comments/4, no luck.

From syslog:
May 23 13:25:31 ubuntu partman: /dev/hda1 is mounted; will not make a filesystem here!

I used mount to check no partition was mounted right before hitting install.

Guess will try alternate.

Revision history for this message
jerrylamos (jerrylamos) wrote :

Gutsy Xubuntu partitioning worked, mind this is very early Alpha and Gutsy is not to ship until October.
Xubuntu Gutsy install partitioner was able to do new and create and format partition and successfully install as 2nd Linux on the hard drive. These are the operations that don't work on Xubuntu Feisty..
So there is a fix for this Feisty Xubuntu problem, but not until Gutsy release unless the Gutsy fix were to be put into Feisty.
Cheers, Jerry

Revision history for this message
memeyou (memeyou) wrote :

I ran into this issue on the Xubuntu 7.10 iso. sda1 was missing while sda2 was there.

Revision history for this message
altgrrr (jonas-grape) wrote :

Trying to install Ubuntu Feisty Fawn on this laptop:

Medion 42427
256 MB RAM

I have previously installed xubuntu 6.04 on that laptop, with success. Now trying to install Ubuntu (Fresh install, no dual boot).

I now get this error:

"The ext3 file system creation in partition #3 of IDE1 master (hda) failed."

Tried the fix suggested in above post https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/99908/comments/4 (editing /lib/partman/commit.d/30parted) but that did not work, still the same error occurs.

2 LOGS:

From /var/log/syslog:

Dec 3 14:12:02 ubuntu ubiquity[23691]: Step_before = stepUserInfo
Dec 3 14:12:02 ubuntu ubiquity[23691]: switched to page stepReady
Dec 3 14:12:02 ubuntu ubiquity[23691]: Step_after = stepReady
Dec 3 14:12:05 ubuntu ubiquity[23691]: debconffilter_done: Summary (current: Su
mmary)
Dec 3 14:12:07 ubuntu ubiquity[23691]: Step_before = stepReady
Dec 3 14:12:07 ubuntu ubiquity[23691]: progress_loop()
Dec 3 14:12:10 ubuntu ubiquity: swapoff: /dev/hda3: Cannot allocate memory
Dec 3 14:12:11 ubuntu NetworkManager: <debug info>^I[1196691131.234203] nm_hal_
device_removed (): Device removed (hal udi is '/org/freedesktop/Hal/devices/volu
me_uuid_8916d1b8_4972_46cb_bffa_377ee4a5bdfd').
Dec 3 14:12:11 ubuntu NetworkManager: <debug info>^I[1196691131.640701] nm_hal_
device_added (): New device added (hal udi is '/org/freedesktop/Hal/devices/volu
me_uuid_985e28d4_f400_48da_ae32_55f823c8fdd6').
Dec 3 14:12:24 ubuntu partman: mke2fs 1.40-WIP (14-Nov-2006)
Dec 3 14:12:51 ubuntu partman: mke2fs 1.40-WIP (14-Nov-2006)
Dec 3 14:12:51 ubuntu partman: /dev/hda3 is mounted;
Dec 3 14:12:51 ubuntu partman: will not make a filesystem here!
Dec 3 14:17:03 ubuntu /USR/SBIN/CRON[8388]: (root) CMD ( cd / && run-parts --
report /etc/cron.hourly)

From /var/log/partman

parted_server: Closing infifo and outfifo
parted_server: main_loop: iteration 528
parted_server: Opening infifo
/lib/partman/commit.d/50format_ext3: Try to create file system for /var/lib/partman/devices/=dev=hda/8003197440-38987827199
/lib/partman/commit.d/50format_ext3: IN: PARTITION_INFO =dev=hda 8003197440-38987827199
parted_server: Read command: PARTITION_INFO
parted_server: command_partition_info()
parted_server: Opening outfifo
parted_server: command_partition_info: info for partition with id 8003197440-38987827199
parted_server: partition_with_id(8003197440-38987827199)
parted_server: OUT: OK

parted_server: command_partition_info: partition found
parted_server: OUT: 3 8003197440-38987827199 30984629760 primary ext3 /dev/hda3

parted_server: Closing infifo and outfifo
parted_server: main_loop: iteration 529
parted_server: Opening infifo

Revision history for this message
altgrrr (jonas-grape) wrote :

In my last post, the log from partman was not up to date, I had not yet closed the partitioner.

The log from /var/log/partman AFTER partitioner was done:

parted_server: Closing infifo and outfifo
parted_server: main_loop: iteration 38
parted_server: Opening infifo
/lib/partman/automatically_partition/10resize_use_free/choices: 3 primary partitions, 0 logical partitions
/lib/partman/automatically_partition/10resize_use_free/choices: Too many primary partitions already exist on /var/lib/partman/devices/=dev=hda without an extended partition
/lib/partman/automatically_partition/10resize_use_free/choices: dev: '/var/lib/partman/devices/=dev=hda', totalfree: '0', diskfree: '0', diskpart: 'none', diskpath: 'none'
/lib/partman/automatically_partition/10resize_use_free/choices: Found no resizable partitions
/lib/partman/automatically_partition/20some_device/choices: *******************************************************
/lib/partman/automatically_partition/50biggest_free/choices: *******************************************************
/lib/partman/automatically_partition/50biggest_free/choices: IN: PARTITIONS =dev=hda
parted_server: Read command: PARTITIONS
parted_server: command_partitions()
parted_server: Opening outfifo
parted_server: OUT: OK

parted_server: OUT: 1 32256-8003197439 8003165184 primary ext3 /dev/hda1

parted_server: OUT: 3 8003197440-38987827199 30984629760 primary unknown /dev/hda3

parted_server: OUT: 2 38987827200-40007761919 1019934720 primary linux-swap /dev/hda2

parted_server: Partitions printed
parted_server: OUT:

parted_server: Closing infifo and outfifo
parted_server: main_loop: iteration 39
parted_server: Opening infifo
/lib/partman/automatically_partition/80custom/choices: *******************************************************

Revision history for this message
Yotam Medini (yotam-medini-gmail) wrote :

Install of Hardy/8.04 failed for me several times.
The failure was always upon trying to make ext3 filesystem.
Before details, let me summarize some points of my case.

+ The problem happened for Ubuntu, Xubuntu, Xubuntu-alternate.
+ LiveCD and alternate-install refers to IDE-disk as /dev/sda and SCSI2,
  while on previous releases it was always /dev/hda.
+ Kernel/initrd 2.6.24-16 fails to recognize root partition.
  Kernel/initrd 2.6.22-14 recognizes the root partition and load well.

I started from a running Gutsy-7.10 having:

    root@durini:~# cat /etc/lsb-release
    DISTRIB_ID=Ubuntu
    DISTRIB_RELEASE=7.10
    DISTRIB_CODENAME=gutsy
    DISTRIB_DESCRIPTION="Ubuntu 7.10"
    root@durini:~# fdisk -l

    Disk /dev/hda: 120.0 GB, 120034123776 bytes
    255 heads, 63 sectors/track, 14593 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
    Disk identifier: 0x00007edb

       Device Boot Start End Blocks Id System
    /dev/hda1 1 5 40131 83 Linux
    /dev/hda2 * 6 2324 18627367+ 83 Linux
    /dev/hda3 2325 4757 19543072+ 83 Linux
    /dev/hda4 4758 14593 79007670 5 Extended
    /dev/hda5 4758 4999 1943833+ 82 Linux swap / Solaris
    /dev/hda6 5000 14593 77063773+ 83 Linux
    root@durini:~# mount | grep hda
    /dev/hda2 on / type ext3 (rw,errors=remount-ro)
    /dev/hda6 on /home type ext3 (rw)
    /dev/hda1 on /media/hda1 type ext3 (rw)
    /dev/hda3 on /media/hda3 type ext3 (rw)
    root@durini:~#

When trying to install via CD, both Ubuntu-8.04 XUbuntu-8.04 failed
with a message:

 ..............................................
  Failed to creae a file system

  The ext3 file system creation in partition #2
  of SCSI2 (0,0,0) (sda) failed
 ..............................................

Attached is a tar.gz file having inside the following:
 parti-dlg.jpeg - partition dialog
 parti-dlg2.jpeg - ready-to-install dialog
 fail.jpeg - partition fail - dialog
 fdisk-l.out - 'fdisk -l' output. Notice: /dev/sda (should be /dev/hda !?)
 messages - /var/log/message of liveCD whole session .

Similar failures happened using the Xubuntu-Alternate-8.04 CD.

After several failures, I re-installed 7.10, and upgraded to 8.04 using
the 'update-manager' tool.
But then the system failed to but with the default 2.6.24-16 kernel.
I got message of
  ldm_validate_partition_table()
  Disk read failed
  ...
  /dev/disk/by/uuid ... does not exist
  ... Dropped to a shell.
  ... Busybox.

Changing grub to use the 2.6.22-14 kernel fixed this problem.
With this kernel, my disk is recognized as /dev/hda and works well.
So may be the above partition problems are related to the 2.6.24-16 kernel.

-- yotam

Revision history for this message
yw_ys (yw-ys) wrote :

I have very similar problem as Yotam Medini.

Using LiveCD for installation, the creation of ext3 system stalls at 5% and the system freeze (no response to keyboard, mouse).

The system is a Celeron 2.0G with 1G DDR-PC2100 memory, I am trying to make a single boot (not dual-boot) system on a dedicated 40G hard drive. At first, I suspected the LiveCD is not good enough, but it is verified that is a good one.

It looks that using alternate CD will not help either (can somebody please confirm this?).

Then, what if I install Xubuntu 8.04.1? Will that change anything?

I am pretty new on Linux, so please be kind to me. ;)

(BTW, for my case, will installation of a 6.X Xubuntu help? On the other hand, if I somehow managed to install some lightweight Linux, such as puppy, then create ext3 system on that, can the installation of Ubuntu/Xubuntu bypass that fatal step I had? )

Thanks!
-yw_ys

Revision history for this message
jerrylamos (jerrylamos) wrote :

Well, Intrepid Ibex Alpha 2 is under development so expect problems (even severe ones) that will be fixed later. The Alpha 2 announcement said to use the Alternate CD (not the CD Live) which installed just fine on my system; the CD Live fails, on two different PC's. Note the Alternate CD is in text mode.

    * Ubuntu: http://cdimage.ubuntu.com/releases/intrepid/alpha-2/
    * Kubuntu: http://cdimage.ubuntu.com/kubuntu/intrepid/alpha-2/
    * Edubuntu: http://cdimage.ubuntu.com/edubuntu/inrepid/alpha-2/
    * Xubuntu: http://cdimage.ubuntu.com/xubuntu/intrepid/alpha-2/

If you want to get some experience on installs, try Ubuntu Hardy Heron 8.04.1. That's pretty stable. When you get some experience dual boot is good; you can have one linux which works and a second to try out. If the try fails you can usually use the one which works to get going again.

BTW, don't try manual partitioning on the Alternate. It made three partitions of 8.2 mb each on a 20.9 mb drive - obviously that's a don't fit. I used Gparted Live to straighten it out. Hardy Heron Install would also fix this.

Jerry

Revision history for this message
Vadim Peretokin (vperetokin) wrote :

I also have a friend who's running into this issue with the 8.04.1 - possible solutions are welcomed.

Revision history for this message
yw_ys (yw-ys) wrote :

Jerry, thanks for your comments. I guess trying alpha's is a step too bold.

So, I will get the 8.04.1 alternate CD for the next step. I hope that failure in creation ext3 file system is addressed.

If this does not work, I guess I will try an earlier Xubuntu (so that if this succeed, I will try your suggestion to have dual boot).

Thanks again for pointing out some pitholes.

-yw_ys

Revision history for this message
Vincent Martinez (chentewarrior79) wrote :

Hello, I am running into this issue with 8.10, possible solutions would be greatly appreciated.

Revision history for this message
dougj (doug+ub) wrote :

I also was stuck on the "Creating ext3 file system for / in partition #1 on SCSI1 (0.0.0)" error for a long time. The answer is to use the separate partition editor to create new partitions, then do the installation and use those existing partitions. I finally installed Ubuntu 9.04 this way on an old formerly-XP computer.

See also
http://ubuntuforums.org/showthread.php?t=580437
http://ubuntuforums.org/showthread.php?p=2718455#post2718455

Revision history for this message
rusivi2 (rusivi2-deactivatedaccount) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. I noticed the package your bugging is updated in Maverick. Does this occur in it? If so, please feel free to mark this bug as new. Thanks in advance!

tags: added: ubiquity-1.4.11
tags: added: feisty
Colin Watson (cjwatson)
Changed in ubiquity (Ubuntu):
assignee: Colin Watson (cjwatson) → nobody
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for ubiquity (Ubuntu) because there has been no activity for 60 days.]

Changed in ubiquity (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.