stado de
> saída de erro 3
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/736534/+subscribe
>
--
Nika Vidal Amor
Inestable GNU/Linux Users Group Member | http://www.inestable.org
--
You received this bug notification because you
devolveu o estado de
> saída de erro 3
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/714187/+subscribe
>
--
Nika Vidal Amor
Inestable GNU/Linux Users Group Member | http://www.inestable.org
--
You received this bug notif
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/736534
Title:
package python2.7-minimal 2.7.1-5 failed to install/upgrade: o
subproceso script post-installation instalado devolveu o estado de
saída
Public bug reported:
Binary package hint: python2.7
My system can't be upgraded neither dist-upgraded because this packet
isn't installable
ProblemType: Package
DistroRelease: Ubuntu 11.04
Package: python2.7-minimal 2.7.1-5
ProcVersionSignature: Ubuntu 2.6.35-23.40-generic 2.6.35.7
Uname: Linux
Public bug reported:
Binary package hint: python2.7
Problem updating from Maverick to Natty.
"apt-get upgrade" worked fine.
The problem appeared on "apt-get dist-upgrade"
ProblemType: Package
DistroRelease: Ubuntu 11.04
Package: python2.7-minimal 2.7.1-3
ProcVersionSignature: Ubuntu 2.6.35-23.4
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/714187
Title:
package python2.7-minimal 2.7.1-3 failed to install/upgrade: o
subproceso script post-installation instalado devolveu o estado de
saí
I also think it's not a kernel bug (I didn't relate the bug report to
it) cause the kernel panic appears at boot begin, when no modules were
loaded.
In the other report they talk about yaboot as guilty one.
An initrd problem is also probable.
--
Powerbook G4 kernel panic
https://launchpad.net/
I've reinstalled with root partition formatted in ext3 filesystem (other
partitions continue being xfs) and it fix the problem, so the kernel
panic and the access to hda1 were induced by the root partition as xfs.
yaboot.conf wasn't changed from installation, I only added bfboot=hd:
cause yaboot g
I've heard a problem with xfs and grub, not with yaboot, is this the
same?.
I'll reinstall with root partition in ext3 (home, usr and other can be
xfs, can't them?).
Anyway, yaboot is trying to load from /dev/hda1 and it isn't in
yaboot.conf, I dont know if it's the same bug.
Excuse my poor Engl
Public bug reported:
When I reboot, after installing Dapper, I get this:
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-
block(0,0)
My partition table is:
/dev/hda4 Apple bootstrap
/dev/hda8 Root (xfs)
I got it working by chroot, loading installation cd and changing loaded
10 matches
Mail list logo
