Correction to my previous comment above (#114) - I meant that 0327(.0)
build was OK.
--
Crash from ide_pci from generic.ko for jmicron controllers
https://launchpad.net/bugs/84964
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
I confirm that Asus P5B-VM (with ICH8 and JMicron) now boots the 0326
amd64 live cd.
I tested with the RAID option for JMicron. Remains to be seen whether
the AHCI and BASIC options work too.
--
Crash from ide_pci from generic.ko for jmicron controllers
https://launchpad.net/bugs/84964
--
ubun
@Gheorge: Heh, it took me 5 minutes to realize that you mean the feisty-
desktop-amd64.manifest on the website and not a file in the iso
If you mean to look at the "linux-generic" line, 0326 has 2.6.20.12.9
So it seems we have to wait one more day (unless there's a 0326.1
under way) Of co
(Does launchpad eat comments? I posted this earlier today and it
dissapeared. Here it is:)
The 2 last picasaweb screenshots posted by MightyE confirm my
observation regarding a floppy problem (see comment 94). I was unable to
see the I/O dev fd0 error because I was booting from the live cd.
Ben m
Still same problem on Asus P5B-VM (ICH8 + Jmicron) with 2.6.20-12.20,
amd64 live 0322 does not boot.
>From what it seems this kernel has fixed ICH6 problems (see bug #93648).
We keep praying for a 0322.1 or a 0323.
--
modprobe abnormal exit - Kernel 2.6.20-8/9/10/11/12 does not boot
https://laun
Sorry to be a pita, but I have made a similar comment in bug #93648 and
I repost it here reversed, just in case the testers and developers of
the 2 bugs have no interaction: Bug #93648 has the same symptoms
(modprobe abnormal exit) with the present one and both seem to be
related to ICHx Intel chip
Judging from the photo above, and the "abnormal exit" message, I think
this bug is somehow related to the also critical bug #84964, which
involves 965 chipsets and ICH5, ICH7R and ICH8 controllers. However, on
the bug's discussions, the Jmicron controller is mostly blamed, and not
so much ICHx. Ple
Still not working on 0320 amd64 desktop, the live cd cannot boot.
I don't know if this is helpful, but all recent days' live cds during
boot attempt to access the floppy about 15 times, then the sequence
results in "abnormal exit".
Could someone please explain why this bug is categorised as "fixe
Sorry for the delay in answering you, I was very busy
all these weeks and interrupted my regular testing
sessions - moreover, I just saw your mail today.
It seems that few people test amd64 (at least in VM),
so perhaps this bug still exists. I plan to check on
Herd4 or later and will add my remark
Confirming it for Herd3 amd64 live, which is identical to 20070201.2 (in
vmware)
There is a bug about a herd3 candidates' alternate cd checking that
leads to crash, maybe these two are related.
--
'check' boots live system on amd64/desktop
https://launchpad.net/bugs/82856
--
ubuntu-bugs mailin
Confirmed in herd3 amd64, which by the way is identical to 20070201.2 so
it has the same bugs.
--
daily live comes with crash report - pre-populated!
https://launchpad.net/bugs/80589
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
I happened to run cdcheck too when testing 20070201 alternate amd64
(because it was missing md5 info) and it worked ok.
If you check the desktop, please use the Herd3 one.
--
error when attempting to test Cd integrity - Feisty
https://launchpad.net/bugs/82033
--
ubuntu-bugs mailing list
ubuntu
Correct, apologise if my comment was not clear enough. Confirm: It did
not appear in 20070131 nor in 20070201.0 (2 new versions already exist
for today,not tested the current one yet). Will let you know if it
reappears.
--
feisty amd64 desktop-live corrupts vmnat service in vmware
https://launchp
I hope there is still time to fix this before Herd3 is released for
testing. Still persists in 20070201 amd64 desktop
Is it possible that this is not a real bug but an artifact, i.e. a file
in /var/crash that gets by accident into the iso distribution and gets
detected by the crash report routine
Bug is fixed in 20070131 amd64 desktop-live
--
feisty amd64 desktop-live corrupts vmnat service in vmware
https://launchpad.net/bugs/82367
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Public bug reported:
(This is a repost of bug #82248 that was misfiled in the ubuntu-iso-
tests section, so I file it here anew. It also has appeared
independently today in the Feisty Fawn Discussions in Ubuntu forums and
does not seem to be a duplicate of any other bug.)
Builds affected:
- feis
Crash also happens with 20070129 & 30 amd64 desktop live (in vmware) for
a bit different reason, see attached log.
** Attachment added: "crash report"
http://librarian.launchpad.net/5933995/_usr_sbin_update-app-install.0.crash
--
Add/Remove programs crashed on Feisty
https://launchpad.net/bug
All the past 10 daily builds of feisty amd64 desktop (in vmware) sufffer
from both bugs and posted workarounds do not work for me. Today's crash
report (20070128) follows:
~$ sudo update-manager
Password:
warning: could not initiate dbus
Unhandled exception in thread started by >
Traceback (most r
I am testing all daily builds of feisty amd64 desktop in VMware (host is
64bit windows), and I never had this bug, installation always proceeded
ok.
However, In this weeks builds, feisty added debug messages during boot.
For the last 3-4 daily builds, there appear several messages regarding
harddi
This bug has been declared as fixed, however I did not manage to see any
improvement when testing all this week's (up to Jan 26) builds of amd64
desktop, which has built-in gnome-app-install version 0.3.6
Might be a particularity of amd64 and/or my testing in vmware.
--
Add/Remove programs crash
I would suggest looking at the changes between today's 20070127 and
yesterday's builds. This bug was fixed for all this week's daily builds
and reappeared just today.
As I have commented in Launchpad some days ago, the disk is partitioned
correctly but feisty cannot format the partitions. The pc f
Today' iso build 20070127 of the amd64 desktop iso has the same old
herd2 bug during installation - it can create partitions but cannot
format them. The machine freezes totally with 100% cpu.
This bug was fixed and reappeared just today - all this week's builds
were OK.
I am testing feisty in vmw
update-manager is 0.53.3
python-dbusis 0.71.3ubuntu1
It seems that more precisely this is bug #81220 so I posted the crash
log there too.
** Attachment added: "crash report"
http://librarian.launchpad.net/5839331/_usr_bin_update-manager.1000.crash
--
update-manager crashed in feist
I can confirm it on a fresh install of 20070123 amd64 desktop as a VM in
vmware.
** Attachment added: "crash report"
http://librarian.launchpad.net/5839319/_usr_bin_update-manager.1000.crash
--
Update Manager Crashes in Feisty when Icon in Panel Clicked
https://launchpad.net/bugs/81220
--
u
** Attachment added: "Stacktrace.txt"
http://librarian.launchpad.net/5839298/Stacktrace.txt
--
evolution-alarm-notify crashes on login of feisty amd64 desktop
https://launchpad.net/bugs/81246
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/
** Attachment added: "ThreadStacktrace.txt"
http://librarian.launchpad.net/5839299/ThreadStacktrace.txt
** Description changed:
Binary package hint: evolution
- same problem here on fresh 20070123 iso amd64 desktop installation in
- vmware (all available updates installed).
+ Note: may b
** Attachment added: "Registers.txt"
http://librarian.launchpad.net/5839297/Registers.txt
--
evolution-alarm-notify crashes on login of feisty amd64 desktop
https://launchpad.net/bugs/81246
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ub
** Attachment added: "ProcStatus.txt"
http://librarian.launchpad.net/5839296/ProcStatus.txt
--
evolution-alarm-notify crashes on login of feisty amd64 desktop
https://launchpad.net/bugs/81246
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/
** Attachment added: "Disassembly.txt"
http://librarian.launchpad.net/5839294/Disassembly.txt
--
evolution-alarm-notify crashes on login of feisty amd64 desktop
https://launchpad.net/bugs/81246
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinf
** Attachment added: "Dependencies.txt"
http://librarian.launchpad.net/5839293/Dependencies.txt
--
evolution-alarm-notify crashes on login of feisty amd64 desktop
https://launchpad.net/bugs/81246
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listi
** Attachment added: "ProcMaps.txt"
http://librarian.launchpad.net/5839295/ProcMaps.txt
--
evolution-alarm-notify crashes on login of feisty amd64 desktop
https://launchpad.net/bugs/81246
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubun
Public bug reported:
Binary package hint: evolution
Note: may be a duplicate of #66860 (I may have pressed 'submit' as a new
bug rather hastily).
evolution-alarm-notify crashes on fresh 20070123 iso amd64 desktop
installation in vmware (all available updates installed). This was fixed
in some pr
It does not seem to be fixed in 20070123 amd64 desktop iso installation
(in vmware).
After installing all the 37 updates, the bug persists for me.
Running update-manager in a root terminal gives:
warning: could not initiate dbus
Unhandled exception in thread started by >
Traceback (most recent ca
As I reported in http://www.ubuntuforums.org/showthread.php?t=341532 the
crash exists in 20070120 amd64 desktop (as a VM guest).
In previous daily builds installing the available distribution updates
permanently removed this particular crash, on subsequent reboots.
The crash notification says "So
According to my testing I can confirm the bug on post Herd2 amd64.
Installing 20070117 alternate amd64 on a physical HDD (sata) with
existing partitions fails in the same way - the installer cannot choose
for installation neither free space nor select pre-formatted / and /swap
partitions .
Howeve
Yesterday I dloaded both live and alternate 0117 builds for X64 and
tested them first in VMware.
The live x64 CD (after doing the debconf thing) hangs during
partitioning. Rebooting the live CD showed that the virtual HD was
partitioned correctly but not formatted (ext3 + swap). The problem must
b
I have been plagued by the same debconf problem in all post Herd2 daily
amd64 builds (which are my interest).
The wonderful workaround described here allowed me to proceed, but then
I stumbled again in the same error depicted in 3c.png
May the bug fairy come to your dreams so you wake up with a s
37 matches
Mail list logo
