Here you go.
** Attachment added: partman
http://launchpadlibrarian.net/44217497/partman
--
unable to create filesystem on 7.5TB partition with lucid beta
https://bugs.launchpad.net/bugs/543838
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
And the other one.
** Attachment added: syslog
http://launchpadlibrarian.net/44217538/syslog
--
unable to create filesystem on 7.5TB partition with lucid beta
https://bugs.launchpad.net/bugs/543838
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Unfortunately, I just tried it with today's daily build (April 10) and
assuming it has the fix, it still gives the same error. Let me know how
else I can help.
--
unable to create filesystem on 7.5TB partition with lucid beta
https://bugs.launchpad.net/bugs/543838
You received this bug
I will test it with the next daily build (looks like the current one out
there was built on the 6th) or BETA2 whichever comes first. Thanks for
looking into it!
--
unable to create filesystem on 7.5TB partition with lucid beta
https://bugs.launchpad.net/bugs/543838
You received this bug
Yes, while it is possible to use the livecd to get a workable system
with mdadm, it is a fairly involved process, and would be even more
difficult to setup with encryption on top of that by hand. Hence, it
would be nice to have an Alternate CD that worked like it used to! If
this is just a
This bug still exist in the latest daily build. It seems that the
alternate CD at present will not work with disks/partitions greater than
2TB.
** Package changed: linux (Ubuntu) = partman-base (Ubuntu)
--
unable to create filesystem on 7.5TB partition with lucid beta
Well, my workaround was use the livecd and install mdadm, and configure
the array manually on the command line before running the installer. It
is far from a perfect install however, because you still have to
manually boot into rescue mode after the install and install mdadm again
and then mess
After trying some more things - I think this is a problem with the
partition manager - not the kernel. If I switch over to console two
during install and manually run mkfs.xfs or mkfs.ext4 or similar
commands on the command line on the large partition, they work fine and
I can then mount the
Public bug reported:
AMD64 Lucid BETA1 Alternate CD seems to have a problem with large
filesystems. I'm thinking the kernel was probably built with the wrong
options maybe, but not sure. I have another identical media server
running AMD64 karmic with this setup running fine so this is something
Running karmic alpha6 (2.6.31-10-generic), this my 88E8001 based sky2
adapter works fine at 100Mb/s, but won't work at 1000Mb/s despite
various ethtool hacks I've tried. It worked fine in Gutsy thru Jaunty.
It seems there is another patch that may be relevant that hopefully we
can get included in
Oops - I was looking at the wrong screen when I typed the chipset in my
last post - should have been:
02:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8053 PCI-E
Gigabit Ethernet Controller (rev 20)
and the relevant kernel snippet:
[ 4586.187722] sky2 eth0: Link is up at 100 Mbps,
This still doesn't work as of today with latest updates installed. I'm
seeing it on a Dell M1330. Jay's fix above makes it work for Vino, but
then of course breaks it if you actually go to the machine.
--
vino: mouse cursor stays in upper left corner
https://bugs.launchpad.net/bugs/337926
You
This problem is still in Hardy too, FWIW. If someone would point me at
the right source package and a quick start on how to submit patches,
I'll make a stab at fixing it. Either that, or perhaps I should report
it on one of the Xorg mailing lists. As I only use ubuntu, I don't know
for certain
Actually, a little more searching found this bug, which is a duplicate -
but does identify the problem as one with gnome-screensaver and
discusses some work arounds and possibilities of fixing.
https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/93466
--
Do not detect Mouse
I agree. OpenJDK isn't ready from prime time - at least on the two
mission critical applications and applets I've tried (which are
unfortunately proprietary or I would include links and test procedures).
Unfortunately, even Sun's JRE isn't a great solution on AMD64 - as there
is no applet
*** This bug is a duplicate of bug 175449 ***
https://bugs.launchpad.net/bugs/175449
Actually, I'm using a Brother MFC-8840D hooked up via USB - and my
problems all went away when I installed the Brother Linux driver you can
download from their site (rather than using the one that gets
I haven't had time to verify the i386 Desktop build of alpha2, but I can
confirm that the AMD64 server build of alpha2 no longer exhibits this problem.
I copied 3TB of data over NFS at full speed with no problems.
- Leann Ogasawara [EMAIL PROTECTED] wrote:
Hardy Heron Alpha2 was recently
FWIW, all my problems went away when I actually installed the Brother
driver rather than using the built-in one that Gutsy suggest. You might
try it.
- directhex [EMAIL PROTECTED] wrote:
Same symptom, on a network-attached MFC-7820N, with my own (private,
unfortunately for bug-test
Public bug reported:
Binary package hint: kernel-image-2.6.22-14-generic-di
Gigabit ethernet adapters use 400-500% more CPU in Gutsy compared to
Feisty for the same load.
To reproduce:
1. Find two computers with gigabit NICs (I've tested with e1000,
rt8169, tg3, sky2, forcedeth) plugged in to
More testing with these boards and latest Gutsy (2.6.22-14-generic x86)
yields the following observations above and beyond those previously
reported:
1. It still locks up under Gutsy latest (I can't tell any change
between 2.6.22-12 and 2.6.22-14). Someone should probably report this
as a
Public bug reported:
Binary package hint: gcc-4.1
I've been trying to build some stuff today, and while basic hello world
apps compile and run, more complicated things invariably yield a
compiler error as follows:
[EMAIL PROTECTED]:~/iperf-1.7.0$ make
rm -f lib/libdast.a
make[1]: Entering
All the problems seem to be fixed in Gutsy latest, with the exception of
the comment in 2) about the Windows key not being passed thru. I can
live with that though.
--
multiple minor problems with KVM (kernel virtual machine)
https://bugs.launchpad.net/bugs/87359
You received this bug
This bug is still in gutsy latest - I hope someone out there is looking
into it.
--
Do not detect Mouse activity on Second screen while on Dual Desktop
Configuration
https://bugs.launchpad.net/bugs/96440
You received this bug notification because you are a member of Ubuntu
Bugs, which is the
Public bug reported:
Binary package hint: rhythmbox
Using gutsy latest:
My music library is stored as FLAC. I have a Nokia N770 that I
occasionally sync music to. HAL correctly recognizes this device, and
mounts it as USB storage. However, when I drag and drop songs/albums
onto it in
Public bug reported:
Binary package hint: evince
This probably shouldn't be filed against evince, but some part of the
cups subsystem but I wasn't sure which part so I filed it against
evince.
When I try to print the attached PDF from evince in gutsy latest, all I
get is a page of paper that
** Attachment added: x360-hd-dvd-offer.pdf
http://launchpadlibrarian.net/9623754/x360-hd-dvd-offer.pdf
--
printer crashing when printing PDF
https://bugs.launchpad.net/bugs/147759
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
** Attachment added: HL-2070N.png
http://launchpadlibrarian.net/9623756/HL-2070N.png
--
printer crashing when printing PDF
https://bugs.launchpad.net/bugs/147759
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs
** Attachment added: MFC-8840D.png
http://launchpadlibrarian.net/9623758/MFC-8840D.png
--
printer crashing when printing PDF
https://bugs.launchpad.net/bugs/147759
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
I've been playing with mplayer SVN and the attached eac3 patch for
playing back EVO files from here:
http://forum.doom9.org/showthread.php?t=129050page=7
Seems to work pretty good. Any chance this stuff could make it in?
** Attachment added: eac3v2.patch
I tried printing several of the sample ODT files in oowriter and they
all came thru fine. I tried the previously attached HL-2070N.png file
in eog, and it gave the same error as the problematic PDF. Hope that
helps.
- Pedro Villavicencio [EMAIL PROTECTED] wrote:
Does it happens with
Public bug reported:
Binary package hint: compiz
Using gutsy latest, I'm having a problem enabling desktop effects on my
second display. I have two LCDs - a 24 soyo as the main display at
1920x1200 and a 20 dell as my secondary that I use rotate to be
1200x1600 (for web browsing). Works fine
** Attachment added: xorg.conf
http://launchpadlibrarian.net/9627749/xorg.conf
--
compiz doesn't work with multiple X screens
https://bugs.launchpad.net/bugs/147814
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
** Attachment added: Screenshot.png
http://launchpadlibrarian.net/9627751/Screenshot.png
--
compiz doesn't work with multiple X screens
https://bugs.launchpad.net/bugs/147814
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
This seems to be caused by a bug in the compiz script. When I run it
from the command line I see:
Checking for Xgl: not present.
Detected PCI ID for VGA: 07:00.0 0300: 10de:0391 (rev a1) (prog-if 00 [VGA])
Checking for texture_from_pixmap: present.
Checking for non power of two support:
I've been testing with Gutsy latest on these boards, and some moderately
good news is that with 2.6.22-12-generic, it seems to take much longer
for the machine to lockup. Using Feisty's 2.6.20 kernel, and the
aforementioned iperf test, it would hang almost instantly. With Gutsy,
it takes 30-60
And how can Nvidia market this as their stable Business Platform?
I'm feeling cheated. If Steen's post is correct, then my motherboard
clearly doesn't do what it claims to do.
I'm ordering a couple of these to see if just disabling the nforce NICs
on these boards will result in a stable system
*** This bug is a duplicate of bug 131530 ***
https://bugs.launchpad.net/bugs/131530
FWIW, this is still a problem with gutsy latest (BETA + all updates) -
but the above workaround still works.
--
Bluetooth fails to connect to phone: obex://[mac:address] is not a valid
location.
I'm seeing this also with trying to pair to a Jabra BT-150 headset. As
the previous post says, installing gnome-vfs-obexftp doesn't solve the
problem - it just changes the error message.
--
connect to bluetooth mouse fails
https://bugs.launchpad.net/bugs/146418
You received this bug
Here are the files you requested (I had to go into restricted drivers
and turn fglrx off of course to get them). I noticed there was a new
version of the ATI driver in this mornings updates - which doesn't
appear to fix the problem.
** Attachment added: xsession-errors
Here are the files you requested (I had to go into restricted drivers
and turn fglrx off of course to get them). I noticed there was a new
version of the ATI driver in this mornings updates - which doesn't
appear to fix the problem.
** Attachment added: Xorg.0.log.old
Adding Option DRI off seems to have fixed it. Let me know if I can
do anything else to help.
- Tormod Volden [EMAIL PROTECTED] wrote:
As the log says Direct rendering experimental on RS400/Xpress 200
enabled. Try disabling DRI with this in the Device section of
xorg.conf:
Option DRI off
Here is a UDF patch that seems to compile and work against the latest
gutsy GIT kernel sources:
It was obtained from:
http://sourceforge.net/tracker/index.php?func=detailaid=1738126group_id=295atid=300295
** Attachment added: UDF_2.50-linux-2.6.22-rc4+.patch.bz2
I try to boot with the nosmp option to test this and 2.6.20-16-generic
just hangs shortly into the boot (no output on any of the virtual
screens). Any ideas on how to work around? I don't really see nosmp as
a viable solution, but am willing to at least validate it as an option
for some. If
Public bug reported:
The following article in the wiki talks about BluRay and HD-DVD support
in Ubuntu:
https://help.ubuntu.com/community/RestrictedFormats/BluRayAndHDDVD
I was really hoping that Gutsy would have the UDF fix and the newer
version of mplayer/ffmpeg that supports playing back
** Attachment added: lspci.out
http://launchpadlibrarian.net/9528413/lspci.out
--
full gnome session hangs with ATI driver and gutsy BETA
https://bugs.launchpad.net/bugs/146138
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
Public bug reported:
Binary package hint: xserver-xorg-driver-ati
I couldn't ever get to the desktop on the LiveCD with gutsy BETA - gnome would
try to login, crash, retry, crash, etc.
Finally, I tried a failsafe X session, that worked, so I tried a failsafe gnome
session, and that worked. I
I've played around with it a bit more, and even with the options
max_interrupt_work=20 set in /etc/modprobe.d/forcedeth, it still
happens. Only additional thing to report, is I happened upon an easy
way to reproduce the hangup every time:
1. Login to machine1 which has a gigabit ethernet card
FWIW, I downloaded the gutsy GIT kernel, built it, and replaced the
forcedeth.ko on my feisty systems with the newer one. I still get a few
of the:
eth0: too many iterations (6) in nv_nic_irq messages
but it doesn't appear to hang anymore under heavy load. I'll be stress
testing it today by
An hour or so into the transfer, using the gutsy forcedeth.ko - the
machine locked up and eth0 stopped responding just like it was doing
with the default feisty version of the module. This is a fairly serious
bug - so I hope someone can escalate it so it gets looked at and
minimally fixed for
I just ran into this bug and it almost cost me data with feisty latest!
For some reason when the forcedeth ethernet adapter locked up, it also
locked up two out of six of my sata ports (I'm presuming because of some
PCI bus issue). Luckily it was raid6, so the array is still functional,
but it
it is work in progress.
- BullCreek [EMAIL PROTECTED] wrote:
I'll try tribe-5 next week when I get a spare moment. Thanks!
- Pedro Villavicencio [EMAIL PROTECTED] wrote:
Could you try to reproduce this in Gutsy? you can get a CD Image
from
here: http://www.ubuntu.com/testing
I'll try tribe-5 next week when I get a spare moment. Thanks!
- Pedro Villavicencio [EMAIL PROTECTED] wrote:
Could you try to reproduce this in Gutsy? you can get a CD Image from
here: http://www.ubuntu.com/testing/ ; thanks in advance.
--
panel problem with dual head on feisty latest
All three stored values (Name, Command, Comment) seem to be improperly
handled. I changed them as follows in order:
Display :0.0
Name: Firefox Left
Command: firefox -P left %u
Comment: Browse the World Wide Web Left
Display :0.1
Name: Firefox Right
Command: firefox -P default %u
Comment:
Public bug reported:
Binary package hint: gnome-panel
I have a dual-head setup with two displays, :0.0 1600x1200 and :0.1
1024x1280 (rotated). Because firefox won't allow more than one instance
access to a profile, I created two firefox icons in the panel, one on
each screen with commands as
I switched over to using the nvidia driver rather than the nv driver,
and everything works perfectly now.
--
evdev not working with multiple X instances
https://bugs.launchpad.net/bugs/121792
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for
Public bug reported:
Binary package hint: xserver-xorg-input-evdev
I'm building a carpc using feisty. I want my two kids in the back to be
able to watch/play independent movies/games, and my prius has a touch
screen that I'm interfacing into in the front for music. Three separate
video cards
** Attachment added: xorg.conf
http://launchpadlibrarian.net/8168635/xorg.conf
--
evdev not working with multiple X instances
https://bugs.launchpad.net/bugs/121792
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
Another good link for more background info:
http://en.wikibooks.org/wiki/Multiterminal_with_evdev
--
evdev not working with multiple X instances
https://bugs.launchpad.net/bugs/121792
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for
Public bug reported:
I'm running feisty on my workstation and my laptop, and in both cases, I
use dual-head. It works great, with one annoying caveat:
If nothing is happening on the primary display, the screen saver will
kick in, no matter that I'm typing and mousing furiously over on the
Public bug reported:
Before I switched to linux, I used to use WMV to archive movies. For TV
shows, I usually used 2 channel WMA for the sound, but for films that I
liked, I converted the 5.1 AC3 to 6 channel WMA PRO. Totem in Feisty
(and Edgy) can't play back the audio on these 6 channel
I tend to agree about this problem needing to be fixed sooner rather
than later if possible since it essentially breaks apt. I ran into it
recently, and there is no easy workaround other than to hack the scripts
enough to make apt-get remove work as mentioned above.
FWIW, I believe the root of
I agree. I don't really think the problem is with mdadm - but instead
with the order that the disk and controller drivers are loaded in
feisty. Don't know what module controls that though. Hopefully this
bug will be addressed before release!
- Original Message -
From: marcw [EMAIL
It started working again around herd 5. Thanks!
--
ubuntu 7.04 feisty herd 2 hangs on install
https://bugs.launchpad.net/bugs/84741
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
Tried it, no joy. If I get time tomorrow I'm going to experiment with
manual changes to the initrd to see if I can work around the module
problem that way. I looked, and while I thought I remembered an mdadm
mailing list, it seems my memory was faulty or it no longer exists. If
you have any
FWIW, the April 2 daily build boots fine from CD whether the network is
plugged in or not - so I guess this bug is fixed.
--
tty missing from busybox in feisty BETA
https://bugs.launchpad.net/bugs/99843
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug
I did, but still the same thing, I think because break=mount doesn't
come into play until later in initrd.
FWIW, I reinstalled the first disk with yesterdays daily build, and I
still get the same thing (namely when I boot off RAID, /dev/hda* and
/dev/hdc* don't show up at all in /proc/partitions
I had a XenExpress 3.2 cd handy to boot in this same machine, and one
thing I note is that it assigns the same hardware/drives significantly
differently.
XenExpress 2.6.16.38 Feisty 2.6.20.13
hd[a-d] Promise Controller 1 hd[a-d] Onboard VIA controller
I think I may have found it. Attempting to boot from RAID,
/proc/ide/ide0/hda/driver is ide-default version 0.9.newide whereas
booting successfully via non-RAID, /proc/ide/ide0/hda/driver is ide-
disk version 1.18.
Googling ide-default ide-disk reveals some bugs/race conditions that
were
I spent part of this afternoon battling the same thing I think using
feisty BETA also. I'm quite familiar with software RAID on linux, and a
few comments:
1. It seems that unlike in older distros, /etc/mdadm/mdadm.conf in
feisty is fairly important. Without adding the ARRAYs entries to it, my
Well after I got home this afternoon, I started downloading a daily build to
test,
but I also accidentally happened to boot the laptop in question with the BETA
disc
still in, and it worked this time. I thought - what's different??? Turns out
I had moved
the laptop and unplugged the
Public bug reported:
Binary package hint: busybox-initramfs
I have an averatec c3500 tablet pc I've been testing feisty on. The
previous herd builds worked fine, but when I go to install the BETA,
booting the CD-ROM, I get the following error during initramfs
initialization:
BusyBox:
/bin/sh:
Public bug reported:
Binary package hint: fglrx-driver
Running latest feisty. The driver works ok, but if I log out, or try to
switch user or even Ctrl+Alt+Backspace the driver locks the laptop up
tight as a drum and I have to power cycle it. Probably nothing anyone
can do, but I thought I'd
Public bug reported:
Binary package hint: totem
I'm going to add this to the community howto if I can, but thought I'd
pass it on as a feature request. I have a new laptop, and just
installed Feisty Herd 5. After following the community howto for Feisty
DVD playback, it wouldn't work (kept
Public bug reported:
I was copying a file from an SMB share to my desktop - the first attempt failed
because my wireless
network crapped out - so on the second attempt, I chose Replace since the
partial file was still
there, and shortly thereafter, the crash occurred. Not sure it was related,
** Attachment added: CoreDump.gz
http://librarian.launchpad.net/6650800/CoreDump.gz
** Attachment added: Dependencies.txt
http://librarian.launchpad.net/6650801/Dependencies.txt
** Attachment added: Disassembly.txt
http://librarian.launchpad.net/6650802/Disassembly.txt
** Attachment
Public bug reported:
Binary package hint: kvm
A few minor problems running on an Acer 5102 WLMi Turion 64-X2 laptop
with 2GB RAM and Feisty 64bit Herd 3.
1. It appears that you have to use sudo to run kvm given the default
permissions on /dev/kvm. Don't know if this is a bug for sure or by
FWIW, after trying herd 3 32 bit, i downloaded and tried herd 3 64 bit,
and it works fine (in fact I'm typing this message on it). Off to see
if I can get WinXP running inside KVM!
--
ubuntu 7.04 feisty herd 2 hangs on install
https://launchpad.net/bugs/84741
--
ubuntu-bugs mailing list
Using herd 2, I was able to work around this problem, by getting rid of
grub/MBR using:
dd if=/dev/zero of=/dev/hda bs=1024 count=1024
All other attempts including manually partitioning still resulted in the
error.
Unfortunately, now I'm getting a different error much further into the
install -
Public bug reported:
Binary package hint: ubiquity
Acer Aspire 5102WLMi Laptop
During the Detecting hardware, please wait... phase near the end of
the install, it says:
Loading module 'sata_sil' for 'ATI Technologies Inc Standard...'
Then, the installer just hangs. I've tried to sudo kill -9
I just downloaded and tried the Herd 3 build of feisty-desktop-i386.iso
and get the same problem with it.
Let me know what else I can do to help.
--
ubuntu 7.04 feisty herd 2 hangs on install
https://launchpad.net/bugs/84741
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Public bug reported:
Binary package hint: ubiquity
Feisty 7.04 Herd 2 i386
Attempting to install onto an Acer Aspire 5100 laptop that previously
had FC6 installed on it. At first I thought maybe the FC6 LVM stuff was
messing it up, so I switched over to a terminal and manually ran fdisk
to
Any status on this? I have three systems (one AMD Turion 64X2 and two
Intel C2D) that exhibit the behavior, and would be happy to help testing
in anyway.
--
Hangs at boot on AMD64
https://launchpad.net/bugs/65788
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
82 matches
Mail list logo
