Goh Lip wrote:
> Chan Chung Hang Christopher wrote:
>
>>> I take it that you now have no problem booting after the root...setup...
>>> from the livecd.
>>>
>>>
>> Yup.
>>
>>
>>> Grub legacy have precisely some problems not only with LBA cylinder but
>>> also with newer bios. Ins
Dane Mutters wrote:
> It sounds like your menu.lst file in /boot/grub is being overwritten by
> the maintainer's version of the config file from the updated package.
> Usually, if you've edited that file even a little, it'll ask whether you
> want to change it or keep it the same and update it manu
On Sun, 20 Sep 2009 15:53:06 -0400 Andrew SB wrote:
>On Sun, Sep 20, 2009 at 3:25 PM, Sense Hofstede wrote:
>> Reporting bugs against every package would indeed result in a lot of new bug
>> reports, but I do think that it would be a good way of keeping track of
>> the implementation process. We
Benjamin Drung [2009-09-20 21:59 +0200]:
> Start with packages with >= 50 bugs open.
>
> Look at audacity, eclipse, vlc, to name a view.
I'd think that it makes more sense to start with packages which are
actually maintained in Ubuntu, i. e. where someone actually looks at
bugs.
Also, apport hoo
Hello,
I would like to know, if possible, the reasons why SLiM will not be
present in the karmic release, since the SLiM team found a new mantainer
and developpers and the project is still going on.
I also would like to know why the new stable release of tint2 (0.7) has
not been included in kar
Am Sonntag, den 20.09.2009, 15:53 -0400 schrieb Andrew SB:
> As someone who would be willing to write hooks and incorporate
> them into a package, looking at a bug list of over 16,000 wouldn't
> give me any idea where to start.
Start with packages with >= 50 bugs open.
Look at audacity, eclipse,
On Sun, Sep 20, 2009 at 3:25 PM, Sense Hofstede wrote:
> Reporting bugs against every package would indeed result in a lot of new bug
> reports, but I do think that it would be a good way of keeping track of
> the implementation process. We could use python-launchpadbugs to make the
> task easier.
2009/9/20 Andrew SB
> On Sun, Sep 20, 2009 at 10:00 AM, Sense Hofstede wrote:
> > What should this operation do? The idea is to create an 'apport-hook'
> tag,
> > report bugs against all packages (that don't have a hook yet) and start
> > watching the bugs. Then we can write hooks and watch the
On Sun, Sep 20, 2009 at 10:00 AM, Sense Hofstede wrote:
> What should this operation do? The idea is to create an 'apport-hook' tag,
> report bugs against all packages (that don't have a hook yet) and start
> watching the bugs. Then we can write hooks and watch the tag for bugs that
> have a prope
It sounds like your menu.lst file in /boot/grub is being overwritten by
the maintainer's version of the config file from the updated package.
Usually, if you've edited that file even a little, it'll ask whether you
want to change it or keep it the same and update it manually. Something
to consider
2009/9/20 Caroline Ford
> 2009/9/20 Sense Hofstede
>
>> Hello,
>> Recently Brian Murray asked for more Apport hooks to be added to as many
>> packages as possible,[0] because of the choice for Apport as the preferred
>> way to report bugs. (For more information, have a look at the QATeam spec
>>
Chan Chung Hang Christopher wrote:
> Hello all,
>
> What package takes care of shutting down?
>
> I have this problem with Jaunty. When I first installed Jaunty, it
> booted up without problems. However, after an update was done, it would
> always show me a grub error 18 screen on the next atte
> I take it that you now have no problem booting after the root...setup...
> from the livecd.
>
Yup.
> Grub legacy have precisely some problems not only with LBA cylinder but
> also with newer bios. Instead of trying to fix your grub, I suggest you
> convert your grub legacy to grub2. After
> I remember reading something about commenting out some line that did
> something with grub that would solve this problem. Unfortunately I have
> not been able to find that url again and I wondered whether anybody
> knows where a command involving grub during shutdown might be located in
> th
Hello all,
What package takes care of shutting down?
I have this problem with Jaunty. When I first installed Jaunty, it
booted up without problems. However, after an update was done, it would
always show me a grub error 18 screen on the next attempt to boot the
machine after a shutdown.
Booti
2009/9/20 Sense Hofstede
> Hello,
> Recently Brian Murray asked for more Apport hooks to be added to as many
> packages as possible,[0] because of the choice for Apport as the preferred
> way to report bugs. (For more information, have a look at the QATeam spec
> [1])
>
> The move away from the w
Hello,
Recently Brian Murray asked for more Apport hooks to be added to as many
packages as possible,[0] because of the choice for Apport as the preferred
way to report bugs. (For more information, have a look at the QATeam spec
[1])
The move away from the web interface ought to make our lives eas
Mike Pontillo wrote:
>Thank you for your response. I can confirm that rebuilding the same
> version of the valgrind package solves the problem for me as well.
>
>Should anything else be done to triage this? Could other packages
> be lurking in the repository that need to be rebuilt?
TWIMC
18 matches
Mail list logo