Indeed, looks like this issue is related to initramfs-tools, be that
through an incompatibility introduced in either.
I tested with the package in Debian Sid dropbear-initramfs (2024.84-1)
and got the same error. Meanwhile, on a Debian Sid install, it works.
Based on the above, I added
The above was observed on a QEMU KVM VM using server installer defaults
as well as with specific curtin storage definitions.
I also reproduced the same on a QEMU KVM VM using desktop installer and
clicking next on all questions (except user).
--
You received this bug notification because you
Public bug reported:
dropbear-initramfs seems to fail on not figuring out what the root
device is. This applies both to autoinstall and manual install and is
observed on today's beta (ubuntu-24.04-beta-live-server-amd64.iso on
2024-04-12)
ubuntu@ubuntu-server:~$ sudo apt install
I can confirm the workaround by boxeus works on Ubuntu 20.04 LTS. To
improve on that, the lines can be added to the /etc/dropbear-
initramfs/config config file instead to avoid upgrade issues. It is
loaded towards the end of /usr/share/initramfs-tools/scripts/init-
bottom/dropbear anyway.
Which version of Mint (or which upstream Ubuntu it is based on?) I
wonder if there is a way to get those rows into the configs rather than
editing packaged files?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
In our case we decided to spend the same effort on orchestrating for
images:ubuntu/focal/cloud (which comes without snapd) rather than
working around issues with snap on the thicker default image.
But the workaround above can be used, and I remember it was documented
elsewhere on launchpad or
It seems the workaround above does not work on Ubuntu 20.04.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1813394
Title:
DROPBEAR_IFDOWN=* takes interface down but leaves netplan config
To manage
Public bug reported:
Since initramfs networking is rather limited, a simple flag to reset
networking afterwards (or not to generate netplan files) would be
valuable. The intended effect is to allow fully featured networking
tools to set up the network afterwards.
Use cases include the following,
Public bug reported:
The first bullet point of Netplans' Key Goals is "Usable in initramfs
(few dependencies and fast)".
This is currently not supported in Ubuntu.
A basic approach would be to use the same /etc/netplan/*.yaml whenever
initramfs depends on networking.
Supporting netplan in
Digging even further back, it turns out that IFDOWN is in itself a
workaround for an equal issue dating back to ~2012. As such, the core of
the issue lies with how initramfs network setup overrides netplan.
Adding that package.
Given the very limited setup /etc/initramfs-tools/initramfs.conf
Investigating further reveals that the package is not adapted for
netplan in the first place. The maintainer is not on launchpad and the
package was imported from Debian Sid.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This also applies when set up with static IP's in /etc/initramfs-
tools/initramfs.conf. That case is most prominently noticed as lacking
nameservers after boot.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I agree. I confirm this is still happening on Ubuntu 20.04.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1813394
Title:
DROPBEAR_IFDOWN=* takes interface down but leaves netplan config
To manage
The situation where this arose is in testing our Ubuntu 20.04
orchestration. Previously we used a script to ensure boot coherence. We
use two mirrored system drives, mirroring everything to the extent that
the system must be completely bootable after pulling a drive/having one
drive fail
Container management seems to be the source of the error, sudo just
suppresses it. So a potential fix is in LXD or related packages.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1868456
Title:
Workaround:
echo "Set disable_coredump false" | sudo tee -a /etc/sudo.conf
** Also affects: lxd (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I am seeing this as well. A workaround is to remove all snaps but core,
then unmount the snap core before purging with apt.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1878674
Title:
apt purge
** Changed in: grub2 (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1876974
Title:
Support multiple ESPs
To manage notifications about this bug go to:
OK, so for anyone hitting this error until there may be a fix: For cases
where snapd is not needed (and perhaps purged later), and orchestration
relies on cloud-init to finish, the workaround in the container is:
systemctl stop snapd.seeded.service
or on the host:
lxc exec $CONTAINERNAME --
Chad, were you able to find the config that caused the effect? There is a
similar issue open here:
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1878225
I am trying to find out if it is a regression or something in my config.
--
You received this bug notification because you are a
Have you tested this on amd64? I am seeing the same outputs on amd64 and
trying to find out if it is a regression or something in my config. A
similar report has suggestions it may be due to faulty network setup for
the container:
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1806070
--
This is fairly problematic when core functionality that is orchestrated
in the cloud moves from deb to snap. In our example, lxc (LXD command
line tool) was assumed to be in the path when building the
orchestration. Using the full path makes it less portable. It also makes
managing multiple
I ran 'grub-install', and expected both efi to be updated. It updates
only the primary ESP.
Both 'dpkg-reconfigure grub-efi-amd64' and running 'grub-multi-install'
directly update both ESPs. So on the package updates part it looks like
we are good to go.
The part that I am missing, is making it
Public bug reported:
Subiquity has the brilliant feature of supporting installing to multiple
ESP's. See https://bugs.launchpad.net/subiquity/+bug/1817066 for
details.
grub-install does not mirror this feature this out of the box, but
updates the ESP on /boot/efi only by default on such an
Removing the package after the failed install is not straight forward, here is
a workarond:
sudo systemctl stop tenshi.service; sudo killall tenshi; sudo apt purge
tenshi
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Tested on three different Ubuntu 18.04 LTS systems. It seems something
is broken in the packaging of tenshi. Installation stalls for several
minutes and then fails.
$ sudo apt install tenshi
Reading package lists... Done
Building dependency tree
Reading state information...
Here is a one-line to work around the issue:
sed -i 's#export KEY_CONFIG.*#export
KEY_CONFIG="$EASY_RSA/openssl-1.0.0.cnf"#' /home/ubuntu/openvpn-ca/vars
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
The following simple netplan config results in a 2-minut unneccessary
delay on boot. Everything works like it should in the end. The bridge
has no interfaces due to a regression in Ubuntu migrating to netplan
(see
Public bug reported:
While systemd supports bringing up independent openvpn services, there
is currently no way of declaring these in netplan like it was in
/etc/network/interfaces.
Critically, it is no longer feasible to have such a device in a bridge
that is declared in netplan.
Related bugs:
I can verify the fix. However,
rm -Rf /var/lib/cloud /var/log/cloud*
will cause the SSH key to be reset, which is easily a bigger issue than getting
a cloud-init warning.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Can a maintainer please nominate this for xenial separately. The status
is misleading since the fix is not in released in xenial, which is what
this bug was filed against. The janitor does not act on tags.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
On Xenial with glusterfs 3.7.6, running a volume heal full command works
well but the glustershd log shows this repeated many times:
[2017-01-05 15:26:20.138562] E [client-rpc-
fops.c:5058:client3_3_getxattr] (-->/usr/lib/x86_64-linux-
Yes this makes a lot of sense. The situation is the same for me, but I
started automatically removing a list of packages from my lxd containers
- including mdadm. That's why the problem disappeared.
Mdadm could still make sense in a container (privileged with raw access
to devices etc.) but
With the latest updates and a reboot and a few days of uptime, the message has
not yet reappeared. This may have been fixed?
linux-image 4.4.0-36-generic
libc 2.23-0ubuntu3
mdadm 3.3-2ubuntu7.1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Description changed:
- fstrun daily cronjob output in an unprivileged LXD container:
+ fstrun weekly cronjob output in an unprivileged LXD container:
/etc/cron.weekly/fstrim:
fstrim: cannot open /dev/.lxd-mounts: Permission denied
fstrim: /dev/fuse: not a directory
fstrim: /dev/lxd:
Public bug reported:
On Ubuntu 16.04.1 LTS Xenial, mdadm segfaults every day on two machines.
Everything works as normal though, and the RAID arrays are not degraded.
[3712474.763430] mdadm[17665]: segfault at 0 ip 7fd0369bed16 sp
7fff8c5c9478 error 4 in
Public bug reported:
Maybe wishlist: it would be nice to have GlusterFS client mounts in an
unprivileged container.
Tested with LXD 2.0.0 and glusterfs 3.7.6 (i.e. Xenial without any PPA)
on an LXD container with the same versions and fuse enabled in the
profile.
Currently, trying a mount in an
Public bug reported:
On a fresh Ubuntu Xenial 16.04 LTS Server install, the boot stalls for
exactly 90 seconds when using a fairly complex partitioning setup. After
this, everything works as expected.
The partitioning is as follows:
/sda GPT
/sda1 ESP (/boot/efi)
/sda2 raid1 md0 ext4 (/boot)
I can also confirm the proposed package works nicely.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1573639
Title:
ownCloud Client system tray icon integration broken
To manage notifications about
Still the case on 14.04 LTS. In Xenial, icedtea-8 works.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/517
Title:
javaws doesn't open Supermicro remote console (IP-KVM)
To manage notifications
** Description changed:
- upgrade to MySQL 5.7.10 and above, ununtu 16.04
+ upgrade to MySQL 5.7.10 and above, Ubuntu 16.04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1528583
Title:
[FFe]
** Description changed:
- upgrade to MySQL 5.7.10 and above, ununtu 16.04
+ upgrade to MySQL 5.7.10 and above, Ubuntu 16.04
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1528583
On my 14.04 LTS system the workaround was to add 'dns_v4_first on' to
/etc/maas/maas-proxy.conf
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to squid in Ubuntu.
https://bugs.launchpad.net/bugs/1547640
Title:
proxy tries ipv6 and
On my 14.04 LTS system the workaround was to add 'dns_v4_first on' to
/etc/maas/maas-proxy.conf
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1547640
Title:
proxy tries ipv6 and gets 503 when no
I confirm the fix is effective. For large environments where hooks have failed,
here's a one-liner after running the fix to re-run all the failed hooks, which
should return the agents to normal (idle) state:
for i in `juju status --format tabular|grep failed|awk '{print $1;}'`;do echo
Fixing
I confirm the fix is effective. For large environments where hooks have failed,
here's a one-liner after running the fix to re-run all the failed hooks, which
should return the agents to normal (idle) state:
for i in `juju status --format tabular|grep failed|awk '{print $1;}'`;do echo
Fixing
Public bug reported:
Running Juju 1.20.12-trusty-amd64 on MaaS.
May be related to:
https://code.launchpad.net/~thumper/juju-core/kvm-constraints/+merge/197815
Setting constraints does not affect the creation of KVM containers.
johan@maas:~$ juju deploy --to kvm:2 --constraints mem=2G
Public bug reported:
Running Juju 1.20.12-trusty-amd64 on MaaS.
May be related to:
https://code.launchpad.net/~thumper/juju-core/kvm-constraints/+merge/197815
Setting constraints does not affect the creation of KVM containers.
johan@maas:~$ juju deploy --to kvm:2 --constraints mem=2G
Public bug reported:
Ubuntu 14.04 LTS mplayer 2:1.1+dfsg1-0ubuntu3
This bug is easy to reproduce. I noticed it while uncompressing scenes
from my camera for editing.
My projects have 1-100 clips and I stumble upon this about 1 in 15
uncompressed files, indicating that the concerned AVI files
** Description changed:
Ubuntu 14.04 LTS mplayer 2:1.1+dfsg1-0ubuntu3
This bug is easy to reproduce. I noticed it while uncompressing scenes
from my camera for editing.
My projects have 1-100 clips and I stumble upon this about 1 in 15
uncompressed files, indicating that the
Further testing shows that it actually only occurs just after the first
chunk end. With the description's specifications, that is between
11.550-12.500 seconds of video or 1078431852-1165705924 bytes of output
file size, tested with 0.05 second precision.
** Description changed:
Ubuntu 14.04
Running Ubuntu 12.04.2 LTS 64 bit on Windows XP 32 bit. When installing
with the patch in #29 I am getting a bit further but compiling stops at
CC [M] /var/lib/dkms/virtualbox-guest/4.1.12/build/vboxsf/vfsmod.o
/var/lib/dkms/virtualbox-guest/4.1.12/build/vboxsf/vfsmod.c: In function
Public bug reported:
The post install trigger in /etc/initramfs/post-update.d/flash-kernel
said no Android boot partition could be found.
It seems caused by the removed abootimg through 'apt-get autoremove.'
This was after a clean install followed by a 'apt-get dist-upgrade', so
it should not
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1035647
Title:
package initramfs-tools 0.103ubuntu0.1 failed to install/upgrade:
subprocess installed post-installation script returned error exit
The bug is closed, but for future reference:
It sound like the external keyboard turned and left Num Lock on, which
on a laptop keyboard results in the right side of the keyboard to give
numbers etc. Not all laptop keyboards have these marked, which may cause
difficulties in noticing this. I
I tried linux-image-2.6.34-999-generic_2.6.34-999.201005061008_i386.deb
and the problem no longer appears. I even reverted to stock
2.6.32-22-generic and reproduced the problem easily. A sure way of
reproducing the problem is to access the host with unison through its
external IP and NIC (even
Public bug reported:
I'm getting this repeatedly after a a day or so, after upgrading to
Lucid. I have a Sundance Technology IPG Triple-Speed Ethernet (stops
working when this happens, mentioned in the oops) and a 2001:3c05 D-Link
Corp. [hex] DUB-E100 Fast Ethernet [asix] USB. Ifdown + ifup
** Attachment added: BootDmesg.txt
http://launchpadlibrarian.net/47744401/BootDmesg.txt
** Attachment added: CurrentDmesg.txt
http://launchpadlibrarian.net/47744402/CurrentDmesg.txt
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/47744403/Dependencies.txt
**
** Changed in: linux (Ubuntu)
Assignee: (unassigned) = Ubuntu Kernel Network Team
(ubuntu-kernel-network)
--
Lucid on Asus EEE PC 901 and 1000H fails to connect to any wireless network
https://bugs.launchpad.net/bugs/545443
You received this bug notification because you are a member of
*** This bug is a duplicate of bug 496093 ***
https://bugs.launchpad.net/bugs/496093
** Changed in: linux (Ubuntu)
Assignee: Ubuntu Kernel Network Team (ubuntu-kernel-network) =
(unassigned)
** This bug has been marked a duplicate of bug 496093
[lucid] rt2860 frequently fails to
Correction: any non-protected network works. After that, protected
networks also seem to work mostly. Connecting to a protected network as
the first network works as often/seldom as before.
--
Lucid on Asus EEE PC 901 and 1000H fails to connect to any wireless network
With the latest updates today, I was able to connect to every network I
managed to find (1 unprotected with WDA, 1 unprotected rather typical AP
from TP-LINK, 1 unprotected in hotel mode with web authentication, 1
WPA/WPA2 protected private network). Rinsed and repeated each network a
few times.
The latest version fixed this.
** Changed in: fglrx-installer (Ubuntu)
Status: New = Fix Released
--
Regression: Segfault with Radeon HD 3300
https://bugs.launchpad.net/bugs/559150
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This still happens in Beta 2. Can we narrow it down to this specific PCI
ID?
RaLink RT2860 [1814:0781] with Subsystem: RaLink Device [1814:2790]
** Summary changed:
- Lucid Beta 1 on Asus EEE PC 901 Fails to connect to any wireless network
+ Lucid on Asus EEE PC 901 Fails to connect to any
Public bug reported:
Binary package hint: fglrx
On a system upgraded from 9.10 to Lucid Beta 1, fglrx does not work and
X.org crashes with a segfault.
ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: fglrx 2:8.721-0ubuntu8
ProcVersionSignature: Ubuntu 2.6.32-19.28-generic 2.6.32.10+drm33.1
** Attachment added: BootDmesg.txt
http://launchpadlibrarian.net/43537552/BootDmesg.txt
** Attachment added: CurrentDmesg.txt
http://launchpadlibrarian.net/43537553/CurrentDmesg.txt
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/43537554/Dependencies.txt
**
Got this when I tried sound test in mythbuntu.
--
gst_pipeline_test crashed with GError in main()
https://bugs.launchpad.net/bugs/355279
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
We have confirmed this bug. I wonder how many affected EEE PC:s are
being tested with lucid, because this could be pretty serious if it
affects all 901 and 1000H (and other models?).
** Changed in: network-manager (Ubuntu)
Status: New = Confirmed
--
Lucid Beta 1 on Asus EEE PC 901 Fails
I tried manually with iwconfig and dhclient to rule out NetworkManager,
and confirmed it still happens. It seems setting the ESSID does not work
correctly, only succeeding around one out of 5-10 times.
Here's a quick test command that I used:
sudo killall dhclient; sudo ifconfig wlan0 down; sleep
I get this too.
** Changed in: rhythmbox (Ubuntu)
Status: New = Confirmed
--
rhythmbox crashed with SIGSEGV in g_object_notify()
https://bugs.launchpad.net/bugs/548679
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Public bug reported:
Binary package hint: network-manager
This may also belong to linux.
My Asus EEE PC 901 running lucid beta1 live cd from USB cannot connect
to any WLAN network, protected or not. The same network works with the
installed system (9.10), and with another computer running
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/41770896/Dependencies.txt
** Attachment added: Gconf.txt
http://launchpadlibrarian.net/41770897/Gconf.txt
** Attachment added: IpAddr.txt
http://launchpadlibrarian.net/41770898/IpAddr.txt
** Attachment added:
I have to add that I did get it to connect once, but trying to connect
again immediately after failed. I tried to reproduce this seemingly
random success (simply boot from clean live USB with wired plugged in,
and connect as soon as the desktop is available) but failed.
--
Lucid Beta 1 on Asus
I tested Beta 1 and it now works fine out of the box. Good work, whoever
did it! Closing the bug.
** Changed in: xserver-xorg-video-openchrome (Ubuntu)
Status: Confirmed = Fix Released
--
[CLE266]Lucid Alpha graphical mode does not work on VIA EPIA MII (Chrome)
My setup is Ubuntu 9.10 with sun-java6 and at the time I was able to
produce this with and without any custom settings.
Today, I was unable to reproduce the bug. I am no longer actively
working on the document in question, so I will not bump into it
spontaneously. However, I'd be happy to help if
I have either an LCD over analog (=CRT in BIOS/xorg.conf) or PAL TV-
Out (CRT+TV set in BIOS) but not both connected at the same time.
The ActiveDevice option had no effect on the situation. However, this
time, modeSwitch did. I tried a few different settings with Alpha 3:
No xorg.conf (noxorg):
** Attachment added: crt-xorg1
http://launchpadlibrarian.net/39956025/crt-xorg1
--
[CLE266]Lucid Alpha graphical mode does not work on VIA EPIA MII (Chrome)
https://bugs.launchpad.net/bugs/523911
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
** Attachment added: crt-xorg1-log
http://launchpadlibrarian.net/39956034/crt-xorg1-log
--
[CLE266]Lucid Alpha graphical mode does not work on VIA EPIA MII (Chrome)
https://bugs.launchpad.net/bugs/523911
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Attachment added: crt-xorg2
http://launchpadlibrarian.net/39956048/crt-xorg2
--
[CLE266]Lucid Alpha graphical mode does not work on VIA EPIA MII (Chrome)
https://bugs.launchpad.net/bugs/523911
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
** Attachment added: crt-xorg2-log
http://launchpadlibrarian.net/39956057/crt-xorg2-log
--
[CLE266]Lucid Alpha graphical mode does not work on VIA EPIA MII (Chrome)
https://bugs.launchpad.net/bugs/523911
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Attachment added: crt-xorg3
http://launchpadlibrarian.net/39956061/crt-xorg3
--
[CLE266]Lucid Alpha graphical mode does not work on VIA EPIA MII (Chrome)
https://bugs.launchpad.net/bugs/523911
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Bryce Harrington seems to have confirmed this bug, what hardware are you
using?
Maybe this new modeSwitch could be made the default for appropriate
hardware?
--
[CLE266]Lucid Alpha graphical mode does not work on VIA EPIA MII (Chrome)
https://bugs.launchpad.net/bugs/523911
You received this bug
** Attachment added: crt-xorg3-log
http://launchpadlibrarian.net/39956087/crt-xorg3-log
--
[CLE266]Lucid Alpha graphical mode does not work on VIA EPIA MII (Chrome)
https://bugs.launchpad.net/bugs/523911
You received this bug notification because you are a member of Ubuntu
Bugs, which is
You already suggested new mode switch, see results above.
NoAccel did not help.
--
[CLE266]Lucid Alpha graphical mode does not work on VIA EPIA MII (Chrome)
https://bugs.launchpad.net/bugs/523911
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
The hardware has a working TV-Out, yes.
Mostly, I have tried using no xorg.conf (default) but all of the
variations have likewise been in vain. I'll get back to you with some
examples tomorrow from a daily build USB Live CD, as I have to recreate
them.
--
[CLE266]Lucid Alpha graphical mode does
This still happens on Alpha 3. I did a fresh re-install of 9.10 and it
works well with the openchrome driver, so this seems to be a regression.
I will continue testing 10.04 live CD builds from USB, get in touch with
me if there is anything in specific you need tested.
--
[CLE266]Lucid Alpha
The original setup was without xorg.conf.
I created a simple xorg.conf and added the line you asked. Xorg says:
(WW) CHROME(0): Option modeSwitch is not used
There is no option to turn TV encoder off specifically as far as I know.
It does not seem to matter what BIOS settings have been selected.
With the older via driver gone, and vesa not working with this chip for
some reason, the only workaround available is fbdev.
--
[CLE266]Lucid Alpha graphical mode does not work on VIA EPIA MII (Chrome)
https://bugs.launchpad.net/bugs/523911
You received this bug notification because you are a
Public bug reported:
When booting the live CD or USB, the screen goes blank when it starts
xorg. Interestingly, the monitor stays on for a while and then seems to
get power save commands normally. There is no picture, that's all.
Going to a terminal works. Switching back does not help.
The
apport information
** Tags added: apport-collected
** Description changed:
When booting the live CD or USB, the screen goes blank when it starts
xorg. Interestingly, the monitor stays on for a while and then seems to
get power save commands normally. There is no picture, that's all.
apport information
** Attachment added: BootDmesg.txt
http://launchpadlibrarian.net/39368734/BootDmesg.txt
--
Mythbuntu Lucid Live CD Alpha 2 graphical mode does not work on VIA EPIA MII
(Chrome)
https://bugs.launchpad.net/bugs/523911
You received this bug notification because you are a
apport information
** Attachment added: Card0.Amixer.values.txt
http://launchpadlibrarian.net/39368735/Card0.Amixer.values.txt
--
Mythbuntu Lucid Live CD Alpha 2 graphical mode does not work on VIA EPIA MII
(Chrome)
https://bugs.launchpad.net/bugs/523911
You received this bug notification
apport information
** Attachment added: Card0.Codecs.codec97.0.ac97.0.0.txt
http://launchpadlibrarian.net/39368736/Card0.Codecs.codec97.0.ac97.0.0.txt
--
Mythbuntu Lucid Live CD Alpha 2 graphical mode does not work on VIA EPIA MII
(Chrome)
https://bugs.launchpad.net/bugs/523911
You received
apport information
** Attachment added: Card0.Codecs.codec97.0.ac97.0.0.regs.txt
http://launchpadlibrarian.net/39368737/Card0.Codecs.codec97.0.ac97.0.0.regs.txt
--
Mythbuntu Lucid Live CD Alpha 2 graphical mode does not work on VIA EPIA MII
(Chrome)
https://bugs.launchpad.net/bugs/523911
apport information
** Attachment added: CurrentDmesg.txt
http://launchpadlibrarian.net/39368738/CurrentDmesg.txt
--
Mythbuntu Lucid Live CD Alpha 2 graphical mode does not work on VIA EPIA MII
(Chrome)
https://bugs.launchpad.net/bugs/523911
You received this bug notification because you are
apport information
** Attachment added: Lspci.txt
http://launchpadlibrarian.net/39368739/Lspci.txt
--
Mythbuntu Lucid Live CD Alpha 2 graphical mode does not work on VIA EPIA MII
(Chrome)
https://bugs.launchpad.net/bugs/523911
You received this bug notification because you are a member of
apport information
** Attachment added: AplayDevices.txt
http://launchpadlibrarian.net/39368729/AplayDevices.txt
--
Mythbuntu Lucid Live CD Alpha 2 graphical mode does not work on VIA EPIA MII
(Chrome)
https://bugs.launchpad.net/bugs/523911
You received this bug notification because you are
apport information
** Attachment added: ArecordDevices.txt
http://launchpadlibrarian.net/39368731/ArecordDevices.txt
--
Mythbuntu Lucid Live CD Alpha 2 graphical mode does not work on VIA EPIA MII
(Chrome)
https://bugs.launchpad.net/bugs/523911
You received this bug notification because you
apport information
** Attachment added: PciMultimedia.txt
http://launchpadlibrarian.net/39368741/PciMultimedia.txt
--
Mythbuntu Lucid Live CD Alpha 2 graphical mode does not work on VIA EPIA MII
(Chrome)
https://bugs.launchpad.net/bugs/523911
You received this bug notification because you
apport information
** Attachment added: ProcCpuinfo.txt
http://launchpadlibrarian.net/39368743/ProcCpuinfo.txt
--
Mythbuntu Lucid Live CD Alpha 2 graphical mode does not work on VIA EPIA MII
(Chrome)
https://bugs.launchpad.net/bugs/523911
You received this bug notification because you are a
1 - 100 of 156 matches
Mail list logo
