Confirmed. I can reproduce this, and a user in the forums also hit it
http://ubuntuforums.org/showpost.php?p=7446117postcount=21. Manually
installing dpkg-dev allows the module to build successfully.
** Changed in: bcmwl (Ubuntu)
Status: New = Confirmed
--
Unable to build driver on AMD64
Public bug reported:
Binary package hint: gedit
The modelines plugin doesn't quite work as documented in the gedit
manual. Modelines are not recognized on some lines where there should
be, and they are recognized on some lines where they should not be.
Expected results (according to the
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/25988762/Dependencies.txt
** Attachment added: ProcMaps.txt
http://launchpadlibrarian.net/25988763/ProcMaps.txt
** Attachment added: ProcStatus.txt
http://launchpadlibrarian.net/25988764/ProcStatus.txt
** Description
Yes. The other day, I temporarily enabled the root account so I could
use it with cupsaddsmb. When I was done, I locked it with 'sudo passwd
-l root' per the instructions in
https://help.ubuntu.com/community/RootSudo.
Actually, I just did some more searching bases on what you said, and it
looks
s/bases on/based on/
--
package pygopherd 2.0.17 failed to install/upgrade: subprocess
post-installation script returned error exit status 1
https://bugs.launchpad.net/bugs/251696
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Public bug reported:
Binary package hint: pygopherd
Here's what happens when I try to install pygopherd:
[EMAIL PROTECTED]:~$ sudo apt-get install pygopherd
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following NEW packages will be
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/16295190/Dependencies.txt
** Attachment added: DpkgTerminalLog.txt
http://launchpadlibrarian.net/16295191/DpkgTerminalLog.txt
--
package pygopherd 2.0.17 failed to install/upgrade: subprocess
post-installation script
Show the mount point (with '/media/' prefix stripped off) instead of
'XX MB removable device' for mounted volumes without a label.
This behavior seems to be broken in Hardy. I have a computer with two
external hard drives (NTFS-formatted) mounted to /media/external and
/media/backup,
Ah, I think you may have misunderstood me. I agree 100% that we
shouldn't expect users to work around this problem on their own. That
would be extremely lame.
All I was trying to suggest is that instead of waiting until the next
kernel update to fix this, Ubuntu could just release an update to
While I agree that this is a serious and very annoying bug, I don't
think a kernel backport is necessary to fix it. A simple udev rule is
all that's needed to make sure the allow_restart flag is always set.
Here's how to fix it on Gutsy:
1) Open a terminal.
2) Type [ sudo nano
Oops, I typo'd the udev rule in my last comment. It is missing a comma.
Oddly enough, udev appears to parse it just fine, but I doubt you'll
want to rely on that.
Here's the correct version:
# Set the allow_restart flag for all USB mass storage devices
ACTION==add, \
SUBSYSTEM==scsi, DRIVER==sd,
Double oops. It turns out that the last udev rule I posted doesn't
always work. I can't figure out why that is, but here's a simpler rule
that seems to work all of the time.
# Set the allow_restart flag for all SCSI disks.
ACTION==add, \
SUBSYSTEM==scsi_disk, \
ATTR{allow_restart}=1
(Note that
** Attachment added: Patch for
/usr/share/hal/fdi/policy/10osvendor/20-storage-methods.fdi adding the above
options
http://launchpadlibrarian.net/8519573/patch.diff
--
hal doesn't allow several valid options for NTFS filesystems
https://bugs.launchpad.net/bugs/126798
You received this bug
Public bug reported:
Binary package hint: hal
On Feisty with hal 0.5.8.1-4ubuntu12, there are several valid NTFS-3G
mount options that are not listed in the volume.mount.valid_options key
for NTFS filesystems. This can cause mounting NTFS-3G devices through
GNOME to fail unnecessarily.
I
14 matches
Mail list logo
