Hi, I'm on Ubuntu 23.10 using Brave browser SNAP and I still face the
issue (cannot open links in evince -using Brave browser snap).
Here are the versions:
```console
❯ apt list --installed | rg 'evince|apparmor'
apparmor/mantic,now 4.0.0~alpha2-0ubuntu5 amd64 [installed,automatic]
evince-common
Public bug reported:
I'm under Ubuntu 16.04
kernel : Linux micronet-HP 4.4.0-24-generic #43-Ubuntu SMP Wed Jun 8 19:27:37
UTC 2016 x86_64 x86_64 x86_64 GNU/Linux.
from the very beginning I could not be connected thru wifi.
The guy in charge of this bug, bug already declared and on which we did
Upstream feature request: https://github.com/canonical/lightdm/issues/95
** Bug watch added: github.com/canonical/lightdm/issues #95
https://github.com/canonical/lightdm/issues/95
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscrib
Public bug reported:
The stanza
Match User
PasswordAuthentication no
in /etc/ssh/sshd_config works as expected.
The same stanza in /etc/ssh/sshd_config.d/username.conf does not work.
The Include in /etc/ssh/sshd_config is not commented out, and
/usr/sbin/sshd -D -ddd
shows the userna
sshd_config.d file that doesn't work
** Attachment added: "cweatherby.conf"
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2012298/+attachment/5656820/+files/cweatherby.conf
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subsc
working sshd_config with Match block inline.
** Attachment added: "work"
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2012298/+attachment/5656821/+files/work
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to opens
Failing sshd_config
** Attachment added: "fail"
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2012298/+attachment/5656819/+files/fail
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bug
I don't think it's a duplicate of 2002994.
I tried moving the Include line in the main sshd_config to the end of
the file and the behavior was unaffected.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
htt
Public bug reported:
Installing pulseaudio/focal-updates,now 1:13.99.1-1ubuntu3.13 amd64
recommends packages
pavumeter paman paprefs ubuntu-sounds
Attempting to install paman gives error:
Package paman is not available, but is referred to by another package.
This may mean that the package is
@lvoytek
PPA works as expected, thank you.
For completeness, I'll note the affected packages appear to be:
sudo apt-get install -y openssh-client openssh-server openssh-sftp-
server
(We manage our systems such that we don't apply non-security updates
during system lifecycle so our users have a
I'm not familiar with the Ubuntu update timeline -- is there an ETA for
when we will see this in the mainline repository?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/20122
Tested openssh-server/focal-proposed,now 1:8.2p1-4ubuntu0.7 amd64
[installed]
creating /etc/ssh/sshd_config.d/.conf:
Match User
PasswordAuthentication No
worked as expected: prohibited password login while allow publickey
authentication
** Tags removed: verification-needed-focal
** Tags adde
Do we have an estimate for when this will go mainline?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/2012298
Title:
PasswordAuthenticaion in sshd_config.d
Status in port
Public bug reported:
I had the same issue when trying to update my current system. Any
application which needed python3 failed with python3.
ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: python3 3.10.6-1~22.04
ProcVersionSignature: Ubuntu 5.19.0-41.42~22.04.1-generic 5.19.17
Uname: Li
The proposed solution fixes the bug I filed when joining against older
Windows Active Directory servers.
(https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1906673) i.e. The
domain join works without the --use-ldaps.
We do not currently have the correct certificate set up to use --use-
ldaps, so
Public bug reported:
First time upgrade, fresh Bionic Beaver instance
ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: uuid-runtime 2.31.1-0.4ubuntu3.2
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Archite
Public bug reported:
Attempting to access the property raised the exception 'SystemError: error
return without exception set'
The error occurs when version._records.hashes.file_size == 0.
The package occurred on (cups=2.2.7-1ubuntu2.5) on an Ubnuntu 18.04.2 LTS
system ; attempting to download th
Public bug reported:
I cannot update becuase of some problem with tird party programs, howeve
I deleted all of them an it is still occurring. It also appears a new
user called LibvirtQuemu.
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libdrm-intel1 2.4.83-1~16.04.1
ProcVersionSignatu
Proposed update fixed the issue, thanks.
product: Mobile 4 Series Chipset Integrated Graphics Controller
vendor: Intel Corporation
$ apt policy libgl1-mesa-dri
libgl1-mesa-dri:
Installed: 17.2.4-0ubuntu1~16.04.4
Candidate: 17.2.4-0ubuntu1~16.04.4
Version table:
*** 17.2.4-0ubuntu1~16.04.4
** Changed in: alsa-driver (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1720693
Title:
[10MVCTO1WW, Realtek ALC
Ran into this, too.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upstart in Ubuntu.
https://bugs.launchpad.net/bugs/1476753
Title:
When sshd exits because of a bad configuration, upstart claims the job
is in "start/run
Also just got greeted by this message. QkiZ's fix seems to work for me
as well (for the last few reboots), but given the sporadic nature of the
bug I can't be sure.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ub
Pointlessly aggravating to break something that long term linux users
have relied on for years. At a minimum, a comment in the default
/etc/hosts would be useful.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager
Public bug reported:
If you do a Wily desktop install, /var/lib/dbus/machine-id is a symlink
to /etc/machine-id.
If you do a Wily server install, /var/lib/dbus/machine-id is a file
containing the same value as /etc/machine-id.
Minor issue, but still a weird inconsistency between Ubuntu desktop a
Side note: when /var/lib/dbus/machine-id is a symlink to /etc/machine-
id, a related issue issue is that systemd fails to create the later when
missing:
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1508697
--
You received this bug notification because you are a member of Ubuntu
Touch seed
Public bug reported:
If /etc/machine-id is missing at boot, systemd does not create it.
I came across lp:1387090 in which Martin Pitt mentions that it should be
created if missing, but is unsure why this doesn't work.
I'm likewise unsure why it doesn't work, but this bit from dmesg makes
me thin
** Description changed:
If /etc/machine-id is missing at boot, systemd does not create it.
I came across lp:1387090 in which Martin Pitt mentions that it should be
created if missing, but is unsure why this doesn't work.
I'm likewise unsure why it doesn't work, but this bit from dmes
@seb128: yes.
The two are related in that when /var/lib/dbus/machine-id is a symlink,
the act of starting the system dbus instance can't (or wont, I guess)
generate a machine-id (as the path in question is there, just the
symlink target is missing).
And because of lp:1508697, systemd doesn't inse
Oops, sorry for the confusion, haven't been sleeping enough lately :P
I meant to refer to lp:1508766 which I filed about systemd not creating
/etc/machine-id if it's missing:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1508766
Now that /var/lib/dbus/machine-id is a symlink to /etc/mac
Which I guess raises another question... when booting with sysvinit or
Upstart, what should dbus do when /var/lib/dbus/machine-id is a symlink
to /etc/machine-id and the latter doesn't exist?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Simon,
I've never really dug into initramfs-tools enough to know for sure, but
my guess has always been that the rootfs got remounted based on what's
in /etc/fstab, which as far as I know is handled by systemd. But perhaps
the initramfs remounts the rootfs read-write, and then it is remounted a
3r
Simon,
Also, I just tested with an empty /etc/machine-id file... in this case,
systemd does correctly create a write a random machine-id.
Which kinda makes me wonder if systemd is erroneously concluding the
rootfs is mounted read-write when the /etc/machine-id file is missing
altogether.
--
Yo
For what it's worth, network-manager 0.9.10.0-4ubuntu15.2 seems to fix
the problem for me.
`route -n` with *ubuntu15.1 with both WiFi and Ethernet connections:
Kernel IP routing table
Destination Gateway Genmask Flags Metric RefUse Iface
0.0.0.0 10.17.75.1 0.0
Timo,
I didn't realize that this module is being loaded during the initrd
phase before the rootfs is mounted. Mystery solved, I think :D
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
http
Andy, I spotted the problem:
Line 120 in /usr/share/initramfs-tools/hook-functions:
cp -a "$firmware" "$target_dir"
`cp -a` copies the symlink itself rather than the target it points to,
so we end up with a broken symlink in initramfs and no actual firmware
file.
The fix that comes to mind
Andy: oops, didn't refresh the page and see your latest comments before
I posted the above, please ignore.
I just tested the initramfs-tools package in your PPA, confirmed it
works:
1) No more error in dmesg about skl_dmc not being loaded
2) `lsinitramfs -l` shows both the "skl_dmc_ver1.bin" sym
Likewise, I've been doing extensive testing with mesa 11 from the
x-staging PPA on Haswell, Broadwell, and Skylake hardware, haven't hit
any issues.
Timo, when do you expect mesa 11 to at least hit wily-proposed? I'll
admit it makes me a bit nervous that mesa 11 isn't in wily proper yet :D
--
Yo
FYI, this bug wasn't initially present on the final 15.04 release, but
has since raised it's ugly head again on 15.04.
Not sure what has changed, but from my previous experience, my bet is
still on `unity-greeter`, even though I'm not sure how exactly it's
causing it.
--
You received this bug no
As with 14.10, this problem isn't happening with Ubuntu MATE 15.04.
Haven't tried the other flavors yet, but I'm guessing that again this is
only happening with Ubuntu/Unity.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to net
I've started testing the mesa 11 rc2 packages here:
https://launchpad.net/~canonical-x/+archive/ubuntu/x-staging
One issue I've hit is that with mesa 11 rc2 installed, Unity will no
longer run under qemu (note I'm testing with an amd64 VM, Wily host and
Wily guest).
Attaching the full unit7.log f
Timo,
Awesome, thanks for the quick fix! I'll test it under qemu as soon as
the builds are finished.
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1484279
Title:
[
Timo, 11.0.0~rc2-1ubuntu1~ppa2 seems shiny with Unity under qemu.
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1484279
Title:
[FFe] Mesa 11.0.0
Status in mesa pack
Karl,
FYI, network-manager should ignore any interfaces defined in
/etc/network/interfaces.
Which is not to say this bug isn't frustrating, just that you should be
able to manually configure things as you wish without removing network-
manager :D
--
You received this bug notification because yo
Quick question: mesa11 depends on libllvm3.7, but libllvm3.7 is still in
universe.
Is there a plan to promote libllvm3.7 to main?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs
Oops, never mind... I see that libllvm3.7 being in main is mentioned in
the summary, sorry for the noise!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1484279
Title:
[FFe]
Fix seems solid.
`route -n` with up-to-date Vivid:
Kernel IP routing table
Destination Gateway Genmask Flags Metric RefUse Iface
0.0.0.0 10.17.76.1 0.0.0.0 UG1024 00 eth0
10.17.75.0 0.0.0.0 255.255.255.0 U 0 0
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1436330
Title:
Network Manager doesn't set met
Sorry I attached a wrong file, this one is the correct one!
** Attachment added: "e2fsck_output_ok"
https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1637779/+attachment/4920266/+files/error_32_1.JPG
--
You received this bug notification because you are a member of Ubuntu
Touch seede
We have an error quiet similar to this one reported.
We are using Ubuntu 14.04 .. but I really think it's not a matter of version
though.
We are getting randomly the following errors:
--
[97030.025645] EXT4-fs error (device sdb5): ext4_iget:4156: inode #26351669:
comm apache2: checksum i
First of all thank you very much for your quickly response.
I am glad to say you we fixed that issue thanks to your post :)
The problem was we formatted the disk (sb5) using some tool from newer Ubuntu
version which put metadata_csum feature on it. And because using on Ubuntu
14.04 it had some
Except that previously this wasn't racy behavior in practice.
I have automation tooling that has executed tens of thousands of reboot
and shutdown commands over SSH in this way with perfect consistency over
the last two years. The moment the switchover to systemd happened in
Vivid, this tooling br
Public bug reported:
Steps to reproduce
===
1) Enable both a WiFi connection and plug into Ethernet
2) Test your network connectivity or run `route`
Expected results
=
NetworkManager should prefer the wired connection over the WiFi
connection, and `route` should return s
Public bug reported:
On Trusty and Utopic, when you run `apt-get remove openssh-server` over
an SSH connection, your existing SSH connection remains open, so it's
possible to run additional commands afterward.
However, on Vivid now that the switch to systemd has been made, `apt-
get remove opens
Being able to run a script like this over SSH:
apt-get -y remove openssh-server
shutdown -h now
Can be extremely useful in automation tooling, but the switch to systemd
breaks this:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1429938
--
You received this bug notification because you
Also, just to clarify, this is definitely a change (or in my mind
regression) introduced by systemd. Yesterday, the System76 image master
tool worked fine and dandy with an up-to-date Vivid VM, as it has
throughout the rest of the previous Vivid dev cycle.
Today things broke.
--
You received thi
Hmm, now I'm thinking this has nothing to do with openssh-server.
I think the problem is actually that when I run this over SSH:
# shutdown -h now
My ssh client exists with status 255... whereas running the same thing
prior to the flip-over to systemd would exit with status 0.
--
You received
Okay, here's a simple way to reproduce:
$ ssh root@whatever shutdown -h now
$ echo $?
On Vivid, the exist status from the ssh client will be 255. On Trusty
and Utopic it will be 0.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribe
Also, on Vivid there will be this error: "Connection to localhost closed
by remote host."
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1429938
Title:
stopping ssh.servic
Same problem when running `reboot`, which I'd say is even more important
for automation. Port 2204 is forwarding to a qemu VM running Utopic,
port 2207 is running Vivid:
jderose@jgd-kudp1:~$ ssh root@localhost -p 2204 reboot
jderose@jgd-kudp1:~$ echo $?
0
jderose@jgd-kudp1:~$ ssh root@localhost -p
Martin,
Okay, much thanks!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1429938
Title:
reboot does not return under systemd
Status in systemd package in Ubuntu:
Inva
So interestingly, this isn't happening when I just type these commands
into an SSH session. But if you create a script like this in say
/tmp/test.sh:
#!/bin/bash
apt-get -y purge openssh-server ssh-import-id
apt-get -y autoremove
shutdown -h now
And then execute this through an ssh call like this
** Description changed:
- On Trusty and Utopic, when you run `apt-get remove openssh-server` over
- an SSH connection, your existing SSH connection remains open, so it's
- possible to run additional commands afterward.
+ If you send a shutdown or reboot command over SSH to a Trusty or Utopic
+ hos
I reworked the description as my original assessment was quite off.
But after more thought, I think this behavior change is something that
really needs mentioning in the Vivid releases notes.
After all, the perceived "correct" behavior of a system strongly tends
toward what the actual behavior ha
Info from fstab, crypttab, and journalctl:
$cat /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. Se
Public bug reported:
I'm still sorting out the details and eliminating variables, but as far
as I can tell:
Steps to reproduce
===
1) Install Ubuntu using GPT partitioning for the OS drive[*]
2) Choose "require my password to login", and check "encrypt my home
directory"
Expected b
** Summary changed:
- Prompted for cryptoswap passphrase when using GPT partitioning + encrypted
home directory (ecrptfs)
+ Prompted for cryptoswap passphrase when using GPT partitioning + encrypted
home directory (ecryptfs)
--
You received this bug notification because you are a member of Ubu
As far as I can tell, lp:1447282 is a different bug, but it would be helpful to
have input from the other ecryptfs users who are following this bug:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1447282
--
You received this bug notification because you are a member of Ubuntu
Touch seede
Oops, when I copy+pasted my fstab earlier, I accidentally left out the
final line, but the cryptswap1 line is actually there.
This is from a different install, so the UUIDs are different. Also, I
forgot that Martin Pitt asked me to include the output from blkid:
$ cat /etc/fstab
# /etc/fstab: st
Martin,
Another interesting tidbit is that this pre-lightdm passphrase prompt
isn't actually doing anything... you can enter a blank passphrase or the
wrong passphrase, and it will still happily proceed to lightdm.
Here's the output you asked for:
$ systemctl --all | grep -i swap
dev-mapper-cr
One more interesting tidbit: it seems that when booting with systemd,
it's never enabling encrypted swap, it's just enabling normal swap using
the underlying physical swap partition.
After booting with systemd:
$ sudo swapon --summary
FilenameTypeSize
Yesterday I didn't have access to a UEFI system or a >2TiB drive to test
with... but I just did a normal install on a UEFI system, and I'm
experiencing this same bug.
As before, booting with init=/sbin/upstart fixes it.
I just wanted to rule out this being a problem introduced by the
System76 ima
Also attached a tarball with everything from generator/
** Attachment added: "generator.tgz"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1447282/+attachment/4382430/+files/generator.tgz
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
I attached a tarball will everything from generator.late/, just in case
any other files are useful.
** Attachment added: "generator.late.tgz"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1447282/+attachment/4382428/+files/generator.late.tgz
--
You received this bug notification bec
To eliminate more variables, I just tried xubuntu 14.10 (with nvidia-343
from ppa:system76-dev/stable)... and I can connect to password-protected
WiFi just fine.
As Xubuntu and Ubuntu are using most of the same lower-level stack, this
kinda suggests the problem is fairly high-level, potentially ev
More variables eliminated: this bug does *not* occur on:
- Ubuntu GNOME 14.10
- Ubuntu MATE 14.10
- Kubuntu 14.10
- Xubuntu 14.10 (as mentioned above)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
Another possible hint: some in this set of packages currently in vivid
proposed breaks the WiFi password dialog:
Calculating upgrade... Done
The following NEW packages will be installed:
libisl13
The following packages will be upgraded:
apport apport-gtk btrfs-tools fontconfig fontconfig-confi
Er, I mean an ABI mismatched in policykit-1, not network-manager
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1388130
Title:
Cannot connect to WiFi with Nvid
Okay, on vivid, unity-greeter 15.04.2-0ubuntu1 re-introduces this bug.
I have a vivid image that was up-to-date as of Fri 5 Dec. In this
snapshot, with applying any updates, I can connect to protected WiFi
just fine.
However, today something landing from proposed re-introduced this bug,
and I not
Mathieu,
Okay, just finished testing with xenial-proposed, no issues found.
Things are working as expected for my use-case (with no adjustments on
my end), so at least for the corners that my particular use-cases
covers, this proposed package seems regression free.
I tested PXE booting into a "d
Okay, an interesting hint is that this problem seems to be fixed if
u-s-d is started under the Upstart user session instead of the systemd
user session.
If anyone wants to try this, just comment out these three lines in
/etc/X11/Xsession.d/00upstart:
if [ "${1#*.target}" != "$1" ]; then
`sudo forkstat -D 4` when u-s-d is started under systemd and I press the
brightness up hotkey.
** Attachment added: "with-systemd.txt"
https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1626651/+attachment/4756099/+files/with-systemd.txt
--
You received this bug notificatio
I'm back to testing u-s-d started under systemd, and I found some
serious wackiness observing `sudo journalctl -f` when I use the
brigtness up/down hotkeys.
The attached "wacky-journalctl.txt" file has the output of `sudo
journalctl -f` during which I used the brightness hotkeys *twice*, and
you'l
As asked by chiluk on IRC, here's my PXE boot configuration (well,
representative one anyway, the exact kernel version will obviously
change):
DEFAULT ubuntu
LABEL ubuntu
LINUX vmlinuz-4.4.0-36-generic
APPEND initrd=initrd.img-4.4.0-36-generic root=/dev/nfs
nfsroot=10.17.76.1:/var/lib/tribble/eph
@chiluk - the package in your PPA fixes it from my use case, thanks!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1631474
Title:
No networking with initramfs-too
Public bug reported:
The 20161012.1 yakkety desktop ISO fails to reboot after the install
completes (see attached screenshot).
Tested on QEMU in BIOS and UEFI mode, which is where the screenshot is
from. Same thing is seemingly happening on hardware (reboot hangs),
although I don't see this parti
@chiluk - I tested the latest package in your PPA, but something seems
slightly wonky for my use case.
Networking seems to come up correctly, but it takes longer than it
should and I see warnings like this repeated several times:
ip: ether "dev" is duplicate, or "permanent" is garbage
--
You re
Attaching a tarbal of everything i have in /var/log, not sure it's
useful (not my "ephemeral" environment is read-only with /var/log on a
tmpfs, so it's mostly empty).
Also here's my exact /proc/cmdline from within the booted ephemeral
environment:
BOOT_IMAGE=vmlinuz-4.4.0-42-generic initrd=initr
@martin - I tested the proposed package, and it's workable, but there
are behavior changes still compared to prior to when this regression was
introduced (in particular, the boot is a lot slower when there are
mulitple NICs but only one will be configured, even when I use
"ip=:eth0:dhcp").
@sc
Oh, and to be clear, I have no problem with this change in Yakkety. It's
just starting to feel a bit too invasive in my opinion for Xenial.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bug
@jbicha hmm, I didn't experience this with the final Ubuntu desktop
16.10 ISOs... what was your experience with the final 16.10 Ubuntu GNOME
ISOs?
But I also don't think this is happening with perfect determinism
either.
--
You received this bug notification because you are a member of Ubuntu
To
Okay, tested 0.122ubuntu8.5 from xenial-proposed, and it fixes the issue
for my use-case.
But I'm not changing verification-needed to verification-done yet as I
don't know if it fixes the use case of the original reporter.
@scotte - can you please confirm whether this fixes things for you?
--
Y
This problem seems to exist currently on both 15.10 and Xenial
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ureadahead in Ubuntu.
https://bugs.launchpad.net/bugs/1085766
Title:
/var/log/upstart/ureadahead.log contains ga
Mathieu,
I tested your PPA package with Xenial: with no config changes on my end,
it's working as expected from my use case.
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.lau
Public bug reported:
This is an extremely odd bug that requires a very specific scenario to
reproduce:
1) You need to be using an ecryptfs-style cryptoswap partition (as would
be setup when you choose "Encrypt my home directory" during the
installation)
2) The underlying physical swap partition
Also attaching a screenshot, just so folks don't think I'm making this
up :P
** Attachment added: "screenshot.png"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1597876/+attachment/4692953/+files/screenshot.png
--
You received this bug notification because you are a member of Ubuntu
Possibly as a result of this change, unity/compiz is failing to start
when trying to install from the latest 16.04.1 daily ISO under qemu
(xenial-desktop-amd64.iso 20160713, sha1sum
c9b1ad9b1044c4e68684395daa3f85e016491c3a).
I attached a screenshot as I couldn't file a bug from within the qemu VM
Here's another screenshot that shows the SegvAnalysis.
In my testing thus far, this failure (assuming it's related to this
unity/nux change) only seems to happen when trying to install under
qemu. I tried -vga qxl, -vga std, and -vga virtio... none of them yield
a working installation. Compiz alwa
@Marco: thanks for the FYI!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to nux in Ubuntu.
https://bugs.launchpad.net/bugs/1598770
Title:
Unity in low-graphics mode has animations and unneeded redraws
Status in compiz pack
On a whim, I just checked in on this with the 20160601 Xenial daily
amd64 ISO (sha1sum e07c8b4df1fc71a487fafb309bd318041a65774f), and
everything works great:
http://cdimages.ubuntu.com/xenial/daily-live/pending/
So seems things are on track for this not being a problem in the 16.04.1
release.
--
I get the impression this is known and expected, but this problem still
exists in the latest 14.04.4 daily ISOs (which have proposed enabled).
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.lau
1 - 100 of 135 matches
Mail list logo
