Public bug reported:
The version of systemd (249.5-2ubuntu4) currently packaged for the
Ubuntu development version (22.04 Jammy Jellyfish) totally ignores the
RootDirectory= option in systemd service files. With RootDirectory,
systemd should start the service after calling chroot() on the
Posted a 10 USD bounty on this issue:
https://www.bountysource.com/issues/96530138-do-release-upgrade-ignores-apt-proxy-exemption
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1913240
Title:
Public bug reported:
When I try to check for an upgrade, this is what happens:
# do-release-upgrade -c
Checking for a new Ubuntu release
Failed to connect to https://changelogs.ubuntu.com/meta-release-lts. Check your
Internet connection or proxy settings
There is no development version of an
Sorry, I didn't actually test Focal and Groovy.
Xenial will be supported for about a year, so I think it worth to fix it
there as well; however it's relative what worth to fix and what not, as
most users probably left Xenial behind already or applied a workaround
if they were ever affected by
Hi Steve, Julian, Łukasz, everyone,
Sorry that I didn't test the package on time – my life circumstances
have significantly changed since I reported this bug, nowadays I don't
have enough free time to do as much testing as I did back in the day.
I've been using the workaround ever since then,
Thanks for the fix, it solved my issue too! :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1847551
Title:
Mutter 3.34.1 broke Night Light, screen color profiles in Wayland
sessions
To manage
Guys, with today's reboot Night Light works with Wayland. Now I see a
fix for Mutter has been released for #1847551 that I installed on Nov 21
but didn't reboot until today. Indeed it was not an issue with Wayland,
sorry for reporting it as such.
--
You received this bug notification because you
** Tags added: eoan
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1798840
Title:
Night Light is not functioning
To manage notifications about this bug go to:
Now I found out that it depends on whether I login with Xorg or Wayland.
Night Light works with Xorg, but doesn't with Wayland.
I honestly don't remember whether I was running Disco with Xorg or Wayland,
most probably I just went with the default. My guess is that Disco used Xorg by
default and
Night light stopped working for me from Disco to Eoan upgrade.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1798840
Title:
Night Light is not functioning
To manage notifications about this bug go
It works, thanks! \o/
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1770913
Title:
Software rendering is forced
# LANG=C apt-cache policy libnvidia-gl-390
libnvidia-gl-390:
Installed: 390.48-0ubuntu3
Candidate: 390.48-0ubuntu3
Version table:
*** 390.48-0ubuntu3 500
500 http://hu.archive.ubuntu.com/ubuntu bionic/restricted amd64 Packages
100 /var/lib/dpkg/status
# LANG=C dpkg -l
I'm not using oibaf.
I used to use it, but uninstalled it with ppa-purge, but this problem is
present regardless of oibaf is installed.
** Changed in: mesa (Ubuntu)
Status: Invalid => New
** Changed in: xorg-server (Ubuntu)
Status: Invalid => New
--
You received this bug
How can I switch to Wayland? Contrary to the articles those tell
otherwise, I have no option to select it on the login screen.
Anyway, 17.10 worked fine with Wayland, so switching back to Wayland
might probably help.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Also affects: xorg-server (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1770913
Title:
Software rendering is forced after 18.04 upgrade
To
** Attachment added: "Xorg log from ~/.local/share/xorg/"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1770913/+attachment/5141626/+files/Xorg.1.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I don't know why, but apport attached wrong (outdate) Xorg logs to my
report. Probably it's a gdm feature that it puts logs elsewhere instead
of the usual /var/log/Xorg.0.log.
The actual logs made by my X11 server are located here:
/var/lib/gdm3/.local/share/xorg/Xorg.0.log
/home/megabrutal
** Attachment added: "thinkpad-glxinfo-normalboot.txt"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1770913/+attachment/5141597/+files/thinkpad-glxinfo-normalboot.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I've made a live bootable pendrive to test the issue. I've found that
it's not present when I boot a live OS, so something must have gone
wrong during the upgrade. I've attached glxinfo outputs.
thinkpad-glxinfo-livecd.txt: How it looks like when I boot from USB drive. It's
normal.
OpenGL
** Also affects: xorg (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1770913
Title:
Software rendering is forced after 18.04 upgrade
To manage
Public bug reported:
Unclear whether to report it against kexec-tools or systemd.
After upgrading to Ubuntu 18.04, the „systemctl kexec” command gives the
following error message:
Cannot find the ESP partition mount point.
What's interesting is that strace shows that systemctl tries to find
Public bug reported:
After upgrading to Ubuntu 18.04, my desktop uses software rendering, no matter
what I do.
As far as I know, all necessary packages are installed.
Formerly I had oibaf installed, but suspecting that this may cause the problem,
I removed it with ppa-purge. It didn't help.
** Description changed:
My display freezed and I had to forcefully restart my laptop.
Since then, my applications and some UI elements are rendered darker
than usual for no apparent reason. Not all applications are affected.
For example, Firefox, LibreOffice are not affected. GNOME
Public bug reported:
My display freezed and I had to forcefully restart my laptop.
Since then, my applications and some UI elements are rendered darker
than usual for no apparent reason. Not all applications are affected.
For example, Firefox, LibreOffice are not affected. GNOME Terminal,
System
Public bug reported:
My computer running Ubuntu Yakkety with 32 bit 4.8.0-41-generic kernel
often locks up. Error messages like this appear in syslog:
Mar 10 09:49:22 ReThinkCentre kernel: [47896.075600] NMI watchdog: BUG:
soft lockup - CPU#0 stuck for 23s! [kswapd0:38]
In later mainline
OK, men, but then what is the replacement for iscsitarget? What should I
replace my current configuration with?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1613758
Title:
[RM] iscsitarget should
Public bug reported:
I'm not sure whether I should report this, and whether is it an
intentional change or not. I just installed an update for Firefox via
apt. Now I have package version 50.0+build2-0ubuntu0.16.04.2. I noticed,
when I open a tab and load a page, the little spinning circle (or
Public bug reported:
I'm using FreeRDP to connect through an SCB (Shell Control Box) v4.1 to
a Windows 2008 Server. When I connect to the server, FreeRDP immediately
disconnects with the following error message:
ERRINFO_INVALID_INPUT_PDU_MOUSE (0x10D0):
(a) A Slow-Path Mouse Event (section
Public bug reported:
The „setkey” service should run at system startup to add keys defined in
/etc/ipsec-tools.conf.
However, no keys are defined after system boot:
root@ReThinkCentre:~# setkey -D
No SAD entries.
After inquiring systemd, I learn this:
root@ReThinkCentre:~# systemctl status
** Also affects: ubuntu-release-upgrader (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1540157
Title:
Xenial: Mouse pointer disappears after
Public bug reported:
After release upgrade from Wily to Xenial, the mouse pointer is
invisible.
Reproduce:
– Install Ubuntu Wily Werewolf desktop from the official Live CD.
– Upgrade to Xenial Xerus with „do-release-upgrade -d”.
Only had a chance to test it on KVM virtual machine, but it
Thanks for the workaround! It seems adding raid1 is enough.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1509717
Title:
Wily LVM-RAID1 – md: personality for level 1 is not loaded
To manage
Same here:
$ ubuntu-support-status
Traceback (most recent call last):
File "/usr/bin/ubuntu-support-status", line 135, in
pkg.name, support_tag)
File "/usr/bin/ubuntu-support-status", line 51, in get_maintenance_status
raise Exception("No date tag found")
Exception: No date tag
Public bug reported:
When I try to upgrade from 15.10 Wily to 16.04 Xenial (actual
development version) within an LXC container, the upgrade script hangs
at the message „Calculating the changes”.
Steps to reproduce:
1. Make an LXC container with Wily (quickest option is to use lxc-create -t
Public bug reported:
When I try to upgrade from 15.10 Wily to 16.04 Xenial (actual
development version) within an LXC container, the upgrade script hangs
at the message „Calculating the changes”.
Steps to reproduce:
1. Make an LXC container with Wily (quickest option is to use lxc-create -t
** Description changed:
When I try to upgrade from 15.10 Wily to 16.04 Xenial (actual
development version) within an LXC container, the upgrade script hangs
at the message „Calculating the changes”.
Steps to reproduce:
1. Make an LXC container with Wily (quickest option is to use
** Description changed:
When I try to upgrade from 15.10 Wily to 16.04 Xenial (actual
development version) within an LXC container, the upgrade script hangs
at the message „Calculating the changes”.
Steps to reproduce:
1. Make an LXC container with Wily (quickest option is to use
Reproducible: upgraded another Ubuntu installation in VM and got the same
result.
Since the bug prevents booting, I suggest to increase priority to High.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
After upgrading to Wily, raid1 LVs don't activate during the initrd
phase. Since the root LV is also RAID1-mirrored, the system doesn't
boot.
I get the following message each time LVM tries to activate a raid1 LV:
md: personality for level 1 is not loaded!
Everything was
I can't collect logs on non-booting system.
** 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.
https://bugs.launchpad.net/bugs/1509717
Title:
Wily LVM-RAID1 – md:
** Tags added: regression-release wily
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1509717
Title:
Wily LVM-RAID1 – md: personality for level 1 is not loaded
To manage notifications about this
Public bug reported:
I have GnuCash 2.6.6 rev 132c9e3+ on 2015-08-12.
When I have many tabs open (accounts and reports), so that they don't
fit in the GnuCash windows horizontally, I used to scroll over the open
accounts to select one that is not seen on the screen at the moment. The
crash used
I experience this even today with Ubuntu Vivid. Anyone has a workaround (which
not involves building QEMU/KVM from source)?
My current qemu package version is 1:2.2+dfsg-5expubuntu9.2.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
I experience this even today with Ubuntu Vivid. Anyone has a workaround (which
not involves building QEMU/KVM from source)?
My current qemu package version is 1:2.2+dfsg-5expubuntu9.2.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I used the Trusty 14.04.0 Live CD for like half a day and didn't
experience the issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1444268
Title:
[Lenovo ThinkPad T400] Screen corruption
To
I experience the exact same problems with the most recent Vivid Vervet
Live CD build.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1444268
Title:
[Lenovo ThinkPad T400] Screen corruption
To
To be honest, I don't remember. It appeared around the time when Utopic
was released, but I don't know whether it was before or after the
upgrade.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1444268
Public bug reported:
I often perceive massive screen corruption, most prominently in Firefox
/ GMail, but it may happen with any application, including terminals.
Sometimes oversized letters appear. I run video stress tests, but they
run without errors. I suspect the problem presents when many
** Attachment added: Képernyőkép – 2015-04-15 07:39:27.png
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1444268/+attachment/4375900/+files/K%C3%A9perny%C5%91k%C3%A9p%20%E2%80%93%202015-04-15%2007%3A39%3A27.png
--
You received this bug notification because you are a member of Ubuntu
** Attachment added: Képernyőkép – 2014-12-06 15:04:50.png
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1444268/+attachment/4375901/+files/K%C3%A9perny%C5%91k%C3%A9p%20%E2%80%93%202014-12-06%2015%3A04%3A50.png
--
You received this bug notification because you are a member of Ubuntu
** Summary changed:
- Screen corruption under KVM with Spice display
+ Screen corruption under KVM
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1437536
Title:
Screen corruption under KVM
To
** Attachment added: Xorg.0.log
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-driver-vesa/+bug/1437536/+attachment/4359299/+files/Xorg.0.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Also affects: xorg-server (Ubuntu)
Importance: Undecided
Status: New
** Also affects: xserver-xorg-driver-vesa (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The issue was fixed with `linux-image-3.16.0-33-generic`, as it finally
contains commit f285f4a21c3253887caceed493089ece17579d59.
** Changed in: linux (Ubuntu)
Status: Triaged = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
I was experimenting with Ubuntu MATE, and I found severe screen
corruption whenever I run the image under a KVM virtual machine. I
attached a screenshot. I don't think the problem is Ubuntu MATE
specific. I also found it doesn't depend on the display manager. (It can
be
This is another example of the display bug.
** Attachment added: Screenshot_UbuntuMATE_2015-03-27_05:19:14.png
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1428952/+attachment/4357560/+files/Screenshot_UbuntuMATE_2015-03-27_05%3A19%3A14.png
--
You received this bug
This bug seems to be very prominent with beta versions of Vivid,
recently I encountered it on a virtual machine during Ubuntu MATE
installation. I'd suggest to triage it asap and increase its priority.
** Tags added: utopic vivid
--
You received this bug notification because you are a member of
@Astara:
Now, I've noticed when I am booting, it *does* take a bit of time to mount
bring up and mount all of the lvs, but you can the root mount is NOT
in an VG/LV -- It's on a regular device (numbers on left are w/kernel time
printing turned on -- so they are in seconds after boot):
[
*** This bug is a duplicate of bug 1396213 ***
https://bugs.launchpad.net/bugs/1396213
** This bug is no longer a duplicate of bug 995645
udevd: timeout: killing 'watershed sh -c '/sbin/lvm vgscan; /sbin/lvm
vgchange -a y''
** This bug has been marked a duplicate of bug 1396213
LVM VG
*** This bug is a duplicate of bug 1396213 ***
https://bugs.launchpad.net/bugs/1396213
** This bug has been marked a duplicate of bug 1396213
LVM VG is not activated during system boot
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Got an interesting reply from the Red Hat LVM mailing list:
https://www.redhat.com/archives/linux-lvm/2015-March/msg00022.html
Haven't tested the suggestion yet.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Turns out, the suggested --setactivationskip option is not present in
Utopic, as Utopic comes with an LVM version which dates back to 2012
(2.02.98(2) (2012-10-15)), while the feature was implemented in 2013.
Vivid will come with a newer LVM: 2.02.111(2) (2014-09-01).
Activation skip could be a
With the knowledge that the hang is caused by snapshots, some googling has
brought up some duplicates:
https://bugs.launchpad.net/lvm2/+bug/360237
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/995645
It seems the issue was hanging around since 2009 or earlier.
In Trusty (or probably even
Today's update of xserver-xorg-core has fixed the issue.
xorg-server (2:1.17.1-0ubuntu3) vivid; urgency=medium
* Add a patch to fix vesa int10 failure. (LP: #1433198)
-- Maarten Lankhorst maarten.lankho...@ubuntu.com Thu, 19 Mar 2015
10:13:08 +0100
** Changed in: xorg-server (Ubuntu)
** Also affects: initramfs-tools (Ubuntu)
Importance: Undecided
Status: New
** Changed in: initramfs-tools (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Now I have some more info about this. What actually makes the VG
activation so long is that I have a snapshot. Activating the snapshot
takes very long, and bringing up the entire VG takes about 5 minutes.
This wouldn't be such a big problem, as I could just patiently wait for
the activation (with
** Also affects: xserver-xorg-driver-vesa (Ubuntu)
Importance: Undecided
Status: New
** Also affects: xorg (Ubuntu)
Importance: Undecided
Status: New
** Also affects: xorg-server (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification
Is there anything I can do to get the patch actually backported? Can I somehow
backport it myself or something?
Even with the latest Utopic kernel which was published few days ago, I still
don't have a kexec-able kernel.
I can imagine the Vivid release will happen earlier than I'll get a patched
** Description changed:
- I'm experiencing with Vivid Vervet on a virtual machine and tried a new
+ I'm experimenting with Vivid Vervet on a virtual machine and tried a new
LVM feature, lvmcache. I made a cache for the root file system, rebuilt
the initrd and rebooted the VM.
At boot
** Tags added: vivid
** Description changed:
I'm experiencing with Vivid Vervet on a virtual machine and tried a new
LVM feature, lvmcache. I made a cache for the root file system, rebuilt
the initrd and rebooted the VM.
At boot time, the system failed to activate the root LV. After
Public bug reported:
I'm experiencing with Vivid Vervet on a virtual machine and tried a new
LVM feature, lvmcache. I made a cache for the root file system, rebuilt
the initrd and rebooted the VM.
At boot time, the system failed to activate the root LV. After some
investigation, I found out,
This is an lvm2 bug and I wanted to report it to lvm2, not Linux. I
remember that I exactly typed lvm2, I don't know why it was still
reported to linux. Could someone help me to sort it out?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
The following commit fixes the problem in mainline:
commit f285f4a21c3253887caceed493089ece17579d59
Author: Kees Cook keesc...@chromium.org
Date: Thu Jan 15 16:51:46 2015 -0800
x86, boot: Skip relocs when load address unchanged
On 64-bit, relocation is not required unless the load
I've tested the issue with mainline kernel v3.19-rc7-vivid, and it works now!
However, the actual Ubuntu kernel, 3.16.0-30-generic, still has the issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Please try the patch mentioned here:
https://lkml.org/lkml/2014/12/1/790
If it works, it would be nice to tell the authors to get it included in the
mainline kernel. I've already told them, but one man is probably not enough.
(I'm not sure if it's included already, and currently I have no time
Public bug reported:
I've seen there are packages to set up git-daemon easily with sysvinit
and runit (git-daemon-sysvinit and git-daemon-run). I've been wondering
why there isn't a package which sets up an Upstart job, since Upstart is
widely used in Ubuntu.
I've made such package:
Yeah, but I always felt, using sysvinit scripts under Upstart is a
legacy solution which is provided for compatibility, but is deprecated.
I remembered the switch would happen with the next LTS, but probably you
have more accurate information.
--
You received this bug notification because you
I've had a backup of my old Trusty system, and I've built an initrd for
3.16.0-23-generic in that environment. With that initrd, the kernel
booted properly. Note, still it takes several minutes for the VG to
activate, but it eventually comes up if the kernel waits enough with
rootdelay=300.
Now,
Reported upstream to BTRFS developers:
https://bugzilla.kernel.org/show_bug.cgi?id=89121
** Bug watch added: Linux Kernel Bug Tracker #89121
http://bugzilla.kernel.org/show_bug.cgi?id=89121
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
The first bad commit is
8ab3820fd5b2896d66da7bb2a906bc382e63e7bc x86, kaslr: Return location from
decompress_kernel
which introduces KASLR.
The problem only presents itself when CONFIG_RANDOMIZE_BASE=y.
While this bug has been around in the kernel source for quite a time, it
was dormant, as
I've posted the problem report.
Here are the URLs to track from several mail archives:
http://www.spinics.net/lists/kernel/msg1878907.html
http://marc.info/?l=linux-kernelm=141741553905446w=2
https://lkml.org/lkml/2014/12/1/15
--
You received this bug notification because you are a member of
apport information
** Attachment added: BootDmesg.txt
https://bugs.launchpad.net/bugs/1396213/+attachment/4269731/+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/1396213
apport information
** Attachment added: PciMultimedia.txt
https://bugs.launchpad.net/bugs/1396213/+attachment/4269737/+files/PciMultimedia.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: Lspci.txt
https://bugs.launchpad.net/bugs/1396213/+attachment/4269736/+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/1396213
Title:
LVM
apport information
** Attachment added: Card1.Codecs.codec97.0.ac97.0.0.txt
https://bugs.launchpad.net/bugs/1396213/+attachment/4269733/+files/Card1.Codecs.codec97.0.ac97.0.0.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: Card0.Codecs.codec.0.txt
https://bugs.launchpad.net/bugs/1396213/+attachment/4269732/+files/Card0.Codecs.codec.0.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Description changed:
Hi all,
I open this report based on the linked conversation I had on the linux-lvm
mailing list, and the Ask Ubuntu question I posted regarding this case.
https://www.redhat.com/archives/linux-lvm/2014-November/msg00023.html
apport information
** Attachment added: Card1.Codecs.codec97.0.ac97.0.0.regs.txt
https://bugs.launchpad.net/bugs/1396213/+attachment/4269734/+files/Card1.Codecs.codec97.0.ac97.0.0.regs.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
apport information
** Attachment added: UdevLog.txt
https://bugs.launchpad.net/bugs/1396213/+attachment/4269742/+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/1396213
Title:
apport information
** Attachment added: ProcCpuinfo.txt
https://bugs.launchpad.net/bugs/1396213/+attachment/4269738/+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/1396213
apport information
** Attachment added: ProcModules.txt
https://bugs.launchpad.net/bugs/1396213/+attachment/4269740/+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/1396213
apport information
** Attachment added: WifiSyslog.txt
https://bugs.launchpad.net/bugs/1396213/+attachment/4269743/+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/1396213
apport information
** Attachment added: ProcInterrupts.txt
https://bugs.launchpad.net/bugs/1396213/+attachment/4269739/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: UdevDb.txt
https://bugs.launchpad.net/bugs/1396213/+attachment/4269741/+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/1396213
Title:
LVM
apport information
** Attachment added: CurrentDmesg.txt
https://bugs.launchpad.net/bugs/1396213/+attachment/4269735/+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/1396213
AudioDevicesInUse:
- USERPID ACCESS COMMAND
- /dev/snd/controlC0: megabrutal 2497 F pulseaudio
- /dev/snd/seq:timidity 1420 F timidity
+ USERPID ACCESS COMMAND
+ /dev/snd/controlC0: megabrutal 2497 F pulseaudio
+ /dev/snd/seq:timidity 1420 F
Yeah, I was in hurry and didn't have the time to give you the reason why
I did this.
I sent the latest apport from a kernel with which I don't experience the
issue. The difference is that I see these messages:
[5.527952] bio: create slab bio-1 at 1
[ 151.415509] bio: create slab bio-2 at 2
I did the BIOS upgrade and nothing has changed.
7UET94WW (3.24 )
10/17/2012
** 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.
https://bugs.launchpad.net/bugs/1396889
** Description changed:
Hi all,
I open this report based on the linked conversation I had on the linux-lvm
mailing list, and the Ask Ubuntu question I posted regarding this case.
https://www.redhat.com/archives/linux-lvm/2014-November/msg00023.html
** Tags added: kernel-bug-exists-upstream kernel-bug-exists-
upstream-3.18-rc6
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1396213
Title:
LVM VG is not activated during system boot
To manage
1 - 100 of 129 matches
Mail list logo
