Public bug reported:
occured by first installation from USB-stick
ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: libc6-dbg 2.19-0ubuntu6.6
ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
Uname: Linux 3.13.0-24-generic i686
NonfreeKernelModules: nvidia
ApportVersion:
Public bug reported:
update from 2015-10-05
ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: libcuda1-340-updates (not installed)
ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
Uname: Linux 3.13.0-24-generic i686
NonfreeKernelModules: nvidia
ApportVersion: 2.14.1-0ubuntu3.15
Same symptoms here.
--
wake up from suspend ends up as hiberate
https://bugs.launchpad.net/bugs/116826
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Yes, I'm running gutsy, no upload here either.
--
ccontrol SEGVs on startup
https://bugs.launchpad.net/bugs/109157
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Diffs are all very well, but is there any ETA on actually getting the
fixed package into the repository?
--
ccontrol SEGVs on startup
https://bugs.launchpad.net/bugs/109157
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
Ok. It would be good to backport the fix to Feisty at least, which also
has this bug.
--
ccontrol SEGVs on startup
https://bugs.launchpad.net/bugs/109157
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing
Have you used update-initramfs to rebuild the ramdisks once the new
busybox was installed?
--
Segfaults during boot (from mount)
https://bugs.launchpad.net/bugs/131961
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
The busybox fix works here.
--
Segfaults during boot (from mount)
https://bugs.launchpad.net/bugs/131961
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
*** This bug is a duplicate of bug 131961 ***
https://bugs.launchpad.net/bugs/131961
There's now a fix, see the log for bug #131961, of which this is a
duplicate.
** Changed in: initramfs-tools (Ubuntu)
Status: New = Fix Released
--
[gutsy] segmentation fault during boot in
The version with -fno-stack-protectore doesn't seem to have showed up in
the gutsy archive yet. Any ETA on that?
--
ccontrol SEGVs on startup
https://bugs.launchpad.net/bugs/109157
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
Yes, I've been using a custom build with -fno-strack-protector for some
time.
I just retested on the latest source package and it still appears to
work (although I quickly found an unrelated bug in ccontrol-init).
--
ccontrol SEGVs on startup
https://bugs.launchpad.net/bugs/109157
You received
No dice, I'm afraid.
mulberryst:~$ ccontrol
Segmentation fault (core dumped)
--
ccontrol SEGVs on startup
https://bugs.launchpad.net/bugs/109157
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
Oh, that's with:
mulberryst:~$ dpkg -p ccontrol
Package: ccontrol
Priority: optional
Section: devel
Installed-Size: 144
Maintainer: Ubuntu MOTU Developers [EMAIL PROTECTED]
Architecture: i386
Version: 0.9.1+20060806-3
Depends: python, gcc, make, binutils, ccache
Suggests: distcc
Size: 33170
I'm also observing this problem. Here, with a root-on-lvm-on-raid1
setup, these failures confuse the udev initialization sufficiently that
although the system boots, it fails to mount any filesystems other than
root, and things are generally confused later on.
This looks like the same problem as
*** This bug is a duplicate of bug 131961 ***
https://bugs.launchpad.net/bugs/131961
This appears to be the same problem as bug #131961.
** This bug has been marked a duplicate of bug 131961
segfault when booting 2.6.22-9-generic
--
busybox 1:1.1.3-5ubuntu3 mount -o bind crash
Sorry, my mistake. Somehow I had an /et/mdadm/mdadm.conf with bogus
UUID causing the raid assembly failure. Looks like this is, indeed,
fixed.
--
Root fs on LVM on mdadm fails to boot
https://bugs.launchpad.net/bugs/87745
You received this bug notification because you are a member of Ubuntu
In reference to Robert Vollmert's comment: not having any other
filesystems would explain why you don't get further symptoms.
For me, this is a serious bug. In fact, contrary to my previous
comment, the system won't really boot after this - instead it will give
the give root password for
As bug #132120 suggests, I've verified that just replacing the busybox
binary (both as /bin/busybox and /bin/sh on the initramfs) with an
older, working version is sufficient to fix the problem.
Replacing the failing calls to mount with explicit calls to /bin/mount -
thereby invoking the klibc
Martin, but are you seeing the SEGVs during boot?
--
segfault when booting 2.6.22-9-generic
https://bugs.launchpad.net/bugs/131961
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
Ok. How are the devices for your secondary filesystems specified in
/etc/fstab? For me at least, the problem seems to be that some of the
convenience symlinks are not created, so depending on the names you use,
it might work.
--
segfault when booting 2.6.22-9-generic
Uh.. did you forget an attachment there?
--
segfault when booting 2.6.22-9-generic
https://bugs.launchpad.net/bugs/131961
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
I'm afraid that mdadm 2.6.2-1ubuntu2 doesn't fix the problem here. Or
rather, it changes the problem. Now, I drop to an (initramfs) prompt
with one of my md devices unassembled. Previously the md devices all
assembled but LVM did not get started. Now, if I manually assemble the
md at the
I've also observed this problem in gutsy: LVM on md (raid1) fails to
boot, an lvm vgchange -ay on at the (initramfs) prompt is sufficient
to get it working.
My investigations show two parts to the problem. First, udev's 65
-persistent-storage.rules file explicitly excludes md* devices from
I didn't ever see the problem with edgy. However, it's been present for
most of the Feisty development cycle.
--
forcedeth changes MAC address after suspend/resume
https://bugs.launchpad.net/bugs/82108
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug
Public bug reported:
Binary package hint: ccontrol
In Feisty, ccontrol as built from the current ccontrol package gets a
Segmentation Fault immediately after exec(), before executing any other
system calls.
This appears to be because Feisty has made gcc implement stack
protection by default,
Public bug reported:
Binary package hint: workrave
In Feisty, workrave's rest break countdown in the panel no longer
decrements visibly. It still appears to count down internally, and will
eventually pop up the take a rest dialog, however the on-screen
counter never changes, except occasionally
I've hit this problem as well on a G5 with Radeon, in Feisty final.
Driver package version is 6.6.3-2ubuntu6.
With Ben Herrenschmidt's help, tracked the problem down to an Ubuntu
patch which adds some VBE based DDC probing code to the driver as a
fallback. That gets triggered on powerpc, and VBE
Bug also appears with the 2.6.20-9-generic kernel.
--
forcedeth changes MAC address after suspend/resume
https://launchpad.net/bugs/82108
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Like you, I have finite time, I just haven't had a chance to send in the
information yet.
Incidentally, apologies for the lack of information in the first place.
I got sloppy :(.
godiva:~$ uname -a
Linux godiva 2.6.20-8-generic #2 SMP Tue Feb 13 01:14:41 UTC 2007 x86_64
GNU/Linux
lspci
** Attachment added: dmesg output after clean boot
http://librarian.launchpad.net/6522000/dmesg-boot.log
--
forcedeth changes MAC address after suspend/resume
https://launchpad.net/bugs/82108
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Here is the dmesg output after a resume (same boot as the previous dmesg
attachment). On this occasion, the MAC address was clobbered.
In fact, I just noticed that the clobbered MAC address (which is always
the same) is the correct MAC address reversed byte-for-byte:
58:41:6D:2F:11:00 instead of
Public bug reported:
Binary package hint: linux-image-2.6.20-5-generic
After an ACPI suspend-to-RAM and resume, the inbuilt Nforce2 ethernet
adaptor has a different MAC address than it has on an initial boot.
This did not occur with the kernel from edgy.
** Affects: linux-source-2.6.20 (Ubuntu)
32 matches
Mail list logo
