Public bug reported:
Binary package hint: findutils
In a fresh install of Intrepid there is no '/etc/cron.daily/find' file.
However, when upgrading from Hardy to Intrepid, a previously existing
'/etc/cron.daily/find' is retained (and even included in
/var/lib/dpkg/info/findutils.list which I find
My previous note about this bug being corrected in intrepid and kernel
2.6.27 was a bit premature: currently with the linux-
image-2.6.27-7-generic version 2.6.27-7.16 the problem still occurs
quite often. It has been improved a little, namely only the first 'stat
file' results in 'stat: cannot st
The firmware file /lib/firmware/dvb-usb-af9015.fw in linux-firmware-1.11
of jaunty seems a bit old (apparently v. 4.65.0). If this file is
changed to v. 4.95.0 (as suggested by http://www.linuxtv.org/pipermail
/linux-dvb/2009-June/032211.html) the looping error message 'af9015:
command failed:255'
I can reproduce this with intrepid up-to-date as of 29-Oct-2008 with the
steps above and with the same error messages.
The same crash can be triggered at least with both "Link" and "Image"
buttons, by using the "folder" icon in the appearing dialogs to browse
for the file to be linked. When the f
Public bug reported:
Binary package hint: e2fsprogs
e2fsprogs version: 1.41.0-3ubuntu3 in Intrepid features a new option '-t' to
select the filesystem
type. This explicit selection is however silently ignored if other options
imply/require a more
"advanced" filesystem, ext2 -> ext3 -> ext4.
T
"man mke2fs" (dated "July 2008" in the man page headers) describes the
'-t' option as:
-t fs-type
Specify the filesystem (i.e., ext2, ext3, ext4, etc., is to be
created. If this option is not specified mke2fs will pick a
default either how the
The 'man mke2fs' of upstream 1.41.2 (released on 02-Oct-2008) contains an
updated
description of the '-t' option, thanks Theodore! I don't know if it is too
late for Intrepid
to incorporate 1.41.2, probably it is...
--
mke2fs creates ext4 ignoring '-t ext3' if ext4 features specified
https://b
I'm also running 8.04.1 with linux-image-2.6.24-19-generic
(2.6.24-19.41) and I can confirm this problem.
By running 'while true; do date; ls -il .Xauthority ; sleep 1; done' on
both my Ubuntu client and Debian etch NFS server (running
2.6.18-6-amd64) I can see that doing a 'ssh -X third-machine'
We performed further testing with NFS clients of various kernel versions:
- Debian etch with 2.6.18.dfsg.1-22etch2: ok
- Ubuntu Hardy 8.04.1 with linux-image-2.6.24-19-generic 2.6.24-19.41: stat()
returns ESTALE indefinitely
- Debian etch with vanilla kernel.org 2.6.26.1: ok
- Ubuntu Intrepid
Further testing with various kernel versions seem to confirm this bug to
be specific to NFS clients running a 2.6.24 kernel.
** Changed in: linux (Ubuntu)
Sourcepackagename: openssh => linux
Status: New => Confirmed
--
ssh -X breaks Xauthority on NFS mounted home dir
https://bugs.launchpa
Ah, the easiest steps to reproduce:
1) Take two NFS clients, one of which is running 2.6.24-something (machine B)
and the other can run any version (machine A). You can equally well use the
NFS server itself as machine A, as long as machine B is running 2.6.24 NFS
client.
2) On A: 'touch file'.
Public bug reported:
Binary package hint: nut-usb
The file /etc/udev/rules.d/025_nut-usbups.rules does not conform to Ubuntu
conventions
of udev rules files. It should apparently be
/etc/udev/rules.d/25-nut-usbups.rules or similar.
With the name starting with 025 this causes USB UPS HID device
Public bug reported:
Both in jaunty-desktop(i386/amd64) and jaunty-server the drbd subsystem
is started by '/etc/rc2.d/S70drbd' script which does not interact well
with the network-device-based filesystems being mounted by '/etc/network
/if-up.d/mountnfs' after network devices have all come up (a
Architecture: amd64
DistroRelease: Ubuntu 9.04
Package: drbd8
ProcEnviron:
SHELL=/bin/bash
LANG=en_US.UTF-8
Uname: Linux 2.6.28-15-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare vboxusers
--
drbd devices not automatically mounted via /etc/fstab even witn _netdev
h
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/33044209/Dependencies.txt
--
drbd devices not automatically mounted via /etc/fstab even witn _netdev
https://bugs.launchpad.net/bugs/443321
You received this bug notification because you are a member of Ubuntu
Bugs, which i
I mentioned that this affects jaunty-server, too, but I forgot to
describe how. By default the server edition doesn't rely on "if-up.d"
mechanism but relies on /etc/rcS.d/S40networking to bring up what is
defined in /etc/network/interfaces and then gives
/etc/rcS.d/S45mountnfs.sh a chance to do NF
We have exactly the same kind of ATI board ("01:00.0 VGA compatible
controller: ATI Technologies Inc RV350 AS [Radeon 9550]") which we can
quite reliably and quickly crash in Jaunty by just taking "Preferences /
Screensaver" and with "Preview" previewing some 3D-intensive
screensavers; "SkyRocket"
I fiddled with AGPMode and other settings (and did not file a new bug
since nothing helped).
Model: MicroStar MS-7030 motherboard
Host bridge [0600]: nVidia Corporation nForce3 250Gb Host Bridge [10de:00e1]
(rev a1)
01:00.0 VGA compatible controller [0300]: ATI Technologies Inc RV350 AS [Radeon
Public bug reported:
In bionic, pdl package (based on 2.019-5 upstream) had working
PDL::Graphics::PGPLOT interface.
In focal, pdl package is based on 2.020-3 and upstream changed the
generation of PDL::Graphics::PGPLOT interface to only happen if the
build machine has libpgplot* libraries instal
19 matches
Mail list logo
