midisport-firmware; please replace Ubuntu package with package from Debian

2008-04-07 Thread Forest Bond
Hi,

I am not sure who this request should go to.

I am the maintainer of the Ubuntu package midisport-firmware.  This package has
never worked correctly OOTB, due to changes in udev/usbfs.  This will again be
the case in Hardy.

I am no longer in possession of my midisport device, which has made testing
difficult for me.  Further, I'm quite busy with other things, and have neglected
to keep this package up-to-date with the udev/usbfs changes that seem to occur
once every 3-6 months, and without obvious notification for a package maintainer
like myself.

Debian now has a midisport-firmware package that should be used instead.  The
potential for regression is zero, since this was already broken in Gutsy.

Please drop the Ubuntu package and sync from Debian.  It would be really great
if this could be done for Hardy.  I would hate to see yet another Ubuntu release
with broken support for these devices.

Thanks,
Forest
-- 
Forest Bond
http://www.alittletooquiet.net
http://www.pytagsfs.org


signature.asc
Description: Digital signature
-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss


Re: Please keep the old IDE chipset drivers so that external CD writers can work

2008-04-07 Thread Rick Knight
Wenzhuo Zhang wrote:
> Rick Knight wrote:
>
>   
>> I downloaded the Kubuntu 8.04 Desktop CD ISO, burned the ISO and booted.
>> It DOES install my hard drives as /dev/hd devices, not /dev/sd and I can
>> access them without any problem, so whatever is causing my problem with
>> Gutsy, has been fixed in Hardy. Also, I think tells me my Via controller
>> is not compatible with libata.
>> 
>
> In Feisty and Gutsy kernels, the IDE driver via82cxxx is the only driver
> that supports VIA_82C586_1(1106:0571), and the new libata based driver
> pata_via is not enabled. So the Gutsy problem you experienced is probably
> a regression of via82cxxx driver introduced in linux-image-2.6.22.
>
> Starting from linux-image-2.6.24-13.23, via82cxxx is disabled in favor
> of pata_via. Kubuntu 8.04 beta CD ships with 2.6.24-12, which includes
> both via82cxxx and pata_via. Judging from the fact your drives are
> recognized as /dev/hd?, via82cxxx is loaded first, which means the
> via82cxxx issue has been fixed in 2.6.24-12.
>
> You may want to download and install all the hardy updates up-to-date
> using Update Manager. linux-image-2.6.25-15-generic will be installed
> in the update process. Be sure to remove the IDE drivers you added to
> /etc/initramfs-tools/modules before starting to update. You'll then find
> out whether pata_via is working properly for VIA_82C586_1. If it does
> not work for you, you can file another bug report.
>
> Wenzhuo
>   
Wenzhuo,

I'm not sure I follow you here. Are you suggesting I upgrade to the 
Hardy beta, or just set my repositories to Hardy and update. Won't that 
be an upgrade? How stable is Hardy. I know the code freeze is this week, 
but is it safe to upgrade to Hardy?

Also, I rebuilt the Gutsy kernel to add support for the pata_via module, 
but that didn't help, I still can't boot into the Gutsy kernel.

Thanks,
Rick

-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss


Problems with SELinux

2008-04-07 Thread Marc Baas
Dear all,

Since I don't know where else to put this problem I ran into and I
cannot specify it clearly enough to file a bug report, I'm sending it to
this mail group.

I've been testing Hardy since early alpha 6. I also tried installing
SELinux according to the specifications of the Ubuntu SELinux wiki (run
sudo apt-get install selinux) and it worked flawlessly for me at the
time.

Today I tried it again on a current up to date beta of hardy. I call it
a clean install since I haven't manually changed anything and have only
installed packages with apt that I normally do by default through a
script, to not have to do everything manually.
This time however, after rebooting and having the labeling finish, I was
welcomed with a message telling me HAL failed to initialize. On top of
that, while it was first loading, the whole gnome menu disappeared and
left me with nothing but an empty desktop. Immagine Alt+F2 didn't work
either.

I managed to work around this and get a terminal going, tried to restart
HAL, but got permission errors from SELinux telling me that this user
was not allowed to, etc.

Needless to say, lots of things were not working (at some point even my
ethernet adapter was blocked) and in the end, I removed SELinux in order
to be able to use my system. Hence I don't have all the detailed info
one could wish for in order to file a bug report.
Due to lack of time and wanting to be sure things would run properly I
went ahead and did a reinstall.

As a result of this I'm under the impression that the policies that came
with alpha 6, which worked fine for me, must have been changed one way
or another and now don't work for me anymore.
Is this something that can be confirmed by the ones that are working on
the implementation of SELinux?

Together with that, when can we expect configuration tools for SELinux
like the ones one finds in Fedora? It really is very user unfriendly and
complex to work with SELinux and try to configure it with the tools, let
alone without those.

Thanks in advance for your time and attention.

Marc



-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss


Re: midisport-firmware; please replace Ubuntu package with package from Debian

2008-04-07 Thread Conrad Knauer
On Mon, Apr 7, 2008 at 6:22 AM, Forest Bond <[EMAIL PROTECTED]> wrote:

> Please drop the Ubuntu [midisport-firmware] package and sync from Debian.
and
> I am not sure who this request should go to.

That would be bugs.launchpad.net wouldn't it? :)

I've filed it for you:
https://bugs.launchpad.net/ubuntu/+source/midisport-firmware/+bug/213498

CK

-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss


Re: midisport-firmware; please replace Ubuntu package with package from Debian

2008-04-07 Thread Scott Kitterman
On Monday 07 April 2008 14:36, Conrad Knauer wrote:
> On Mon, Apr 7, 2008 at 6:22 AM, Forest Bond <[EMAIL PROTECTED]> 
wrote:
> > Please drop the Ubuntu [midisport-firmware] package and sync from Debian.
>
> and
>
> > I am not sure who this request should go to.
>
> That would be bugs.launchpad.net wouldn't it? :)
>
> I've filed it for you:
> https://bugs.launchpad.net/ubuntu/+source/midisport-firmware/+bug/213498
>
> CK

Actually we can't currently sync due to different source tarballs, but the 
Debian changes have been merged into the Ubuntu package now.  Thanks for hte 
heads up.

Scott K

midisport-firmware (1.2+dsfg1-0ubuntu4) hardy; urgency=low

  * Merge w/ debian:
- Drop debian/po/ directory.  Firmware now included.
- Drop debian/README.Debian
- Drop debian/{config,postinst,preinst,postrm, templates}
- Update debian/control
- Update debian/dirs
- Drop debian/install
- Add debian/menu
- Update udev rules. (LP: #193891)
- Fix watch file
- Update debian/rules
- Update Makefile.in to put firmware outside /lib.

  * In the even there is a new version this package can
be synced.  It hasn't been synced now because our version
number (1.2+dsfg1) is greater than upstream's (1.2).  Adding
an epoch now would make this a worse situation.

 -- Mario Limonciello < [EMAIL PROTECTED]>   Mon, 07 Apr 2008 09:22:06 -0500

-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss


pulseaudio enabled on dist-upgrades?

2008-04-07 Thread Matt Price
i notice on my hardy upgrade that pulseaudio, though installed, is not
active by default.  is there a standard way to enable it on upgrades?
the wiki lists this for gutsy:
https://wiki.ubuntu.com/PulseAudio
but that looks dated.  happy to write up any changes for the wiki if a
developer knows more & can respond on thel ist.  thanks,
matt



-- 
Matt Price
[EMAIL PROTECTED]

-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss


Re: Problem with Grub being installed in MBR as default (GG)

2008-04-07 Thread Nigel Henry
On Tuesday 01 April 2008 21:09, Mackenzie Morgan wrote:
> On Tue, 2008-04-01 at 20:53 +0200, Nigel Henry wrote:
> > On Tuesday 01 April 2008 19:35, Mackenzie Morgan wrote:
> > > On Tue, 2008-04-01 at 19:23 +0200, Nigel Henry wrote:
> > > > The request I have is, is it possible to include options as to where
> > > > the bootloader is going to be installed in Gutsy Gibbons installer
> > > > program, as are present in other distros. The default is usually the
> > > > MBR, but you are usually presented with other places to install the
> > > > bootloader.
> > >
> > > It's an option in the "Advanced" button on the "confirmation page" of
> > > the installer that says what's going where, what settings you chose,
> > > and lists that GRUB is going on the MBR.
> >
> > Thanks for your quick reply. I've since got the Grub bootloader for Gutsy
> > Gibbon installed on the / partition for GG, and now have access to all 4
> > distros on the harddrive again.
> >
> > I'll try another install of GG, if I can find space on another drive. I'd
> > obviously missed the "Advanced" button on the "confirmation page" of the
> > installer.
>
> By confirmation page, I just mean that last page before you hit the
> "Apply" or "Install" or whatever it is button where it lists all your
> choices.

I'm just installing another instance of Gutsy Gibbon on one of my drives, and 
as you say the "Advanced" button is there on the confirmation page you 
mention above, but can easily be missed, as I did on my first install of 
Gutsy Gibbon, and ended up with Gutsy Gibbons Grub overwriting my FC2 Grub 
that was in the MBR, with chainloaders to other distros on the drive.

Yes. Gutsy Gibbons Grub had all the kernels listed for FC2, Debian Etch, and 
Debian Lenny, but as the the kernels for Debian Etch, and Lenny are the same, 
it would be a bit hit and miss as to which Debian version I would be booting.

Personally I think it would be better to have a separate page for the 
bootloader, as on other distros, and where you have choices presented to you 
as to where you want to install the bootloader. In most cases the default of 
installing to the MBR would be ok if you were a first time user of the 
distro, but for those of us that have dual/triple installs on the drive, 
options as to where you want to install the bootloader, I'm sure would be 
appreciated.

Just some thoughts.

Nigel.





-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss


Re: pulseaudio enabled on dist-upgrades?

2008-04-07 Thread James Westby
On Mon, 2008-04-07 at 13:31 -0700, Matt Price wrote:
> i notice on my hardy upgrade that pulseaudio, though installed, is not
> active by default.  is there a standard way to enable it on upgrades?
> the wiki lists this for gutsy:
> https://wiki.ubuntu.com/PulseAudio
> but that looks dated.  happy to write up any changes for the wiki if a
> developer knows more & can respond on thel ist.  thanks,
> matt

Hi,

pulseaudio doesn't start because of the file

  /etc/default/pulseaudio

the comments in their explain how to make it start. I don't know
if you need to do anything else.

Thanks,

James



-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss


Re: pulseaudio enabled on dist-upgrades?

2008-04-07 Thread Christopher James Halse Rogers
On Mon, 2008-04-07 at 21:51 +0100, James Westby wrote:
> On Mon, 2008-04-07 at 13:31 -0700, Matt Price wrote:
> > i notice on my hardy upgrade that pulseaudio, though installed, is not
> > active by default.  is there a standard way to enable it on upgrades?
> > the wiki lists this for gutsy:
> > https://wiki.ubuntu.com/PulseAudio
> > but that looks dated.  happy to write up any changes for the wiki if a
> > developer knows more & can respond on thel ist.  thanks,
> > matt
> 
> Hi,
> 
> pulseaudio doesn't start because of the file
> 
>   /etc/default/pulseaudio
> 
> the comments in their explain how to make it start. I don't know
> if you need to do anything else.

My understanding is that we don't use the system-wide daemon even on
fresh installs, because running per-user daemons offers less of a
security target (among other things) and works just as well or better.
My system is far from a vanilla dist-upgrade, but I believe that
System->Preferences->Sound->Sounds->Enable Software Mixing is the button
you want to press.  Assuming the pulseaudio ESD bridge is installed as a
part of the upgrade (I believe it is), that will get gnome-session to
start pulseaudio on login.


signature.asc
Description: This is a digitally signed message part
-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss


Re: pulseaudio enabled on dist-upgrades?

2008-04-07 Thread Luke Yelavich
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Tue, Apr 08, 2008 at 06:31:05AM EST, Matt Price wrote:
> i notice on my hardy upgrade that pulseaudio, though installed, is not
> active by default.  is there a standard way to enable it on upgrades?

Since PulseAudio only runs per user, it will not run unless you have enabled 
the software sound mixing option in GNOME.

Luke
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFH+qDvjVefwtBjIM4RAqjTAKDafnIxzBbz2jds4OSGIJ3Wz0FEsACfe5Z4
hxy0i9dqqZOyQoYDiNOHef8=
=r3BZ
-END PGP SIGNATURE-

-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss


Re: Problem with Grub being installed in MBR as default (GG)

2008-04-07 Thread Gezim Hoxha
>
> Personally I think it would be better to have a separate page for the
> bootloader, as on other distros, and where you have choices presented to
> you
> as to where you want to install the bootloader. In most cases the default
> of
> installing to the MBR would be ok if you were a first time user of the
> distro, but for those of us that have dual/triple installs on the drive,
> options as to where you want to install the bootloader, I'm sure would be
> appreciated.
>

Adding a new page would first, confuse new users (potentially) and second,
it's an extra page that you have to click through; I think it's not a good
idea.

Regards,
-Gezim
-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss


Re: Problem with Grub being installed in MBR as default (GG)

2008-04-07 Thread Onno Benschop
On 08/04/08 04:39, Nigel Henry wrote:
> I'm just installing another instance of Gutsy Gibbon on one of my drives, and 
> as you say the "Advanced" button is there on the confirmation page you 
> mention above, but can easily be missed, as I did on my first install of 
> Gutsy Gibbon, and ended up with Gutsy Gibbons Grub overwriting my FC2 Grub 
> that was in the MBR, with chainloaders to other distros on the drive.
>
> Yes. Gutsy Gibbons Grub had all the kernels listed for FC2, Debian Etch, and 
> Debian Lenny, but as the the kernels for Debian Etch, and Lenny are the same, 
> it would be a bit hit and miss as to which Debian version I would be booting.
>
> Personally I think it would be better to have a separate page for the 
> bootloader, as on other distros, and where you have choices presented to you 
> as to where you want to install the bootloader. In most cases the default of 
> installing to the MBR would be ok if you were a first time user of the 
> distro, but for those of us that have dual/triple installs on the drive, 
> options as to where you want to install the bootloader, I'm sure would be 
> appreciated.
>   

Words fail me.

Personally I'd like to take this opportunity to thank the developers who
wrote software that was able to detect kernels across at least 4
operating systems, (Etch, Lenny, FC2 and two instances of Gutsy).

As for the suggestion; adding 30 seconds of effort to 99.9% of
installations for the "benefit" of 0.1% of the users seems a step
backward, both for Ubuntu and society as a whole.

-- 
Onno Benschop

Connected via Optus B3 at S31°54'06" - E115°50'39" (Yokine, WA)
--
()/)/)()..ASCII for Onno..
|>>?..EBCDIC for Onno..
--- -. -. ---   ..Morse for Onno..

ITmaze   -   ABN: 56 178 057 063   -  ph: 04 1219    -   [EMAIL PROTECTED]



-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss


Re: Problem with Grub being installed in MBR as default (GG)

2008-04-07 Thread Felix Miata
On 2008/04/07 17:11 (GMT-0600) Gezim Hoxha apparently typed:

> Adding a new page would first, confuse new users (potentially) and second,
> it's an extra page that you have to click through; I think it's not a good
> idea.

Right. Better to be rude like windoz and automatically overwrite the MBR 
contents without asking for permission or explaining the consequences first. :-(
-- 
"Either the constitution controls the judges, or the
judges rewrite the constitution." Judge Robert Bork

 Team OS/2 ** Reg. Linux User #211409

Felix Miata  ***  http://fm.no-ip.com/

-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss


Re: Problem with Grub being installed in MBR as default (GG)

2008-04-07 Thread Evan
IMHO, adding a boot-loader page to the installer would cause more trouble
than it's worth with new users.

However, the 'advanced' button should be far more visible. Make it bigger,
and label it 'configure boot-loader' or something. Very few people will use
it, but those who do need to be able to find it without a map.

Just my two cents.
-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss


Re: pulseaudio enabled on dist-upgrades?

2008-04-07 Thread Mario Vukelic
On Tue, 2008-04-08 at 08:31 +1000, Christopher James Halse Rogers wrote:
> System->Preferences->Sound->Sounds->Enable Software Mixing

Exactly


-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss


Re: pulseaudio enabled on dist-upgrades?

2008-04-07 Thread Mario Vukelic
On Mon, 2008-04-07 at 21:51 +0100, James Westby wrote:
> the comments in their explain how to make it start. I don't know
> if you need to do anything else.

The comment also explains why you shouldn't start it from there :) See
the other replies about running the daemon per-user from the Gnome
preferences.


-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss