Well I won't agree the guest shouldn't have its own policy (it depends
on your use case), but I do agree the host should be able to set a
domain to protect it self from the guest, but until AppArmor supports
policy stacking the solution is either or.
The solution depends on what confinement is
1. If the guest is to have its own policy, then the host needs to create
a new policy namespace, and then it needs to transition the guest to the
new namespace. Guest policy will then be loaded into the new namespace,
and will not generally* conflict with system policy.
That's great - can
** CVE removed: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2012-0055
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/915941
Title:
overlayfs does not honor lxc-related
I have uploaded some test kernels with a fix
http://people.canonical.com/~jj/linux-image-3.2.0-12-generic_3.2.0-12.21~aadentry_amd64.deb
http://people.canonical.com/~jj/linux-headers-3.2.0-12-generic_3.2.0-12.21~aadentry_amd64.deb
--
You received this bug notification because you are a member
** Changed in: linux (Ubuntu)
Status: In Progress = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/925024
Title:
apparmor makes it impossible to install
I have a test kernel at
http://people.canonical.com/~jj/linux-
image-3.2.0-23-generic_3.2.0-23.36~aa_amd64.deb
and believe this to be the same as Bug #978038
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
** Package changed: lxc (Ubuntu) = apparmor (Ubuntu)
** Changed in: apparmor (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1061537
Title:
thankyou for reporting this,
I can suggest a work around while you wait for a fix to logprof
edit the /etc/apparmor.d/abstractions/lxc/container-base file and comment out
the line that has
capability,
by changing it to
# capability,
do this to any line containing a mount rule too.
mount
Francesco,
The mediate_deleted flag should fix the rejection shown in comment #12
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/969299
Title:
apparmor prevents dpkg-divert and
Serge,
see comments on bug 970647, there is some progress but I have not found
a specific bug affecting logging of this case. The larger fix which is
the extended labeling, is in progress and will enter into the apparmor-
dev ppa soon for testing.
--
You received this bug notification because
I went back and retested this and it has already been fixed and released
(commit fcbc05a1be0a7600153e78207dcb8b62fe753a4a), it was just not
properly closed.
mapl,
If you are running an updated hardy guest running the 2.6.24-29 kernel this bug
should not be a problem. Can you please provide
So I have experimented with this a bit and so far I haven't gotten an
instance to boot without the patch. It should work, so I just need to
tinker with it more.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in ubuntu.
I took a look at this and it is behaving correctly, though I haven't
established whether it is due to a deviation in AppArmor's behavior, the
scripts or both. The executable /sbin/dhclient3 does a Px transition
(as specified in its profile) to /sbin/dhclient-script.
/sbin/dhclient-script
This turns out to be a regression in Jaunty, that is now fixed and
behaving properly in Karmic
** Changed in: linux (Ubuntu Karmic)
Status: Confirmed = Invalid
--
dhclient-script fails with apparmor
https://bugs.launchpad.net/bugs/400349
You received this bug notification because you are
practice.
** Changed in: linux (Ubuntu Jaunty)
Status: New = Confirmed
** Changed in: linux (Ubuntu Jaunty)
Assignee: (unassigned) = John Johansen (jjohansen)
--
dhclient-script fails with apparmor
https://bugs.launchpad.net/bugs/400349
You received this bug notification because you
No I haven't been able to confirm it is a kernel issue yet, though I am
planning on devoting some good time to this bug over the next couple
days.
--
Frequent random KVM host kernel OOPS
https://bugs.launchpad.net/bugs/361819
You received this bug notification because you are a member of Ubuntu
** Changed in: linux (Ubuntu Maverick)
Assignee: (unassigned) = John Johansen (jjohansen)
--
pad block corrupted error when trying to register an image with 2.6.34 kernel
https://bugs.launchpad.net/bugs/588861
You received this bug notification because you are a member of Ubuntu
Server Team
I haven't, though it is possible I just haven't spent enough time
testing it in karmic yet.
--
Frequent random KVM host kernel OOPS
https://bugs.launchpad.net/bugs/361819
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to kvm in ubuntu.
--
I have placed a test kernel at
http://kernel.ubuntu.com/~jj/linux-image-2.6.31-14-generic_2.6.31-14.48~jj_amd64.deb
--
apparmor complains about write access to a readonly file
https://bugs.launchpad.net/bugs/453335
You received this bug notification because you are a member of Ubuntu
Server
** Changed in: linux (Ubuntu)
Status: Triaged = In Progress
** Changed in: linux (Ubuntu Karmic)
Status: Triaged = In Progress
--
apparmor complains about write access to a readonly file
https://bugs.launchpad.net/bugs/453335
You received this bug notification because you are a
The syntax allows for spaces or commas to separate items, because people
kept using them. However list of items must be inside of parenthesis.
mount options in (rw, slave),
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in
Ondergetekende, can you provide further details to why you believe Bug
#1326367 is causing this? Would you be willing to test a
3.11.0-24-generic kernel (reported stable) + the futex fix, or a chosen
stable version of the 3.13 or 3.15 kernel with just the futex fix. To
verify that the futex fix is
This looks like it might be caused by bug in path lookups and bind mount
handling that I have a test patch for. I will build a test kernel for
trusty (14.04). Please let me know if there are any other kernels you
would like to test on.
--
You received this bug notification because you are a
I have uploaded a kernel with the potential fix to
http://people.canonical.com/~jj/lp1357103/
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1357103
Title:
apparmor denied a golang
Can you please attach the output of
apparmor_parser -p /etc/apparmor.d/usr.bin.lxc-start
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1401148
Title:
Re/starting an lxc container
This is a side effect of linux personalities. When booting on an ia32
machine hardy has the READ_IMPLIES_EXEC flag set in its personality.
This causes an mmap for read permission to also ask for PROT_EXEC, which
causes the extra 'm' request seen above. Ubuntu by default is mounting
several
sorry, I jumped the gun slightly and mis read a mount line and a piece
of code. The nosuid option does interact with this but is not whats
causing the clearing of the personality. Execution of any setuid binary
will cause the personality to get cleared, so using either su or sudo to
switch from
Vincent can you attach your /var/log/messages if present
/var/log/audit/audit.log
--
fails to start: cannot apply additional memory protection after relocation -
apparmor doesn't work on stacked file system (livecd)
https://bugs.launchpad.net/bugs/131976
You received this bug notification
The log isn't displaying correctly in the browser because its type is
set as html, but it is a plain text file.
The log is corrupt but in a very odd way that I have never encountered
before. I have a few possible ideas:
Your kernel ring buffer is being filled and the messages are wrapping,
If auditd is working for you, I wouldn't worry about it.
If however you want to use syslog or just want to try debugging this I
can walk you through it step by step. It really wouldn't be much more
than copying and pasting some script lines and commenting others out.
--
Corrupted AppArmor
okay the first thing I want you to try is removing the use of dd from
the auditing chain
open /etc/init.d/klogd in an editor (you need to be root), find the line
that looks like this
# shovel /proc/kmsg to pipe readable by klogd user
start-stop-daemon --start --pidfile $kmsgpidfile
your console log (near the end) shows that klogd is not running, which means
none of the kernel messages will get logged.
21:06:01~ps aux | grep logd
syslog5093 0.1 0.0 1916 700 ?Ss 20:35 0:03 /sbin/syslogd
-u syslog
ubuntu8032 0.0 0.0 2976 768 pts/0R+
Sadly the man pages didn't get updated to reflect locking, append,
network rules, or change_profile, this is a bug and you can add it to
launch pad or reference the bug filed in the forge bugzilla
https://bugzilla.novell.com/show_bug.cgi?id=326210.
genprof/logprof should be able to update the
hmm, strange it works for me. Is there away that I can get a login on
the machine, and take a look at what is going on?
If not I will see what else we can do.
--
Corrupted AppArmor audit log messages
https://bugs.launchpad.net/bugs/160238
You received this bug notification because you are a
Could you provide more detail about how your system is crashing? What
part of your system is crashing? Is this a default fiesty install or
have installed a custom kernel? I didn't see any oops in your dmesg
dump. The only error that I can see is the message below
audit(1196006403.262:3):
You can either manually edit the klogd profile or use the profiling tool
logprof.
logprof /sbin/klogd
logprof should scan your log file and find the reject and then ask to add r
permission for /proc/kallsyms, saying
yes will allow this and then you can save and place the profile in enforce
Okay thankyou, looking at the kmesg dump it would appear I need to look
into the kernel auditing code more closely.
As for not being able to start klogd, sorry about that I seemed to have
edited my local profiles for testing long ago and had forgotten about
making the changes.
--
Corrupted
Both of those flags would be easy to implement, the question is it worth it?
As Kees pointed out an unconfined user can easily circumvent policy attachment
and thus the flags that AppArmor would be enforcing. There are four cases I
can see this working in:
- trusted start up of deamon, only
Sean,
would it be possible to attach your log files or a section of them so that I
can analyze why it is requiring
@{HOME}/Desktop/ w,
@{HOME}/Desktop/* w,
--
cups-pdf fails to generate file when user does not print to default ~/PDF
(apparmor vs.cups-pdf inconsistency)
well, I can confirm it, and even provide some insight.
MUGEN does some very uhm interesting things on startup. It creates a
new elf file in tmp, uses open to pin the file and then it deletes it.
This results in the file being removed from the namespace and completely
inaccessable except to
hrmm, well it seems I did fix this for unconfined processes before the
final version of hardy (I remember fixing it for AppArmor 2.3 but I
thought the fix missed Hardy), and my test machine wasn't properly
updating. So after a fresh install MUGEN now works.
So to clarify, in Hardy MUGEN will run
Well I can say that this isn't related to
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/140508 as the
problem there was a message format change and not the message being
logged.
Since messages being sent to the kernel ring buffer (dmesg), we can
infer that auditd isn't running. What
could you take a look and verify the messages are showing up in
/var/log/syslog and /var/log/kern.log
and could you also attach your /etc/apparmor/logprofi.conf
--
Profile violations fail to log correctly
https://bugs.launchpad.net/bugs/157952
You received this bug notification because you are
err sorry for the typo the config file is /etc/apparmor/logprof.conf
--
Profile violations fail to log correctly
https://bugs.launchpad.net/bugs/157952
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
Can you check and see if the genprof marks and kernel messages are going
to /var/log/syslog and if they both are can you try editing your
/etc/apparmor/logprof.conf
from
logfiles = /var/log/audit/audit.log /var/log/messages /var/log/syslog
to
logfiles = /var/log/syslog
--
Profile
If the above doesn't work could you include the output from the
following command
ps aux | grep logd
--
Profile violations fail to log correctly
https://bugs.launchpad.net/bugs/157952
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for
Your ps output shows that klogd isn't running. This means none of the
kernel messages will make it to syslog.
do ps aux | grep logd and kill the dd process and then run
/etc/init.d/klogd start, then rerun ps aux | grep logd to make sure
klogd and syslogd are running. If they are try profiling
Glad to hear it worked. My guess is that it happened because Ubuntu
runs klogd under the klogd user instead of root.
--
Profile violations fail to log correctly
https://bugs.launchpad.net/bugs/157952
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug
No that shouldn't have caused this oops. If the trace is good, it would
either be the security context missing, or the profile having a null
value. My guess is the latter as we have had a couple bugs with that
after replacement/removal (though I thought all of those had been
fixed).
--
This may have already been fixed in proposed by commit
df0c3fa26fb5214c30f8f40753f99ef40b475451
--
apparmor crashing apache when removing/changing hats
https://bugs.launchpad.net/bugs/502442
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Same conflict here with a tablet pc. The failure message from synaptic
is:
Could not mark all packages for installation or upgrade
The following packages have unresolvable dependencies.
Make sure that all required repositories are added and enabled
in the preferences.
xserver-xorg-input-wacom:
Make that xserver-xorg-core
Which is installed.
--
xserver-xorg-input-wacom conflicts with xserver-xorg-core
https://bugs.launchpad.net/bugs/501206
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Link was this a clean Karmic 64 bit install that is failing?
Also what happens if you add apparmor=0 to the grub command line?
--
Fresh Install of Karmic, Boot ends with Kernel Panic
https://bugs.launchpad.net/bugs/477050
You received this bug notification because you are a member of Ubuntu
Yes I have now tested with the linux-backports-modules-wireless-karmic-
generic and a fully updated karmic but the problem persists. Network
manager now reports it as connect speed unknown and iwconfig as Bit
Rate=0 kb/s.
--
Wireless reports connection Bit Rate=0 kb/s
** Changed in: linux (Ubuntu Karmic)
Status: In Progress = Invalid
** Changed in: linux (Ubuntu Lucid)
Status: In Progress = Invalid
--
aufs fchown() bug caused by apparmor
https://bugs.launchpad.net/bugs/487097
You received this bug notification because you are a member of Ubuntu
This bug has been isolated to the dfa and transition table generation in
the apparmor_parser, the HOMEDIRS tunable triggered this by causing many
extra states to be generated. The bug is not Atom specific but the
Atom doesn't deal well with the current code doing the generation.
There are a
I have placed a test kernel with the fix at
http://kernel.ubuntu.com/~jj/linux-image-2.6.31-14-generic_2.6.31-14.48~jj_amd64.deb
--
apparmor fails to log change_hat transitions
https://bugs.launchpad.net/bugs/462824
You received this bug notification because you are a member of Ubuntu
Bugs,
I have placed a test kernel with a fix at
http://kernel.ubuntu.com/~jj/linux-image-2.6.31-14-generic_2.6.31-14.48~jj_amd64.deb
--
apparmor_parser: page allocation failure. order:5
https://bugs.launchpad.net/bugs/458299
You received this bug notification because you are a member of Ubuntu
I have placed a test kernel at
http://kernel.ubuntu.com/~jj/linux-image-2.6.31-14-generic_2.6.31-14.48~jj_amd64.deb
--
apparmor complains about write access to a readonly file
https://bugs.launchpad.net/bugs/453335
You received this bug notification because you are a member of Ubuntu
Bugs, which
I have placed a test kernel at
http://kernel.ubuntu.com/~jj/linux-image-2.6.31-14-generic_2.6.31-14.48~jj_amd64.deb
--
apparmor disallows truncate of deleted file
https://bugs.launchpad.net/bugs/451375
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Iakov,
yes you will need to reenable the apparmor firefox profile to reproduce,
however I have already had reports of issues with the patch and I am
working on a new version so I would wait for the newer version.
--
apparmor disallows truncate of deleted file
Kees,
have you been able to reproduce this, recently? I have been hammering
AA with restarts and replacements and it has survived a torture run of
more than 10,000 replacements with several running in parallel.
--
BUG: soft lockup - CPU#2 stuck for 61s! [apparmor_parser:30147]
** Attachment added: proposed patch, fixing both deleted file delegation and
creation
http://launchpadlibrarian.net/33573232/aa.diff
--
apparmor not properly handling file deletion on NFS
https://bugs.launchpad.net/bugs/415632
You received this bug notification because you are a member of
This seems to have been two issues,
1. AppArmor was enforcing tighter deleted file delegation semantics and
2. With the new hook placement under certain filesystems creation of files/nods
was showing up as deleted paths.
The attached patch is the proposed fix and a test kernel with the patch
** Changed in: linux (Ubuntu)
Status: New = Invalid
** Changed in: linux (Ubuntu)
Status: Invalid = New
--
BUG: soft lockup - CPU#2 stuck for 61s! [apparmor_parser:30147]
https://bugs.launchpad.net/bugs/424440
You received this bug notification because you are a member of Ubuntu
I haven't, though it is possible I just haven't spent enough time
testing it in karmic yet.
--
Frequent random KVM host kernel OOPS
https://bugs.launchpad.net/bugs/361819
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
This appears to be fixed now, I haven't tested in awhile so I can't
which update fixed it, but I can no longer reproduce with the latest
updates.
--
[i965GM] Screen goes blank after rotation
https://bugs.launchpad.net/bugs/410309
You received this bug notification because you are a member of
** Changed in: linux (Ubuntu)
Status: New = Fix Released
--
BUG: soft lockup - CPU#2 stuck for 61s! [apparmor_parser:30147]
https://bugs.launchpad.net/bugs/424440
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
*** This bug is a duplicate of bug 415632 ***
https://bugs.launchpad.net/bugs/415632
** This bug has been marked a duplicate of bug 415632
apparmor not properly handling file deletion on NFS
--
Error creating files on NFS
https://bugs.launchpad.net/bugs/261525
You received this bug
*** This bug is a duplicate of bug 415632 ***
https://bugs.launchpad.net/bugs/415632
I have marked this as a duplicate Bug #415632 as that bug exposed
problems with the handling of some creation operations on NFS. Bug
415632 was exposing it self in a slightly different way so it is
possible
Hi David,
There were some fixes to profile loading/replacement/removal that went
in that may be related to this bug but I haven't been able to confirm or
deny that, nor replicate this bug. It would be good to now if you have
seen an oops recently even if you can't readily reproduce.
--
BUG:
At this time, this is not possible, priority ordering by hierarchy (ie
local rules taking precedence over include rules) is not currently
implemented and deny rules take precedence over allow rules.
--
most specific AppArmor rule doesn't always match
https://bugs.launchpad.net/bugs/451422
You
, unconfined_str);
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: John Johansen (jjohansen)
Status: Confirmed
** Changed in: linux (Ubuntu)
Status: New = Confirmed
** Changed in: linux (Ubuntu)
Assignee: (unassigned) = John Johansen (jjohansen)
--
AppArmor
Public bug reported:
Wireless iface is not reporting connection speed
iwconfig reports Bit Rate=0 kb/s, network manager connection information
reports Speed unknown.
ProblemType: Bug
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: Intel [HDA Intel],
** Attachment added: AlsaDevices.txt
http://launchpadlibrarian.net/34447802/AlsaDevices.txt
** Attachment added: AplayDevices.txt
http://launchpadlibrarian.net/34447804/AplayDevices.txt
** Attachment added: BootDmesg.txt
http://launchpadlibrarian.net/34447805/BootDmesg.txt
**
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: ubuntu 4771 F pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xfe8f8000 irq 16'
Mixer name : 'Realtek ALC888'
Components :
** Attachment added: AlsaDevices.txt
http://launchpadlibrarian.net/34448644/AlsaDevices.txt
--
Wireless reports connection Bit Rate=0 kb/s
https://bugs.launchpad.net/bugs/461830
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Attachment added: AplayDevices.txt
http://launchpadlibrarian.net/34448645/AplayDevices.txt
--
Wireless reports connection Bit Rate=0 kb/s
https://bugs.launchpad.net/bugs/461830
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Attachment added: BootDmesg.txt
http://launchpadlibrarian.net/34448648/BootDmesg.txt
--
Wireless reports connection Bit Rate=0 kb/s
https://bugs.launchpad.net/bugs/461830
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Attachment added: ArecordDevices.txt
http://launchpadlibrarian.net/34448646/ArecordDevices.txt
--
Wireless reports connection Bit Rate=0 kb/s
https://bugs.launchpad.net/bugs/461830
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: Card0.Codecs.codec.0.txt
http://launchpadlibrarian.net/34448651/Card0.Codecs.codec.0.txt
--
Wireless reports connection Bit Rate=0 kb/s
https://bugs.launchpad.net/bugs/461830
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
** Attachment added: Card0.Amixer.values.txt
http://launchpadlibrarian.net/34448649/Card0.Amixer.values.txt
--
Wireless reports connection Bit Rate=0 kb/s
https://bugs.launchpad.net/bugs/461830
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Attachment added: CurrentDmesg.txt
http://launchpadlibrarian.net/34448652/CurrentDmesg.txt
--
Wireless reports connection Bit Rate=0 kb/s
https://bugs.launchpad.net/bugs/461830
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Attachment added: IwConfig.txt
http://launchpadlibrarian.net/34448653/IwConfig.txt
--
Wireless reports connection Bit Rate=0 kb/s
https://bugs.launchpad.net/bugs/461830
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Attachment added: Lspci.txt
http://launchpadlibrarian.net/34448654/Lspci.txt
--
Wireless reports connection Bit Rate=0 kb/s
https://bugs.launchpad.net/bugs/461830
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
** Attachment added: Lsusb.txt
http://launchpadlibrarian.net/34448655/Lsusb.txt
--
Wireless reports connection Bit Rate=0 kb/s
https://bugs.launchpad.net/bugs/461830
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
** Attachment added: PciMultimedia.txt
http://launchpadlibrarian.net/34448656/PciMultimedia.txt
--
Wireless reports connection Bit Rate=0 kb/s
https://bugs.launchpad.net/bugs/461830
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Attachment added: ProcInterrupts.txt
http://launchpadlibrarian.net/34448658/ProcInterrupts.txt
--
Wireless reports connection Bit Rate=0 kb/s
https://bugs.launchpad.net/bugs/461830
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: ProcCpuinfo.txt
http://launchpadlibrarian.net/34448657/ProcCpuinfo.txt
--
Wireless reports connection Bit Rate=0 kb/s
https://bugs.launchpad.net/bugs/461830
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Attachment added: ProcModules.txt
http://launchpadlibrarian.net/34448659/ProcModules.txt
--
Wireless reports connection Bit Rate=0 kb/s
https://bugs.launchpad.net/bugs/461830
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Attachment added: RfKill.txt
http://launchpadlibrarian.net/34448660/RfKill.txt
--
Wireless reports connection Bit Rate=0 kb/s
https://bugs.launchpad.net/bugs/461830
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
** Attachment added: UdevDb.txt
http://launchpadlibrarian.net/34448662/UdevDb.txt
--
Wireless reports connection Bit Rate=0 kb/s
https://bugs.launchpad.net/bugs/461830
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
This is indeed fixed in the RC.
--
livecd fails to boot with --splash option
https://bugs.launchpad.net/bugs/454529
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
This is fixed in the RC
** Changed in: linux (Ubuntu)
Status: New = Fix Released
--
livecd slow boot spends several minutes probing dvd /dev/sr0
https://bugs.launchpad.net/bugs/454522
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: ubuntu 4771 F pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xfe8f8000 irq 16'
Mixer name : 'Realtek ALC888'
Components :
** Attachment added: AlsaDevices.txt
http://launchpadlibrarian.net/34448825/AlsaDevices.txt
--
Wireless reports connection Bit Rate=0 kb/s
https://bugs.launchpad.net/bugs/461830
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Attachment added: AplayDevices.txt
http://launchpadlibrarian.net/34448826/AplayDevices.txt
--
Wireless reports connection Bit Rate=0 kb/s
https://bugs.launchpad.net/bugs/461830
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Attachment added: ArecordDevices.txt
http://launchpadlibrarian.net/34448831/ArecordDevices.txt
--
Wireless reports connection Bit Rate=0 kb/s
https://bugs.launchpad.net/bugs/461830
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: BootDmesg.txt
http://launchpadlibrarian.net/34448843/BootDmesg.txt
--
Wireless reports connection Bit Rate=0 kb/s
https://bugs.launchpad.net/bugs/461830
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Attachment added: Card0.Amixer.values.txt
http://launchpadlibrarian.net/34448849/Card0.Amixer.values.txt
--
Wireless reports connection Bit Rate=0 kb/s
https://bugs.launchpad.net/bugs/461830
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
1 - 100 of 8080 matches
Mail list logo
