[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#553195: marked as done (No longer detects mounted Windows partitions)

Your message dated Tue, 17 Nov 2009 05:54:02 -0800
with message-id <20091117135402.GK8151@ftbfs.org>
and subject line Re: Bug#553195: Reproducible if /usr/lib/os-prober/newns replaced with newns.c
has caused the Debian Bug report #553195,
regarding No longer detects mounted Windows partitions
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
553195: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=553195
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package:  os-prober
Version:  1.35

There seems to be a problem with this version detecting Windows 
partitions that are mounted on a system.  I have tried this version then 
reverted back to the 1.29 version which works correcting in finding the 
Windows partition.  I noticed in the bug-reports there was an instance 
of os-prober not finding the MacX partition, which sounds somewhat like 
the problem I am experiencing.  Any help would be welcomed.

In my log file associated with the installer we use, there seems to be 
some problems with the program "newns" as well.  I am including the log 
file, so you may see what I mean.

Thanks,
Patrick


-- 
           ---   KMail 1.12.2--- Zenwalk v6.x - Linux 2.6.31   ---
          "Ever tried Zen computing?"  http://www.zenwalk.org

Installing to: '/dev/sda'

Installation finished. No error reported.
This is the contents of the device map /boot/grub/device.map.
Check if this is correct or not. If any of the lines is incorrect,
fix it and re-run the script `grub-install'.

(hd0)	/dev/sda


Generating grub.cfg ...
Found background: zenwalk.png
Found linux image: /boot/vmlinuz
Found initrd image: /boot/initrd.splash
/usr/lib/os-prober/newns: line 8: syntax error near unexpected token `('
/usr/lib/os-prober/newns: line 8: `int main(int argc, char **argv)'
done

Saved the GRUB2 environment variables to '/etc/default/grub'.

GRUB_DEFAULT='0'
GRUB_TIMEOUT='5'
GRUB_GFXMODE='640x480'
GRUB_TERMINAL_OUTPUT='gfxterm'
GRUB_DISTRIBUTOR='Zenwalk'
GRUB_CMDLINE_LINUX_DEFAULT='splash=silent resume=/dev/sda4 vga=794'
GRUB_CMDLINE_LINUX=' '
GRUB_USE_LINUX_SYMLINK='yes'
GRUB_TARGET='/dev/sda'
GRUB_FONT=''


The installation has finished without errors. You should now be able to use your freshly installed GRUB2.

--- End Message ---
--- Begin Message --- 
Version: 1.35

On Tue, Nov 17, 2009 at 07:44:55AM -0500, BandiPat wrote:
> On Tuesday 17 November 2009, Matt Kraai included these bytes:
> > Hi,
> > 
> > I can reproduce this behavior if I manually replace
> > /usr/lib/os-prober/newns with newns.c extracted from the source
> > package.  BandiPat, have you done anything to newns?  Could you
> >  please send us a copy of it from your system?
> > 
> ========
> Matt,
> Please mark this bug as solved.  Since submitting it, I have found the 
> method in which to make all this work correctly.  I should have given 
> myself more time before submitting a bug report, but I was in a rush to 
> get things working for the new version.  You can close the bug now, as 
> it really wasn't a bug with your code, just the way I was trying to 
> handle it.
> 
> Thanks for your help and patience.  Sorry if this has caused you any 
> inconvenience.
> 
> Bug should be closed.

OK, thanks.  I'm closing the bug with this message.

In the future, if you'd like to close a bug yourself, you can do so by
sending email to BUGNUMBER-done@bugs.debian.org and adding a
"Version:" pseudo-header indicating the version in which it was fixed.

-- 
Matt                                            http://ftbfs.org/kraai

--- End Message ---
Reply to: