-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Soren Hansen wrote:
> On Fri, Feb 22, 2008 at 12:35:14AM -, Soren Hansen wrote:
>>* New release.
>
> Sorry, that was a little.. um.. terse :)
>
> This is a bugfix release that fixes a few typos (well, several instances
> of the same typo, rea
On Fri, Feb 22, 2008 at 12:35:14AM -, Soren Hansen wrote:
>* New release.
Sorry, that was a little.. um.. terse :)
This is a bugfix release that fixes a few typos (well, several instances
of the same typo, really), and fixes a call to qemu-img that breaks
because I added more sanity check
> The Ubuntu QA team has assembled a list of bugs that we think should
> be fixed for Hardy. These are often long-standing bugs or bugs with
> many subscribers, comments or duplicates. They are generally in a
> mature triage state and should be ready to work on. We've split the
> list
On 22/02/08 07:22, Emmet Hikory wrote:
> From a maintenance perspective, it is significantly easier when
> there is only one copy of any given source in the archive. While it
> may be a little more complicated to download the source providing
> linux-restricted-modules-`uname -r` to patch, a full
On 21/02/08 20:28, Matthew Garrett wrote:
> The madwifi code is already in linux-restricted-modules, so there's no
> benefit in providing a separate source package as well.
>
I understand that, however, if you have a machine that has a card that
is not supported by the linux-restricted-modules,
Onno Benschop wrote:
> On 21/02/08 20:28, Matthew Garrett wrote:
> > The madwifi code is already in linux-restricted-modules, so there's no
> > benefit in providing a separate source package as well.
> >
> I understand that, however, if you have a machine that has a card that
> is not supporte
On Wednesday 20 February 2008 07:16:11 Michael T wrote:
> Wouldn't the solution for this just be to add a couple of extra utilities,
> like e.g. srm (== saferm)? This provides the functionality without
> breaking anything. The utilities could also be aliases.
And finally, there is libtrash for al
On Thursday 21 February 2008 13:29, Kenneth Loafman wrote:
> I made the mistake of upgrading to Firefox 3 Beta on Hardy. It has many
> many problems, but the main one is that you can't launch a URL from
> Thunderbird, or elsewhere. You have to copy&paste the URL into the
> browser windows. [ Are
What I just now found was that when I swapped from 'Custom' back to
'Firefox' the links are now being launched. On my system (a Hardy
upgraded from Gutsy), /usr/bin/firefox links to firefox-3.0 which links
to /usr/lib/firefox-3.0b3/firefox.sh. I'm guessing the upgrade may have
done something diff
You should be able to launch URL's from any application just fine in
Firefox 3. Check System->Preferences->Preferred Applications, set Web
Browser to Custom, and use '/usr/lib/firefox-3.0b3/firefox "%s" ' for
the command (this is assuming you have the Firefox3 beta from the Hardy
repos, and not a
I made the mistake of upgrading to Firefox 3 Beta on Hardy. It has many
many problems, but the main one is that you can't launch a URL from
Thunderbird, or elsewhere. You have to copy&paste the URL into the
browser windows. [ Are AOL folks having their revenge? ;-) ]
Long story short, its too
The madwifi code is already in linux-restricted-modules, so there's no
benefit in providing a separate source package as well.
--
Matthew Garrett | [EMAIL PROTECTED]
--
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubu
On Wed, Feb 20, 2008 at 09:19:04AM -0800, Ted Gould wrote:
> Yes, but that HAL patch ignores all battery entries in /proc if it finds
> one in /sys. Which seems rather risky to me... but I was curious if
> that seems logical to those who know the kernel better.
Yes, the only way a battery can en
13 matches
Mail list logo
