As kubuntu-11.10-alpha3 will not install, I have run apport from an
ubuntu-11.04 installation on the same machine.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ht
apport information
** Attachment added: "PciMultimedia.txt"
https://bugs.launchpad.net/bugs/829142/+attachment/2351363/+files/PciMultimedia.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/829142
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/829142/+attachment/2351371/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/829142
Titl
apport information
** Attachment added: "UdevLog.txt"
https://bugs.launchpad.net/bugs/829142/+attachment/2351370/+files/UdevLog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/829142
Title:
ke
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/829142/+attachment/2351369/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/829142
Title:
kern
apport information
** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/829142/+attachment/2351368/+files/RfKill.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/829142
Title:
kern
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/829142/+attachment/2351366/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/8291
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/829142/+attachment/2351367/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/829142
Ti
apport information
** Attachment added: "ProcCpuinfo_.txt"
https://bugs.launchpad.net/bugs/829142/+attachment/2351365/+files/ProcCpuinfo_.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/829142
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/829142/+attachment/2351364/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/829142
Ti
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/829142/+attachment/2351362/+files/Lsusb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/829142
Title:
kernel
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/829142/+attachment/2351361/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/829142
Title:
kernel
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/829142/+attachment/2351360/+files/IwConfig.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/829142
Title:
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/829142/+attachment/2351359/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/829142
apport information
** Attachment added: "Card0.Codecs.codec.1.txt"
https://bugs.launchpad.net/bugs/829142/+attachment/2351358/+files/Card0.Codecs.codec.1.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.n
apport information
** Attachment added: "Card0.Codecs.codec.0.txt"
https://bugs.launchpad.net/bugs/829142/+attachment/2351357/+files/Card0.Codecs.codec.0.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.n
apport information
** Attachment added: "Card0.Amixer.values.txt"
https://bugs.launchpad.net/bugs/829142/+attachment/2351356/+files/Card0.Amixer.values.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net
apport information
** Attachment added: "BootDmesg.txt"
https://bugs.launchpad.net/bugs/829142/+attachment/2351355/+files/BootDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/829142
Title:
apport information
** Attachment added: "ArecordDevices.txt"
https://bugs.launchpad.net/bugs/829142/+attachment/2351354/+files/ArecordDevices.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/8291
apport information
** Attachment added: "AplayDevices.txt"
https://bugs.launchpad.net/bugs/829142/+attachment/2351353/+files/AplayDevices.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/829142
apport information
** Attachment added: "AlsaDevices.txt"
https://bugs.launchpad.net/bugs/829142/+attachment/2351352/+files/AlsaDevices.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/829142
Ti
apport information
** Tags added: apport-collected natty
** Description changed:
After booting kubuntu-alpha3 from USB, and running the installer the
kernel reports
kernel BUG at /build/builddd/linux-3.0.0/fs/btrfs/super.c:984
Invalid opcode: [#1] SMP
EIP is at btrfs_calc_avail
Public bug reported:
After booting kubuntu-alpha3 from USB, and running the installer the
kernel reports
kernel BUG at /build/builddd/linux-3.0.0/fs/btrfs/super.c:984
Invalid opcode: [#1] SMP
EIP is at btrfs_calc_avail_data_space + 0x375/0x380
call trace:
? kmem_cache_alloc +0x11d/0x140
?
Ok, found the issue: a kernel will only boot in Lucid if devtmpfs is
compiled in. Just setting the following in my .config results in a
successful boot:
CONFIG_DEVTMPFS=y
CONFIG_DEVTMPFS_MOUNT=y
Just to repeat: this is a change that occurred late in the lucid
development cycle; before then, devtm
Some more testing results:
* lucid alpha-3 boots fine with exactly the same kernel that fails to
boot under current (released) lucid. So this *is* something that got
broken recently.
* lucid's current kernel (2.6.32-22) + initrd boots fine with
root=/dev/sda5
So previousy, /dev/sd* nodes were be
The weird "logging function" messages have just gone away; can't
replicate now. Don't know why.
The "--script not working" comment was not well phrased; the problem is
actually that parted doesn't accept commands to execute from stdin. I could
swear this worked before, ie
echo "mklabel msdos"
I should point out that labelling this as related to the "mountall"
package is only a guess. The problem could be devtmpfs or udev or
something else in that area.
I have noted that if I press "M" (maintenance shell), then type "mount"
it shows that "/dev/sda5" *is* mounted as the rootfs. And I can
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/47859484/Dependencies.txt
--
parted shows "custom logging function", --script not working
https://bugs.launchpad.net/bugs/575672
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribe
Public bug reported:
Binary package hint: parted
I've been using parted regularly with lucid lynx betas without problems.
But just recently I have started seeing two problems:
(1) the "--script" option doesn't appear to work any more.
(2) When I run parted commands (other than "p") manually, I g
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/47856418/Dependencies.txt
--
cannot boot custom kernel with no initrd
https://bugs.launchpad.net/bugs/575666
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ub
Public bug reported:
Binary package hint: mountall
Trying to boot a custom kernel without an initrd (hence using
root=/dev/sda5) causes the "waiting for /" message to be displayed, and
then no progress is made.
Booting the standard Ubuntu kernel with root=/dev/sda5 works. And doing
"sudo mount"
2.6.32-21 fixes this issue for me (without any "raden.new_pll=0").
--
severe graphics flicker for radeon
https://bugs.launchpad.net/bugs/538344
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@list
Tried 2.6.32-18 : flicker still there; this kernel therefore unusable
for me.
--
severe graphics flicker for radeon
https://bugs.launchpad.net/bugs/538344
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubunt
No, I have no ntfs partition. The one I can't mount is '/', of type ext4
(see grub.cfg entry above).
What I have noticed is that if I get the 'waiting for / [SM]' message,
and select M then ctrl-d, booting continues correctly.
This suggests to me that the filesystem ('/' in my case) did in fact
m
The bug related to eternal "waiting for / [SM]" appears to be a real
problem then.
The message "mountall.c:2726: Not reached assertion failed" is
unfortunately not helpful though. I've looked at mountall.c, and that
message is simply because we both pressed , when the valid
choices were "[SM]", ie
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/41358442/Dependencies.txt
--
Not reached assertion failed in boredom_timeout
https://bugs.launchpad.net/bugs/542378
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Binary package hint: mountall
Booting the normal lucid kernel works fine.
Booting a custom 2.6.34-rc1 kernel *intermittently* causes the following:
mountall:mountall.c:2726: Not reached assertion failed in boredom_timeout
General error mounting filesystems
and a maintena
I've done further testing, and can say:
2.6.33 --> flicker
2.6.34 pre rc1 (commit 3474cbd11df8cdd6413781ea95bd51dd469098ff) is good, no
flicker.
So at least the problem appears to have been fixed in HEAD. Hopefully
the patch will find its way into the 2.6.32 series soon..
And booting with "n
Public bug reported:
When booting Lucid with linux-image-2.6.32-14, graphics works fine.
But booting with 2.6.32-16 triggers nasty flickering.
Weirdly, the flickering does not happen immediately. If I boot the bad
kernel from a "cold" system then the login screen displays fine. Without
doing any
I can confirm that it originally failed for me ("/sbin"), and by
updating manually to "/sbin/crda" resolved the issue.
I have tried manually changing it to "/sbin//crda" and this also works
fine for me. So the first fix probably did resolve the issue, despite
the odd-looking extra slash.
If you c
Also confirmed: editing /lib/udev/rules.d/85-regulatory.rules as shown by
syscon-hh fixed this issue for me too.
Problem was caused during a jaunty update I performed on March 4 (prev update
was a few days before).
Hardware was iwl3945, network was hidden.
--
wireless-crda breaks capability to
41 matches
Mail list logo
